Public report of KonkerLabs/konker-platform, 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, 07:12 UTC · Survey ID cd_7206ab64235c48048c45aea219b8c1a8
KonkerLabs/konker-platform
Measured 17 November 2026, 07:11 UTC, at code version 007a3ee
Bus factor is not measured: No living knowledge left to concentrate.
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: 40,665 lines of product code in 19 projects, tests not counted · Estimated rebuild effort: about 0.4 person-years · Weakest lens: Accessibility, 26.3
Findings by how serious they are
261 critical795 serious681 minor
11 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, 07:11 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 ▸
73of 73 dimensions measured by tools.
1715of 1737 findings point to an exact file and line, so you can open each one in the code. The other 22 concern the repository as a whole, such as missing documentation.
73dimensions across 6 lenses, read from 40,665 lines of product code in 19 projects.
KonkerLabs/konker-platform is rated At risk because critical security findings are open. Its score is held back in part because it has images with no text description. It scores 32.0 out of 100, which the At risk rating leaves unchanged.
Accessibility, at 26.3, is the weakest lens and counts most in the score. The best first step is fixing focus, motion and contrast, worth about 3.7 points. Adding text alternatives comes next, worth about 3.5 points. Raising Accessibility to 70 would lift the score to about 37.7.
Fifty-three known security holes in the packages the code depends on can be used by attackers. Forty settings leave the servers or containers unsafe, and forty images have no description for people who can't see them. Updating the vulnerable packages, correcting the unsafe settings and describing the images would close these risks. Pinning each tool to an exact version would fix the 20 pipeline tools referenced by a changeable name, and the nine passwords or keys in the code's history need replacing, with the old ones switched off. Giving the shared object a factory instead of the short-lived one would take care of the 33 shared objects holding on to short-lived ones.
The product code is 40,665 lines, about €61,000 to rebuild.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
If Accessibility rose from 26.3 to 70, the lowest score rated Strong, the score would rise from 32.0 to about 37.7.
Code composition: what the lines of code are
Product code 57%Tests 43%
Rebuild cost: about €61,000 · Estimate
Cost to rebuild
€20,000 to €100,000, for 337 to 1,068 hours of work, about 0.4 person-years for one engineer
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.7 at a score of 32. 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: 40,665 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
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
Raises the score by about 3.5 points · Medium effort · Text alternatives
3
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
Raises the score by about 3.1 points · Medium effort · Keyboard semantics
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 €61,000 to build again, about 0.4 person-years of work. Its weakest lens is Accessibility, at 26.3 (Weak). Accessibility is about whether the interface is built so that everyone can use it, including people who can't see the screen or can't use a mouse. Because the weakest lens counts most in the score, work on Accessibility also moves the score most.
Based on: the rebuild estimate · the Accessibility grade · how much each lens counts
What to do: Start with the Accessibility actions in Top priorities.
If you do one thing first · First action
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1. Of all the actions in this report, it raises the score most for the work it takes: about 3.7 points for medium effort. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
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.3 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 4% to 10% on every change. The history of the code shows how much it changes: about 664 lines over the last 90 days, which is about 2,693 lines a year. At that pace, the extra work comes to an estimated 0.3 to 1.7 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.
126 modules, with 177 dependencies between them. One loop runs through 6 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 86 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.
8 pairs of types, where a type in com.konkerlabs.platform.registry.business.model uses a type in com.konkerlabs.platform.registry.business.model.enumerations.
com.konkerlabs.platform.registry.business.model uses com.konkerlabs.platform.registry.business.model.enumerations, so a change to com.konkerlabs.platform.registry.business.model.enumerations can break com.konkerlabs.platform.registry.business.model, while a change to com.konkerlabs.platform.registry.business.model can't break com.konkerlabs.platform.registry.business.model.enumerations.
Position
Below the diagonal: com.konkerlabs.platform.registry.business.model uses a module listed above it, which is the healthy direction.
com.konkerlabs.platform.registry.business.model uses com.konkerlabs.platform.utilities.parsers.json, so a change to com.konkerlabs.platform.utilities.parsers.json can break com.konkerlabs.platform.registry.business.model, while a change to com.konkerlabs.platform.registry.business.model can't break com.konkerlabs.platform.utilities.parsers.json.
Position
Below the diagonal: com.konkerlabs.platform.registry.business.model uses a module listed above it, which is the healthy direction.
com.konkerlabs.platform.registry.audit.repositories uses com.konkerlabs.platform.registry.audit.model, so a change to com.konkerlabs.platform.registry.audit.model can break com.konkerlabs.platform.registry.audit.repositories, while a change to com.konkerlabs.platform.registry.audit.repositories can't break com.konkerlabs.platform.registry.audit.model.
Position
Below the diagonal: com.konkerlabs.platform.registry.audit.repositories uses a module listed above it, which is the healthy direction.
com.konkerlabs.platform.registry.audit.repositories uses com.konkerlabs.platform.registry.business.model, so a change to com.konkerlabs.platform.registry.business.model can break com.konkerlabs.platform.registry.audit.repositories, while a change to com.konkerlabs.platform.registry.audit.repositories can't break com.konkerlabs.platform.registry.business.model.
Position
Below the diagonal: com.konkerlabs.platform.registry.audit.repositories uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in com.konkerlabs.platform.registry.business.repositories uses a type in com.konkerlabs.platform.registry.business.model.enumerations.
com.konkerlabs.platform.registry.business.repositories uses com.konkerlabs.platform.registry.business.model.enumerations, so a change to com.konkerlabs.platform.registry.business.model.enumerations can break com.konkerlabs.platform.registry.business.repositories, while a change to com.konkerlabs.platform.registry.business.repositories can't break com.konkerlabs.platform.registry.business.model.enumerations.
Position
Below the diagonal: com.konkerlabs.platform.registry.business.repositories uses a module listed above it, which is the healthy direction.
28 pairs of types, where a type in com.konkerlabs.platform.registry.business.repositories uses a type in com.konkerlabs.platform.registry.business.model. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
com.konkerlabs.platform.registry.business.repositories uses com.konkerlabs.platform.registry.business.model, so a change to com.konkerlabs.platform.registry.business.model can break com.konkerlabs.platform.registry.business.repositories, while a change to com.konkerlabs.platform.registry.business.repositories can't break com.konkerlabs.platform.registry.business.model.
Position
Below the diagonal: com.konkerlabs.platform.registry.business.repositories uses a module listed above it, which is the healthy direction.
8 pairs of types, where a type in com.konkerlabs.platform.registry.business.repositories.events.api uses a type in com.konkerlabs.platform.registry.business.model.
com.konkerlabs.platform.registry.business.repositories.events.api uses com.konkerlabs.platform.registry.business.model, so a change to com.konkerlabs.platform.registry.business.model can break com.konkerlabs.platform.registry.business.repositories.events.api, while a change to com.konkerlabs.platform.registry.business.repositories.events.api can't break com.konkerlabs.platform.registry.business.model.
Position
Below the diagonal: com.konkerlabs.platform.registry.business.repositories.events.api uses a module listed above it, which is the healthy direction.
5 pairs of types, where a type in com.konkerlabs.platform.registry.data.core.services.routes.api uses a type in com.konkerlabs.platform.registry.business.model.
com.konkerlabs.platform.registry.data.core.services.routes.api uses com.konkerlabs.platform.registry.business.model, so a change to com.konkerlabs.platform.registry.business.model can break com.konkerlabs.platform.registry.data.core.services.routes.api, while a change to com.konkerlabs.platform.registry.data.core.services.routes.api can't break com.konkerlabs.platform.registry.business.model.
Position
Below the diagonal: com.konkerlabs.platform.registry.data.core.services.routes.api uses a module listed above it, which is the healthy direction.
com.konkerlabs.platform.registry.idm.web.form uses com.konkerlabs.platform.registry.business.model, so a change to com.konkerlabs.platform.registry.business.model can break com.konkerlabs.platform.registry.idm.web.form, while a change to com.konkerlabs.platform.registry.idm.web.form can't break com.konkerlabs.platform.registry.business.model.
Position
Below the diagonal: com.konkerlabs.platform.registry.idm.web.form uses a module listed above it, which is the healthy direction.
6 pairs of types, where a type in com.konkerlabs.platform.registry.web.forms uses a type in com.konkerlabs.platform.registry.business.model.enumerations.
com.konkerlabs.platform.registry.web.forms uses com.konkerlabs.platform.registry.business.model.enumerations, so a change to com.konkerlabs.platform.registry.business.model.enumerations can break com.konkerlabs.platform.registry.web.forms, while a change to com.konkerlabs.platform.registry.web.forms can't break com.konkerlabs.platform.registry.business.model.enumerations.
Position
Below the diagonal: com.konkerlabs.platform.registry.web.forms uses a module listed above it, which is the healthy direction.
com.konkerlabs.platform.registry.web.forms uses com.konkerlabs.platform.registry.business.model, so a change to com.konkerlabs.platform.registry.business.model can break com.konkerlabs.platform.registry.web.forms, while a change to com.konkerlabs.platform.registry.web.forms can't break com.konkerlabs.platform.registry.business.model.
Position
Below the diagonal: com.konkerlabs.platform.registry.web.forms uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in com.konkerlabs.platform.registry.business.repositories.events uses a type in com.konkerlabs.platform.registry.business.repositories.config.
com.konkerlabs.platform.registry.business.repositories.events uses com.konkerlabs.platform.registry.business.repositories.config, so a change to com.konkerlabs.platform.registry.business.repositories.config can break com.konkerlabs.platform.registry.business.repositories.events, while a change to com.konkerlabs.platform.registry.business.repositories.events can't break com.konkerlabs.platform.registry.business.repositories.config.
Position
Below the diagonal: com.konkerlabs.platform.registry.business.repositories.events uses a module listed above it, which is the healthy direction.
6 pairs of types, where a type in com.konkerlabs.platform.registry.business.repositories.events uses a type in com.konkerlabs.platform.registry.business.model.
com.konkerlabs.platform.registry.business.repositories.events uses com.konkerlabs.platform.registry.business.model, so a change to com.konkerlabs.platform.registry.business.model can break com.konkerlabs.platform.registry.business.repositories.events, while a change to com.konkerlabs.platform.registry.business.repositories.events can't break com.konkerlabs.platform.registry.business.model.
Position
Below the diagonal: com.konkerlabs.platform.registry.business.repositories.events uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in com.konkerlabs.platform.registry.business.repositories.events uses a type in com.konkerlabs.platform.registry.business.repositories.
com.konkerlabs.platform.registry.business.repositories.events uses com.konkerlabs.platform.registry.business.repositories, so a change to com.konkerlabs.platform.registry.business.repositories can break com.konkerlabs.platform.registry.business.repositories.events, while a change to com.konkerlabs.platform.registry.business.repositories.events can't break com.konkerlabs.platform.registry.business.repositories.
Position
Below the diagonal: com.konkerlabs.platform.registry.business.repositories.events uses a module listed above it, which is the healthy direction.
4 pairs of types, where a type in com.konkerlabs.platform.registry.business.repositories.events uses a type in com.konkerlabs.platform.registry.business.repositories.events.api.
com.konkerlabs.platform.registry.business.repositories.events uses com.konkerlabs.platform.registry.business.repositories.events.api, so a change to com.konkerlabs.platform.registry.business.repositories.events.api can break com.konkerlabs.platform.registry.business.repositories.events, while a change to com.konkerlabs.platform.registry.business.repositories.events can't break com.konkerlabs.platform.registry.business.repositories.events.api.
Position
Below the diagonal: com.konkerlabs.platform.registry.business.repositories.events uses a module listed above it, which is the healthy direction.
com.konkerlabs.platform.registry.business.services.api uses com.konkerlabs.platform.registry.audit.model, so a change to com.konkerlabs.platform.registry.audit.model can break com.konkerlabs.platform.registry.business.services.api, while a change to com.konkerlabs.platform.registry.business.services.api can't break com.konkerlabs.platform.registry.audit.model.
Position
Below the diagonal: com.konkerlabs.platform.registry.business.services.api uses a module listed above it, which is the healthy direction.
com.konkerlabs.platform.registry.business.services.api uses com.konkerlabs.platform.registry.billing.model, so a change to com.konkerlabs.platform.registry.billing.model can break com.konkerlabs.platform.registry.business.services.api, while a change to com.konkerlabs.platform.registry.business.services.api can't break com.konkerlabs.platform.registry.billing.model.
Position
Below the diagonal: com.konkerlabs.platform.registry.business.services.api uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in com.konkerlabs.platform.registry.business.services.api uses a type in com.konkerlabs.platform.registry.business.model.enumerations.
com.konkerlabs.platform.registry.business.services.api uses com.konkerlabs.platform.registry.business.model.enumerations, so a change to com.konkerlabs.platform.registry.business.model.enumerations can break com.konkerlabs.platform.registry.business.services.api, while a change to com.konkerlabs.platform.registry.business.services.api can't break com.konkerlabs.platform.registry.business.model.enumerations.
Position
Below the diagonal: com.konkerlabs.platform.registry.business.services.api uses a module listed above it, which is the healthy direction.
105 pairs of types, where a type in com.konkerlabs.platform.registry.business.services.api uses a type in com.konkerlabs.platform.registry.business.model. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
com.konkerlabs.platform.registry.business.services.api uses com.konkerlabs.platform.registry.business.model, so a change to com.konkerlabs.platform.registry.business.model can break com.konkerlabs.platform.registry.business.services.api, while a change to com.konkerlabs.platform.registry.business.services.api can't break com.konkerlabs.platform.registry.business.model.
Position
Below the diagonal: com.konkerlabs.platform.registry.business.services.api uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in com.konkerlabs.platform.registry.business.services.api uses a type in com.konkerlabs.platform.registry.business.repositories.
com.konkerlabs.platform.registry.business.services.api uses com.konkerlabs.platform.registry.business.repositories, so a change to com.konkerlabs.platform.registry.business.repositories can break com.konkerlabs.platform.registry.business.services.api, while a change to com.konkerlabs.platform.registry.business.services.api can't break com.konkerlabs.platform.registry.business.repositories.
Position
Below the diagonal: com.konkerlabs.platform.registry.business.services.api uses a module listed above it, which is the healthy direction.
14→29 com.konkerlabs.platform.registry.business.services.api uses com.konkerlabs.platform.registry.configpart of a loop✕
Connections
2 pairs of types, where a type in com.konkerlabs.platform.registry.business.services.api uses a type in com.konkerlabs.platform.registry.config.
com.konkerlabs.platform.registry.business.services.api uses com.konkerlabs.platform.registry.config, so a change to com.konkerlabs.platform.registry.config can break com.konkerlabs.platform.registry.business.services.api, while a change to com.konkerlabs.platform.registry.business.services.api can't break com.konkerlabs.platform.registry.config.
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.
com.konkerlabs.platform.registry.security uses com.konkerlabs.platform.registry.business.model, so a change to com.konkerlabs.platform.registry.business.model can break com.konkerlabs.platform.registry.security, while a change to com.konkerlabs.platform.registry.security can't break com.konkerlabs.platform.registry.business.model.
Position
Below the diagonal: com.konkerlabs.platform.registry.security uses a module listed above it, which is the healthy direction.
com.konkerlabs.platform.registry.security uses com.konkerlabs.platform.registry.business.repositories, so a change to com.konkerlabs.platform.registry.business.repositories can break com.konkerlabs.platform.registry.security, while a change to com.konkerlabs.platform.registry.security can't break com.konkerlabs.platform.registry.business.repositories.
Position
Below the diagonal: com.konkerlabs.platform.registry.security uses a module listed above it, which is the healthy direction.
15→29 com.konkerlabs.platform.registry.security uses com.konkerlabs.platform.registry.configpart of a loop✕
Connections
1 pair of types, where a type in com.konkerlabs.platform.registry.security uses a type in com.konkerlabs.platform.registry.config.
com.konkerlabs.platform.registry.security uses com.konkerlabs.platform.registry.config, so a change to com.konkerlabs.platform.registry.config can break com.konkerlabs.platform.registry.security, while a change to com.konkerlabs.platform.registry.security can't break com.konkerlabs.platform.registry.config.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
1 pair of types, where a type in com.konkerlabs.platform.registry.api.model uses a type in com.konkerlabs.platform.registry.business.model.enumerations.
com.konkerlabs.platform.registry.api.model uses com.konkerlabs.platform.registry.business.model.enumerations, so a change to com.konkerlabs.platform.registry.business.model.enumerations can break com.konkerlabs.platform.registry.api.model, while a change to com.konkerlabs.platform.registry.api.model can't break com.konkerlabs.platform.registry.business.model.enumerations.
Position
Below the diagonal: com.konkerlabs.platform.registry.api.model uses a module listed above it, which is the healthy direction.
com.konkerlabs.platform.registry.api.model uses com.konkerlabs.platform.registry.business.model, so a change to com.konkerlabs.platform.registry.business.model can break com.konkerlabs.platform.registry.api.model, while a change to com.konkerlabs.platform.registry.api.model can't break com.konkerlabs.platform.registry.business.model.
Position
Below the diagonal: com.konkerlabs.platform.registry.api.model uses a module listed above it, which is the healthy direction.
com.konkerlabs.platform.registry.api.model uses com.konkerlabs.platform.registry.business.services.api, so a change to com.konkerlabs.platform.registry.business.services.api can break com.konkerlabs.platform.registry.api.model, while a change to com.konkerlabs.platform.registry.api.model can't break com.konkerlabs.platform.registry.business.services.api.
Position
Below the diagonal: com.konkerlabs.platform.registry.api.model uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in com.konkerlabs.platform.registry.data.core.integration.converters.helper uses a type in com.konkerlabs.platform.registry.business.model.
com.konkerlabs.platform.registry.data.core.integration.converters.helper uses com.konkerlabs.platform.registry.business.model, so a change to com.konkerlabs.platform.registry.business.model can break com.konkerlabs.platform.registry.data.core.integration.converters.helper, while a change to com.konkerlabs.platform.registry.data.core.integration.converters.helper can't break com.konkerlabs.platform.registry.business.model.
Position
Below the diagonal: com.konkerlabs.platform.registry.data.core.integration.converters.helper uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in com.konkerlabs.platform.registry.data.core.integration.converters.helper uses a type in com.konkerlabs.platform.registry.business.services.api.
com.konkerlabs.platform.registry.data.core.integration.converters.helper uses com.konkerlabs.platform.registry.business.services.api, so a change to com.konkerlabs.platform.registry.business.services.api can break com.konkerlabs.platform.registry.data.core.integration.converters.helper, while a change to com.konkerlabs.platform.registry.data.core.integration.converters.helper can't break com.konkerlabs.platform.registry.business.services.api.
Position
Below the diagonal: com.konkerlabs.platform.registry.data.core.integration.converters.helper uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in com.konkerlabs.platform.registry.data.core.services.api uses a type in com.konkerlabs.platform.registry.business.model.
com.konkerlabs.platform.registry.data.core.services.api uses com.konkerlabs.platform.registry.business.model, so a change to com.konkerlabs.platform.registry.business.model can break com.konkerlabs.platform.registry.data.core.services.api, while a change to com.konkerlabs.platform.registry.data.core.services.api can't break com.konkerlabs.platform.registry.business.model.
Position
Below the diagonal: com.konkerlabs.platform.registry.data.core.services.api uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in com.konkerlabs.platform.registry.data.core.services.api uses a type in com.konkerlabs.platform.registry.business.services.api.
com.konkerlabs.platform.registry.data.core.services.api uses com.konkerlabs.platform.registry.business.services.api, so a change to com.konkerlabs.platform.registry.business.services.api can break com.konkerlabs.platform.registry.data.core.services.api, while a change to com.konkerlabs.platform.registry.data.core.services.api can't break com.konkerlabs.platform.registry.business.services.api.
Position
Below the diagonal: com.konkerlabs.platform.registry.data.core.services.api uses a module listed above it, which is the healthy direction.
com.konkerlabs.platform.registry.idm.services uses com.konkerlabs.platform.registry.business.model, so a change to com.konkerlabs.platform.registry.business.model can break com.konkerlabs.platform.registry.idm.services, while a change to com.konkerlabs.platform.registry.idm.services can't break com.konkerlabs.platform.registry.business.model.
Position
Below the diagonal: com.konkerlabs.platform.registry.idm.services uses a module listed above it, which is the healthy direction.
com.konkerlabs.platform.registry.idm.services uses com.konkerlabs.platform.registry.business.repositories, so a change to com.konkerlabs.platform.registry.business.repositories can break com.konkerlabs.platform.registry.idm.services, while a change to com.konkerlabs.platform.registry.idm.services can't break com.konkerlabs.platform.registry.business.repositories.
Position
Below the diagonal: com.konkerlabs.platform.registry.idm.services uses a module listed above it, which is the healthy direction.
com.konkerlabs.platform.registry.idm.services uses com.konkerlabs.platform.registry.business.services.api, so a change to com.konkerlabs.platform.registry.business.services.api can break com.konkerlabs.platform.registry.idm.services, while a change to com.konkerlabs.platform.registry.idm.services can't break com.konkerlabs.platform.registry.business.services.api.
Position
Below the diagonal: com.konkerlabs.platform.registry.idm.services uses a module listed above it, which is the healthy direction.
com.konkerlabs.platform.registry.web.converters.utils uses com.konkerlabs.platform.registry.business.model, so a change to com.konkerlabs.platform.registry.business.model can break com.konkerlabs.platform.registry.web.converters.utils, while a change to com.konkerlabs.platform.registry.web.converters.utils can't break com.konkerlabs.platform.registry.business.model.
Position
Below the diagonal: com.konkerlabs.platform.registry.web.converters.utils uses a module listed above it, which is the healthy direction.
com.konkerlabs.platform.registry.web.converters.utils uses com.konkerlabs.platform.registry.security, so a change to com.konkerlabs.platform.registry.security can break com.konkerlabs.platform.registry.web.converters.utils, while a change to com.konkerlabs.platform.registry.web.converters.utils can't break com.konkerlabs.platform.registry.security.
Position
Below the diagonal: com.konkerlabs.platform.registry.web.converters.utils uses a module listed above it, which is the healthy direction.
20→29 com.konkerlabs.platform.registry.web.converters.utils uses com.konkerlabs.platform.registry.configpart of a loop✕
Connections
1 pair of types, where a type in com.konkerlabs.platform.registry.web.converters.utils uses a type in com.konkerlabs.platform.registry.config.
com.konkerlabs.platform.registry.web.converters.utils uses com.konkerlabs.platform.registry.config, so a change to com.konkerlabs.platform.registry.config can break com.konkerlabs.platform.registry.web.converters.utils, while a change to com.konkerlabs.platform.registry.web.converters.utils can't break com.konkerlabs.platform.registry.config.
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.
com.konkerlabs.platform.registry.web.services.api uses com.konkerlabs.platform.registry.business.model, so a change to com.konkerlabs.platform.registry.business.model can break com.konkerlabs.platform.registry.web.services.api, while a change to com.konkerlabs.platform.registry.web.services.api can't break com.konkerlabs.platform.registry.business.model.
Position
Below the diagonal: com.konkerlabs.platform.registry.web.services.api uses a module listed above it, which is the healthy direction.
3 pairs of types, where a type in com.konkerlabs.platform.registry.web.services.api uses a type in com.konkerlabs.platform.registry.business.services.api.
com.konkerlabs.platform.registry.web.services.api uses com.konkerlabs.platform.registry.business.services.api, so a change to com.konkerlabs.platform.registry.business.services.api can break com.konkerlabs.platform.registry.web.services.api, while a change to com.konkerlabs.platform.registry.web.services.api can't break com.konkerlabs.platform.registry.business.services.api.
Position
Below the diagonal: com.konkerlabs.platform.registry.web.services.api uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in org.konker.registry.cassandraetl.repositories uses a type in com.konkerlabs.platform.registry.business.repositories.config.
org.konker.registry.cassandraetl.repositories uses com.konkerlabs.platform.registry.business.repositories.config, so a change to com.konkerlabs.platform.registry.business.repositories.config can break org.konker.registry.cassandraetl.repositories, while a change to org.konker.registry.cassandraetl.repositories can't break com.konkerlabs.platform.registry.business.repositories.config.
Position
Below the diagonal: org.konker.registry.cassandraetl.repositories uses a module listed above it, which is the healthy direction.
org.konker.registry.cassandraetl.repositories uses com.konkerlabs.platform.registry.business.model, so a change to com.konkerlabs.platform.registry.business.model can break org.konker.registry.cassandraetl.repositories, while a change to org.konker.registry.cassandraetl.repositories can't break com.konkerlabs.platform.registry.business.model.
Position
Below the diagonal: org.konker.registry.cassandraetl.repositories uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in org.konker.registry.cassandraetl.repositories uses a type in com.konkerlabs.platform.registry.business.repositories.events.
org.konker.registry.cassandraetl.repositories uses com.konkerlabs.platform.registry.business.repositories.events, so a change to com.konkerlabs.platform.registry.business.repositories.events can break org.konker.registry.cassandraetl.repositories, while a change to org.konker.registry.cassandraetl.repositories can't break com.konkerlabs.platform.registry.business.repositories.events.
Position
Below the diagonal: org.konker.registry.cassandraetl.repositories uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in com.konkerlabs.platform.registry.data.core.integration.processors uses a type in com.konkerlabs.platform.utilities.parsers.json.
com.konkerlabs.platform.registry.data.core.integration.processors uses com.konkerlabs.platform.utilities.parsers.json, so a change to com.konkerlabs.platform.utilities.parsers.json can break com.konkerlabs.platform.registry.data.core.integration.processors, while a change to com.konkerlabs.platform.registry.data.core.integration.processors can't break com.konkerlabs.platform.utilities.parsers.json.
Position
Below the diagonal: com.konkerlabs.platform.registry.data.core.integration.processors uses a module listed above it, which is the healthy direction.
3 pairs of types, where a type in com.konkerlabs.platform.registry.data.core.integration.processors uses a type in com.konkerlabs.platform.registry.business.model.
com.konkerlabs.platform.registry.data.core.integration.processors uses com.konkerlabs.platform.registry.business.model, so a change to com.konkerlabs.platform.registry.business.model can break com.konkerlabs.platform.registry.data.core.integration.processors, while a change to com.konkerlabs.platform.registry.data.core.integration.processors can't break com.konkerlabs.platform.registry.business.model.
Position
Below the diagonal: com.konkerlabs.platform.registry.data.core.integration.processors uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in com.konkerlabs.platform.registry.data.core.integration.processors uses a type in com.konkerlabs.platform.registry.data.core.services.routes.api.
com.konkerlabs.platform.registry.data.core.integration.processors uses com.konkerlabs.platform.registry.data.core.services.routes.api, so a change to com.konkerlabs.platform.registry.data.core.services.routes.api can break com.konkerlabs.platform.registry.data.core.integration.processors, while a change to com.konkerlabs.platform.registry.data.core.integration.processors can't break com.konkerlabs.platform.registry.data.core.services.routes.api.
Position
Below the diagonal: com.konkerlabs.platform.registry.data.core.integration.processors uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in com.konkerlabs.platform.registry.data.core.integration.processors uses a type in com.konkerlabs.platform.registry.business.services.api.
com.konkerlabs.platform.registry.data.core.integration.processors uses com.konkerlabs.platform.registry.business.services.api, so a change to com.konkerlabs.platform.registry.business.services.api can break com.konkerlabs.platform.registry.data.core.integration.processors, while a change to com.konkerlabs.platform.registry.data.core.integration.processors can't break com.konkerlabs.platform.registry.business.services.api.
Position
Below the diagonal: com.konkerlabs.platform.registry.data.core.integration.processors uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in com.konkerlabs.platform.registry.data.core.integration.processors uses a type in com.konkerlabs.platform.registry.data.core.services.api.
com.konkerlabs.platform.registry.data.core.integration.processors uses com.konkerlabs.platform.registry.data.core.services.api, so a change to com.konkerlabs.platform.registry.data.core.services.api can break com.konkerlabs.platform.registry.data.core.integration.processors, while a change to com.konkerlabs.platform.registry.data.core.integration.processors can't break com.konkerlabs.platform.registry.data.core.services.api.
Position
Below the diagonal: com.konkerlabs.platform.registry.data.core.integration.processors uses a module listed above it, which is the healthy direction.
com.konkerlabs.platform.registry.idm.security uses com.konkerlabs.platform.registry.business.model, so a change to com.konkerlabs.platform.registry.business.model can break com.konkerlabs.platform.registry.idm.security, while a change to com.konkerlabs.platform.registry.idm.security can't break com.konkerlabs.platform.registry.business.model.
Position
Below the diagonal: com.konkerlabs.platform.registry.idm.security uses a module listed above it, which is the healthy direction.
com.konkerlabs.platform.registry.idm.security uses com.konkerlabs.platform.registry.business.repositories, so a change to com.konkerlabs.platform.registry.business.repositories can break com.konkerlabs.platform.registry.idm.security, while a change to com.konkerlabs.platform.registry.idm.security can't break com.konkerlabs.platform.registry.business.repositories.
Position
Below the diagonal: com.konkerlabs.platform.registry.idm.security uses a module listed above it, which is the healthy direction.
com.konkerlabs.platform.registry.idm.security uses com.konkerlabs.platform.registry.idm.services, so a change to com.konkerlabs.platform.registry.idm.services can break com.konkerlabs.platform.registry.idm.security, while a change to com.konkerlabs.platform.registry.idm.security can't break com.konkerlabs.platform.registry.idm.services.
Position
Below the diagonal: com.konkerlabs.platform.registry.idm.security uses a module listed above it, which is the healthy direction.
com.konkerlabs.platform.registry.idm.web.controllers uses com.konkerlabs.platform.registry.business.model, so a change to com.konkerlabs.platform.registry.business.model can break com.konkerlabs.platform.registry.idm.web.controllers, while a change to com.konkerlabs.platform.registry.idm.web.controllers can't break com.konkerlabs.platform.registry.business.model.
Position
Below the diagonal: com.konkerlabs.platform.registry.idm.web.controllers uses a module listed above it, which is the healthy direction.
com.konkerlabs.platform.registry.idm.web.controllers uses com.konkerlabs.platform.registry.idm.web.form, so a change to com.konkerlabs.platform.registry.idm.web.form can break com.konkerlabs.platform.registry.idm.web.controllers, while a change to com.konkerlabs.platform.registry.idm.web.controllers can't break com.konkerlabs.platform.registry.idm.web.form.
Position
Below the diagonal: com.konkerlabs.platform.registry.idm.web.controllers uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in com.konkerlabs.platform.registry.idm.web.controllers uses a type in com.konkerlabs.platform.registry.business.services.api.
com.konkerlabs.platform.registry.idm.web.controllers uses com.konkerlabs.platform.registry.business.services.api, so a change to com.konkerlabs.platform.registry.business.services.api can break com.konkerlabs.platform.registry.idm.web.controllers, while a change to com.konkerlabs.platform.registry.idm.web.controllers can't break com.konkerlabs.platform.registry.business.services.api.
Position
Below the diagonal: com.konkerlabs.platform.registry.idm.web.controllers uses a module listed above it, which is the healthy direction.
com.konkerlabs.platform.registry.idm.web.controllers uses com.konkerlabs.platform.registry.idm.services, so a change to com.konkerlabs.platform.registry.idm.services can break com.konkerlabs.platform.registry.idm.web.controllers, while a change to com.konkerlabs.platform.registry.idm.web.controllers can't break com.konkerlabs.platform.registry.idm.services.
Position
Below the diagonal: com.konkerlabs.platform.registry.idm.web.controllers uses a module listed above it, which is the healthy direction.
com.konkerlabs.platform.registry.web.converters uses com.konkerlabs.platform.registry.security, so a change to com.konkerlabs.platform.registry.security can break com.konkerlabs.platform.registry.web.converters, while a change to com.konkerlabs.platform.registry.web.converters can't break com.konkerlabs.platform.registry.security.
Position
Below the diagonal: com.konkerlabs.platform.registry.web.converters uses a module listed above it, which is the healthy direction.
com.konkerlabs.platform.registry.web.converters uses com.konkerlabs.platform.registry.web.converters.utils, so a change to com.konkerlabs.platform.registry.web.converters.utils can break com.konkerlabs.platform.registry.web.converters, while a change to com.konkerlabs.platform.registry.web.converters can't break com.konkerlabs.platform.registry.web.converters.utils.
Position
Below the diagonal: com.konkerlabs.platform.registry.web.converters uses a module listed above it, which is the healthy direction.
com.konkerlabs.platform.registry.web.services uses com.konkerlabs.platform.utilities.parsers.json, so a change to com.konkerlabs.platform.utilities.parsers.json can break com.konkerlabs.platform.registry.web.services, while a change to com.konkerlabs.platform.registry.web.services can't break com.konkerlabs.platform.utilities.parsers.json.
Position
Below the diagonal: com.konkerlabs.platform.registry.web.services uses a module listed above it, which is the healthy direction.
com.konkerlabs.platform.registry.web.services uses com.konkerlabs.platform.registry.business.model, so a change to com.konkerlabs.platform.registry.business.model can break com.konkerlabs.platform.registry.web.services, while a change to com.konkerlabs.platform.registry.web.services can't break com.konkerlabs.platform.registry.business.model.
Position
Below the diagonal: com.konkerlabs.platform.registry.web.services uses a module listed above it, which is the healthy direction.
com.konkerlabs.platform.registry.web.services uses com.konkerlabs.platform.registry.business.repositories, so a change to com.konkerlabs.platform.registry.business.repositories can break com.konkerlabs.platform.registry.web.services, while a change to com.konkerlabs.platform.registry.web.services can't break com.konkerlabs.platform.registry.business.repositories.
Position
Below the diagonal: com.konkerlabs.platform.registry.web.services uses a module listed above it, which is the healthy direction.
com.konkerlabs.platform.registry.web.services uses com.konkerlabs.platform.registry.business.services.api, so a change to com.konkerlabs.platform.registry.business.services.api can break com.konkerlabs.platform.registry.web.services, while a change to com.konkerlabs.platform.registry.web.services can't break com.konkerlabs.platform.registry.business.services.api.
Position
Below the diagonal: com.konkerlabs.platform.registry.web.services uses a module listed above it, which is the healthy direction.
com.konkerlabs.platform.registry.web.services uses com.konkerlabs.platform.registry.web.services.api, so a change to com.konkerlabs.platform.registry.web.services.api can break com.konkerlabs.platform.registry.web.services, while a change to com.konkerlabs.platform.registry.web.services can't break com.konkerlabs.platform.registry.web.services.api.
Position
Below the diagonal: com.konkerlabs.platform.registry.web.services uses a module listed above it, which is the healthy direction.
org.konker.registry.cassandraetl.services uses com.konkerlabs.platform.registry.business.model, so a change to com.konkerlabs.platform.registry.business.model can break org.konker.registry.cassandraetl.services, while a change to org.konker.registry.cassandraetl.services can't break com.konkerlabs.platform.registry.business.model.
Position
Below the diagonal: org.konker.registry.cassandraetl.services uses a module listed above it, which is the healthy direction.
org.konker.registry.cassandraetl.services uses com.konkerlabs.platform.registry.business.repositories, so a change to com.konkerlabs.platform.registry.business.repositories can break org.konker.registry.cassandraetl.services, while a change to org.konker.registry.cassandraetl.services can't break com.konkerlabs.platform.registry.business.repositories.
Position
Below the diagonal: org.konker.registry.cassandraetl.services uses a module listed above it, which is the healthy direction.
4 pairs of types, where a type in org.konker.registry.cassandraetl.services uses a type in com.konkerlabs.platform.registry.business.repositories.events.
org.konker.registry.cassandraetl.services uses com.konkerlabs.platform.registry.business.repositories.events, so a change to com.konkerlabs.platform.registry.business.repositories.events can break org.konker.registry.cassandraetl.services, while a change to org.konker.registry.cassandraetl.services can't break com.konkerlabs.platform.registry.business.repositories.events.
Position
Below the diagonal: org.konker.registry.cassandraetl.services uses a module listed above it, which is the healthy direction.
org.konker.registry.cassandraetl.services uses org.konker.registry.cassandraetl.repositories, so a change to org.konker.registry.cassandraetl.repositories can break org.konker.registry.cassandraetl.services, while a change to org.konker.registry.cassandraetl.services can't break org.konker.registry.cassandraetl.repositories.
Position
Below the diagonal: org.konker.registry.cassandraetl.services uses a module listed above it, which is the healthy direction.
com.konkerlabs.platform.registry.config uses com.konkerlabs.platform.registry.business.repositories.config, so a change to com.konkerlabs.platform.registry.business.repositories.config can break com.konkerlabs.platform.registry.config, while a change to com.konkerlabs.platform.registry.config can't break com.konkerlabs.platform.registry.business.repositories.config.
Position
Below the diagonal: com.konkerlabs.platform.registry.config uses a module listed above it, which is the healthy direction.
com.konkerlabs.platform.registry.config uses com.konkerlabs.platform.registry.business.services.api, so a change to com.konkerlabs.platform.registry.business.services.api can break com.konkerlabs.platform.registry.config, while a change to com.konkerlabs.platform.registry.config can't break com.konkerlabs.platform.registry.business.services.api.
Position
Below the diagonal: com.konkerlabs.platform.registry.config uses a module listed above it, which is the healthy direction.
com.konkerlabs.platform.registry.config uses com.konkerlabs.platform.registry.idm.services, so a change to com.konkerlabs.platform.registry.idm.services can break com.konkerlabs.platform.registry.config, while a change to com.konkerlabs.platform.registry.config can't break com.konkerlabs.platform.registry.idm.services.
Position
Below the diagonal: com.konkerlabs.platform.registry.config uses a module listed above it, which is the healthy direction.
com.konkerlabs.platform.registry.config uses com.konkerlabs.platform.registry.web.converters, so a change to com.konkerlabs.platform.registry.web.converters can break com.konkerlabs.platform.registry.config, while a change to com.konkerlabs.platform.registry.config can't break com.konkerlabs.platform.registry.web.converters.
Position
Below the diagonal: com.konkerlabs.platform.registry.config uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in com.konkerlabs.platform.registry.api.config uses a type in com.konkerlabs.platform.registry.business.repositories.config.
com.konkerlabs.platform.registry.api.config uses com.konkerlabs.platform.registry.business.repositories.config, so a change to com.konkerlabs.platform.registry.business.repositories.config can break com.konkerlabs.platform.registry.api.config, while a change to com.konkerlabs.platform.registry.api.config can't break com.konkerlabs.platform.registry.business.repositories.config.
Position
Below the diagonal: com.konkerlabs.platform.registry.api.config uses a module listed above it, which is the healthy direction.
com.konkerlabs.platform.registry.api.config uses com.konkerlabs.platform.registry.config, so a change to com.konkerlabs.platform.registry.config can break com.konkerlabs.platform.registry.api.config, while a change to com.konkerlabs.platform.registry.api.config can't break com.konkerlabs.platform.registry.config.
Position
Below the diagonal: com.konkerlabs.platform.registry.api.config uses a module listed above it, which is the healthy direction.
com.konkerlabs.platform.registry.business.services uses com.konkerlabs.platform.registry.audit.model, so a change to com.konkerlabs.platform.registry.audit.model can break com.konkerlabs.platform.registry.business.services, while a change to com.konkerlabs.platform.registry.business.services can't break com.konkerlabs.platform.registry.audit.model.
Position
Below the diagonal: com.konkerlabs.platform.registry.business.services uses a module listed above it, which is the healthy direction.
com.konkerlabs.platform.registry.business.services uses com.konkerlabs.platform.registry.billing.model, so a change to com.konkerlabs.platform.registry.billing.model can break com.konkerlabs.platform.registry.business.services, while a change to com.konkerlabs.platform.registry.business.services can't break com.konkerlabs.platform.registry.billing.model.
Position
Below the diagonal: com.konkerlabs.platform.registry.business.services uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in com.konkerlabs.platform.registry.business.services uses a type in com.konkerlabs.platform.registry.business.model.enumerations.
com.konkerlabs.platform.registry.business.services uses com.konkerlabs.platform.registry.business.model.enumerations, so a change to com.konkerlabs.platform.registry.business.model.enumerations can break com.konkerlabs.platform.registry.business.services, while a change to com.konkerlabs.platform.registry.business.services can't break com.konkerlabs.platform.registry.business.model.enumerations.
Position
Below the diagonal: com.konkerlabs.platform.registry.business.services uses a module listed above it, which is the healthy direction.
com.konkerlabs.platform.registry.business.services uses com.konkerlabs.platform.utilities.parsers.json, so a change to com.konkerlabs.platform.utilities.parsers.json can break com.konkerlabs.platform.registry.business.services, while a change to com.konkerlabs.platform.registry.business.services can't break com.konkerlabs.platform.utilities.parsers.json.
Position
Below the diagonal: com.konkerlabs.platform.registry.business.services uses a module listed above it, which is the healthy direction.
105 pairs of types, where a type in com.konkerlabs.platform.registry.business.services uses a type in com.konkerlabs.platform.registry.business.model. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
com.konkerlabs.platform.registry.business.services uses com.konkerlabs.platform.registry.business.model, so a change to com.konkerlabs.platform.registry.business.model can break com.konkerlabs.platform.registry.business.services, while a change to com.konkerlabs.platform.registry.business.services can't break com.konkerlabs.platform.registry.business.model.
Position
Below the diagonal: com.konkerlabs.platform.registry.business.services uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in com.konkerlabs.platform.registry.business.services uses a type in com.konkerlabs.platform.registry.audit.repositories.
com.konkerlabs.platform.registry.business.services uses com.konkerlabs.platform.registry.audit.repositories, so a change to com.konkerlabs.platform.registry.audit.repositories can break com.konkerlabs.platform.registry.business.services, while a change to com.konkerlabs.platform.registry.business.services can't break com.konkerlabs.platform.registry.audit.repositories.
Position
Below the diagonal: com.konkerlabs.platform.registry.business.services uses a module listed above it, which is the healthy direction.
69 pairs of types, where a type in com.konkerlabs.platform.registry.business.services uses a type in com.konkerlabs.platform.registry.business.repositories. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
com.konkerlabs.platform.registry.business.services uses com.konkerlabs.platform.registry.business.repositories, so a change to com.konkerlabs.platform.registry.business.repositories can break com.konkerlabs.platform.registry.business.services, while a change to com.konkerlabs.platform.registry.business.services can't break com.konkerlabs.platform.registry.business.repositories.
Position
Below the diagonal: com.konkerlabs.platform.registry.business.services uses a module listed above it, which is the healthy direction.
3 pairs of types, where a type in com.konkerlabs.platform.registry.business.services uses a type in com.konkerlabs.platform.registry.business.repositories.events.api.
com.konkerlabs.platform.registry.business.services uses com.konkerlabs.platform.registry.business.repositories.events.api, so a change to com.konkerlabs.platform.registry.business.repositories.events.api can break com.konkerlabs.platform.registry.business.services, while a change to com.konkerlabs.platform.registry.business.services can't break com.konkerlabs.platform.registry.business.repositories.events.api.
Position
Below the diagonal: com.konkerlabs.platform.registry.business.services uses a module listed above it, which is the healthy direction.
86 pairs of types, where a type in com.konkerlabs.platform.registry.business.services uses a type in com.konkerlabs.platform.registry.business.services.api. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
com.konkerlabs.platform.registry.business.services uses com.konkerlabs.platform.registry.business.services.api, so a change to com.konkerlabs.platform.registry.business.services.api can break com.konkerlabs.platform.registry.business.services, while a change to com.konkerlabs.platform.registry.business.services can't break com.konkerlabs.platform.registry.business.services.api.
Position
Below the diagonal: com.konkerlabs.platform.registry.business.services uses a module listed above it, which is the healthy direction.
com.konkerlabs.platform.registry.business.services uses com.konkerlabs.platform.registry.config, so a change to com.konkerlabs.platform.registry.config can break com.konkerlabs.platform.registry.business.services, while a change to com.konkerlabs.platform.registry.business.services can't break com.konkerlabs.platform.registry.config.
Position
Below the diagonal: com.konkerlabs.platform.registry.business.services uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in com.konkerlabs.platform.registry.data.core.config uses a type in com.konkerlabs.platform.registry.business.repositories.config.
com.konkerlabs.platform.registry.data.core.config uses com.konkerlabs.platform.registry.business.repositories.config, so a change to com.konkerlabs.platform.registry.business.repositories.config can break com.konkerlabs.platform.registry.data.core.config, while a change to com.konkerlabs.platform.registry.data.core.config can't break com.konkerlabs.platform.registry.business.repositories.config.
Position
Below the diagonal: com.konkerlabs.platform.registry.data.core.config uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in com.konkerlabs.platform.registry.data.core.config uses a type in com.konkerlabs.platform.registry.business.services.api.
com.konkerlabs.platform.registry.data.core.config uses com.konkerlabs.platform.registry.business.services.api, so a change to com.konkerlabs.platform.registry.business.services.api can break com.konkerlabs.platform.registry.data.core.config, while a change to com.konkerlabs.platform.registry.data.core.config can't break com.konkerlabs.platform.registry.business.services.api.
Position
Below the diagonal: com.konkerlabs.platform.registry.data.core.config uses a module listed above it, which is the healthy direction.
com.konkerlabs.platform.registry.data.core.config uses com.konkerlabs.platform.registry.config, so a change to com.konkerlabs.platform.registry.config can break com.konkerlabs.platform.registry.data.core.config, while a change to com.konkerlabs.platform.registry.data.core.config can't break com.konkerlabs.platform.registry.config.
Position
Below the diagonal: com.konkerlabs.platform.registry.data.core.config uses a module listed above it, which is the healthy direction.
com.konkerlabs.platform.registry.data.core.services uses com.konkerlabs.platform.utilities.parsers.json, so a change to com.konkerlabs.platform.utilities.parsers.json can break com.konkerlabs.platform.registry.data.core.services, while a change to com.konkerlabs.platform.registry.data.core.services can't break com.konkerlabs.platform.utilities.parsers.json.
Position
Below the diagonal: com.konkerlabs.platform.registry.data.core.services uses a module listed above it, which is the healthy direction.
com.konkerlabs.platform.registry.data.core.services uses com.konkerlabs.platform.registry.business.model, so a change to com.konkerlabs.platform.registry.business.model can break com.konkerlabs.platform.registry.data.core.services, while a change to com.konkerlabs.platform.registry.data.core.services can't break com.konkerlabs.platform.registry.business.model.
Position
Below the diagonal: com.konkerlabs.platform.registry.data.core.services uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in com.konkerlabs.platform.registry.data.core.services uses a type in com.konkerlabs.platform.registry.business.repositories.events.api.
com.konkerlabs.platform.registry.data.core.services uses com.konkerlabs.platform.registry.business.repositories.events.api, so a change to com.konkerlabs.platform.registry.business.repositories.events.api can break com.konkerlabs.platform.registry.data.core.services, while a change to com.konkerlabs.platform.registry.data.core.services can't break com.konkerlabs.platform.registry.business.repositories.events.api.
Position
Below the diagonal: com.konkerlabs.platform.registry.data.core.services uses a module listed above it, which is the healthy direction.
5 pairs of types, where a type in com.konkerlabs.platform.registry.data.core.services uses a type in com.konkerlabs.platform.registry.business.services.api.
com.konkerlabs.platform.registry.data.core.services uses com.konkerlabs.platform.registry.business.services.api, so a change to com.konkerlabs.platform.registry.business.services.api can break com.konkerlabs.platform.registry.data.core.services, while a change to com.konkerlabs.platform.registry.data.core.services can't break com.konkerlabs.platform.registry.business.services.api.
Position
Below the diagonal: com.konkerlabs.platform.registry.data.core.services uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in com.konkerlabs.platform.registry.data.core.services uses a type in com.konkerlabs.platform.registry.data.core.services.api.
com.konkerlabs.platform.registry.data.core.services uses com.konkerlabs.platform.registry.data.core.services.api, so a change to com.konkerlabs.platform.registry.data.core.services.api can break com.konkerlabs.platform.registry.data.core.services, while a change to com.konkerlabs.platform.registry.data.core.services can't break com.konkerlabs.platform.registry.data.core.services.api.
Position
Below the diagonal: com.konkerlabs.platform.registry.data.core.services uses a module listed above it, which is the healthy direction.
com.konkerlabs.platform.registry.data.core.services uses com.konkerlabs.platform.registry.config, so a change to com.konkerlabs.platform.registry.config can break com.konkerlabs.platform.registry.data.core.services, while a change to com.konkerlabs.platform.registry.data.core.services can't break com.konkerlabs.platform.registry.config.
Position
Below the diagonal: com.konkerlabs.platform.registry.data.core.services uses a module listed above it, which is the healthy direction.
com.konkerlabs.platform.registry.web.controllers uses com.konkerlabs.platform.utilities.parsers.json, so a change to com.konkerlabs.platform.utilities.parsers.json can break com.konkerlabs.platform.registry.web.controllers, while a change to com.konkerlabs.platform.registry.web.controllers can't break com.konkerlabs.platform.utilities.parsers.json.
Position
Below the diagonal: com.konkerlabs.platform.registry.web.controllers uses a module listed above it, which is the healthy direction.
27 pairs of types, where a type in com.konkerlabs.platform.registry.web.controllers uses a type in com.konkerlabs.platform.registry.business.model. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
com.konkerlabs.platform.registry.web.controllers uses com.konkerlabs.platform.registry.business.model, so a change to com.konkerlabs.platform.registry.business.model can break com.konkerlabs.platform.registry.web.controllers, while a change to com.konkerlabs.platform.registry.web.controllers can't break com.konkerlabs.platform.registry.business.model.
Position
Below the diagonal: com.konkerlabs.platform.registry.web.controllers uses a module listed above it, which is the healthy direction.
com.konkerlabs.platform.registry.web.controllers uses com.konkerlabs.platform.registry.web.forms, so a change to com.konkerlabs.platform.registry.web.forms can break com.konkerlabs.platform.registry.web.controllers, while a change to com.konkerlabs.platform.registry.web.controllers can't break com.konkerlabs.platform.registry.web.forms.
Position
Below the diagonal: com.konkerlabs.platform.registry.web.controllers uses a module listed above it, which is the healthy direction.
41 pairs of types, where a type in com.konkerlabs.platform.registry.web.controllers uses a type in com.konkerlabs.platform.registry.business.services.api. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
com.konkerlabs.platform.registry.web.controllers uses com.konkerlabs.platform.registry.business.services.api, so a change to com.konkerlabs.platform.registry.business.services.api can break com.konkerlabs.platform.registry.web.controllers, while a change to com.konkerlabs.platform.registry.web.controllers can't break com.konkerlabs.platform.registry.business.services.api.
Position
Below the diagonal: com.konkerlabs.platform.registry.web.controllers uses a module listed above it, which is the healthy direction.
com.konkerlabs.platform.registry.web.controllers uses com.konkerlabs.platform.registry.web.services.api, so a change to com.konkerlabs.platform.registry.web.services.api can break com.konkerlabs.platform.registry.web.controllers, while a change to com.konkerlabs.platform.registry.web.controllers can't break com.konkerlabs.platform.registry.web.services.api.
Position
Below the diagonal: com.konkerlabs.platform.registry.web.controllers uses a module listed above it, which is the healthy direction.
com.konkerlabs.platform.registry.web.controllers uses com.konkerlabs.platform.registry.web.converters, so a change to com.konkerlabs.platform.registry.web.converters can break com.konkerlabs.platform.registry.web.controllers, while a change to com.konkerlabs.platform.registry.web.controllers can't break com.konkerlabs.platform.registry.web.converters.
Position
Below the diagonal: com.konkerlabs.platform.registry.web.controllers uses a module listed above it, which is the healthy direction.
com.konkerlabs.platform.registry.web.controllers uses com.konkerlabs.platform.registry.config, so a change to com.konkerlabs.platform.registry.config can break com.konkerlabs.platform.registry.web.controllers, while a change to com.konkerlabs.platform.registry.web.controllers can't break com.konkerlabs.platform.registry.config.
Position
Below the diagonal: com.konkerlabs.platform.registry.web.controllers uses a module listed above it, which is the healthy direction.
29 pairs of types, where a type in com.konkerlabs.platform.registry.api.web.controller uses a type in com.konkerlabs.platform.registry.business.model. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
com.konkerlabs.platform.registry.api.web.controller uses com.konkerlabs.platform.registry.business.model, so a change to com.konkerlabs.platform.registry.business.model can break com.konkerlabs.platform.registry.api.web.controller, while a change to com.konkerlabs.platform.registry.api.web.controller can't break com.konkerlabs.platform.registry.business.model.
Position
Below the diagonal: com.konkerlabs.platform.registry.api.web.controller uses a module listed above it, which is the healthy direction.
46 pairs of types, where a type in com.konkerlabs.platform.registry.api.web.controller uses a type in com.konkerlabs.platform.registry.business.services.api. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
com.konkerlabs.platform.registry.api.web.controller uses com.konkerlabs.platform.registry.business.services.api, so a change to com.konkerlabs.platform.registry.business.services.api can break com.konkerlabs.platform.registry.api.web.controller, while a change to com.konkerlabs.platform.registry.api.web.controller can't break com.konkerlabs.platform.registry.business.services.api.
Position
Below the diagonal: com.konkerlabs.platform.registry.api.web.controller uses a module listed above it, which is the healthy direction.
41 pairs of types, where a type in com.konkerlabs.platform.registry.api.web.controller uses a type in com.konkerlabs.platform.registry.api.model. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
com.konkerlabs.platform.registry.api.web.controller uses com.konkerlabs.platform.registry.api.model, so a change to com.konkerlabs.platform.registry.api.model can break com.konkerlabs.platform.registry.api.web.controller, while a change to com.konkerlabs.platform.registry.api.web.controller can't break com.konkerlabs.platform.registry.api.model.
Position
Below the diagonal: com.konkerlabs.platform.registry.api.web.controller uses a module listed above it, which is the healthy direction.
com.konkerlabs.platform.registry.api.web.controller uses com.konkerlabs.platform.registry.idm.services, so a change to com.konkerlabs.platform.registry.idm.services can break com.konkerlabs.platform.registry.api.web.controller, while a change to com.konkerlabs.platform.registry.api.web.controller can't break com.konkerlabs.platform.registry.idm.services.
Position
Below the diagonal: com.konkerlabs.platform.registry.api.web.controller uses a module listed above it, which is the healthy direction.
com.konkerlabs.platform.registry.api.web.controller uses com.konkerlabs.platform.registry.api.config, so a change to com.konkerlabs.platform.registry.api.config can break com.konkerlabs.platform.registry.api.web.controller, while a change to com.konkerlabs.platform.registry.api.web.controller can't break com.konkerlabs.platform.registry.api.config.
Position
Below the diagonal: com.konkerlabs.platform.registry.api.web.controller uses a module listed above it, which is the healthy direction.
3 pairs of types, where a type in com.konkerlabs.platform.registry.data.core.integration.gateway uses a type in com.konkerlabs.platform.registry.business.model.
com.konkerlabs.platform.registry.data.core.integration.gateway uses com.konkerlabs.platform.registry.business.model, so a change to com.konkerlabs.platform.registry.business.model can break com.konkerlabs.platform.registry.data.core.integration.gateway, while a change to com.konkerlabs.platform.registry.data.core.integration.gateway can't break com.konkerlabs.platform.registry.business.model.
Position
Below the diagonal: com.konkerlabs.platform.registry.data.core.integration.gateway uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in com.konkerlabs.platform.registry.data.core.integration.gateway uses a type in com.konkerlabs.platform.registry.data.core.config.
com.konkerlabs.platform.registry.data.core.integration.gateway uses com.konkerlabs.platform.registry.data.core.config, so a change to com.konkerlabs.platform.registry.data.core.config can break com.konkerlabs.platform.registry.data.core.integration.gateway, while a change to com.konkerlabs.platform.registry.data.core.integration.gateway can't break com.konkerlabs.platform.registry.data.core.config.
Position
Below the diagonal: com.konkerlabs.platform.registry.data.core.integration.gateway uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in com.konkerlabs.platform.registry.data.core.services.publishers uses a type in com.konkerlabs.platform.utilities.parsers.json.
com.konkerlabs.platform.registry.data.core.services.publishers uses com.konkerlabs.platform.utilities.parsers.json, so a change to com.konkerlabs.platform.utilities.parsers.json can break com.konkerlabs.platform.registry.data.core.services.publishers, while a change to com.konkerlabs.platform.registry.data.core.services.publishers can't break com.konkerlabs.platform.utilities.parsers.json.
Position
Below the diagonal: com.konkerlabs.platform.registry.data.core.services.publishers uses a module listed above it, which is the healthy direction.
19 pairs of types, where a type in com.konkerlabs.platform.registry.data.core.services.publishers uses a type in com.konkerlabs.platform.registry.business.model.
com.konkerlabs.platform.registry.data.core.services.publishers uses com.konkerlabs.platform.registry.business.model, so a change to com.konkerlabs.platform.registry.business.model can break com.konkerlabs.platform.registry.data.core.services.publishers, while a change to com.konkerlabs.platform.registry.data.core.services.publishers can't break com.konkerlabs.platform.registry.business.model.
Position
Below the diagonal: com.konkerlabs.platform.registry.data.core.services.publishers uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in com.konkerlabs.platform.registry.data.core.services.publishers uses a type in com.konkerlabs.platform.registry.business.repositories.
com.konkerlabs.platform.registry.data.core.services.publishers uses com.konkerlabs.platform.registry.business.repositories, so a change to com.konkerlabs.platform.registry.business.repositories can break com.konkerlabs.platform.registry.data.core.services.publishers, while a change to com.konkerlabs.platform.registry.data.core.services.publishers can't break com.konkerlabs.platform.registry.business.repositories.
Position
Below the diagonal: com.konkerlabs.platform.registry.data.core.services.publishers uses a module listed above it, which is the healthy direction.
4 pairs of types, where a type in com.konkerlabs.platform.registry.data.core.services.publishers uses a type in com.konkerlabs.platform.registry.business.services.api.
com.konkerlabs.platform.registry.data.core.services.publishers uses com.konkerlabs.platform.registry.business.services.api, so a change to com.konkerlabs.platform.registry.business.services.api can break com.konkerlabs.platform.registry.data.core.services.publishers, while a change to com.konkerlabs.platform.registry.data.core.services.publishers can't break com.konkerlabs.platform.registry.business.services.api.
Position
Below the diagonal: com.konkerlabs.platform.registry.data.core.services.publishers uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in com.konkerlabs.platform.registry.data.core.services.publishers uses a type in com.konkerlabs.platform.registry.data.core.integration.converters.helper.
com.konkerlabs.platform.registry.data.core.services.publishers uses com.konkerlabs.platform.registry.data.core.integration.converters.helper, so a change to com.konkerlabs.platform.registry.data.core.integration.converters.helper can break com.konkerlabs.platform.registry.data.core.services.publishers, while a change to com.konkerlabs.platform.registry.data.core.services.publishers can't break com.konkerlabs.platform.registry.data.core.integration.converters.helper.
Position
Below the diagonal: com.konkerlabs.platform.registry.data.core.services.publishers uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in com.konkerlabs.platform.registry.data.core.services.publishers uses a type in com.konkerlabs.platform.registry.data.core.services.api.
com.konkerlabs.platform.registry.data.core.services.publishers uses com.konkerlabs.platform.registry.data.core.services.api, so a change to com.konkerlabs.platform.registry.data.core.services.api can break com.konkerlabs.platform.registry.data.core.services.publishers, while a change to com.konkerlabs.platform.registry.data.core.services.publishers can't break com.konkerlabs.platform.registry.data.core.services.api.
Position
Below the diagonal: com.konkerlabs.platform.registry.data.core.services.publishers uses a module listed above it, which is the healthy direction.
3 pairs of types, where a type in com.konkerlabs.platform.registry.data.core.services.publishers uses a type in com.konkerlabs.platform.registry.data.core.integration.gateway.
com.konkerlabs.platform.registry.data.core.services.publishers uses com.konkerlabs.platform.registry.data.core.integration.gateway, so a change to com.konkerlabs.platform.registry.data.core.integration.gateway can break com.konkerlabs.platform.registry.data.core.services.publishers, while a change to com.konkerlabs.platform.registry.data.core.services.publishers can't break com.konkerlabs.platform.registry.data.core.integration.gateway.
Position
Below the diagonal: com.konkerlabs.platform.registry.data.core.services.publishers uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in com.konkerlabs.platform.registry.data.core.services.routes uses a type in com.konkerlabs.platform.utilities.parsers.json.
com.konkerlabs.platform.registry.data.core.services.routes uses com.konkerlabs.platform.utilities.parsers.json, so a change to com.konkerlabs.platform.utilities.parsers.json can break com.konkerlabs.platform.registry.data.core.services.routes, while a change to com.konkerlabs.platform.registry.data.core.services.routes can't break com.konkerlabs.platform.utilities.parsers.json.
Position
Below the diagonal: com.konkerlabs.platform.registry.data.core.services.routes uses a module listed above it, which is the healthy direction.
6 pairs of types, where a type in com.konkerlabs.platform.registry.data.core.services.routes uses a type in com.konkerlabs.platform.registry.business.model.
com.konkerlabs.platform.registry.data.core.services.routes uses com.konkerlabs.platform.registry.business.model, so a change to com.konkerlabs.platform.registry.business.model can break com.konkerlabs.platform.registry.data.core.services.routes, while a change to com.konkerlabs.platform.registry.data.core.services.routes can't break com.konkerlabs.platform.registry.business.model.
Position
Below the diagonal: com.konkerlabs.platform.registry.data.core.services.routes uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in com.konkerlabs.platform.registry.data.core.services.routes uses a type in com.konkerlabs.platform.registry.business.repositories.
com.konkerlabs.platform.registry.data.core.services.routes uses com.konkerlabs.platform.registry.business.repositories, so a change to com.konkerlabs.platform.registry.business.repositories can break com.konkerlabs.platform.registry.data.core.services.routes, while a change to com.konkerlabs.platform.registry.data.core.services.routes can't break com.konkerlabs.platform.registry.business.repositories.
Position
Below the diagonal: com.konkerlabs.platform.registry.data.core.services.routes uses a module listed above it, which is the healthy direction.
3 pairs of types, where a type in com.konkerlabs.platform.registry.data.core.services.routes uses a type in com.konkerlabs.platform.registry.data.core.services.routes.api.
com.konkerlabs.platform.registry.data.core.services.routes uses com.konkerlabs.platform.registry.data.core.services.routes.api, so a change to com.konkerlabs.platform.registry.data.core.services.routes.api can break com.konkerlabs.platform.registry.data.core.services.routes, while a change to com.konkerlabs.platform.registry.data.core.services.routes can't break com.konkerlabs.platform.registry.data.core.services.routes.api.
Position
Below the diagonal: com.konkerlabs.platform.registry.data.core.services.routes uses a module listed above it, which is the healthy direction.
3 pairs of types, where a type in com.konkerlabs.platform.registry.data.core.services.routes uses a type in com.konkerlabs.platform.registry.business.services.api.
com.konkerlabs.platform.registry.data.core.services.routes uses com.konkerlabs.platform.registry.business.services.api, so a change to com.konkerlabs.platform.registry.business.services.api can break com.konkerlabs.platform.registry.data.core.services.routes, while a change to com.konkerlabs.platform.registry.data.core.services.routes can't break com.konkerlabs.platform.registry.business.services.api.
Position
Below the diagonal: com.konkerlabs.platform.registry.data.core.services.routes uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in com.konkerlabs.platform.registry.data.core.services.routes uses a type in com.konkerlabs.platform.registry.data.core.integration.gateway.
com.konkerlabs.platform.registry.data.core.services.routes uses com.konkerlabs.platform.registry.data.core.integration.gateway, so a change to com.konkerlabs.platform.registry.data.core.integration.gateway can break com.konkerlabs.platform.registry.data.core.services.routes, while a change to com.konkerlabs.platform.registry.data.core.services.routes can't break com.konkerlabs.platform.registry.data.core.integration.gateway.
Position
Below the diagonal: com.konkerlabs.platform.registry.data.core.services.routes uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in com.konkerlabs.platform.registry.integration.processors uses a type in com.konkerlabs.platform.utilities.parsers.json.
com.konkerlabs.platform.registry.integration.processors uses com.konkerlabs.platform.utilities.parsers.json, so a change to com.konkerlabs.platform.utilities.parsers.json can break com.konkerlabs.platform.registry.integration.processors, while a change to com.konkerlabs.platform.registry.integration.processors can't break com.konkerlabs.platform.utilities.parsers.json.
Position
Below the diagonal: com.konkerlabs.platform.registry.integration.processors uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in com.konkerlabs.platform.registry.integration.processors uses a type in com.konkerlabs.platform.registry.business.model.
com.konkerlabs.platform.registry.integration.processors uses com.konkerlabs.platform.registry.business.model, so a change to com.konkerlabs.platform.registry.business.model can break com.konkerlabs.platform.registry.integration.processors, while a change to com.konkerlabs.platform.registry.integration.processors can't break com.konkerlabs.platform.registry.business.model.
Position
Below the diagonal: com.konkerlabs.platform.registry.integration.processors uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in com.konkerlabs.platform.registry.integration.processors uses a type in com.konkerlabs.platform.registry.business.services.api.
com.konkerlabs.platform.registry.integration.processors uses com.konkerlabs.platform.registry.business.services.api, so a change to com.konkerlabs.platform.registry.business.services.api can break com.konkerlabs.platform.registry.integration.processors, while a change to com.konkerlabs.platform.registry.integration.processors can't break com.konkerlabs.platform.registry.business.services.api.
Position
Below the diagonal: com.konkerlabs.platform.registry.integration.processors uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in com.konkerlabs.platform.registry.integration.processors uses a type in com.konkerlabs.platform.registry.data.core.integration.converters.helper.
com.konkerlabs.platform.registry.integration.processors uses com.konkerlabs.platform.registry.data.core.integration.converters.helper, so a change to com.konkerlabs.platform.registry.data.core.integration.converters.helper can break com.konkerlabs.platform.registry.integration.processors, while a change to com.konkerlabs.platform.registry.integration.processors can't break com.konkerlabs.platform.registry.data.core.integration.converters.helper.
Position
Below the diagonal: com.konkerlabs.platform.registry.integration.processors uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in com.konkerlabs.platform.registry.integration.processors uses a type in com.konkerlabs.platform.registry.data.core.integration.gateway.
com.konkerlabs.platform.registry.integration.processors uses com.konkerlabs.platform.registry.data.core.integration.gateway, so a change to com.konkerlabs.platform.registry.data.core.integration.gateway can break com.konkerlabs.platform.registry.integration.processors, while a change to com.konkerlabs.platform.registry.integration.processors can't break com.konkerlabs.platform.registry.data.core.integration.gateway.
Position
Below the diagonal: com.konkerlabs.platform.registry.integration.processors uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in com.konkerlabs.platform.registry.integration.endpoints uses a type in com.konkerlabs.platform.registry.business.model.enumerations.
com.konkerlabs.platform.registry.integration.endpoints uses com.konkerlabs.platform.registry.business.model.enumerations, so a change to com.konkerlabs.platform.registry.business.model.enumerations can break com.konkerlabs.platform.registry.integration.endpoints, while a change to com.konkerlabs.platform.registry.integration.endpoints can't break com.konkerlabs.platform.registry.business.model.enumerations.
Position
Below the diagonal: com.konkerlabs.platform.registry.integration.endpoints uses a module listed above it, which is the healthy direction.
4 pairs of types, where a type in com.konkerlabs.platform.registry.integration.endpoints uses a type in com.konkerlabs.platform.utilities.parsers.json.
com.konkerlabs.platform.registry.integration.endpoints uses com.konkerlabs.platform.utilities.parsers.json, so a change to com.konkerlabs.platform.utilities.parsers.json can break com.konkerlabs.platform.registry.integration.endpoints, while a change to com.konkerlabs.platform.registry.integration.endpoints can't break com.konkerlabs.platform.utilities.parsers.json.
Position
Below the diagonal: com.konkerlabs.platform.registry.integration.endpoints uses a module listed above it, which is the healthy direction.
3 pairs of types, where a type in com.konkerlabs.platform.registry.integration.endpoints uses a type in com.konkerlabs.platform.registry.business.model.
com.konkerlabs.platform.registry.integration.endpoints uses com.konkerlabs.platform.registry.business.model, so a change to com.konkerlabs.platform.registry.business.model can break com.konkerlabs.platform.registry.integration.endpoints, while a change to com.konkerlabs.platform.registry.integration.endpoints can't break com.konkerlabs.platform.registry.business.model.
Position
Below the diagonal: com.konkerlabs.platform.registry.integration.endpoints uses a module listed above it, which is the healthy direction.
11 pairs of types, where a type in com.konkerlabs.platform.registry.integration.endpoints uses a type in com.konkerlabs.platform.registry.business.services.api.
com.konkerlabs.platform.registry.integration.endpoints uses com.konkerlabs.platform.registry.business.services.api, so a change to com.konkerlabs.platform.registry.business.services.api can break com.konkerlabs.platform.registry.integration.endpoints, while a change to com.konkerlabs.platform.registry.integration.endpoints can't break com.konkerlabs.platform.registry.business.services.api.
Position
Below the diagonal: com.konkerlabs.platform.registry.integration.endpoints uses a module listed above it, which is the healthy direction.
com.konkerlabs.platform.registry.integration.endpoints uses com.konkerlabs.platform.registry.idm.services, so a change to com.konkerlabs.platform.registry.idm.services can break com.konkerlabs.platform.registry.integration.endpoints, while a change to com.konkerlabs.platform.registry.integration.endpoints can't break com.konkerlabs.platform.registry.idm.services.
Position
Below the diagonal: com.konkerlabs.platform.registry.integration.endpoints uses a module listed above it, which is the healthy direction.
4 pairs of types, where a type in com.konkerlabs.platform.registry.integration.endpoints uses a type in com.konkerlabs.platform.registry.data.core.integration.processors.
com.konkerlabs.platform.registry.integration.endpoints uses com.konkerlabs.platform.registry.data.core.integration.processors, so a change to com.konkerlabs.platform.registry.data.core.integration.processors can break com.konkerlabs.platform.registry.integration.endpoints, while a change to com.konkerlabs.platform.registry.integration.endpoints can't break com.konkerlabs.platform.registry.data.core.integration.processors.
Position
Below the diagonal: com.konkerlabs.platform.registry.integration.endpoints uses a module listed above it, which is the healthy direction.
com.konkerlabs.platform.registry.integration.endpoints uses com.konkerlabs.platform.registry.config, so a change to com.konkerlabs.platform.registry.config can break com.konkerlabs.platform.registry.integration.endpoints, while a change to com.konkerlabs.platform.registry.integration.endpoints can't break com.konkerlabs.platform.registry.config.
Position
Below the diagonal: com.konkerlabs.platform.registry.integration.endpoints uses a module listed above it, which is the healthy direction.
3 pairs of types, where a type in com.konkerlabs.platform.registry.integration.endpoints uses a type in com.konkerlabs.platform.registry.data.core.services.
com.konkerlabs.platform.registry.integration.endpoints uses com.konkerlabs.platform.registry.data.core.services, so a change to com.konkerlabs.platform.registry.data.core.services can break com.konkerlabs.platform.registry.integration.endpoints, while a change to com.konkerlabs.platform.registry.integration.endpoints can't break com.konkerlabs.platform.registry.data.core.services.
Position
Below the diagonal: com.konkerlabs.platform.registry.integration.endpoints uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in com.konkerlabs.platform.registry.integration.endpoints uses a type in com.konkerlabs.platform.registry.data.core.integration.gateway.
com.konkerlabs.platform.registry.integration.endpoints uses com.konkerlabs.platform.registry.data.core.integration.gateway, so a change to com.konkerlabs.platform.registry.data.core.integration.gateway can break com.konkerlabs.platform.registry.integration.endpoints, while a change to com.konkerlabs.platform.registry.integration.endpoints can't break com.konkerlabs.platform.registry.data.core.integration.gateway.
Position
Below the diagonal: com.konkerlabs.platform.registry.integration.endpoints uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in com.konkerlabs.platform.registry.integration.endpoints uses a type in com.konkerlabs.platform.registry.integration.processors.
com.konkerlabs.platform.registry.integration.endpoints uses com.konkerlabs.platform.registry.integration.processors, so a change to com.konkerlabs.platform.registry.integration.processors can break com.konkerlabs.platform.registry.integration.endpoints, while a change to com.konkerlabs.platform.registry.integration.endpoints can't break com.konkerlabs.platform.registry.integration.processors.
Position
Below the diagonal: com.konkerlabs.platform.registry.integration.endpoints uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 30.6 · Weak · gated by D4, R1, R7, X5 ·
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A02:2025 — Security Misconfiguration
143
High / Critical
A05:2025 — Injection
105
High / Critical
A03:2025 — Software Supply Chain Failures
73
High / Critical
A07:2025 — Authentication Failures
11
High / Critical
Roadmap
Top priorities: Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1; Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video; Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.
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 — 261
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 — 795
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 — 681
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 11
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 73 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 — 73 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, 1715 of 1737 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 READ here — but this repository measures it: a coverage step in CI (JaCoCo's report goal in REDACTED) shows that coverage is collected and tracked in your own CI. The built-in collector has no runner for this ecosystem (.java), so the analyzer could not read the number — a gap in the analyzer's language coverage, not an unmeasured repo. Not scored.
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 (.java) and this repository declares a JVM test suite (repository root, Maven), 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 Maven build resolved 22 artifact(s) (19 behind a shipped release, reported), but the build resolved only part of the graph, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. All 193 significant source file(s) were last meaningfully changed so long ago that no living knowledge remains — nothing since has been substantial enough to re-establish ownership (a broad, mechanical sweep that touches many files shallowly does not count, and neither does no activity at all). There is no concentration to measure, so the bus factor is not scored. This is not a clean bill: nobody currently holds working knowledge of this code (see D34 Knowledge Freshness). Counted over 4 of the 512 production source files in this repository: 319 are under the ~2,400-byte size floor this dimension measures over, and the remaining 189 have no attributable history left to measure.
D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 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 (REDACTED), 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 — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
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. Konker.registry.api/devops/k8s/konker-registry-api-helm/templates/deployment.yaml:3, REDACTED:3, REDACTED:3, REDACTED:3, REDACTED:3, REDACTED:2, REDACTED:2, REDACTED:2, REDACTED:2, REDACTED:2 and 1 more 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.
AC1 Text alternatives — 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. 26 further occurrence(s) are not listed individually; the score already reflects all 66.
AC2 Forms & labels — 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. 49 further occurrence(s) are not listed individually; the score already reflects all 89.
AC3 Page structure — 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. 114 further occurrence(s) are not listed individually; the score already reflects all 154.
AC6 Visual & motion safety — 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. 29 further occurrence(s) are not listed individually; the score already reflects all 69.
AX1 Captive dependencies — 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 check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
C4 Data Retention — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
C5 Data-Subject Rights — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X27 Collection changed while being enumerated — 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 check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned REDACTED, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
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 REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
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".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
What it measures: How tangled the control flow is — methods with many branches are hard to test and change.
Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.
36 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was d3.d3.svg.brush at 79. A further 5 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 d3.d3.dsv at 26 — they are counted neither in the figure above nor in this dimension's score.
+ 27 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 2 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with d3.d3.svg.brush (cyclomatic 79), d3.d3.layout.force (cyclomatic 61). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cyclomatic Complexity from 6.3 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
+ 50 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 59 bodies over 15 down to 15 or less in Cognitive Complexity — start with d3.d3.geom.quadtree.quadtree (cognitive 65), d3.d3_geom_voronoiCloseCells (cognitive 62), d3.d3.svg.arc.arc (cognitive 61). — 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 59 together lifts Cognitive Complexity from 6.5 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes8.8 / 10Strong✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 5 ClassTooLong finding(s) in God Classes — start with TimeZone.java, DeviceRegisterServiceImpl.java, UserServiceImpl.java. — One of this dimension's main actionable groups (5 warning-level).
Resolve the 3 FileTooLong finding(s) in God Classes — start with d3.js, TimeZone.java, DeviceRegisterServiceImpl.java. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 3 TooManyMethods finding(s) in God Classes — start with KonkerLogger.java, OauthClientDetails.java, KonkerLoggerContext.java. — One of this dimension's main actionable groups (3 warning-level).
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D4 · Code Duplication2.7 / 10Weak✓ Tool-verified
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.
199 duplicated block group(s) detected. 18.3 % of the production lines (7,451 of 40,665) are in a reported copy. A further 115 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
+ 140 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 18 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with TenantUserDetailsService.java (2), DeviceModelServiceImpl.java (2), EventRouteServiceImpl.java (2). — One of this dimension's main actionable groups (18 warning-level).
Resolve the 15 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with LocationServiceImpl.java (3), AlertTriggerServiceImpl.java (2), ApplicationServiceImpl.java (2). — One of this dimension's main actionable groups (15 warning-level).
Resolve the 11 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with DeviceConfigRabbitEndpoint.java, OAuthClientDetailsService.java, ApplicationServiceImpl.java. — One of this dimension's main actionable groups (11 warning-level).
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling7.7 / 10Strong✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
14 production modules (Maven+Python), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 4 module(s) off the main sequence.
Off the main sequence: konker.security · ×4
What to do
Resolve the 4 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (4 warning-level).
Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
Resolve the 2 Low cohesion finding(s) in Cohesion (LCOM4) — start with KonkerLoggingEvent.java, RabbitMQConfig.java. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D10 · Test Quality9.0 / 10Strong✓ Tool-verified
What it measures: Whether the tests truly assert behaviour rather than just running the code.
Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.
0 skipped, 422 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 1359 tests (2 harness-style project(s) excluded from the assertion penalty).
No assertions: shoulRaiseAnExceptionIfHttpMethodIsNull · ×95konker.registry.data.core/src/test/java/com/konkerlabs/platform/registry/test/data/core/integration/gateway/HttpGatewayTest.java:64
No direct assertions: shouldCreateAlertTrigger · ×327konker.registry.api/src/test/java/com/konkerlabs/platform/registry/api/test/web/controller/AlertTriggerRestControllerTest.java:210
What to do
Resolve the 327 No direct assertions finding(s) in Test Quality — start with DeviceRestControllerTest.java (22), EventRouteRestControllerTest.java (22), RestDestinationControllerTest.java (17). — One of this dimension's main actionable groups (327 recommendation-level).
Resolve the 95 No assertions finding(s) in Test Quality — start with EventRepositoryMongoTest.java (12), EventPublisherRestTest.java (10), DeviceEventRestEndpointTest.java (9). — One of this dimension's main actionable groups (95 warning-level).
Detailed fixes: d10_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
REDACTED scan ran and found no leaked secrets. 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.
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 67 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 14 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. 19 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. A further 7 coordinate(s) are not published to Maven Central — another repository (Google's Maven hosts androidx), a SNAPSHOT, or a private artifact — so their licences are not readable from here and they are outside this verdict.
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: 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.
8 deducted task-comment markers across 40665 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
Resolve the 8 TodoComment finding(s) in Explicit Debt — start with EventRouteServiceTest.java (2), TransformationForm.java, UserNotificationController.java. — One of this dimension's main actionable groups (8 warning-level).
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.
1 of 1 documentation facets pass in full. 18 document(s) read across 1 unit(s).
✓ On the Gold path — maintain.
Detailed fixes: d19_recommendation.md.
Do you agree with this assessment?
D20 · ADR Quality0.0 / 10Critical✓ Tool-verified
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with setup.py. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d20_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).
Method: Every inline C# comment compared word by word with the identifiers, literals and constructs of the code it annotates (taken from the syntax); a comment whose words that code already contains is redundant, as are closing-brace labels and generator template text. Comments giving a reason or a reference are kept; other scripts and languages are not judged. Deterministic, exhaustive, advisory.
3 of 19 build units (Maven, Python) flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesion · ×3REDACTED:1
What to do
Resolve the 3 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with REDACTED (3). — One of this dimension's main actionable groups (3 recommendation-level).
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.
Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.
Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.
77 % of calls cross a namespace and 15 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: REDACTED scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
10 finding(s): 0 critical, 9 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
REDACTED
REDACTED
REDACTED
REDACTED
What to do
Resolve the 6 REDACTED finding(s) in Secrets (history) — start with REDACTED (4), REDACTED (2). — One of this dimension's main actionable groups (6 issue-level).
Resolve the 3 High secret finding(s) in Secrets (history) — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
Resolve the 1 REDACTED finding(s) in Secrets (history) — start with REDACTED. — 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).
105 finding(s): 0 critical, 26 high, 50 medium, 29 low. 20 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 107 file(s) — `konker.registry.api/devops/k8s/konker-registry-api-helm/templates/configmap.yaml`, `REDACTED`, `konker.registry.api/devops/k8s/konker-registry-api-helm/templates/ingress.yaml`, `konker.registry.api/devops/k8s/konker-registry-api-helm/templates/secrets.yaml`, `konker.registry.api/docker-resources/nginx/filebeat/module/apache2/access/config/access.yml`, … (+102 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 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 11 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 5 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (5). — One of this dimension's main actionable groups (5 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).
No action in Static Analysis (SAST) — all 20 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (20 issue-level, 0 of them charged here).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `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 34 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (18), REDACTED (16). — One of this dimension's main actionable groups (34 issue-level).
Resolve the 19 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (19). — One of this dimension's main actionable groups (19 issue-level).
Resolve the 13 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (7), REDACTED (6). — One of this dimension's main actionable groups (13 warning-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
Resolve the 54 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (30), REDACTED (20), REDACTED (4). — One of this dimension's main actionable groups (54 warning-level).
Resolve the 49 Low IaC finding(s) in IaC & Container Security — start with REDACTED (36), REDACTED (10), REDACTED (3). — One of this dimension's main actionable groups (49 recommendation-level).
Resolve the 40 High IaC finding(s) in IaC & Container Security — start with REDACTED (28), REDACTED (6), REDACTED (6). — One of this dimension's main actionable groups (40 issue-level).
Detailed fixes: d31_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
193 of 193 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/model/enumerations/TimeZone.java. Counted over 193 of the 512 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Most significant orphaned file · ×3konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/model/enumerations/TimeZone.java:1
Dormant codebase
What to do
Resolve the 190 Orphaned file finding(s) in Knowledge Freshness — start with migrate_beat_config_1_x_to_5_0.py (5), WebMvcConfig.java (5), OAuth2Config.java (3). — One of this dimension's main actionable groups (190 recommendation-level).
Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with TimeZone.java, DeviceRegisterServiceImpl.java, UserServiceImpl.java. — One of this dimension's main actionable groups (3 recommendation-level).
Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
Resolve the 2 Boundary-crossing change coupling finding(s) in Change Coupling — start with UserRestController.java, LocationRestController.java. — One of this dimension's main actionable groups (2 issue-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
+ 2 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 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).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether 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 1 end-of-life framework(s), read from 5 platform declaration(s) and 210 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.
End-of-life framework: Spring Boot 1REDACTED:1
What to do
Resolve the 1 End-of-life framework finding(s) in Platform End-of-Life — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d44_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
Frontend & cross-cutting dimensions
R = React/JS · M = Maturity · P = Readiness.
AC1 · Text alternatives1.4 / 10Critical✓ Tool-verified
Other · Accessibility — Whether non-text content carries a text alternative — img/area/input[type=image] have alt, a meaningful svg has a title or aria-label, video has a captions track, and object/embed/canvas have a name or fallback content. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: every img/area/input[type=image] checked for alt, svg[role=img] for a title/aria-label, video for a captions <track>. Components skipped, spreads suppressed. Deterministic, hard fact per element.
Coverage: Population: image/media elements — img, area, input[type=image], svg, video, object, embed, canvas — across the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and dynamic-attribute elements are skipped. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is NOT read by any producer, so it contributes no element to this population; where such a frontend is present the card discloses it as an analyzer gap rather than scoring around it.
An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative. (×40) — konker.registry.web/src/main/webapp/resources/konker/scripts/jquery.magnific-popup.min.js:55, konker.registry.web/src/main/webapp/resources/konker/scripts/jquery.magnific-popup.min.js:111, konker.registry.web/src/main/webapp/views/destinations/rest/form.html:91, …
What to do
Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
Do you agree with this assessment?
AC2 · Forms & labels5.0 / 10Adequate✓ Tool-verified
Other · Accessibility — Whether form controls have a programmatic label (an associated label, aria-label or aria-labelledby), buttons have text, links have an accessible name, a click handler on a plain element names the control it declares, fieldsets have a non-empty legend, known UI-library field components carry a label prop, and a placeholder isn't used as the only label. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: inputs/selects/textareas checked for an associated label[for]/wrapping label/aria-label/aria-labelledby (per document), buttons for accessible text, fieldsets for a legend; placeholder-only labelling flagged. Deterministic, hard fact per control.
Coverage: Population: form controls, buttons, links, fieldsets and known UI-library field components in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and spread/dynamic-attribute elements are skipped, so a control whose label arrives through a spread or a runtime expression is deliberately not judged. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×19) — konker.registry.web/src/main/webapp/views/destinations/rest/custom-body.html:10, konker.registry.web/src/main/webapp/views/destinations/rest/form.html:57, konker.registry.web/src/main/webapp/views/destinations/rest/form.html:67, …
A fieldset groups related controls but has no <legend> to name the group. Add a <legend> as its first child — or, if the group already has a visible caption beside it (or the fieldset is there only to disable its subtree and carries no group box), point aria-labelledby at that caption's id instead, which names the group without rendering a second one. (×10) — konker.registry.web/src/main/webapp/views/destinations/rest/form.html:13, konker.registry.web/src/main/webapp/views/destinations/rest/index.html:7, konker.registry.web/src/main/webapp/views/destinations/rest/show.html:7, …
This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label. — konker.registry.web/src/main/webapp/views/destinations/rest/form.html:76
A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one). — konker.registry.web/src/main/webapp/views/destinations/rest/form.html:126
This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id. (×9) — konker.registry.web/src/main/webapp/views/destinations/rest/form.html:141, konker.registry.web/src/main/webapp/views/destinations/rest/show.html:99, konker.registry.web/src/main/webapp/views/devices/events.html:51, …
What to do
Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
Do you agree with this assessment?
AC3 · Page structure3.2 / 10Weak✓ Tool-verified
Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.
Coverage: Population: the PARSED MARKUP documents (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx). The page-level checks — lang, title, single main landmark — fire ONCE PER FULL DOCUMENT (an <html> root) and never on a partial or component fragment, so a repo of fragments is assessed only on the per-element checks (heading order, table headers, iframe titles, meta-refresh, zoom). Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
An iframe with no title (or an empty one) is announced only as "frame". Add a non-empty title describing its content, or an aria-label. — konker.registry.web/src/main/webapp/resources/konker/scripts/jquery.magnific-popup.min.js:99
The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). (×13) — konker.registry.web/src/main/webapp/views/destinations/rest/custom-body.html:2, konker.registry.web/src/main/webapp/views/destinations/rest/empty-body.html:2, konker.registry.web/src/main/webapp/views/destinations/rest/form.html:2, …
A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>. (×12) — konker.registry.web/src/main/webapp/views/destinations/rest/custom-body.html:2, konker.registry.web/src/main/webapp/views/destinations/rest/empty-body.html:2, konker.registry.web/src/main/webapp/views/destinations/rest/form.html:2, …
No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. (×11) — konker.registry.web/src/main/webapp/views/destinations/rest/custom-body.html:2, konker.registry.web/src/main/webapp/views/destinations/rest/form.html:2, konker.registry.web/src/main/webapp/views/destinations/rest/index.html:2, …
No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div>, so there is no content here to wrap — render the <main> from the component mounted into it. — konker.registry.web/src/main/webapp/views/destinations/rest/empty-body.html:2
A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope). (×2) — konker.registry.web/src/main/webapp/views/destinations/rest/form.html:97, konker.registry.web/src/main/webapp/views/destinations/rest/show.html:63
What to do
Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
Other · Accessibility — Whether interactive behaviour is keyboard-reachable — no click handler on a non-interactive element lacking a role, tabindex and key handler, no element the repo's own CSS styles `cursor: pointer` without giving it any of the three, no unfocusable element whose only binding is a mouse enter/leave pair or a double-click, no positive tabindex, no href-less anchor, no placeholder-href (#/javascript) link acting as a button. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: click handlers on non-interactive elements lacking role+tabindex+key handler, positive tabindex values, and href-less anchors. Components skipped, spreads suppressed. Deterministic, hard fact per element.
Coverage: Population: elements that pose a keyboard-semantics question, in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) — a non-natively-interactive element carrying a click handler, a double-click or hover enter/leave binding, a pointer-only gesture on a tabindex="0" element, or `cursor: pointer` from the repo's own CSS; an href-less or placeholder-href (#, javascript:) anchor; and any element with a positive tabindex. Natively interactive elements used correctly (<button>, <a href>, form controls) are NOT in the population — there is nothing to judge — so a page of nothing but correct controls gives AC4 nothing to measure. Keyboard reachability is judged from the markup, never from a rendered page. ★ An interactive element declared in a tagged-template (html`…`) or hyperscript frontend is NOT in this population — no producer reads either — so an empty population is reported as an analyzer gap, never as "this repository has no interactive elements".
The repo's own CSS styles .password-eye with `cursor: pointer`, so this <img> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler. (×2) — konker.registry.web/src/main/webapp/views/destinations/rest/form.html:91, konker.registry.web/src/main/webapp/views/transformations/form.html:113
An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action. (×7) — konker.registry.web/src/main/webapp/views/destinations/rest/form.html:184, konker.registry.web/src/main/webapp/views/devices/events.html:188, konker.registry.web/src/main/webapp/views/devices/form.html:97, …
This <div role="dialog"> is a modal dialog, but focus is moved into it, but nothing keeps it there: Tab walks out to the page behind, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close. (×2) — konker.registry.web/src/main/webapp/views/destinations/rest/form.html:190, konker.registry.web/src/main/webapp/views/devices/form.html:103
This <div role="dialog"> is a modal dialog, but nothing moves focus into it when it opens and nothing keeps focus inside it while it is open, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close. (×5) — konker.registry.web/src/main/webapp/views/payment/checkout.html:338, konker.registry.web/src/main/webapp/views/payment/plans.html:140, konker.registry.web/src/main/webapp/views/routes/form.html:172, …
What to do
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
Other · Accessibility — Whether ARIA is used correctly — valid non-abstract roles, the ARIA state a role requires, valid (non-misspelled) aria-* attribute names, in-enum values for token-typed aria-* attributes, and no aria-hidden on (or wrapping) a focusable element. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: role values checked against the WAI-ARIA role set (abstract/invalid flagged), required ARIA state for a role, and aria-hidden on a focusable element. Deterministic, role/attribute level.
Coverage: Population: elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) that carry a role or an aria-* attribute; roles and token values are checked against the ARIA enums exhaustively within that set. An expression-valued (dynamic) role or aria-* value is skipped rather than guessed, and markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
Other · Accessibility — Whether focus outlines aren't removed without a replacement, motion respects prefers-reduced-motion, and literal CSS colour pairs meet contrast — PARTIAL: inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS literals are read (hex/rgb/hsl/named), never computed/runtime/external-CDN colour. Static markup readiness, not a WCAG conformance claim.
Method: Static markup/CSS scan: inline outline:none/0, literal inline colour/background contrast against the 4.5:1 AA floor, and <style>-block animation without a prefers-reduced-motion guard. Deterministic but PARTIAL — only inline styles and in-repo CSS literals are visible.
Coverage: Population: styled elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx), plus in-repo <style> blocks, in-repo .css files and CSS-in-JS literals. Colour contrast is computed from LITERAL colour pairs only (hex/rgb/hsl/named, including var() tokens and Tailwind neutral utilities) — computed, runtime-themed and external-CDN colour is never resolved, so this is a partial read of contrast by construction. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
`.btn-menu a:hover` sets color: #90161d on background-color: #e30613 — 1.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — konker.registry.web/src/main/webapp/resources/konker/css/create-account.css:129
`input[type="text"], input[type="password"], textarea, textarea.form-control` sets color: #888 on background-color: #f8f8f8 — 3.3:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — konker.registry.web/src/main/webapp/resources/konker/css/form-elements.css:5
`#subscribe form input` sets color: #999999 on background-color: #ffffff — 2.8:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — konker.registry.web/src/main/webapp/resources/konker/css/main.css:1387
`.subscribe-box input[type="submit"]` sets color: #fff on background-color: #4676fa — 4.0:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — konker.registry.web/src/main/webapp/resources/konker/css/main.css:1579
`body` sets color: #797979 on background-color: #f2f2f2 — 3.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — konker.registry.web/src/main/webapp/resources/konker/css/style2.css:43
`table.table thead` sets color: #fff on background-color: #2e8dac — 3.8:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — konker.registry.web/src/main/webapp/resources/konker/css/style2.css:135
`.table-hover > tbody > tr:hover td` sets color: #fff on background-color: #50c8ea — 1.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — konker.registry.web/src/main/webapp/resources/konker/css/style2.css:140
`.btn-theme:hover, .btn-theme:focus, .btn-theme:active, .btn-theme.active, .open .dropdown-toggle.btn-theme` sets color: #fff on background-color: #5986de — 3.6:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — konker.registry.web/src/main/webapp/resources/konker/css/style2.css:234
`.btn-theme02:hover, .btn-theme02:focus, .btn-theme02:active, .btn-theme02.active, .open .dropdown-toggle.btn-theme02` sets color: #fff on background-color: #967adc — 3.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — konker.registry.web/src/main/webapp/resources/konker/css/style2.css:249
`.btn-theme03:hover, .btn-theme03:focus, .btn-theme03:active, .btn-theme03.active, .open .dropdown-toggle.btn-theme03` sets color: #fff on background-color: #37bc9b — 2.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — konker.registry.web/src/main/webapp/resources/konker/css/style2.css:264
`.btn-theme04:hover, .btn-theme04:focus, .btn-theme04:active, .btn-theme04.active, .open .dropdown-toggle.btn-theme04` sets color: #fff on background-color: #da4453 — 4.3:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — konker.registry.web/src/main/webapp/resources/konker/css/style2.css:279
`ul.top-menu > li > .logout` sets color: #f2f2f2 on background-color: #68dff0 — 1.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — konker.registry.web/src/main/webapp/resources/konker/css/style2.css:372
`.profile-info.dropdown .dropdown-menu li a:hover` sets color: #FFF on background-color: #50c8ea — 1.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — konker.registry.web/src/main/webapp/resources/konker/css/style2.css:412
`ul.sidebar-menu li a.active, ul.sidebar-menu li a:hover, ul.sidebar-menu li a:focus` sets color: #fff on background-color: #68dff0 — 1.6:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — konker.registry.web/src/main/webapp/resources/konker/css/style2.css:754
`.dropdown-menu.extended li p.green` sets color: #fff on background-color: #68dff0 — 1.6:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — konker.registry.web/src/main/webapp/resources/konker/css/style2.css:924
`.dropdown-menu.extended li p.yellow` sets color: #fff on background-color: #fcb322 — 1.8:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — konker.registry.web/src/main/webapp/resources/konker/css/style2.css:929
`.ds h3` sets color: #ffffff on background-color: #ff865c — 2.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — konker.registry.web/src/main/webapp/resources/konker/css/style2.css:1192
`.has-switch span.switch-right` sets color: #ffffff on background-color: #bdc3c7 — 1.8:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — konker.registry.web/src/main/webapp/resources/konker/css/style2.css:1966
`.login-form .login-form-heading` sets color: #888 on background-color: #ececec — 3.0:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — konker.registry.web/src/main/webapp/resources/konker/css/style2.css:2031
`#failogin .alert-danger` sets color: #FFF on background-color: #f6676b — 3.0:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — konker.registry.web/src/main/webapp/resources/konker/css/style2.css:2098
`.btn-facebook:hover, .btn-facebook:focus, .btn-facebook:active, .btn-facebook.active, .open .dropdown-toggle.btn-facebook` sets color: #fff on background-color: #2775e2 — 4.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — konker.registry.web/src/main/webapp/resources/konker/css/style2.css:2152
`.btn-twitter:hover, .btn-twitter:focus, .btn-twitter:active, .btn-twitter.active, .open .dropdown-toggle.btn-twitter` sets color: #fff on background-color: #2bb4e8 — 2.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — konker.registry.web/src/main/webapp/resources/konker/css/style2.css:2167
`.btn-success` sets color: #fff on background-color: #5cb85c — 2.5:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — konker.registry.web/src/main/webapp/resources/bootstrap/css/bootstrap.css:3176
`.btn-success:focus, .btn-success.focus` sets color: #fff on background-color: #449d44 — 3.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — konker.registry.web/src/main/webapp/resources/bootstrap/css/bootstrap.css:3182
`.btn-success:hover` sets color: #fff on background-color: #449d44 — 3.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — konker.registry.web/src/main/webapp/resources/bootstrap/css/bootstrap.css:3187
`.btn-success:active, .btn-success.active, .open > .dropdown-toggle.btn-success` sets color: #fff on background-color: #449d44 — 3.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — konker.registry.web/src/main/webapp/resources/bootstrap/css/bootstrap.css:3194
`.btn-success .badge` sets color: #5cb85c on background-color: #fff — 2.5:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — konker.registry.web/src/main/webapp/resources/bootstrap/css/bootstrap.css:3229
`.btn-info:active, .btn-info.active, .open > .dropdown-toggle.btn-info` sets color: #fff on background-color: #31b0d5 — 2.5:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — konker.registry.web/src/main/webapp/resources/bootstrap/css/bootstrap.css:3251
`.btn-info:active:hover, .btn-info.active:hover, .open > .dropdown-toggle.btn-info:hover, .btn-info:active:focus, .btn-info.active:focus, .open > .dropdown-toggle.btn-info:focus, .btn-info:active.focus, .btn-info.active.focus, .open > .dropdown-toggle.btn-info.focus` sets color: #fff on background-color: #269abc — 3.3:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — konker.registry.web/src/main/webapp/resources/bootstrap/css/bootstrap.css:3264
`.btn-warning:active, .btn-warning.active, .open > .dropdown-toggle.btn-warning` sets color: #fff on background-color: #ec971f — 2.3:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — konker.registry.web/src/main/webapp/resources/bootstrap/css/bootstrap.css:3308
`.btn-warning:active:hover, .btn-warning.active:hover, .open > .dropdown-toggle.btn-warning:hover, .btn-warning:active:focus, .btn-warning.active:focus, .open > .dropdown-toggle.btn-warning:focus, .btn-warning:active.focus, .btn-warning.active.focus, .open > .dropdown-toggle.btn-warning.focus` sets color: #fff on background-color: #d58512 — 2.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — konker.registry.web/src/main/webapp/resources/bootstrap/css/bootstrap.css:3321
`a.list-group-item-success:hover, button.list-group-item-success:hover, a.list-group-item-success:focus, button.list-group-item-success:focus` sets color: #3c763d on background-color: #d0e9c6 — 4.2:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — konker.registry.web/src/main/webapp/resources/bootstrap/css/bootstrap.css:5344
`a.list-group-item-info:hover, button.list-group-item-info:hover, a.list-group-item-info:focus, button.list-group-item-info:focus` sets color: #31708f on background-color: #c4e3f3 — 4.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — konker.registry.web/src/main/webapp/resources/bootstrap/css/bootstrap.css:5373
`a.list-group-item-warning:hover, button.list-group-item-warning:hover, a.list-group-item-warning:focus, button.list-group-item-warning:focus` sets color: #8a6d3b on background-color: #faf2cc — 4.3:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — konker.registry.web/src/main/webapp/resources/bootstrap/css/bootstrap.css:5402
`a.list-group-item-danger:hover, button.list-group-item-danger:hover, a.list-group-item-danger:focus, button.list-group-item-danger:focus` sets color: #a94442 on background-color: #ebcccc — 3.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — konker.registry.web/src/main/webapp/resources/bootstrap/css/bootstrap.css:5431
`.btn:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — konker.registry.web/src/main/webapp/resources/konker/css/main.css:46
`.sup-desc-wrap .sup-meta-wrap .sup-title` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — konker.registry.web/src/main/webapp/resources/konker/css/main.css:875
`.form-control:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — konker.registry.web/src/main/webapp/resources/konker/css/main.css:1351
`.subscribe-box input[type="text"]` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — konker.registry.web/src/main/webapp/resources/konker/css/main.css:1576
`.btn-link-1:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — konker.registry.web/src/main/webapp/resources/konker/css/style.css:53
What to do
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
Other · Architecture — Whether any singleton service captures a scoped/transient dependency — a silent lifetime/threading bug.
Method: Roslyn scan: DI registrations parsed from AddSingleton/Scoped/Transient; each singleton checked for captured shorter-lifetime dependencies. Exhaustive, deterministic.
`FormWebSecurityConfig` is a Spring singleton (the default scope) and is injected `LoginAuditService loginAuditService`, whose bean `LoginAuditServiceImpl` is scoped prototype without a scoped proxy (konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/LoginAuditServiceImpl.java:24). The singleton is given ONE instance, once, and keeps it for the life of the application context — the fresh instance per use that the prototype scope promises never happens, and any state it carries is shared by every caller on every thread. Inject `ObjectProvider<LoginAuditServiceImpl>` and call getObject() per use, or declare the scope with proxyMode = ScopedProxyMode.TARGET_CLASS. — REDACTED:54
`AlertTriggerServiceImpl` is a Spring singleton (the default scope) and is injected `HealthAlertService healthAlertService`, whose bean `HealthAlertServiceImpl` is scoped prototype without a scoped proxy (konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/HealthAlertServiceImpl.java:24). The singleton is given ONE instance, once, and keeps it for the life of the application context — the fresh instance per use that the prototype scope promises never happens, and any state it carries is shared by every caller on every thread. Inject `ObjectProvider<HealthAlertServiceImpl>` and call getObject() per use, or declare the scope with proxyMode = ScopedProxyMode.TARGET_CLASS. — konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/AlertTriggerServiceImpl.java:20
`TenantServiceImpl` is a Spring singleton (the default scope) and is injected `ApplicationService applicationService`, whose bean `ApplicationServiceImpl` is scoped prototype without a scoped proxy (konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/ApplicationServiceImpl.java:27). The singleton is given ONE instance, once, and keeps it for the life of the application context — the fresh instance per use that the prototype scope promises never happens, and any state it carries is shared by every caller on every thread. Inject `ObjectProvider<ApplicationServiceImpl>` and call getObject() per use, or declare the scope with proxyMode = ScopedProxyMode.TARGET_CLASS. — konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/TenantServiceImpl.java:40
`UserServiceImpl` is a Spring singleton (the default scope) and is injected `ApplicationService applicationService`, whose bean `ApplicationServiceImpl` is scoped prototype without a scoped proxy (konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/ApplicationServiceImpl.java:27). The singleton is given ONE instance, once, and keeps it for the life of the application context — the fresh instance per use that the prototype scope promises never happens, and any state it carries is shared by every caller on every thread. Inject `ObjectProvider<ApplicationServiceImpl>` and call getObject() per use, or declare the scope with proxyMode = ScopedProxyMode.TARGET_CLASS. — konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/UserServiceImpl.java:50
`UserServiceImpl` is a Spring singleton (the default scope) and is injected `LocationSearchService locationSearchService`, whose bean `LocationSearchServiceImpl` is scoped prototype without a scoped proxy (konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/LocationSearchServiceImpl.java:27). The singleton is given ONE instance, once, and keeps it for the life of the application context — the fresh instance per use that the prototype scope promises never happens, and any state it carries is shared by every caller on every thread. Inject `ObjectProvider<LocationSearchServiceImpl>` and call getObject() per use, or declare the scope with proxyMode = ScopedProxyMode.TARGET_CLASS. — konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/UserServiceImpl.java:53
`UserServiceImpl` is a Spring singleton (the default scope) and is injected `EmailService emailService`, whose bean `EmailServiceImpl` is scoped prototype without a scoped proxy (konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/EmailServiceImpl.java:34). The singleton is given ONE instance, once, and keeps it for the life of the application context — the fresh instance per use that the prototype scope promises never happens, and any state it carries is shared by every caller on every thread. Inject `ObjectProvider<EmailServiceImpl>` and call getObject() per use, or declare the scope with proxyMode = ScopedProxyMode.TARGET_CLASS. — konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/UserServiceImpl.java:62
`RabbitEventQueue` is a Spring singleton (the default scope) and is injected `DeviceRegisterService deviceRegisterService`, whose bean `DeviceRegisterServiceImpl` is scoped prototype without a scoped proxy (konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceRegisterServiceImpl.java:37). The singleton is given ONE instance, once, and keeps it for the life of the application context — the fresh instance per use that the prototype scope promises never happens, and any state it carries is shared by every caller on every thread. Inject `ObjectProvider<DeviceRegisterServiceImpl>` and call getObject() per use, or declare the scope with proxyMode = ScopedProxyMode.TARGET_CLASS. — REDACTED:35
`RabbitEventQueue` is a Spring singleton (the default scope) and is injected `EventRouteService eventRouteService`, whose bean `EventRouteServiceImpl` is scoped prototype without a scoped proxy (konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/EventRouteServiceImpl.java:43). The singleton is given ONE instance, once, and keeps it for the life of the application context — the fresh instance per use that the prototype scope promises never happens, and any state it carries is shared by every caller on every thread. Inject `ObjectProvider<EventRouteServiceImpl>` and call getObject() per use, or declare the scope with proxyMode = ScopedProxyMode.TARGET_CLASS. — REDACTED:38
`ApplicationEventRestEndpoint` is a Spring singleton (the default scope) and is injected `DeviceEventProcessor deviceEventProcessor`, whose bean `DeviceEventProcessor` is scoped prototype without a scoped proxy (konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/integration/processors/DeviceEventProcessor.java:32). The singleton is given ONE instance, once, and keeps it for the life of the application context — the fresh instance per use that the prototype scope promises never happens, and any state it carries is shared by every caller on every thread. Inject `ObjectProvider<DeviceEventProcessor>` and call getObject() per use, or declare the scope with proxyMode = ScopedProxyMode.TARGET_CLASS. — konker.registry.data.processor/src/main/java/com/konkerlabs/platform/registry/integration/endpoints/ApplicationEventRestEndpoint.java:63
`ApplicationEventRestEndpoint` is a Spring singleton (the default scope) and is injected `ApplicationService applicationService`, whose bean `ApplicationServiceImpl` is scoped prototype without a scoped proxy (konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/ApplicationServiceImpl.java:27). The singleton is given ONE instance, once, and keeps it for the life of the application context — the fresh instance per use that the prototype scope promises never happens, and any state it carries is shared by every caller on every thread. Inject `ObjectProvider<ApplicationServiceImpl>` and call getObject() per use, or declare the scope with proxyMode = ScopedProxyMode.TARGET_CLASS. — konker.registry.data.processor/src/main/java/com/konkerlabs/platform/registry/integration/endpoints/ApplicationEventRestEndpoint.java:66
`DeviceConfigRabbitEndpoint` is a Spring singleton (the default scope) and is injected `DeviceConfigSetupService deviceConfigSetupService`, whose bean `DeviceConfigSetupServiceImpl` is scoped prototype without a scoped proxy (konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceConfigSetupServiceImpl.java:36). The singleton is given ONE instance, once, and keeps it for the life of the application context — the fresh instance per use that the prototype scope promises never happens, and any state it carries is shared by every caller on every thread. Inject `ObjectProvider<DeviceConfigSetupServiceImpl>` and call getObject() per use, or declare the scope with proxyMode = ScopedProxyMode.TARGET_CLASS. — konker.registry.data.processor/src/main/java/com/konkerlabs/platform/registry/integration/endpoints/DeviceConfigRabbitEndpoint.java:29
`DeviceConfigRabbitEndpoint` is a Spring singleton (the default scope) and is injected `DeviceRegisterService deviceRegisterService`, whose bean `DeviceRegisterServiceImpl` is scoped prototype without a scoped proxy (konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceRegisterServiceImpl.java:37). The singleton is given ONE instance, once, and keeps it for the life of the application context — the fresh instance per use that the prototype scope promises never happens, and any state it carries is shared by every caller on every thread. Inject `ObjectProvider<DeviceRegisterServiceImpl>` and call getObject() per use, or declare the scope with proxyMode = ScopedProxyMode.TARGET_CLASS. — konker.registry.data.processor/src/main/java/com/konkerlabs/platform/registry/integration/endpoints/DeviceConfigRabbitEndpoint.java:32
`DeviceEventRabbitEndpoint` is a Spring singleton (the default scope) and is injected `DeviceEventProcessor deviceEventProcessor`, whose bean `DeviceEventProcessor` is scoped prototype without a scoped proxy (konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/integration/processors/DeviceEventProcessor.java:32). The singleton is given ONE instance, once, and keeps it for the life of the application context — the fresh instance per use that the prototype scope promises never happens, and any state it carries is shared by every caller on every thread. Inject `ObjectProvider<DeviceEventProcessor>` and call getObject() per use, or declare the scope with proxyMode = ScopedProxyMode.TARGET_CLASS. — konker.registry.data.processor/src/main/java/com/konkerlabs/platform/registry/integration/endpoints/DeviceEventRabbitEndpoint.java:26
`JedisTaskService` is a Spring singleton (the default scope) and is injected `DeviceEventService deviceEventService`, whose bean `DeviceEventServiceImpl` is scoped prototype without a scoped proxy (konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceEventServiceImpl.java:25). The singleton is given ONE instance, once, and keeps it for the life of the application context — the fresh instance per use that the prototype scope promises never happens, and any state it carries is shared by every caller on every thread. Inject `ObjectProvider<DeviceEventServiceImpl>` and call getObject() per use, or declare the scope with proxyMode = ScopedProxyMode.TARGET_CLASS. — konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/services/JedisTaskService.java:30
`JedisTaskService` is a Spring singleton (the default scope) and is injected `DeviceRegisterService deviceRegisterService`, whose bean `DeviceRegisterServiceImpl` is scoped prototype without a scoped proxy (konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceRegisterServiceImpl.java:37). The singleton is given ONE instance, once, and keeps it for the life of the application context — the fresh instance per use that the prototype scope promises never happens, and any state it carries is shared by every caller on every thread. Inject `ObjectProvider<DeviceRegisterServiceImpl>` and call getObject() per use, or declare the scope with proxyMode = ScopedProxyMode.TARGET_CLASS. — konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/services/JedisTaskService.java:33
`EventRouteExecutorImpl` is a Spring singleton (the default scope) and is injected `EventRouteService eventRouteService`, whose bean `EventRouteServiceImpl` is scoped prototype without a scoped proxy (konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/EventRouteServiceImpl.java:43). The singleton is given ONE instance, once, and keeps it for the life of the application context — the fresh instance per use that the prototype scope promises never happens, and any state it carries is shared by every caller on every thread. Inject `ObjectProvider<EventRouteServiceImpl>` and call getObject() per use, or declare the scope with proxyMode = ScopedProxyMode.TARGET_CLASS. — konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/services/routes/EventRouteExecutorImpl.java:38
`EventRouteExecutorImpl` is a Spring singleton (the default scope) and is injected `ExpressionEvaluationService evaluationService`, whose bean `ExpressionEvaluationServiceImpl` is scoped prototype without a scoped proxy (konker.utilities/src/main/java/com/konkerlabs/platform/utilities/expressions/ExpressionEvaluationServiceImpl.java:23). The singleton is given ONE instance, once, and keeps it for the life of the application context — the fresh instance per use that the prototype scope promises never happens, and any state it carries is shared by every caller on every thread. Inject `ObjectProvider<ExpressionEvaluationServiceImpl>` and call getObject() per use, or declare the scope with proxyMode = ScopedProxyMode.TARGET_CLASS. — konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/services/routes/EventRouteExecutorImpl.java:42
`EventRouteExecutorImpl` is a Spring singleton (the default scope) and is injected `LocationSearchService locationSearchService`, whose bean `LocationSearchServiceImpl` is scoped prototype without a scoped proxy (konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/LocationSearchServiceImpl.java:27). The singleton is given ONE instance, once, and keeps it for the life of the application context — the fresh instance per use that the prototype scope promises never happens, and any state it carries is shared by every caller on every thread. Inject `ObjectProvider<LocationSearchServiceImpl>` and call getObject() per use, or declare the scope with proxyMode = ScopedProxyMode.TARGET_CLASS. — konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/services/routes/EventRouteExecutorImpl.java:48
`EventRouteExecutorImpl` is a Spring singleton (the default scope) and is injected `EventRouteCounterService eventRouteCounterService`, whose bean `EventRouteCounterServiceImpl` is scoped prototype without a scoped proxy (konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/EventRouteCounterServiceImpl.java:28). The singleton is given ONE instance, once, and keeps it for the life of the application context — the fresh instance per use that the prototype scope promises never happens, and any state it carries is shared by every caller on every thread. Inject `ObjectProvider<EventRouteCounterServiceImpl>` and call getObject() per use, or declare the scope with proxyMode = ScopedProxyMode.TARGET_CLASS. — konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/services/routes/EventRouteExecutorImpl.java:54
`EventTransformationServiceImpl` is a Spring singleton (the default scope) and is injected `ExpressionEvaluationService evaluationService`, whose bean `ExpressionEvaluationServiceImpl` is scoped prototype without a scoped proxy (konker.utilities/src/main/java/com/konkerlabs/platform/utilities/expressions/ExpressionEvaluationServiceImpl.java:23). The singleton is given ONE instance, once, and keeps it for the life of the application context — the fresh instance per use that the prototype scope promises never happens, and any state it carries is shared by every caller on every thread. Inject `ObjectProvider<ExpressionEvaluationServiceImpl>` and call getObject() per use, or declare the scope with proxyMode = ScopedProxyMode.TARGET_CLASS. — konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/services/routes/EventTransformationServiceImpl.java:37
`EventPublisherDevice` is a Spring singleton (the default scope) and is injected `DeviceRegisterService deviceRegisterService`, whose bean `DeviceRegisterServiceImpl` is scoped prototype without a scoped proxy (konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceRegisterServiceImpl.java:37). The singleton is given ONE instance, once, and keeps it for the life of the application context — the fresh instance per use that the prototype scope promises never happens, and any state it carries is shared by every caller on every thread. Inject `ObjectProvider<DeviceRegisterServiceImpl>` and call getObject() per use, or declare the scope with proxyMode = ScopedProxyMode.TARGET_CLASS. — konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/services/publishers/EventPublisherDevice.java:42
`EventPublisherRest` is a Spring singleton (the default scope) and is injected `RestDestinationService restDestinationService`, whose bean `RestDestinationServiceImpl` is scoped prototype without a scoped proxy (konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/RestDestinationServiceImpl.java:33). The singleton is given ONE instance, once, and keeps it for the life of the application context — the fresh instance per use that the prototype scope promises never happens, and any state it carries is shared by every caller on every thread. Inject `ObjectProvider<RestDestinationServiceImpl>` and call getObject() per use, or declare the scope with proxyMode = ScopedProxyMode.TARGET_CLASS. — konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/services/publishers/EventPublisherRest.java:47
`EventPublisherRest` is a Spring singleton (the default scope) and is injected `ExpressionEvaluationService expressionEvaluationService`, whose bean `ExpressionEvaluationServiceImpl` is scoped prototype without a scoped proxy (konker.utilities/src/main/java/com/konkerlabs/platform/utilities/expressions/ExpressionEvaluationServiceImpl.java:23). The singleton is given ONE instance, once, and keeps it for the life of the application context — the fresh instance per use that the prototype scope promises never happens, and any state it carries is shared by every caller on every thread. Inject `ObjectProvider<ExpressionEvaluationServiceImpl>` and call getObject() per use, or declare the scope with proxyMode = ScopedProxyMode.TARGET_CLASS. — konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/services/publishers/EventPublisherRest.java:49
`SecurityConfig` is a Spring singleton (the default scope) and is injected `DeviceRegisterService deviceRegisterService`, whose bean `DeviceRegisterServiceImpl` is scoped prototype without a scoped proxy (konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceRegisterServiceImpl.java:37). The singleton is given ONE instance, once, and keeps it for the life of the application context — the fresh instance per use that the prototype scope promises never happens, and any state it carries is shared by every caller on every thread. Inject `ObjectProvider<DeviceRegisterServiceImpl>` and call getObject() per use, or declare the scope with proxyMode = ScopedProxyMode.TARGET_CLASS. — REDACTED:59
`DeviceEventRestEndpoint` is a Spring singleton (the default scope) and is injected `DeviceEventProcessor deviceEventProcessor`, whose bean `DeviceEventProcessor` is scoped prototype without a scoped proxy (konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/integration/processors/DeviceEventProcessor.java:32). The singleton is given ONE instance, once, and keeps it for the life of the application context — the fresh instance per use that the prototype scope promises never happens, and any state it carries is shared by every caller on every thread. Inject `ObjectProvider<DeviceEventProcessor>` and call getObject() per use, or declare the scope with proxyMode = ScopedProxyMode.TARGET_CLASS. — konker.registry.data/src/main/java/com/konkerlabs/platform/registry/integration/endpoints/DeviceEventRestEndpoint.java:87
`DeviceEventRestEndpoint` is a Spring singleton (the default scope) and is injected `DeviceEventService deviceEventService`, whose bean `DeviceEventServiceImpl` is scoped prototype without a scoped proxy (konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceEventServiceImpl.java:25). The singleton is given ONE instance, once, and keeps it for the life of the application context — the fresh instance per use that the prototype scope promises never happens, and any state it carries is shared by every caller on every thread. Inject `ObjectProvider<DeviceEventServiceImpl>` and call getObject() per use, or declare the scope with proxyMode = ScopedProxyMode.TARGET_CLASS. — konker.registry.data/src/main/java/com/konkerlabs/platform/registry/integration/endpoints/DeviceEventRestEndpoint.java:89
`DeviceEventRestEndpoint` is a Spring singleton (the default scope) and is injected `DeviceRegisterService deviceRegisterService`, whose bean `DeviceRegisterServiceImpl` is scoped prototype without a scoped proxy (konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceRegisterServiceImpl.java:37). The singleton is given ONE instance, once, and keeps it for the life of the application context — the fresh instance per use that the prototype scope promises never happens, and any state it carries is shared by every caller on every thread. Inject `ObjectProvider<DeviceRegisterServiceImpl>` and call getObject() per use, or declare the scope with proxyMode = ScopedProxyMode.TARGET_CLASS. — konker.registry.data/src/main/java/com/konkerlabs/platform/registry/integration/endpoints/DeviceEventRestEndpoint.java:90
`DeviceEventRestEndpoint` is a Spring singleton (the default scope) and is injected `DeviceFirmwareUpdateService deviceFirmwareUpdateService`, whose bean `DeviceFirmwareUpdateServiceImpl` is scoped prototype without a scoped proxy (konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceFirmwareUpdateServiceImpl.java:24). The singleton is given ONE instance, once, and keeps it for the life of the application context — the fresh instance per use that the prototype scope promises never happens, and any state it carries is shared by every caller on every thread. Inject `ObjectProvider<DeviceFirmwareUpdateServiceImpl>` and call getObject() per use, or declare the scope with proxyMode = ScopedProxyMode.TARGET_CLASS. — konker.registry.data/src/main/java/com/konkerlabs/platform/registry/integration/endpoints/DeviceEventRestEndpoint.java:91
`DeviceEventRestEndpoint` is a Spring singleton (the default scope) and is injected `DeviceConfigSetupService deviceConfigSetupService`, whose bean `DeviceConfigSetupServiceImpl` is scoped prototype without a scoped proxy (konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceConfigSetupServiceImpl.java:36). The singleton is given ONE instance, once, and keeps it for the life of the application context — the fresh instance per use that the prototype scope promises never happens, and any state it carries is shared by every caller on every thread. Inject `ObjectProvider<DeviceConfigSetupServiceImpl>` and call getObject() per use, or declare the scope with proxyMode = ScopedProxyMode.TARGET_CLASS. — konker.registry.data/src/main/java/com/konkerlabs/platform/registry/integration/endpoints/DeviceEventRestEndpoint.java:94
`DeviceUploadRestEndpoint` is a Spring singleton (the default scope) and is injected `DeviceEventProcessor deviceEventProcessor`, whose bean `DeviceEventProcessor` is scoped prototype without a scoped proxy (konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/integration/processors/DeviceEventProcessor.java:32). The singleton is given ONE instance, once, and keeps it for the life of the application context — the fresh instance per use that the prototype scope promises never happens, and any state it carries is shared by every caller on every thread. Inject `ObjectProvider<DeviceEventProcessor>` and call getObject() per use, or declare the scope with proxyMode = ScopedProxyMode.TARGET_CLASS. — konker.registry.data/src/main/java/com/konkerlabs/platform/registry/integration/endpoints/DeviceUploadRestEndpoint.java:65
`GatewayEventRestEndpoint` is a Spring singleton (the default scope) and is injected `GatewayEventProcessor gatewayEventProcessor`, whose bean `GatewayEventProcessor` is scoped prototype without a scoped proxy (konker.registry.data/src/main/java/com/konkerlabs/platform/registry/integration/processors/GatewayEventProcessor.java:28). The singleton is given ONE instance, once, and keeps it for the life of the application context — the fresh instance per use that the prototype scope promises never happens, and any state it carries is shared by every caller on every thread. Inject `ObjectProvider<GatewayEventProcessor>` and call getObject() per use, or declare the scope with proxyMode = ScopedProxyMode.TARGET_CLASS. — konker.registry.data/src/main/java/com/konkerlabs/platform/registry/integration/endpoints/GatewayEventRestEndpoint.java:81
`GatewayEventRestEndpoint` is a Spring singleton (the default scope) and is injected `DeviceRegisterService deviceRegisterService`, whose bean `DeviceRegisterServiceImpl` is scoped prototype without a scoped proxy (konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceRegisterServiceImpl.java:37). The singleton is given ONE instance, once, and keeps it for the life of the application context — the fresh instance per use that the prototype scope promises never happens, and any state it carries is shared by every caller on every thread. Inject `ObjectProvider<DeviceRegisterServiceImpl>` and call getObject() per use, or declare the scope with proxyMode = ScopedProxyMode.TARGET_CLASS. — konker.registry.data/src/main/java/com/konkerlabs/platform/registry/integration/endpoints/GatewayEventRestEndpoint.java:83
`GatewayEventRestEndpoint` is a Spring singleton (the default scope) and is injected `DeviceEventService deviceEventService`, whose bean `DeviceEventServiceImpl` is scoped prototype without a scoped proxy (konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceEventServiceImpl.java:25). The singleton is given ONE instance, once, and keeps it for the life of the application context — the fresh instance per use that the prototype scope promises never happens, and any state it carries is shared by every caller on every thread. Inject `ObjectProvider<DeviceEventServiceImpl>` and call getObject() per use, or declare the scope with proxyMode = ScopedProxyMode.TARGET_CLASS. — konker.registry.data/src/main/java/com/konkerlabs/platform/registry/integration/endpoints/GatewayEventRestEndpoint.java:87
What to do
Spring: don't inject prototype, request or session beans into a singleton directly — inject ObjectProvider<T> (or a Provider<T>, or an @Lookup method) and resolve per use, or declare the shorter scope with proxyMode = ScopedProxyMode.TARGET_CLASS so the singleton holds a proxy.
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 singleton services avoid mutable shared instance state that concurrent callers would race on.
Method: Roslyn scan: singleton field mutations unguarded by lock or Interlocked, per type; syntax-based guard detection. Deterministic, traceable per field.
`EventRepositoryCassandraEtlImpl` is a singleton (@Repository: the container shares one instance across every request thread) but mutates instance state outside any lock (insertIncomingMap; e.g. `insertIncomingMap` in `getInsertIncomingPreparedStatement` at line 63). — konker.registry.cassandra-etl/src/main/java/org/konker/registry/cassandraetl/repositories/EventRepositoryCassandraEtlImpl.java:25
`EqualizeCassandraTablesService` is a singleton (@Service: the container shares one instance across every request thread) but mutates instance state outside any lock (maxSize; e.g. `maxSize` in `process` at line 74). — konker.registry.cassandra-etl/src/main/java/org/konker/registry/cassandraetl/services/EqualizeCassandraTablesService.java:28
`HttpGatewayImpl` is a singleton (@Component: the container shares one instance across every request thread) but mutates instance state outside any lock (defaultHeaders; e.g. `defaultHeaders` in `setUp` at line 98). — konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/integration/gateway/HttpGatewayImpl.java:22
`JedisTaskService` is a singleton (@Service: the container shares one instance across every request thread) but mutates instance state outside any lock (response; e.g. `response` in `subscribeToChannel` at line 43). — konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/services/JedisTaskService.java:22
`UserServiceImpl` is a singleton (@Service: the container shares one instance across every request thread) but mutates instance state outside any lock (passwordManager; e.g. `passwordManager` in `encodePassword` at line 581). — konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/UserServiceImpl.java:35
`EventRepositoryCassandraImpl` is a singleton (@Repository: the container shares one instance across every request thread) but mutates instance state outside any lock (selectStatementCache, insertIncomingMap, insertOutgoingMap; e.g. `selectStatementCache` in `doFindBy` at line 265). — konker.registry.services.storage.cassandra/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/EventRepositoryCassandraImpl.java:34
What to do
Java/Kotlin: keep container singletons stateless — move per-request data into locals or a request-scoped bean — or back the state with java.util.concurrent types (ConcurrentHashMap, AtomicInteger/AtomicReference), guard it with synchronized / a Lock (Kotlin: withLock), or mark a flag that is only ever overwritten volatile (@Volatile).
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.
Other · Code Health — Unreviewed-generation residue in this repository's Java: methods whose whole body only throws a "not implemented" or bare unsupported-operation exception, or returns a default value (or nothing) under a TODO/FIXME marker, 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 Java: methods that only throw a "not implemented" exception, 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.
Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
What to do
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.
Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.
Readiness · Readiness — Whether an automated pipeline builds and tests every change.
Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.
Do you agree with this assessment?
P10 · Library API & versioning9.3 / 10Exemplary✓ Tool-verified
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.
1 public type in `org.konker.registry.cassandraetl.repositories` is marked as implementation by its own namespace, folder or name: `EventRepositoryCassandraEtlImpl` (konker.registry.cassandra-etl/src/main/java/org/konker/registry/cassandraetl/repositories/EventRepositoryCassandraEtlImpl.java:25, name ends in `Impl`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers. — konker.registry.cassandra-etl/src/main/java/org/konker/registry/cassandraetl/repositories/EventRepositoryCassandraEtlImpl.java:25
1 public type in `com.konkerlabs.platform.registry.data.core.integration.gateway` is marked as implementation by its own namespace, folder or name: `HttpGatewayImpl` (konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/integration/gateway/HttpGatewayImpl.java:22, name ends in `Impl`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers. — konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/integration/gateway/HttpGatewayImpl.java:22
1 public type in `com.konkerlabs.platform.registry.data.core.services` is marked as implementation by its own namespace, folder or name: `DeviceLogEventServiceImpl` (konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/services/DeviceLogEventServiceImpl.java:41, name ends in `Impl`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers. — konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/services/DeviceLogEventServiceImpl.java:41
2 public types in `com.konkerlabs.platform.registry.data.core.services.routes` are marked as implementation by their own namespace, folder or name: `EventRouteExecutorImpl` (konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/services/routes/EventRouteExecutorImpl.java:33, name ends in `Impl`), `EventTransformationServiceImpl` (konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/services/routes/EventTransformationServiceImpl.java:30, name ends in `Impl`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/services/routes/EventRouteExecutorImpl.java:33
1 public type in `com.konkerlabs.platform.registry.business.repositories.events.api` is marked as implementation by its own namespace, folder or name: `BaseEventRepositoryImpl` (konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/api/BaseEventRepositoryImpl.java:15, name ends in `Impl`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers. — konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/api/BaseEventRepositoryImpl.java:15
28 public types in `com.konkerlabs.platform.registry.business.services` are marked as implementation by their own namespace, folder or name: `AlertTriggerServiceImpl` (konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/AlertTriggerServiceImpl.java:14, name ends in `Impl`), `ApplicationDocumentStoreServiceImpl` (konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/ApplicationDocumentStoreServiceImpl.java:27, name ends in `Impl`), `ApplicationServiceImpl` (konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/ApplicationServiceImpl.java:27, name ends in `Impl`), `DeviceConfigSetupServiceImpl` (konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceConfigSetupServiceImpl.java:36, name ends in `Impl`), `DeviceCustomDataServiceImpl` (konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceCustomDataServiceImpl.java:30, name ends in `Impl`), `DeviceEventServiceImpl` (konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceEventServiceImpl.java:25, name ends in `Impl`), `DeviceFirmwareServiceImpl` (konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceFirmwareServiceImpl.java:32, name ends in `Impl`), `DeviceFirmwareUpdateServiceImpl` (konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceFirmwareUpdateServiceImpl.java:24, name ends in `Impl`), and 20 more. While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/AlertTriggerServiceImpl.java:14
1 public type in `com.konkerlabs.platform.registry.business.services.api` is marked as implementation by its own namespace, folder or name: `UserNotificationServiceImpl` (konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/api/UserNotificationServiceImpl.java:29, name ends in `Impl`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers. — konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/api/UserNotificationServiceImpl.java:29
2 public types in `com.konkerlabs.platform.registry.business.repositories.events` are marked as implementation by their own namespace, folder or name: `EventRepositoryCassandraImpl` (konker.registry.services.storage.cassandra/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/EventRepositoryCassandraImpl.java:34, name ends in `Impl`), `EventRepositoryMongoImpl` (konker.registry.services.storage.mongodb/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/EventRepositoryMongoImpl.java:34, name ends in `Impl`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — konker.registry.services.storage.cassandra/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/EventRepositoryCassandraImpl.java:34
3 public types in `com.konkerlabs.platform.registry.web.services` are marked as implementation by their own namespace, folder or name: `AvatarServiceImpl` (konker.registry.web/src/main/java/com/konkerlabs/platform/registry/web/services/AvatarServiceImpl.java:32, name ends in `Impl`), `CaptchaServiceImpl` (konker.registry.web/src/main/java/com/konkerlabs/platform/registry/web/services/CaptchaServiceImpl.java:23, name ends in `Impl`), `UploadServiceImpl` (konker.registry.web/src/main/java/com/konkerlabs/platform/registry/web/services/UploadServiceImpl.java:19, name ends in `Impl`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — konker.registry.web/src/main/java/com/konkerlabs/platform/registry/web/services/AvatarServiceImpl.java:32
1 public type in `com.konkerlabs.platform.utilities.expressions` is marked as implementation by its own namespace, folder or name: `ExpressionEvaluationServiceImpl` (konker.utilities/src/main/java/com/konkerlabs/platform/utilities/expressions/ExpressionEvaluationServiceImpl.java:23, name ends in `Impl`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers. — konker.utilities/src/main/java/com/konkerlabs/platform/utilities/expressions/ExpressionEvaluationServiceImpl.java:23
1 public type in `com.konkerlabs.platform.utilities.parsers.json` is marked as implementation by its own namespace, folder or name: `JsonParsingServiceImpl` (konker.utilities/src/main/java/com/konkerlabs/platform/utilities/parsers/json/JsonParsingServiceImpl.java:23, name ends in `Impl`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers. — konker.utilities/src/main/java/com/konkerlabs/platform/utilities/parsers/json/JsonParsingServiceImpl.java:23
What to do
Hide `org.konker.registry.cassandraetl.repositories` (`EventRepositoryCassandraEtlImpl`) (Java: package-private (no modifier), or leave its package out of `module-info` exports): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
Hide `com.konkerlabs.platform.registry.data.core.integration.gateway` (`HttpGatewayImpl`) (Java: package-private (no modifier), or leave its package out of `module-info` exports): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
Hide `com.konkerlabs.platform.registry.data.core.services` (`DeviceLogEventServiceImpl`) (Java: package-private (no modifier), or leave its package out of `module-info` exports): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
Hide `com.konkerlabs.platform.registry.data.core.services.routes` (`EventRouteExecutorImpl`, `EventTransformationServiceImpl`) (Java: package-private (no modifier), or leave its package out of `module-info` exports): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
Hide `com.konkerlabs.platform.registry.business.repositories.events.api` (`BaseEventRepositoryImpl`) (Java: package-private (no modifier), or leave its package out of `module-info` exports): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
Hide `com.konkerlabs.platform.registry.business.services` (`AlertTriggerServiceImpl`, `ApplicationDocumentStoreServiceImpl`, `ApplicationServiceImpl`, `DeviceConfigSetupServiceImpl`, `DeviceCustomDataServiceImpl`, `DeviceEventServiceImpl`, `DeviceFirmwareServiceImpl`, `DeviceFirmwareUpdateServiceImpl`, and 20 more) (Java: package-private (no modifier), or leave its package out of `module-info` exports): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
Hide `com.konkerlabs.platform.registry.business.services.api` (`UserNotificationServiceImpl`) (Java: package-private (no modifier), or leave its package out of `module-info` exports): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
Hide `com.konkerlabs.platform.registry.business.repositories.events` (`EventRepositoryCassandraImpl`, `EventRepositoryMongoImpl`) (Java: package-private (no modifier), or leave its package out of `module-info` exports): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
Hide `com.konkerlabs.platform.registry.web.services` (`AvatarServiceImpl`, `CaptchaServiceImpl`, `UploadServiceImpl`) (Java: package-private (no modifier), or leave its package out of `module-info` exports): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
Hide `com.konkerlabs.platform.utilities.expressions` (`ExpressionEvaluationServiceImpl`) (Java: package-private (no modifier), or leave its package out of `module-info` exports): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
Hide `com.konkerlabs.platform.utilities.parsers.json` (`JsonParsingServiceImpl`) (Java: package-private (no modifier), or leave its package out of `module-info` exports): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
Only 12/15 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `konker.samples/rest-json-enrichment`, `konker.samples/rest-json-transformation`, `konker.samples/smart-temperature`.
What to do
Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
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.
No static application security testing detected. For this repository's stack, add spotbugs with find-sec-bugs (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 1 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
`REDACTED` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — REDACTED:37
What to do
Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.
Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.
No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
Readiness · Readiness — Whether outbound HTTP calls are wrapped in resilience (retry/timeout/circuit-breaker) so a failing dependency doesn't cascade.
Method: Source scan: outbound HTTP clients and what bounds them — resilience handlers (Polly, AddStandardResilienceHandler) on .NET; on Go, the JVM, Python, JavaScript/TypeScript, Ruby, PHP, Rust, Elixir, Swift, Dart and Erlang, a timeout, deadline, retry or breaker beside each call, or a process-wide client default (a framework-wide deadline such as Drupal core's, Laravel's or actix's awc counts). Exhaustive, deterministic.
`new RestTemplate(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. (×4) — konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/config/RestTemplateConfig.java:14, konker.registry.cassandra-etl/src/main/java/org/konker/registry/cassandraetl/config/RestTemplateEtlConfig.java:12, konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/config/IntegrationConfig.java:40, …
`.openConnection(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. — konker.registry.web/src/main/java/com/konkerlabs/platform/registry/web/services/CaptchaRestClient.java:25
`requests.get(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. — REDACTED:14
`requests.post(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. — REDACTED:16
`requests.put(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. — REDACTED:18
What to do
Set connect and read timeouts on every client (`RestTemplateBuilder.connectTimeout/readTimeout`, WebClient `responseTimeout`, `HttpRequest.Builder.timeout`, `HttpURLConnection.setReadTimeout`, Feign `connectTimeout`/`readTimeout` in configuration), and wrap calls to dependencies in resilience4j `@Retry`/`@CircuitBreaker`/`@TimeLimiter` (or Spring Retry).
Pass `timeout=` on every `requests`/`httpx` call (requests has no default and will wait forever), mount an `HTTPAdapter(max_retries=Retry(...))` on shared sessions, and wrap calls to flaky dependencies in `tenacity` retries or a `pybreaker` circuit breaker.
Do you agree with this assessment?
R1 · Type Safety0.0 / 10Critical✓ Tool-verified
React / JS · Code Health — How much of the frontend is typed TypeScript vs untyped JavaScript.
Method: Frontend file inventory: the share of typed TypeScript vs untyped JavaScript across the source tree. Deterministic, exhaustive over frontend files.
0 typed · 30 plain JS — the untyped files are konker.registry.web/src/main/webapp/resources/js/clipboard.js/src/clipboard-action.js, konker.registry.web/src/main/webapp/resources/js/clipboard.js/src/clipboard.js, konker.registry.web/src/main/webapp/resources/js/destinations/rest/form.js, konker.registry.web/src/main/webapp/resources/js/devices/form.js, konker.registry.web/src/main/webapp/resources/js/devices/index.js, konker.registry.web/src/main/webapp/resources/js/devices/password.js (+24 more).
What to do
Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.
React / JS · Code Health — The share of the scored frontend lines inside a near-exact copy-pasted block of substantial extent (the D4 clone algorithm over JS/TS tokens, D-386; each line once, 10 at none and 0 at a quarter of the lines, as D4): a block is reported only where its copies still agree on most of their own identifiers and literals, or were renamed as they were pasted but kept most of their constants, and where the copies carry enough code to stand on their own or the copied extent reaches 30 lines — so a re-implementation sharing neither names nor values, and a small pasted declaration, are both found and deliberately not reported, and a clean R10 is not a claim that nothing was copied.
Method: Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm run over JS/TS tokens). Masking finds the candidates; a block is reported when its copies still agree on most of their own identifiers and literals, or when a renamed copy still agrees on most of its constants, AND the copies carry enough code to stand on their own — or when the copied extent reaches 30 lines. So a re-implementation sharing neither names nor values, and a small pasted declaration, are deliberately not counted. Scored on the share of the scored frontend lines inside a reported copy, on the same curve as D4. Deterministic.
konker.registry.web/src/main/webapp/resources/js/destinations/rest/form.js:72 · konker.registry.web/src/main/webapp/resources/js/routes/form.js:10 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — konker.registry.web/src/main/webapp/resources/js/destinations/rest/form.js:72
konker.registry.web/src/main/webapp/resources/js/users/userdialog.js:23 · konker.registry.web/src/main/webapp/resources/js/users/userdialog.js:75 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — konker.registry.web/src/main/webapp/resources/js/users/userdialog.js:23
REDACTED:159 · REDACTED:170 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — REDACTED:159
konker.registry.web/src/main/webapp/resources/js/destinations/rest/form.js:42 · konker.registry.web/src/main/webapp/resources/js/devices/form.js:1 · konker.registry.web/src/main/webapp/resources/js/routes/form.js:76 — the 3 copies are spread across 3 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — konker.registry.web/src/main/webapp/resources/js/destinations/rest/form.js:42
konker.registry.web/src/main/webapp/resources/konker/scripts/main.js:32 · konker.registry.web/src/main/webapp/resources/konker/scripts/main.js:95 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — konker.registry.web/src/main/webapp/resources/konker/scripts/main.js:32
konker.registry.web/src/main/webapp/resources/js/input-eye.js:4 · konker.registry.web/src/main/webapp/resources/js/input-eye.js:14 — 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. — konker.registry.web/src/main/webapp/resources/js/input-eye.js:4
konker.registry.web/src/main/webapp/resources/js/notifications/index.js:89 · konker.registry.web/src/main/webapp/resources/js/notifications/index.js:96 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — konker.registry.web/src/main/webapp/resources/js/notifications/index.js:89
konker.registry.web/src/main/webapp/resources/js/users/form.js:39 · konker.registry.web/src/main/webapp/resources/js/users/form.js:52 — 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. — konker.registry.web/src/main/webapp/resources/js/users/form.js:39
konker.registry.web/src/main/webapp/resources/js/visualization/graph.js:139 · konker.registry.web/src/main/webapp/resources/js/visualization/graph.js:156 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — konker.registry.web/src/main/webapp/resources/js/visualization/graph.js:139
What to do
Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
React / JS · Code Health — Per-function cyclomatic/cognitive complexity from the token-level function scanner (D-386) — real branching, not a regex heuristic.
Method: Per-function cyclomatic/cognitive complexity from a token-level function scanner (real branching, not a regex heuristic), computed over every frontend function. Deterministic.
parseTemplate has cyclomatic complexity 23 and cognitive complexity 40; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — konker.registry.web/src/main/webapp/resources/konker/scripts/mustache.js:105
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.
Do you agree with this assessment?
R4 · Test Coverage0.0 / 10Critical✓ Tool-verified
React / JS · Readiness — Static test reachability (D-386): the share of production files reachable from any test via the import graph — measured without running anything.
Method: Static test reachability: the share of production files reachable from any test via the import graph — measured without running anything. Deterministic.
0% of 30 production file(s) reachable from 0 test file(s) via the import graph — 'production' here is the RESIDUE: every source file left once tests, tooling, generated output, config, declarations and declaration-only modules, fixture corpora, type fixtures, behaviour-free data modules, re-export barrels, registration/constant data modules and service workers are set aside, so the percentage is taken over a smaller denominator than the workspace's file count
What to do
Add tests that import the unreached modules (directly or through their public entry).
Do you agree with this assessment?
R7 · Dead Code0.0 / 10Critical✓ Tool-verified
React / JS · Code Health — Files unreachable from every application/tooling/test entry point, and exports nothing imports (module-graph reachability, D-386).
Method: Dead code: files unreachable from every application/tooling/test entry point plus exports nothing imports, via module-graph reachability. Deterministic, exhaustive over the import graph.
Unreachable from the 2 application, 0 tooling and 0 test entry point(s) detected in this repo. This repository declares no build, type-check or test script, so nothing here would fail on a wrong deletion — confirm by hand that nothing loads each file (including by a path built at runtime) before removing it. An undetected custom entry would make these reachable.
no import path from any entry point (2 application, 0 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make (×27) — REDACTED, konker.registry.web/src/main/webapp/resources/js/visualization/graph.js, konker.registry.web/src/main/webapp/resources/konker/scripts/wow.js, …
no import path from any entry point (2 application, 0 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (konker.registry.web/src/main/webapp/resources/js/clipboard.js/src/clipboard.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — konker.registry.web/src/main/webapp/resources/js/clipboard.js/src/clipboard-action.js
What to do
Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
React / JS · 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 — Only what this repository's own non-C# files could be read for was assessed — markup this repository SHIPS is scored for third-party script integrity whether or not the repository serves it itself, since a page handed to a consumer runs in that consumer’s origin — and because this repository commits the configuration that serves its own HTTP surface, that configuration could be read in full for the security response headers it sets. Nothing else in this dimension was assessed: the transport, cookie, input-validation and crypto controls are read from a source model that was not loaded for this repository’s language, so their absence here is not a finding about this repository.
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.
`https://developers.google.com/maps/documentation/javascript/examples/markerclusterer/markerclusterer.js` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. The URL also names no version, so it resolves to whatever that origin serves at fetch time — the executed bytes can change with nobody touching this repository. 4 such include(s) across the repository's markup. — konker.registry.web/src/main/webapp/views/devices/events.html:260
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:1
What to do
Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-…"` hash alongside `crossorigin="anonymous"` (both are required — an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the app’s own origin, so no consumer inherits a third-party dependency they did not choose.
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.
Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.
Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. 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 `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.
Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.
Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether 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.
Do you agree with this assessment?
X24 · Document value interpolated into markup unescaped3.5 / 10Weak✓ Tool-verified
Other · Security — Whether text read out of the document being converted is escaped before it is written into generated markup — a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.
Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF — the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.
`Mustache.render($('#notification-template').html(),$.extend({},message,mustacheTranslation))` is text this program did not author, and it is written into the text of an element through the DOM library's `.html()` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — konker.registry.web/src/main/webapp/resources/js/notifications/index.js:89
`result[0].message` is text this program did not author, and it is written into the text of an element through the DOM library's `.html()` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:58
`data` is text this program did not author, and it is written into the text of an element through the DOM library's `.html()` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:189
`v==null?"":v` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js:793
`value` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js:797
`unformattedJSON` is text this program did not author, and it is written into the text of an element through the DOM library's `.html()` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — konker.registry.web/src/main/webapp/resources/konker/scripts/json.formatter.js:30
What to do
Each finding names the expression, the attribute it lands in and the line. Confirm the value's origin from the read this analyzer traced, then escape it at the sink or validate it against the shape the attribute accepts before interpolating.
Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.
Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether an enhanced `for` leaves the collection it is walking alone — a body that adds to or removes from the very collection the loop is iterating invalidates the fail-fast iterator it is holding, so the next `next()` throws `ConcurrentModificationException` and the remaining elements are never seen. Whether a `for` loop leaves the `dict`, `set` or `deque` it is walking alone — CPython's iterators over those check that the collection has not changed size since the loop began, so a body that removes from (or empties) the very collection the loop is walking makes the next step raise `RuntimeError: dictionary changed size during iteration` and the remaining items are never seen.
Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.
Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.
Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×4) — konker.registry.web/src/main/webapp/resources/konker/scripts/json.formatter.js:18, REDACTED:52, REDACTED:1801, …
What to do
Swallowed exception (empty catch)
Do you agree with this assessment?
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.
Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether log calls use message templates (queryable) rather than interpolated strings.
Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `trace`/`debug`/`info`/`warn`/`error`/`fatal`/`verbose`/`silly`/`http`/`log` call on a receiver named for a logger, in a package whose own or an enclosing `package.json` declares a logger that carries values as fields (pino, pino-http, nestjs-pino, Fastify, winston, bunyan, tslog, LogTape, roarr), whose first deciding argument is a template literal with substitutions; an object-literal fields argument is stepped over, a plain string message clears the call. Python is read the same way: a `debug`/`info`/`warning`/`error`/`exception`/`critical`/`log` call on a logger in a file that imports the standard library’s `logging` or structlog (loguru, which formats at the call, is not judged), whose message is a whole f-string with a non-constant field; a `%`-formatted, `.format()`-ed or concatenated message is not convicted, as in C#. PHP is read the same way: a PSR-3 level call (`emergency`…`debug`, `log`) on a logger (`$logger`, `$this->logger`, Laravel’s `Log::`, `logger()`, `\Drupal::logger()`) in a package whose `composer.json` requires a PSR-3 logger or a framework that hands one out (psr/log, Monolog, Laravel, Symfony, Drupal, CakePHP), or a file that imports one, whose message is a double-quoted string interpolating a variable; a single-quoted message clears the call, and `sprintf` or `.` concatenation is not convicted, as in C#. Dart is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on Sentry’s structured logger (`Sentry.logger`) whose message is a whole string literal interpolating a value (`$name`, `${…}`); the `Sentry.logger.fmt` template API clears the call. Dart that logs only through loggers with one message and no fields (package:logging, package:logger, talker, dart:developer) is not applicable rather than a reach gap. Ruby is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on the console gem’s `Console` (declared by a Gemfile, gemspec or Gemfile.lock, or required) or, where SemanticLogger, Ougai or dry-logger is declared or required, on a receiver named for a logger (`logger`, `@logger`, `Rails.logger`, `log`), whose first deciding argument is, as the whole argument, a double-quoted string interpolating a non-constant value (`#{…}`, `#@ivar`); a plain literal clears the call, keyword arguments are the fields, and a block, `%`-format or `+` concatenation is not convicted. Ruby that logs only through the standard Logger (Rails.logger) is not applicable rather than a reach gap. Deterministic.
`warn` at line 57 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — konker.registry.services.storage.cassandra/src/main/java/com/konkerlabs/platform/registry/business/repositories/config/CassandraRegistryConfig.java:57
`info` at line 123 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/config/MongoPrivateStorageConfig.java:123
`info` at line 125 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/config/MongoPrivateStorageConfig.java:125
`info` at line 179 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/UserServiceImpl.java:179
`error` at line 185 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/UserServiceImpl.java:185
`debug` at line 50 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — konker.registry.data.processor/src/main/java/com/konkerlabs/platform/registry/integration/endpoints/DeviceConfigRabbitEndpoint.java:50
`debug` at line 34 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — konker.registry.data.processor/src/main/java/com/konkerlabs/platform/registry/integration/endpoints/DeviceEventRabbitEndpoint.java:34
`warn` at line 147 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/services/DeviceLogEventServiceImpl.java:147
`warn` at line 174 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/services/DeviceLogEventServiceImpl.java:174
`warn` at line 192 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/services/DeviceLogEventServiceImpl.java:192
`warn` at line 209 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/services/DeviceLogEventServiceImpl.java:209
`warn` at line 216 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/services/DeviceLogEventServiceImpl.java:216
`warn` at line 226 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/services/DeviceLogEventServiceImpl.java:226
`warn` at line 232 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/services/DeviceLogEventServiceImpl.java:232
`error` at line 127 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/services/routes/EventRouteExecutorImpl.java:127
`debug` at line 223 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/services/routes/EventRouteExecutorImpl.java:223
`debug` at line 230 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/services/routes/EventRouteExecutorImpl.java:230
`info` at line 77 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/services/publishers/EventPublisherAmazonKinesis.java:77
`debug` at line 85 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/services/publishers/EventPublisherDevice.java:85
`debug` at line 108 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/services/publishers/EventPublisherRest.java:108
`warn` at line 61 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/security/KonkerBasicAuthenticationFilter.java:61
`warn` at line 69 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/security/KonkerBasicAuthenticationFilter.java:69
`warn` at line 75 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/security/KonkerBasicAuthenticationFilter.java:75
`info` at line 149 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/integration/processors/DeviceEventProcessor.java:149
`error` at line 161 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/integration/processors/DeviceEventProcessor.java:161
`debug` at line 179 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/integration/processors/DeviceEventProcessor.java:179
`info` at line 68 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/integration/gateway/RabbitGateway.java:68
`warn` at line 103 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — konker.registry.data/src/main/java/com/konkerlabs/platform/registry/integration/processors/GatewayEventProcessor.java:103
`debug` at line 109 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — konker.registry.data/src/main/java/com/konkerlabs/platform/registry/integration/processors/GatewayEventProcessor.java:109
`warn` at line 176 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — konker.registry.data/src/main/java/com/konkerlabs/platform/registry/integration/processors/GatewayEventProcessor.java:176
`debug` at line 182 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — konker.registry.data/src/main/java/com/konkerlabs/platform/registry/integration/processors/GatewayEventProcessor.java:182
`error` at line 146 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — konker.registry.data/src/main/java/com/konkerlabs/platform/registry/integration/endpoints/DeviceUploadRestEndpoint.java:146
`info` at line 159 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — konker.registry.data/src/main/java/com/konkerlabs/platform/registry/integration/endpoints/GatewayEventRestEndpoint.java:159
`info` at line 72 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — konker.registry.cassandra-etl/src/main/java/org/konker/registry/cassandraetl/EventsMigrationApplication.java:72
`info` at line 74 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — konker.registry.cassandra-etl/src/main/java/org/konker/registry/cassandraetl/EventsMigrationApplication.java:74
`info` at line 70 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — konker.registry.cassandra-etl/src/main/java/org/konker/registry/cassandraetl/services/EqualizeCassandraTablesService.java:70
`info` at line 55 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. (×2) — konker.registry.cassandra-etl/src/main/java/org/konker/registry/cassandraetl/services/EventsCassandraToMongoService.java:55, konker.registry.cassandra-etl/src/main/java/org/konker/registry/cassandraetl/services/EventsMongoToCassandraService.java:55
`info` at line 38 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/interceptor/RequestResponseInterceptor.java:38
Other · Code Health — Whether Java packages are null-marked and not undermined by heavy nullness suppression — a package under `@NullMarked` (or `@NonNullApi`, `@ParametersAreNonnullByDefault`, `@NonNullByDefault`, or a NullAway/Checker Framework configuration naming it) makes an unannotated reference exclude null, and `@SuppressWarnings("NullAway")`, `("nullness")`, `("null")` and `castToNonNull(…)` are what silence it.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
0/97 of this repository's Java package directories are under a non-null default: a `package-info.java` declaring `@NullMarked` (JSpecify) or `@NonNullApi`, `@ParametersAreNonnullByDefault`, `@NonNullByDefault`, `@DefaultQualifier(NonNull.class)`; a `module-info.java` declaring `@NullMarked`; every type in it `@NullMarked`; or a build that runs NullAway with the package in `AnnotatedPackages`, or the Checker Framework's `NullnessChecker`. Elsewhere every reference admits null and no checker warns on the dereference that throws a `NullPointerException`.
What to do
Declare the default where Java declares it: `@NullMarked` (org.jspecify.annotations) in each package's `package-info.java`, or once in `module-info.java`, and run NullAway (Error Prone) or the Checker Framework so the declaration is enforced. Then annotate the real exceptions `@Nullable` and resolve the suppressions rather than adding to them: a `@SuppressWarnings("NullAway")` or `castToNonNull(x)` on a value the checker could show to be null is a `NullPointerException` waiting for the path that makes it true — where the value genuinely cannot be null, say something the checker can see instead (a null check, `Objects.requireNonNull`, a non-null field initialised in the constructor).
Do you agree with this assessment?
WCAG coverage — what static analysis assessed
Statically assessed 15 of 55 WCAG 2.2 Level A/AA success criteria (27%; ≈30% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 40 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).
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.
Capped at Fair by a Critical contributor — resolve it before relying on this lens.
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.
X10 Duplicated predicate — 13 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 4 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 49 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.
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
AX8 Test isolation — no test/production split to check
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 — docker build failed (exit 1) — 110 | >>> COPY build/konker/registry-router.jar /var/lib/konker/ 111 | COPY build/konker/mosquitto-rabbitmq-bridge.jar /var/lib/konker/ 112 | -------------------- ERROR: failed to solve: failed to compute cache key: failed to calculate checksum of ref 7b32dc38-8cfb-43b2-8778-4ca3e507a5a5::rvjv73961c432bsrr95zd2yye: "/build/konker/registry-router.jar": not found; likely cause (the repository): a file the REDACTED copies (`build/konker/registry-router.jar`) is not in the repository's build context (it may be produced by a build step outside the REDACTED, or excluded by .dockerignore); runtime evidence skipped The cause is in the repository, not in our sandbox: a file the REDACTED copies (`build/konker/registry-router.jar`) is not in the repository's build context (it may be produced by a build step outside the REDACTED, or excluded by .dockerignore). 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.
D11 Test Reliability — Test reliability not included — the .java suite was found but not re-run
D12 Dependency Hygiene — Not scored — a Maven build resolved 22 artifact(s) (19 behind a shipped release, reported), but the build resolved only part of the graph, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
D16 Bus Factor — dormant codebase — no living knowledge left to concentrate
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
D21 Naming Consistency — Naming consistency does not read html yet; not measured.
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. Aggregate roots were found in only one source directory (konker.registry.services.core), which is a layered codebase, not two contexts. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D25 ADR Conformance — no ADRs to check
D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
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 included — suite not readable by the collector
DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 2 aggregate root(s) (entities a repository port loads or saves); 6 aggregate root(s) (types guarding their own state behind command methods — this language has no AggregateRoot base to inherit); 6 repository port(s) loading or saving an aggregate/entity; a top-level konker.samples/ tree: a library or framework whose examples are its consumers — these types are building blocks, not a domain
ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
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
P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
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 REDACTED, 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.
PF3 Async & latency hygiene — Not applicable: this repository declares no async functions, so there is no asynchronous code for a blocking call to stall.
R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
R5 Dependency Freshness — no package-lock.json — dependency freshness not measured (would require an npm lockfile); JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
R6 Tooling — no package.json in the repository — test/lint/typecheck wiring is read from package.json scripts (corroborated against CI), so this project's own toolchain isn't measured here
R8 Dependency Hygiene — Not measured — no package.json declares any dependency, so there is nothing to check imports against (imports may resolve through a host runtime rather than node).
X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X12 Unreachable branch — X12 reached only 33% of this repository's production lines — java (35,632 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X2 Cancellation propagation — no C# was loaded; this repository's Java and Python were read, and no request in it can be cancelled by a caller — a Java request off Android takes no token: it is cancelled through the handle it returns (Future.cancel, Call.cancel, a Disposable), ambiently (io.grpc.Context) or by interrupting its thread, 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
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
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
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.
Critical — 261 finding(s)
AC1 · Text alternatives· <img> without a text alternative · ×40
<img> without a text alternative konker.registry.web/src/main/webapp/resources/konker/scripts/jquery.magnific-popup.min.js:55— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative konker.registry.web/src/main/webapp/resources/konker/scripts/jquery.magnific-popup.min.js:111— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative konker.registry.web/src/main/webapp/views/destinations/rest/form.html:91— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative konker.registry.web/src/main/webapp/views/destinations/rest/form.html:176— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative konker.registry.web/src/main/webapp/views/destinations/rest/form.html:180— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative konker.registry.web/src/main/webapp/views/destinations/rest/form.html:186— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative konker.registry.web/src/main/webapp/views/destinations/rest/index.html:51— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative konker.registry.web/src/main/webapp/views/destinations/rest/index.html:58— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative konker.registry.web/src/main/webapp/views/destinations/rest/show.html:135— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative konker.registry.web/src/main/webapp/views/devices/events.html:149— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative konker.registry.web/src/main/webapp/views/devices/events.html:191— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative konker.registry.web/src/main/webapp/views/devices/events.html:227— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative konker.registry.web/src/main/webapp/views/devices/form.html:87— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative konker.registry.web/src/main/webapp/views/devices/form.html:93— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative konker.registry.web/src/main/webapp/views/devices/form.html:99— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative konker.registry.web/src/main/webapp/views/devices/index.html:51— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative konker.registry.web/src/main/webapp/views/devices/index.html:57— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative konker.registry.web/src/main/webapp/views/devices/index.html:63— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative konker.registry.web/src/main/webapp/views/devices/password.html:40— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative konker.registry.web/src/main/webapp/views/devices/password.html:238— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative konker.registry.web/src/main/webapp/views/devices/show.html:87— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative konker.registry.web/src/main/webapp/views/devices/show.html:93— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative konker.registry.web/src/main/webapp/views/error/index.html:12— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative konker.registry.web/src/main/webapp/views/footer.html:63— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative konker.registry.web/src/main/webapp/views/idm/clients/form.html:50— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
Captive dependency: singleton FormWebSecurityConfig captures prototype LoginAuditServiceImpl REDACTED:54— `FormWebSecurityConfig` is a Spring singleton (the default scope) and is injected `LoginAuditService loginAuditService`, whose bean `LoginAuditServiceImpl` is scoped prototype without a scoped proxy (konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/LoginAuditServiceImpl.java:24). The singleton is given ONE instance, once, and keeps it for the life of the application context — the fresh instance per use that the prototype scope promises never happens, and any state it carries is shared by every caller on every thread. Inject `ObjectProvider<LoginAuditServiceImpl>` and call getObject() per use, or declare the scope with proxyMode = ScopedProxyMode.TARGET_CLASS.
Captive dependency: singleton AlertTriggerServiceImpl captures prototype HealthAlertServiceImpl konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/AlertTriggerServiceImpl.java:20— `AlertTriggerServiceImpl` is a Spring singleton (the default scope) and is injected `HealthAlertService healthAlertService`, whose bean `HealthAlertServiceImpl` is scoped prototype without a scoped proxy (konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/HealthAlertServiceImpl.java:24). The singleton is given ONE instance, once, and keeps it for the life of the application context — the fresh instance per use that the prototype scope promises never happens, and any state it carries is shared by every caller on every thread. Inject `ObjectProvider<HealthAlertServiceImpl>` and call getObject() per use, or declare the scope with proxyMode = ScopedProxyMode.TARGET_CLASS.
Captive dependency: singleton TenantServiceImpl captures prototype ApplicationServiceImpl konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/TenantServiceImpl.java:40— `TenantServiceImpl` is a Spring singleton (the default scope) and is injected `ApplicationService applicationService`, whose bean `ApplicationServiceImpl` is scoped prototype without a scoped proxy (konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/ApplicationServiceImpl.java:27). The singleton is given ONE instance, once, and keeps it for the life of the application context — the fresh instance per use that the prototype scope promises never happens, and any state it carries is shared by every caller on every thread. Inject `ObjectProvider<ApplicationServiceImpl>` and call getObject() per use, or declare the scope with proxyMode = ScopedProxyMode.TARGET_CLASS.
Captive dependency: singleton UserServiceImpl captures prototype ApplicationServiceImpl konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/UserServiceImpl.java:50— `UserServiceImpl` is a Spring singleton (the default scope) and is injected `ApplicationService applicationService`, whose bean `ApplicationServiceImpl` is scoped prototype without a scoped proxy (konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/ApplicationServiceImpl.java:27). The singleton is given ONE instance, once, and keeps it for the life of the application context — the fresh instance per use that the prototype scope promises never happens, and any state it carries is shared by every caller on every thread. Inject `ObjectProvider<ApplicationServiceImpl>` and call getObject() per use, or declare the scope with proxyMode = ScopedProxyMode.TARGET_CLASS.
Captive dependency: singleton UserServiceImpl captures prototype LocationSearchServiceImpl konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/UserServiceImpl.java:53— `UserServiceImpl` is a Spring singleton (the default scope) and is injected `LocationSearchService locationSearchService`, whose bean `LocationSearchServiceImpl` is scoped prototype without a scoped proxy (konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/LocationSearchServiceImpl.java:27). The singleton is given ONE instance, once, and keeps it for the life of the application context — the fresh instance per use that the prototype scope promises never happens, and any state it carries is shared by every caller on every thread. Inject `ObjectProvider<LocationSearchServiceImpl>` and call getObject() per use, or declare the scope with proxyMode = ScopedProxyMode.TARGET_CLASS.
Captive dependency: singleton UserServiceImpl captures prototype EmailServiceImpl konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/UserServiceImpl.java:62— `UserServiceImpl` is a Spring singleton (the default scope) and is injected `EmailService emailService`, whose bean `EmailServiceImpl` is scoped prototype without a scoped proxy (konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/EmailServiceImpl.java:34). The singleton is given ONE instance, once, and keeps it for the life of the application context — the fresh instance per use that the prototype scope promises never happens, and any state it carries is shared by every caller on every thread. Inject `ObjectProvider<EmailServiceImpl>` and call getObject() per use, or declare the scope with proxyMode = ScopedProxyMode.TARGET_CLASS.
Captive dependency: singleton RabbitEventQueue captures prototype DeviceRegisterServiceImpl REDACTED:35— `RabbitEventQueue` is a Spring singleton (the default scope) and is injected `DeviceRegisterService deviceRegisterService`, whose bean `DeviceRegisterServiceImpl` is scoped prototype without a scoped proxy (konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceRegisterServiceImpl.java:37). The singleton is given ONE instance, once, and keeps it for the life of the application context — the fresh instance per use that the prototype scope promises never happens, and any state it carries is shared by every caller on every thread. Inject `ObjectProvider<DeviceRegisterServiceImpl>` and call getObject() per use, or declare the scope with proxyMode = ScopedProxyMode.TARGET_CLASS.
Captive dependency: singleton RabbitEventQueue captures prototype EventRouteServiceImpl REDACTED:38— `RabbitEventQueue` is a Spring singleton (the default scope) and is injected `EventRouteService eventRouteService`, whose bean `EventRouteServiceImpl` is scoped prototype without a scoped proxy (konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/EventRouteServiceImpl.java:43). The singleton is given ONE instance, once, and keeps it for the life of the application context — the fresh instance per use that the prototype scope promises never happens, and any state it carries is shared by every caller on every thread. Inject `ObjectProvider<EventRouteServiceImpl>` and call getObject() per use, or declare the scope with proxyMode = ScopedProxyMode.TARGET_CLASS.
Captive dependency: singleton ApplicationEventRestEndpoint captures prototype DeviceEventProcessor konker.registry.data.processor/src/main/java/com/konkerlabs/platform/registry/integration/endpoints/ApplicationEventRestEndpoint.java:63— `ApplicationEventRestEndpoint` is a Spring singleton (the default scope) and is injected `DeviceEventProcessor deviceEventProcessor`, whose bean `DeviceEventProcessor` is scoped prototype without a scoped proxy (konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/integration/processors/DeviceEventProcessor.java:32). The singleton is given ONE instance, once, and keeps it for the life of the application context — the fresh instance per use that the prototype scope promises never happens, and any state it carries is shared by every caller on every thread. Inject `ObjectProvider<DeviceEventProcessor>` and call getObject() per use, or declare the scope with proxyMode = ScopedProxyMode.TARGET_CLASS.
Captive dependency: singleton ApplicationEventRestEndpoint captures prototype ApplicationServiceImpl konker.registry.data.processor/src/main/java/com/konkerlabs/platform/registry/integration/endpoints/ApplicationEventRestEndpoint.java:66— `ApplicationEventRestEndpoint` is a Spring singleton (the default scope) and is injected `ApplicationService applicationService`, whose bean `ApplicationServiceImpl` is scoped prototype without a scoped proxy (konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/ApplicationServiceImpl.java:27). The singleton is given ONE instance, once, and keeps it for the life of the application context — the fresh instance per use that the prototype scope promises never happens, and any state it carries is shared by every caller on every thread. Inject `ObjectProvider<ApplicationServiceImpl>` and call getObject() per use, or declare the scope with proxyMode = ScopedProxyMode.TARGET_CLASS.
Captive dependency: singleton DeviceConfigRabbitEndpoint captures prototype DeviceConfigSetupServiceImpl konker.registry.data.processor/src/main/java/com/konkerlabs/platform/registry/integration/endpoints/DeviceConfigRabbitEndpoint.java:29— `DeviceConfigRabbitEndpoint` is a Spring singleton (the default scope) and is injected `DeviceConfigSetupService deviceConfigSetupService`, whose bean `DeviceConfigSetupServiceImpl` is scoped prototype without a scoped proxy (konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceConfigSetupServiceImpl.java:36). The singleton is given ONE instance, once, and keeps it for the life of the application context — the fresh instance per use that the prototype scope promises never happens, and any state it carries is shared by every caller on every thread. Inject `ObjectProvider<DeviceConfigSetupServiceImpl>` and call getObject() per use, or declare the scope with proxyMode = ScopedProxyMode.TARGET_CLASS.
Captive dependency: singleton DeviceConfigRabbitEndpoint captures prototype DeviceRegisterServiceImpl konker.registry.data.processor/src/main/java/com/konkerlabs/platform/registry/integration/endpoints/DeviceConfigRabbitEndpoint.java:32— `DeviceConfigRabbitEndpoint` is a Spring singleton (the default scope) and is injected `DeviceRegisterService deviceRegisterService`, whose bean `DeviceRegisterServiceImpl` is scoped prototype without a scoped proxy (konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceRegisterServiceImpl.java:37). The singleton is given ONE instance, once, and keeps it for the life of the application context — the fresh instance per use that the prototype scope promises never happens, and any state it carries is shared by every caller on every thread. Inject `ObjectProvider<DeviceRegisterServiceImpl>` and call getObject() per use, or declare the scope with proxyMode = ScopedProxyMode.TARGET_CLASS.
Captive dependency: singleton DeviceEventRabbitEndpoint captures prototype DeviceEventProcessor konker.registry.data.processor/src/main/java/com/konkerlabs/platform/registry/integration/endpoints/DeviceEventRabbitEndpoint.java:26— `DeviceEventRabbitEndpoint` is a Spring singleton (the default scope) and is injected `DeviceEventProcessor deviceEventProcessor`, whose bean `DeviceEventProcessor` is scoped prototype without a scoped proxy (konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/integration/processors/DeviceEventProcessor.java:32). The singleton is given ONE instance, once, and keeps it for the life of the application context — the fresh instance per use that the prototype scope promises never happens, and any state it carries is shared by every caller on every thread. Inject `ObjectProvider<DeviceEventProcessor>` and call getObject() per use, or declare the scope with proxyMode = ScopedProxyMode.TARGET_CLASS.
Captive dependency: singleton JedisTaskService captures prototype DeviceEventServiceImpl konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/services/JedisTaskService.java:30— `JedisTaskService` is a Spring singleton (the default scope) and is injected `DeviceEventService deviceEventService`, whose bean `DeviceEventServiceImpl` is scoped prototype without a scoped proxy (konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceEventServiceImpl.java:25). The singleton is given ONE instance, once, and keeps it for the life of the application context — the fresh instance per use that the prototype scope promises never happens, and any state it carries is shared by every caller on every thread. Inject `ObjectProvider<DeviceEventServiceImpl>` and call getObject() per use, or declare the scope with proxyMode = ScopedProxyMode.TARGET_CLASS.
Captive dependency: singleton JedisTaskService captures prototype DeviceRegisterServiceImpl konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/services/JedisTaskService.java:33— `JedisTaskService` is a Spring singleton (the default scope) and is injected `DeviceRegisterService deviceRegisterService`, whose bean `DeviceRegisterServiceImpl` is scoped prototype without a scoped proxy (konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceRegisterServiceImpl.java:37). The singleton is given ONE instance, once, and keeps it for the life of the application context — the fresh instance per use that the prototype scope promises never happens, and any state it carries is shared by every caller on every thread. Inject `ObjectProvider<DeviceRegisterServiceImpl>` and call getObject() per use, or declare the scope with proxyMode = ScopedProxyMode.TARGET_CLASS.
Captive dependency: singleton EventRouteExecutorImpl captures prototype EventRouteServiceImpl konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/services/routes/EventRouteExecutorImpl.java:38— `EventRouteExecutorImpl` is a Spring singleton (the default scope) and is injected `EventRouteService eventRouteService`, whose bean `EventRouteServiceImpl` is scoped prototype without a scoped proxy (konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/EventRouteServiceImpl.java:43). The singleton is given ONE instance, once, and keeps it for the life of the application context — the fresh instance per use that the prototype scope promises never happens, and any state it carries is shared by every caller on every thread. Inject `ObjectProvider<EventRouteServiceImpl>` and call getObject() per use, or declare the scope with proxyMode = ScopedProxyMode.TARGET_CLASS.
Captive dependency: singleton EventRouteExecutorImpl captures prototype ExpressionEvaluationServiceImpl konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/services/routes/EventRouteExecutorImpl.java:42— `EventRouteExecutorImpl` is a Spring singleton (the default scope) and is injected `ExpressionEvaluationService evaluationService`, whose bean `ExpressionEvaluationServiceImpl` is scoped prototype without a scoped proxy (konker.utilities/src/main/java/com/konkerlabs/platform/utilities/expressions/ExpressionEvaluationServiceImpl.java:23). The singleton is given ONE instance, once, and keeps it for the life of the application context — the fresh instance per use that the prototype scope promises never happens, and any state it carries is shared by every caller on every thread. Inject `ObjectProvider<ExpressionEvaluationServiceImpl>` and call getObject() per use, or declare the scope with proxyMode = ScopedProxyMode.TARGET_CLASS.
Captive dependency: singleton EventRouteExecutorImpl captures prototype LocationSearchServiceImpl konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/services/routes/EventRouteExecutorImpl.java:48— `EventRouteExecutorImpl` is a Spring singleton (the default scope) and is injected `LocationSearchService locationSearchService`, whose bean `LocationSearchServiceImpl` is scoped prototype without a scoped proxy (konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/LocationSearchServiceImpl.java:27). The singleton is given ONE instance, once, and keeps it for the life of the application context — the fresh instance per use that the prototype scope promises never happens, and any state it carries is shared by every caller on every thread. Inject `ObjectProvider<LocationSearchServiceImpl>` and call getObject() per use, or declare the scope with proxyMode = ScopedProxyMode.TARGET_CLASS.
Captive dependency: singleton EventRouteExecutorImpl captures prototype EventRouteCounterServiceImpl konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/services/routes/EventRouteExecutorImpl.java:54— `EventRouteExecutorImpl` is a Spring singleton (the default scope) and is injected `EventRouteCounterService eventRouteCounterService`, whose bean `EventRouteCounterServiceImpl` is scoped prototype without a scoped proxy (konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/EventRouteCounterServiceImpl.java:28). The singleton is given ONE instance, once, and keeps it for the life of the application context — the fresh instance per use that the prototype scope promises never happens, and any state it carries is shared by every caller on every thread. Inject `ObjectProvider<EventRouteCounterServiceImpl>` and call getObject() per use, or declare the scope with proxyMode = ScopedProxyMode.TARGET_CLASS.
Captive dependency: singleton EventTransformationServiceImpl captures prototype ExpressionEvaluationServiceImpl konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/services/routes/EventTransformationServiceImpl.java:37— `EventTransformationServiceImpl` is a Spring singleton (the default scope) and is injected `ExpressionEvaluationService evaluationService`, whose bean `ExpressionEvaluationServiceImpl` is scoped prototype without a scoped proxy (konker.utilities/src/main/java/com/konkerlabs/platform/utilities/expressions/ExpressionEvaluationServiceImpl.java:23). The singleton is given ONE instance, once, and keeps it for the life of the application context — the fresh instance per use that the prototype scope promises never happens, and any state it carries is shared by every caller on every thread. Inject `ObjectProvider<ExpressionEvaluationServiceImpl>` and call getObject() per use, or declare the scope with proxyMode = ScopedProxyMode.TARGET_CLASS.
Captive dependency: singleton EventPublisherDevice captures prototype DeviceRegisterServiceImpl konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/services/publishers/EventPublisherDevice.java:42— `EventPublisherDevice` is a Spring singleton (the default scope) and is injected `DeviceRegisterService deviceRegisterService`, whose bean `DeviceRegisterServiceImpl` is scoped prototype without a scoped proxy (konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceRegisterServiceImpl.java:37). The singleton is given ONE instance, once, and keeps it for the life of the application context — the fresh instance per use that the prototype scope promises never happens, and any state it carries is shared by every caller on every thread. Inject `ObjectProvider<DeviceRegisterServiceImpl>` and call getObject() per use, or declare the scope with proxyMode = ScopedProxyMode.TARGET_CLASS.
Captive dependency: singleton EventPublisherRest captures prototype RestDestinationServiceImpl konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/services/publishers/EventPublisherRest.java:47— `EventPublisherRest` is a Spring singleton (the default scope) and is injected `RestDestinationService restDestinationService`, whose bean `RestDestinationServiceImpl` is scoped prototype without a scoped proxy (konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/RestDestinationServiceImpl.java:33). The singleton is given ONE instance, once, and keeps it for the life of the application context — the fresh instance per use that the prototype scope promises never happens, and any state it carries is shared by every caller on every thread. Inject `ObjectProvider<RestDestinationServiceImpl>` and call getObject() per use, or declare the scope with proxyMode = ScopedProxyMode.TARGET_CLASS.
Captive dependency: singleton EventPublisherRest captures prototype ExpressionEvaluationServiceImpl konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/services/publishers/EventPublisherRest.java:49— `EventPublisherRest` is a Spring singleton (the default scope) and is injected `ExpressionEvaluationService expressionEvaluationService`, whose bean `ExpressionEvaluationServiceImpl` is scoped prototype without a scoped proxy (konker.utilities/src/main/java/com/konkerlabs/platform/utilities/expressions/ExpressionEvaluationServiceImpl.java:23). The singleton is given ONE instance, once, and keeps it for the life of the application context — the fresh instance per use that the prototype scope promises never happens, and any state it carries is shared by every caller on every thread. Inject `ObjectProvider<ExpressionEvaluationServiceImpl>` and call getObject() per use, or declare the scope with proxyMode = ScopedProxyMode.TARGET_CLASS.
Captive dependency: singleton SecurityConfig captures prototype DeviceRegisterServiceImpl REDACTED:59— `SecurityConfig` is a Spring singleton (the default scope) and is injected `DeviceRegisterService deviceRegisterService`, whose bean `DeviceRegisterServiceImpl` is scoped prototype without a scoped proxy (konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceRegisterServiceImpl.java:37). The singleton is given ONE instance, once, and keeps it for the life of the application context — the fresh instance per use that the prototype scope promises never happens, and any state it carries is shared by every caller on every thread. Inject `ObjectProvider<DeviceRegisterServiceImpl>` and call getObject() per use, or declare the scope with proxyMode = ScopedProxyMode.TARGET_CLASS.
Captive dependency: singleton DeviceEventRestEndpoint captures prototype DeviceEventProcessor konker.registry.data/src/main/java/com/konkerlabs/platform/registry/integration/endpoints/DeviceEventRestEndpoint.java:87— `DeviceEventRestEndpoint` is a Spring singleton (the default scope) and is injected `DeviceEventProcessor deviceEventProcessor`, whose bean `DeviceEventProcessor` is scoped prototype without a scoped proxy (konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/integration/processors/DeviceEventProcessor.java:32). The singleton is given ONE instance, once, and keeps it for the life of the application context — the fresh instance per use that the prototype scope promises never happens, and any state it carries is shared by every caller on every thread. Inject `ObjectProvider<DeviceEventProcessor>` and call getObject() per use, or declare the scope with proxyMode = ScopedProxyMode.TARGET_CLASS.
AC2 · Forms & labels· <input> without a programmatic label · ×15
<input> without a programmatic label konker.registry.web/src/main/webapp/views/destinations/rest/form.html:76— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
<input> without a programmatic label konker.registry.web/src/main/webapp/views/destinations/rest/form.html:83— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label konker.registry.web/src/main/webapp/views/destinations/rest/form.html:88— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label konker.registry.web/src/main/webapp/views/destinations/rest/form.html:115— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label konker.registry.web/src/main/webapp/views/destinations/rest/form.html:120— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label konker.registry.web/src/main/webapp/views/destinations/rest/show.html:44— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label konker.registry.web/src/main/webapp/views/destinations/rest/show.html:48— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label konker.registry.web/src/main/webapp/views/destinations/rest/show.html:52— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label konker.registry.web/src/main/webapp/views/destinations/rest/show.html:56— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label konker.registry.web/src/main/webapp/views/destinations/rest/show.html:79— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label konker.registry.web/src/main/webapp/views/destinations/rest/show.html:84— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label konker.registry.web/src/main/webapp/views/devices/events.html:54— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label konker.registry.web/src/main/webapp/views/devices/events.html:62— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label konker.registry.web/src/main/webapp/views/devices/events.html:88— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label konker.registry.web/src/main/webapp/views/devices/events.html:99— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<html> without a lang konker.registry.web/src/main/webapp/views/destinations/rest/custom-body.html:2— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang konker.registry.web/src/main/webapp/views/destinations/rest/empty-body.html:2— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang konker.registry.web/src/main/webapp/views/destinations/rest/form.html:2— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang konker.registry.web/src/main/webapp/views/destinations/rest/index.html:2— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang konker.registry.web/src/main/webapp/views/destinations/rest/show.html:2— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang konker.registry.web/src/main/webapp/views/devices/events-incoming.html:2— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang konker.registry.web/src/main/webapp/views/devices/events-outgoing.html:2— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang konker.registry.web/src/main/webapp/views/devices/events.html:2— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang konker.registry.web/src/main/webapp/views/devices/form.html:2— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang konker.registry.web/src/main/webapp/views/devices/index.html:2— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang konker.registry.web/src/main/webapp/views/devices/password.html:2— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang konker.registry.web/src/main/webapp/views/devices/show.html:2— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang konker.registry.web/src/main/webapp/views/devices/visualization/channels.html:2— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
AC3 · Page structure· Document without a <title> · ×12
Document without a <title> konker.registry.web/src/main/webapp/views/destinations/rest/custom-body.html:2— A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>.
Document without a <title> konker.registry.web/src/main/webapp/views/destinations/rest/empty-body.html:2— A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>.
Document without a <title> konker.registry.web/src/main/webapp/views/destinations/rest/form.html:2— A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>.
Document without a <title> konker.registry.web/src/main/webapp/views/destinations/rest/index.html:2— A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>.
Document without a <title> konker.registry.web/src/main/webapp/views/destinations/rest/show.html:2— A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>.
Document without a <title> konker.registry.web/src/main/webapp/views/devices/events-incoming.html:2— A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>.
Document without a <title> konker.registry.web/src/main/webapp/views/devices/events-outgoing.html:2— A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>.
Document without a <title> konker.registry.web/src/main/webapp/views/devices/events.html:2— A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>.
Document without a <title> konker.registry.web/src/main/webapp/views/devices/form.html:2— A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>.
Document without a <title> konker.registry.web/src/main/webapp/views/devices/index.html:2— A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>.
Document without a <title> konker.registry.web/src/main/webapp/views/devices/password.html:2— A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>.
Document without a <title> konker.registry.web/src/main/webapp/views/devices/show.html:2— A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>.
AC2 · Forms & labels· <label> that labels no control · ×9
<label> that labels no control konker.registry.web/src/main/webapp/views/destinations/rest/form.html:141— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control konker.registry.web/src/main/webapp/views/destinations/rest/show.html:99— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control konker.registry.web/src/main/webapp/views/devices/events.html:51— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control konker.registry.web/src/main/webapp/views/devices/events.html:59— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control konker.registry.web/src/main/webapp/views/devices/events.html:84— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control konker.registry.web/src/main/webapp/views/devices/events.html:95— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control konker.registry.web/src/main/webapp/views/devices/events.html:128— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control konker.registry.web/src/main/webapp/views/devices/events.html:138— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control konker.registry.web/src/main/webapp/views/devices/events.html:180— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
AC2 · Forms & labels· <select> without a programmatic label · ×4
<select> without a programmatic label konker.registry.web/src/main/webapp/views/destinations/rest/form.html:57— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<select> without a programmatic label konker.registry.web/src/main/webapp/views/destinations/rest/form.html:67— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<select> without a programmatic label konker.registry.web/src/main/webapp/views/devices/visualization/channels.html:7— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<select> without a programmatic label konker.registry.web/src/main/webapp/views/devices/visualization/metrics.html:7— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
AC4 · Keyboard semantics· Clickable element isn't keyboard-operable · ×2
Clickable element isn't keyboard-operable konker.registry.web/src/main/webapp/views/destinations/rest/form.html:91— The repo's own CSS styles .password-eye with `cursor: pointer`, so this <img> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler.
Clickable element isn't keyboard-operable konker.registry.web/src/main/webapp/views/transformations/form.html:113— The repo's own CSS styles .password-eye with `cursor: pointer`, so this <img> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler.
Boundary-crossing change coupling: UserRestController.java ↔ UserServiceImpl.java konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/UserRestController.java:1— `konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/UserRestController.java` (context konker.registry) and `konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/UserServiceImpl.java` (context konker.registry.services) sit in DIFFERENT parts of the tree yet change together 75% of the time (9 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 9 shared commits counted here, the most recent 3 are `ac72d344` KRMVP-1065 - [API] Change user update to deny change his own applicat…; `89add8a8` KRMVP-1020 Create delete user; `5579d0b7` KRMVP-995 - Change controller layer — run `git show` on any of them.
Boundary-crossing change coupling: LocationRestController.java ↔ LocationServiceImpl.java konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/LocationRestController.java:1— `konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/LocationRestController.java` (context konker.registry) and `konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/LocationServiceImpl.java` (context konker.registry.services) sit in DIFFERENT parts of the tree yet change together 50% of the time (9 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) — 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 9 shared commits counted here, the most recent 3 are `10da1d17` Fix bug when update application; Fix bug when delete location; Fix bu…; `62194712` fix: location delete bug add validation: service.location.is_root; `baa6aa52` created LocationTreeUtils — run `git show` on any of them.
AC2 · Forms & labels· <textarea> without a programmatic label · ×1
<textarea> without a programmatic label konker.registry.web/src/main/webapp/views/destinations/rest/custom-body.html:10— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
AC2 · Forms & labels· <button> with no accessible text · ×1
<button> with no accessible text konker.registry.web/src/main/webapp/views/destinations/rest/form.html:126— A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
AC3 · Page structure· <iframe> without a title · ×1
<iframe> without a title konker.registry.web/src/main/webapp/resources/konker/scripts/jquery.magnific-popup.min.js:99— An iframe with no title (or an empty one) is announced only as "frame". Add a non-empty title describing its content, or an aria-label.
No assertions: shoulRaiseAnExceptionIfHttpMethodIsNull konker.registry.data.core/src/test/java/com/konkerlabs/platform/registry/test/data/core/integration/gateway/HttpGatewayTest.java:64— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: shouldFailWithExceptionIfPasswordNotDefined konker.registry.data.core/src/test/java/com/konkerlabs/platform/registry/test/data/core/integration/gateway/HttpGatewayTest.java:94— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: shouldFailWithExceptionIfUriNotDefined konker.registry.data.core/src/test/java/com/konkerlabs/platform/registry/test/data/core/integration/gateway/HttpGatewayTest.java:74— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: shouldFailWithExceptionIfUsernameNotDefined konker.registry.data.core/src/test/java/com/konkerlabs/platform/registry/test/data/core/integration/gateway/HttpGatewayTest.java:84— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: shouldRaiseAnExceptionIfResponseStatusIsNotA2xxStatus konker.registry.data.core/src/test/java/com/konkerlabs/platform/registry/test/data/core/integration/gateway/HttpGatewayTest.java:228— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: shouldRaiseAnExceptionIfDeviceApiKeyIsUnknown konker.registry.data.core/src/test/java/com/konkerlabs/platform/registry/test/data/core/integration/processors/DeviceEventProcessorTest.java:275— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: shouldRaiseAnExceptionIfDeviceDoesNotExist konker.registry.data.core/src/test/java/com/konkerlabs/platform/registry/test/data/core/integration/processors/DeviceEventProcessorTest.java:283— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: shouldRaiseAnExceptionIfEventChannelIsUnknown konker.registry.data.core/src/test/java/com/konkerlabs/platform/registry/test/data/core/integration/processors/DeviceEventProcessorTest.java:291— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: shouldRaiseAnExceptionNoChannelProcessDevice konker.registry.data.core/src/test/java/com/konkerlabs/platform/registry/test/data/core/integration/processors/DeviceEventProcessorTest.java:329— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: shouldRaiseAnExceptionIfDataIsNull konker.registry.data.core/src/test/java/com/konkerlabs/platform/registry/test/data/core/services/publishers/EventPublisherAmazonKinesisTest.java:161— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: shouldRaiseAnExceptionIfEventIsNull konker.registry.data.core/src/test/java/com/konkerlabs/platform/registry/test/data/core/services/publishers/EventPublisherAmazonKinesisTest.java:145— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: shouldRaiseAnExceptionIfTenantIsNull konker.registry.data.core/src/test/java/com/konkerlabs/platform/registry/test/data/core/services/publishers/EventPublisherAmazonKinesisTest.java:169— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: shouldRaiseAnExceptionIfURIIsNull konker.registry.data.core/src/test/java/com/konkerlabs/platform/registry/test/data/core/services/publishers/EventPublisherAmazonKinesisTest.java:153— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: shouldSendMessages konker.registry.data.core/src/test/java/com/konkerlabs/platform/registry/test/data/core/services/publishers/EventPublisherAmazonKinesisTest.java:177— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: shouldRaiseAnExceptionIfDataIsNull konker.registry.data.core/src/test/java/com/konkerlabs/platform/registry/test/data/core/services/publishers/EventPublisherDeviceTest.java:183— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: shouldRaiseAnExceptionIfDeviceIsUnknown konker.registry.data.core/src/test/java/com/konkerlabs/platform/registry/test/data/core/services/publishers/EventPublisherDeviceTest.java:219— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: shouldRaiseAnExceptionIfEventIsNull konker.registry.data.core/src/test/java/com/konkerlabs/platform/registry/test/data/core/services/publishers/EventPublisherDeviceTest.java:159— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: shouldRaiseAnExceptionIfMqttChannelIsEmpty konker.registry.data.core/src/test/java/com/konkerlabs/platform/registry/test/data/core/services/publishers/EventPublisherDeviceTest.java:201— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: shouldRaiseAnExceptionIfMqttChannelIsNull konker.registry.data.core/src/test/java/com/konkerlabs/platform/registry/test/data/core/services/publishers/EventPublisherDeviceTest.java:191— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: shouldRaiseAnExceptionIfTenantIsNull konker.registry.data.core/src/test/java/com/konkerlabs/platform/registry/test/data/core/services/publishers/EventPublisherDeviceTest.java:211— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: shouldRaiseAnExceptionIfURIIsEmpty konker.registry.data.core/src/test/java/com/konkerlabs/platform/registry/test/data/core/services/publishers/EventPublisherDeviceTest.java:175— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: shouldRaiseAnExceptionIfURIIsNull konker.registry.data.core/src/test/java/com/konkerlabs/platform/registry/test/data/core/services/publishers/EventPublisherDeviceTest.java:167— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: shouldRaiseAnExceptionIfDataIsNull konker.registry.data.core/src/test/java/com/konkerlabs/platform/registry/test/data/core/services/publishers/EventPublisherModelLocationTest.java:205— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: shouldRaiseAnExceptionIfEventIsNull konker.registry.data.core/src/test/java/com/konkerlabs/platform/registry/test/data/core/services/publishers/EventPublisherModelLocationTest.java:189— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: shouldRaiseAnExceptionIfMqttChannelIsEmpty konker.registry.data.core/src/test/java/com/konkerlabs/platform/registry/test/data/core/services/publishers/EventPublisherModelLocationTest.java:223— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
Duplicated block (8 lines × 2) konker.registry.idm.resourceserver/src/main/java/com/konkerlabs/platform/registry/idm/security/TenantUserDetailsService.java:30— konker.registry.idm.resourceserver/src/main/java/com/konkerlabs/platform/registry/idm/security/TenantUserDetailsService.java:30-37 | konker.registry.web/src/main/java/com/konkerlabs/platform/registry/security/TenantUserDetailsService.java:34-41 — before extracting anything, compare `konker.registry.idm.resourceserver/src/main/java/com/konkerlabs/platform/registry/idm/security/TenantUserDetailsService.java` and `konker.registry.web/src/main/java/com/konkerlabs/platform/registry/security/TenantUserDetailsService.java` as WHOLE FILES: 89% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) konker.registry.idm.resourceserver/src/main/java/com/konkerlabs/platform/registry/idm/security/TenantUserDetailsService.java:39— konker.registry.idm.resourceserver/src/main/java/com/konkerlabs/platform/registry/idm/security/TenantUserDetailsService.java:39-46 | konker.registry.web/src/main/java/com/konkerlabs/platform/registry/security/TenantUserDetailsService.java:55-62 — before extracting anything, compare `konker.registry.idm.resourceserver/src/main/java/com/konkerlabs/platform/registry/idm/security/TenantUserDetailsService.java` and `konker.registry.web/src/main/java/com/konkerlabs/platform/registry/security/TenantUserDetailsService.java` as WHOLE FILES: 89% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `konker.registry.idm.resourceserver/src/main/java/com/konkerlabs/platform/registry/idm/security/TenantUserDetailsService.java:39` 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) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/ApplicationDocumentStoreServiceImpl.java:97— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/ApplicationDocumentStoreServiceImpl.java:97-104 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceCustomDataServiceImpl.java:96-103 — 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 `konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/ApplicationDocumentStoreServiceImpl.java:97` 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) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/ApplicationServiceImpl.java:66— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/ApplicationServiceImpl.java:66-73 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceModelServiceImpl.java:62-69 — 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 `konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/ApplicationServiceImpl.java:66` 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) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceModelServiceImpl.java:190— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceModelServiceImpl.java:190-197 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceModelServiceImpl.java:261-268 — 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 `konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceModelServiceImpl.java:190` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 2) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/EventRouteServiceImpl.java:65— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/EventRouteServiceImpl.java:65-72 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/EventRouteServiceImpl.java:116-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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 2) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/EventRouteServiceImpl.java:79— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/EventRouteServiceImpl.java:79-86 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/RestDestinationServiceImpl.java:150-157 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/EventRouteServiceImpl.java:79` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/LocationServiceImpl.java:252— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/LocationServiceImpl.java:252-259 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/LocationServiceImpl.java:277-284 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 2) REDACTED:479— REDACTED:479-486 | REDACTED:516-523 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 2) REDACTED:114— REDACTED:114-121 | REDACTED:185-192 — 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 `REDACTED:114` 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) konker.security/src/main/java/com/konkerlabs/platform/security/crypto/BCrypt.java:399— konker.security/src/main/java/com/konkerlabs/platform/security/crypto/BCrypt.java:399-406 | konker.security/src/main/java/com/konkerlabs/platform/security/crypto/BCrypt.java:407-414 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceModelServiceImpl.java:145— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceModelServiceImpl.java:145-152 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceModelServiceImpl.java:204-211 — 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 `konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceModelServiceImpl.java:145` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 2) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/UserServiceImpl.java:156— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/UserServiceImpl.java:156-163 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/UserServiceImpl.java:284-291 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 2) konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/config/oauth/OAuth2Config.java:109— konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/config/oauth/OAuth2Config.java:109-116 | konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/config/oauth/OAuth2Config.java:53-60 — before extracting anything, compare `konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/config/oauth/OAuth2Config.java` and `konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/config/oauth/OAuth2Config.java` as WHOLE FILES: 82% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 2) konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/AlertTriggerRestController.java:216— konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/AlertTriggerRestController.java:216-223 | konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/HealthAlertRestController.java:230-237 — 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 2) konker.registry.cassandra-etl/src/main/java/org/konker/registry/cassandraetl/services/EventsCassandraToMongoService.java:59— konker.registry.cassandra-etl/src/main/java/org/konker/registry/cassandraetl/services/EventsCassandraToMongoService.java:59-66 | konker.registry.cassandra-etl/src/main/java/org/konker/registry/cassandraetl/services/EventsMongoToCassandraService.java:59-66 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (8 lines × 2) REDACTED:19— REDACTED:19-26 | konker.registry.web/src/main/java/com/konkerlabs/platform/registry/web/controllers/RecoverPasswordController.java:90-97 — 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 2) konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/model/DeviceFirmwareUpdateInputVO.java:27— konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/model/DeviceFirmwareUpdateInputVO.java:27-34 | konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/model/DeviceFirmwareUpdateSuspendInputVO.java:23-30 — 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 2) konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/model/RestDestinationVO.java:39— konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/model/RestDestinationVO.java:39-47 | konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/RestDestinationController.java:151-159 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (9 lines × 2) konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/config/RedisConfig.java:33— konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/config/RedisConfig.java:33-41 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/config/RedisCacheConfig.java:39-47 — 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 `konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/config/RedisCacheConfig.java:39` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/AlertTriggerServiceImpl.java:119— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/AlertTriggerServiceImpl.java:119-127 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/AlertTriggerServiceImpl.java:220-228 — 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 `konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/AlertTriggerServiceImpl.java:119` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 2) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/AlertTriggerServiceImpl.java:150— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/AlertTriggerServiceImpl.java:150-158 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/AlertTriggerServiceImpl.java:195-203 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 2) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/ApplicationServiceImpl.java:53— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/ApplicationServiceImpl.java:53-61 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceModelServiceImpl.java:49-57 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/ApplicationServiceImpl.java: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 (9 lines × 2) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/ApplicationServiceImpl.java:118— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/ApplicationServiceImpl.java:118-126 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/ApplicationServiceImpl.java:175-183 — 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 `konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/ApplicationServiceImpl.java:118` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (9 lines × 2) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceFirmwareUpdateServiceImpl.java:162— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceFirmwareUpdateServiceImpl.java:162-170 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceFirmwareUpdateServiceImpl.java:181-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 `konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceFirmwareUpdateServiceImpl.java:162` 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 2) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceModelServiceImpl.java:393— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceModelServiceImpl.java:393-401 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/LocationSearchServiceImpl.java:130-138 — 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 2) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/LocationServiceImpl.java:81— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/LocationServiceImpl.java:81-89 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/LocationServiceImpl.java:146-154 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/LocationServiceImpl.java:95— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/LocationServiceImpl.java:95-103 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/LocationServiceImpl.java:162-170 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/LocationServiceImpl.java: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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 2) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/LocationServiceImpl.java:132— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/LocationServiceImpl.java:132-140 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/LocationServiceImpl.java:370-378 — 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 `konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/LocationServiceImpl.java:132` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/LocationServiceImpl.java:381` calls `setLocationParent` and `konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/LocationServiceImpl.java:142` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9 lines × 2) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/model/EventRoute.java:131— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/model/EventRoute.java:131-139 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/model/EventRoute.java:191-199 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/model/EventRoute.java:131` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) REDACTED:104— REDACTED:104-112 | REDACTED:174-182 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 2) konker.registry.data/src/main/java/com/konkerlabs/platform/registry/data/upload/AwsUploadRepository.java:50— konker.registry.data/src/main/java/com/konkerlabs/platform/registry/data/upload/AwsUploadRepository.java:50-58 | konker.registry.web/src/main/java/com/konkerlabs/platform/registry/business/repositories/upload/AwsUploadRepository.java:56-64 — before extracting anything, compare `konker.registry.data/src/main/java/com/konkerlabs/platform/registry/data/upload/AwsUploadRepository.java` and `konker.registry.web/src/main/java/com/konkerlabs/platform/registry/business/repositories/upload/AwsUploadRepository.java` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 65 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 (9 lines × 2) REDACTED:398— REDACTED:398-408 | REDACTED:90-98 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:398` 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.
D30 · Dependency Vulnerabilities· Medium CVE · ×13
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
AC3 · Page structure· Page without a main landmark · ×12
Page without a main landmark konker.registry.web/src/main/webapp/views/destinations/rest/custom-body.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark konker.registry.web/src/main/webapp/views/destinations/rest/empty-body.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div>, so there is no content here to wrap — render the <main> from the component mounted into it.
Page without a main landmark konker.registry.web/src/main/webapp/views/destinations/rest/form.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark konker.registry.web/src/main/webapp/views/destinations/rest/index.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark konker.registry.web/src/main/webapp/views/destinations/rest/show.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark konker.registry.web/src/main/webapp/views/devices/events-incoming.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark konker.registry.web/src/main/webapp/views/devices/events-outgoing.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark konker.registry.web/src/main/webapp/views/devices/events.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark konker.registry.web/src/main/webapp/views/devices/form.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark konker.registry.web/src/main/webapp/views/devices/index.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark konker.registry.web/src/main/webapp/views/devices/password.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark konker.registry.web/src/main/webapp/views/devices/show.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Duplicated block (10 lines × 2) konker.registry.data.processor/src/main/java/com/konkerlabs/platform/registry/integration/endpoints/DeviceConfigRabbitEndpoint.java:49— konker.registry.data.processor/src/main/java/com/konkerlabs/platform/registry/integration/endpoints/DeviceConfigRabbitEndpoint.java:49-58 | konker.registry.data.processor/src/main/java/com/konkerlabs/platform/registry/integration/endpoints/DeviceEventRabbitEndpoint.java:33-42 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (10 lines × 2) konker.registry.idm.resourceserver/src/main/java/com/konkerlabs/platform/registry/idm/services/OAuthClientDetailsService.java:242— konker.registry.idm.resourceserver/src/main/java/com/konkerlabs/platform/registry/idm/services/OAuthClientDetailsService.java:242-251 | konker.registry.idm.resourceserver/src/main/java/com/konkerlabs/platform/registry/idm/services/OAuthClientDetailsService.java:265-274 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 2) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/ApplicationServiceImpl.java:75— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/ApplicationServiceImpl.java:75-84 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceModelServiceImpl.java:71-80 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/ApplicationServiceImpl.java:75` 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) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceCustomDataServiceImpl.java:41— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceCustomDataServiceImpl.java:41-50 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceCustomDataServiceImpl.java:77-86 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 2) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceRegisterServiceImpl.java:202— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceRegisterServiceImpl.java:202-211 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/GatewayServiceImpl.java:76-85 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (10 lines × 2) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/HealthAlertServiceImpl.java:220— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/HealthAlertServiceImpl.java:220-229 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/HealthAlertServiceImpl.java:328-337 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 2) konker.registry.services.storage.cassandra/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/EventRepositoryCassandraImpl.java:607— konker.registry.services.storage.cassandra/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/EventRepositoryCassandraImpl.java:607-616 | konker.registry.services.storage.cassandra/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/EventRepositoryCassandraImpl.java:635-644 — 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, `konker.registry.services.storage.cassandra/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/EventRepositoryCassandraImpl.java:633` calls `add` and `konker.registry.services.storage.cassandra/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/EventRepositoryCassandraImpl.java:605` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (10 lines × 2) konker.registry.web/src/main/java/com/konkerlabs/platform/registry/idm/web/controllers/AccountClientsController.java:205— konker.registry.web/src/main/java/com/konkerlabs/platform/registry/idm/web/controllers/AccountClientsController.java:205-214 | konker.registry.web/src/main/java/com/konkerlabs/platform/registry/idm/web/controllers/AccountClientsController.java:234-243 — 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 `konker.registry.web/src/main/java/com/konkerlabs/platform/registry/idm/web/controllers/AccountClientsController.java:205` 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) konker.security/src/main/java/com/konkerlabs/platform/security/crypto/BCrypt.java:690— konker.security/src/main/java/com/konkerlabs/platform/security/crypto/BCrypt.java:690-699 | konker.security/src/main/java/com/konkerlabs/platform/security/crypto/BCrypt.java:719-728 — 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, `konker.security/src/main/java/com/konkerlabs/platform/security/crypto/BCrypt.java:700` calls `encode_base64` and `konker.security/src/main/java/com/konkerlabs/platform/security/crypto/BCrypt.java:729` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (10 lines × 2) konker.registry.cassandra-etl/src/main/java/org/konker/registry/cassandraetl/repositories/EventRepositoryCassandraEtlImpl.java:44— konker.registry.cassandra-etl/src/main/java/org/konker/registry/cassandraetl/repositories/EventRepositoryCassandraEtlImpl.java:44-53 | konker.registry.services.storage.cassandra/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/EventRepositoryCassandraImpl.java:106-115 — before extracting anything, compare `konker.registry.cassandra-etl/src/main/java/org/konker/registry/cassandraetl/repositories/EventRepositoryCassandraEtlImpl.java` and `konker.registry.services.storage.cassandra/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/EventRepositoryCassandraImpl.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 47 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `konker.registry.cassandra-etl/src/main/java/org/konker/registry/cassandraetl/repositories/EventRepositoryCassandraEtlImpl.java:44` 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) konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/DeviceFirmwareRestController.java:116— konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/DeviceFirmwareRestController.java:116-125 | konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/DeviceFirmwareUpdateRestController.java:147-156 — 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.
AC2 · Forms & labels· <fieldset> without a <legend> · ×10
<fieldset> without a <legend> konker.registry.web/src/main/webapp/views/destinations/rest/form.html:13— A fieldset groups related controls but has no <legend> to name the group. Add a <legend> as its first child — or, if the group already has a visible caption beside it (or the fieldset is there only to disable its subtree and carries no group box), point aria-labelledby at that caption's id instead, which names the group without rendering a second one.
<fieldset> without a <legend> konker.registry.web/src/main/webapp/views/destinations/rest/index.html:7— A fieldset groups related controls but has no <legend> to name the group. Add a <legend> as its first child — or, if the group already has a visible caption beside it (or the fieldset is there only to disable its subtree and carries no group box), point aria-labelledby at that caption's id instead, which names the group without rendering a second one.
<fieldset> without a <legend> konker.registry.web/src/main/webapp/views/destinations/rest/show.html:7— A fieldset groups related controls but has no <legend> to name the group. Add a <legend> as its first child — or, if the group already has a visible caption beside it (or the fieldset is there only to disable its subtree and carries no group box), point aria-labelledby at that caption's id instead, which names the group without rendering a second one.
<fieldset> without a <legend> konker.registry.web/src/main/webapp/views/devices/events.html:35— A fieldset groups related controls but has no <legend> to name the group. Add a <legend> as its first child — or, if the group already has a visible caption beside it (or the fieldset is there only to disable its subtree and carries no group box), point aria-labelledby at that caption's id instead, which names the group without rendering a second one.
<fieldset> without a <legend> konker.registry.web/src/main/webapp/views/devices/events.html:68— A fieldset groups related controls but has no <legend> to name the group. Add a <legend> as its first child — or, if the group already has a visible caption beside it (or the fieldset is there only to disable its subtree and carries no group box), point aria-labelledby at that caption's id instead, which names the group without rendering a second one.
<fieldset> without a <legend> konker.registry.web/src/main/webapp/views/devices/events.html:217— A fieldset groups related controls but has no <legend> to name the group. Add a <legend> as its first child — or, if the group already has a visible caption beside it (or the fieldset is there only to disable its subtree and carries no group box), point aria-labelledby at that caption's id instead, which names the group without rendering a second one.
<fieldset> without a <legend> konker.registry.web/src/main/webapp/views/devices/form.html:7— A fieldset groups related controls but has no <legend> to name the group. Add a <legend> as its first child — or, if the group already has a visible caption beside it (or the fieldset is there only to disable its subtree and carries no group box), point aria-labelledby at that caption's id instead, which names the group without rendering a second one.
<fieldset> without a <legend> konker.registry.web/src/main/webapp/views/devices/index.html:7— A fieldset groups related controls but has no <legend> to name the group. Add a <legend> as its first child — or, if the group already has a visible caption beside it (or the fieldset is there only to disable its subtree and carries no group box), point aria-labelledby at that caption's id instead, which names the group without rendering a second one.
<fieldset> without a <legend> konker.registry.web/src/main/webapp/views/devices/password.html:8— A fieldset groups related controls but has no <legend> to name the group. Add a <legend> as its first child — or, if the group already has a visible caption beside it (or the fieldset is there only to disable its subtree and carries no group box), point aria-labelledby at that caption's id instead, which names the group without rendering a second one.
<fieldset> without a <legend> konker.registry.web/src/main/webapp/views/devices/show.html:7— A fieldset groups related controls but has no <legend> to name the group. Add a <legend> as its first child — or, if the group already has a visible caption beside it (or the fieldset is there only to disable its subtree and carries no group box), point aria-labelledby at that caption's id instead, which names the group without rendering a second one.
Duplicated block (11 lines × 2) konker.registry.data/src/main/java/com/konkerlabs/platform/registry/integration/endpoints/DeviceEventRestEndpoint.java:286— konker.registry.data/src/main/java/com/konkerlabs/platform/registry/integration/endpoints/DeviceEventRestEndpoint.java:286-296 | konker.registry.data/src/main/java/com/konkerlabs/platform/registry/integration/endpoints/DeviceEventRestEndpoint.java:405-415 — 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 `konker.registry.data/src/main/java/com/konkerlabs/platform/registry/integration/endpoints/DeviceEventRestEndpoint.java: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 (11 lines × 2) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceConfigSetupServiceImpl.java:91— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceConfigSetupServiceImpl.java:91-101 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceConfigSetupServiceImpl.java:140-150 — 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 `konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceConfigSetupServiceImpl.java:91` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (11 lines × 2) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceFirmwareUpdateServiceImpl.java:71— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceFirmwareUpdateServiceImpl.java:71-81 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceFirmwareUpdateServiceImpl.java:102-112 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11 lines × 2) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceRegisterServiceImpl.java:158— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceRegisterServiceImpl.java:158-168 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceRegisterServiceImpl.java:625-635 — 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 `konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceRegisterServiceImpl.java:158` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11 lines × 2) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/HealthAlertServiceImpl.java:270— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/HealthAlertServiceImpl.java:270-280 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/HealthAlertServiceImpl.java:406-416 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/LocationSearchServiceImpl.java:243— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/LocationSearchServiceImpl.java:243-253 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/LocationSearchServiceImpl.java:266-276 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11 lines × 2) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/api/UserNotificationServiceImpl.java:81— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/api/UserNotificationServiceImpl.java:81-91 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/api/UserNotificationServiceImpl.java:123-133 — 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 `konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/api/UserNotificationServiceImpl.java:81` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11 lines × 2) konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/services/publishers/EventPublisherDevice.java:60— konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/services/publishers/EventPublisherDevice.java:60-70 | konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/services/publishers/EventPublisherModelLocation.java:77-87 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/services/publishers/EventPublisherDevice.java:60` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) konker.registry.data/src/main/java/com/konkerlabs/platform/registry/integration/processors/GatewayEventProcessor.java:81— konker.registry.data/src/main/java/com/konkerlabs/platform/registry/integration/processors/GatewayEventProcessor.java:81-91 | konker.registry.data/src/main/java/com/konkerlabs/platform/registry/integration/processors/GatewayEventProcessor.java:149-159 — 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 `konker.registry.data/src/main/java/com/konkerlabs/platform/registry/integration/processors/GatewayEventProcessor.java:81` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) konker.registry.web/src/main/java/com/konkerlabs/platform/registry/web/csv/CsvDownload.java:38— konker.registry.web/src/main/java/com/konkerlabs/platform/registry/web/csv/CsvDownload.java:38-48 | konker.registry.web/src/main/java/com/konkerlabs/platform/registry/web/csv/EventCsvDownload.java:108-118 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `konker.registry.web/src/main/java/com/konkerlabs/platform/registry/web/csv/CsvDownload.java:38` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `clazz` to `Class<T>` in one and `Class<EventDecorator>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (5 lines × 2) konker.registry.services.storage.mongodb/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/EventRepositoryMongoImpl.java:176— konker.registry.services.storage.mongodb/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/EventRepositoryMongoImpl.java:176-180 | konker.registry.services.storage.mongodb/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/EventRepositoryMongoImpl.java:191-196 — 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 `konker.registry.services.storage.mongodb/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/EventRepositoryMongoImpl.java:176` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) REDACTED:119— REDACTED:119-123 | REDACTED:125-129 — 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 `REDACTED:119` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) konker.registry.data/src/main/java/com/konkerlabs/platform/registry/data/upload/AwsUploadRepository.java:178— konker.registry.data/src/main/java/com/konkerlabs/platform/registry/data/upload/AwsUploadRepository.java:178-182 | konker.registry.web/src/main/java/com/konkerlabs/platform/registry/business/repositories/upload/AwsUploadRepository.java:231-235 — before extracting anything, compare `konker.registry.data/src/main/java/com/konkerlabs/platform/registry/data/upload/AwsUploadRepository.java` and `konker.registry.web/src/main/java/com/konkerlabs/platform/registry/business/repositories/upload/AwsUploadRepository.java` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 65 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (5 lines × 2) konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/integration/processors/DeviceEventProcessor.java:91— konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/integration/processors/DeviceEventProcessor.java:91-95 | konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/integration/processors/DeviceEventProcessor.java:112-116 — 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, `konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/integration/processors/DeviceEventProcessor.java:97` calls `getJsonPayload` and `konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/integration/processors/DeviceEventProcessor.java:118` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (5 lines × 2) konker.registry.data/src/main/java/com/konkerlabs/platform/registry/integration/endpoints/DeviceEventRestEndpoint.java:159— konker.registry.data/src/main/java/com/konkerlabs/platform/registry/integration/endpoints/DeviceEventRestEndpoint.java:159-163 | konker.registry.data/src/main/java/com/konkerlabs/platform/registry/integration/endpoints/DeviceEventRestEndpoint.java:195-199 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `konker.registry.data/src/main/java/com/konkerlabs/platform/registry/integration/endpoints/DeviceEventRestEndpoint.java:165` calls `isValidMgmtChannel`, `buildResponse`, `getCode` and `konker.registry.data/src/main/java/com/konkerlabs/platform/registry/integration/endpoints/DeviceEventRestEndpoint.java:201` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (5 lines × 2) konker.registry.idm.resourceserver/src/main/java/com/konkerlabs/platform/registry/business/model/OauthClientDetails.java:340— konker.registry.idm.resourceserver/src/main/java/com/konkerlabs/platform/registry/business/model/OauthClientDetails.java:340-344 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/model/User.java:82-86 — 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 (5 lines × 2) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/api/BaseEventRepositoryImpl.java:162— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/api/BaseEventRepositoryImpl.java:162-166 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/api/BaseEventRepositoryImpl.java:174-178 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) konker.security/src/main/java/com/konkerlabs/platform/security/crypto/BCrypt.java:494— konker.security/src/main/java/com/konkerlabs/platform/security/crypto/BCrypt.java:494-498 | konker.security/src/main/java/com/konkerlabs/platform/security/crypto/BCrypt.java:501-505 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) REDACTED:7— REDACTED:7-11 | REDACTED:7-11 — 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.
TodoComment konker.registry.web/src/main/java/com/konkerlabs/platform/registry/web/forms/TransformationForm.java:18— // colocar guid? TODO — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment konker.registry.web/src/main/java/com/konkerlabs/platform/registry/web/controllers/UserNotificationController.java:145— // TODO: check error — 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 konker.registry.services.core/src/test/java/com/konkerlabs/platform/registry/test/business/model/RestDestinationTest.java:105— // TODO: Reactivate this test on model i18n refactoring — 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 konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/api/AbstractURLBlacklistValidation.java:8— // TODO: implement — 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 konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/api/DeviceRegisterService.java:214— // TODO: should be moved to a KEYs service — 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 konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/api/UserNotificationServiceImpl.java:106— // TODO: improve efficiency. We should not iterate on the application - — 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 konker.registry.data.processor/src/test/java/com/konkerlabs/platform/registry/test/data/services/EventRouteServiceTest.java:482— //TODO Verify this constraint for effectiveness — 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 konker.registry.data/src/test/java/com/konkerlabs/platform/registry/test/data/services/EventRouteServiceTest.java:484— //TODO Verify this constraint for effectiveness — 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.
Duplicated block (12 lines × 2) konker.registry.idm.resourceserver/src/main/java/com/konkerlabs/platform/registry/idm/services/OAuthClientDetailsService.java:304— konker.registry.idm.resourceserver/src/main/java/com/konkerlabs/platform/registry/idm/services/OAuthClientDetailsService.java:304-315 | konker.registry.idm.resourceserver/src/main/java/com/konkerlabs/platform/registry/idm/services/OAuthClientDetailsService.java:333-344 — 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 `konker.registry.idm.resourceserver/src/main/java/com/konkerlabs/platform/registry/idm/services/OAuthClientDetailsService.java:304` 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) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceCustomDataServiceImpl.java:117— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceCustomDataServiceImpl.java:117-128 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceCustomDataServiceImpl.java:145-156 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceCustomDataServiceImpl.java:117` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (12 lines × 2) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/PrivateStorageServiceImpl.java:204— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/PrivateStorageServiceImpl.java:204-215 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/PrivateStorageServiceImpl.java:282-293 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/PrivateStorageServiceImpl.java:295` calls `ofNullable`, `isPresent` and `konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/PrivateStorageServiceImpl.java:217` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (12 lines × 2) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/UserServiceImpl.java:417— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/UserServiceImpl.java:417-428 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/UserServiceImpl.java:528-539 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) konker.registry.services.storage.cassandra/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/EventRepositoryCassandraImpl.java:517— konker.registry.services.storage.cassandra/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/EventRepositoryCassandraImpl.java:517-528 | konker.registry.services.storage.cassandra/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/EventRepositoryCassandraImpl.java:555-566 — 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 `konker.registry.services.storage.cassandra/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/EventRepositoryCassandraImpl.java:517` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) konker.registry.services.storage.cassandra/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/EventRepositoryCassandraImpl.java:538— konker.registry.services.storage.cassandra/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/EventRepositoryCassandraImpl.java:538-549 | konker.registry.services.storage.cassandra/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/EventRepositoryCassandraImpl.java:573-584 — 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 `konker.registry.services.storage.cassandra/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/EventRepositoryCassandraImpl.java:538` 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, `konker.registry.services.storage.cassandra/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/EventRepositoryCassandraImpl.java:536` calls `add` and `konker.registry.services.storage.cassandra/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/EventRepositoryCassandraImpl.java:571` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (12 lines × 2) REDACTED:181— REDACTED:181-192 | REDACTED:206-217 — 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 `REDACTED:181` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (12 lines × 2) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceModelServiceImpl.java:334— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceModelServiceImpl.java:334-345 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceModelServiceImpl.java:366-377 — 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 `konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceModelServiceImpl.java:334` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 2) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/model/Gateway.java:71— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/model/Gateway.java:71-77 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/model/Location.java:82-88 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (7 lines × 2) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/AlertTriggerServiceImpl.java:48— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/AlertTriggerServiceImpl.java:48-54 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/AlertTriggerServiceImpl.java:66-72 — 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 `konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/AlertTriggerServiceImpl.java:48` 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 (7 lines × 2) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceEventServiceImpl.java:66— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceEventServiceImpl.java:66-72 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceEventServiceImpl.java:155-161 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 2) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceModelServiceImpl.java:348— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceModelServiceImpl.java:348-354 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceModelServiceImpl.java:380-386 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceModelServiceImpl.java:348` 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 2) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/HealthAlertServiceImpl.java:352— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/HealthAlertServiceImpl.java:352-358 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/HealthAlertServiceImpl.java:393-399 — 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 `konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/HealthAlertServiceImpl.java:352` 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 2) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/RestDestinationServiceImpl.java:112— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/RestDestinationServiceImpl.java:112-118 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/RestDestinationServiceImpl.java:176-182 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 2) konker.registry.web/src/main/java/com/konkerlabs/platform/registry/idm/web/controllers/AccountClientsController.java:198— konker.registry.web/src/main/java/com/konkerlabs/platform/registry/idm/web/controllers/AccountClientsController.java:198-204 | konker.registry.web/src/main/java/com/konkerlabs/platform/registry/idm/web/controllers/AccountClientsController.java:272-278 — 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 `konker.registry.web/src/main/java/com/konkerlabs/platform/registry/idm/web/controllers/AccountClientsController.java:198` 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 lines × 2) konker.security/src/main/java/com/konkerlabs/platform/security/crypto/BCrypt.java:547— konker.security/src/main/java/com/konkerlabs/platform/security/crypto/BCrypt.java:547-553 | konker.security/src/main/java/com/konkerlabs/platform/security/crypto/BCrypt.java:576-582 — 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 `konker.security/src/main/java/com/konkerlabs/platform/security/crypto/BCrypt.java:547` 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, `konker.security/src/main/java/com/konkerlabs/platform/security/crypto/BCrypt.java:583` calls `streamtoword` and `konker.security/src/main/java/com/konkerlabs/platform/security/crypto/BCrypt.java:554` 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.
Outbound HTTP without resilience konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/config/RestTemplateConfig.java:14— `new RestTemplate(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience konker.registry.cassandra-etl/src/main/java/org/konker/registry/cassandraetl/config/RestTemplateEtlConfig.java:12— `new RestTemplate(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/config/IntegrationConfig.java:40— `new RestTemplate(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience konker.registry.web/src/main/java/com/konkerlabs/platform/registry/config/RestTemplateConfig.java:12— `new RestTemplate(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience konker.registry.web/src/main/java/com/konkerlabs/platform/registry/web/services/CaptchaRestClient.java:25— `.openConnection(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience REDACTED:14— `requests.get(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience REDACTED:16— `requests.post(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience REDACTED:18— `requests.put(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
AC4 · Keyboard semantics· Anchor without href · ×7
Anchor without href konker.registry.web/src/main/webapp/views/destinations/rest/form.html:184— An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
Anchor without href konker.registry.web/src/main/webapp/views/devices/events.html:188— An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
Anchor without href konker.registry.web/src/main/webapp/views/devices/form.html:97— An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
Anchor without href konker.registry.web/src/main/webapp/views/idm/clients/show.html:81— An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
Anchor without href konker.registry.web/src/main/webapp/views/login.html:93— An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
Anchor without href konker.registry.web/src/main/webapp/views/routes/form.html:166— An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
Anchor without href konker.registry.web/src/main/webapp/views/transformations/form.html:190— An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
AC4 · Keyboard semantics· Modal dialog does not manage focus · ×7
Modal dialog does not manage focus konker.registry.web/src/main/webapp/views/destinations/rest/form.html:190— This <div role="dialog"> is a modal dialog, but focus is moved into it, but nothing keeps it there: Tab walks out to the page behind, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close.
Modal dialog does not manage focus konker.registry.web/src/main/webapp/views/devices/form.html:103— This <div role="dialog"> is a modal dialog, but focus is moved into it, but nothing keeps it there: Tab walks out to the page behind, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close.
Modal dialog does not manage focus konker.registry.web/src/main/webapp/views/payment/checkout.html:338— This <div role="dialog"> is a modal dialog, but nothing moves focus into it when it opens and nothing keeps focus inside it while it is open, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close.
Modal dialog does not manage focus konker.registry.web/src/main/webapp/views/payment/plans.html:140— This <div role="dialog"> is a modal dialog, but nothing moves focus into it when it opens and nothing keeps focus inside it while it is open, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close.
Modal dialog does not manage focus konker.registry.web/src/main/webapp/views/routes/form.html:172— This <div role="dialog"> is a modal dialog, but nothing moves focus into it when it opens and nothing keeps focus inside it while it is open, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close.
Modal dialog does not manage focus konker.registry.web/src/main/webapp/views/users/userdialog.html:7— This <div role="dialog"> is a modal dialog, but nothing moves focus into it when it opens and nothing keeps focus inside it while it is open, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close.
Modal dialog does not manage focus konker.registry.web/src/main/webapp/views/users/userdialog.html:25— This <div role="dialog"> is a modal dialog, but nothing moves focus into it when it opens and nothing keeps focus inside it while it is open, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close.
Duplicated block (13 lines × 2) konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/exceptions/BadRequestResponseException.java:20— konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/exceptions/BadRequestResponseException.java:20-32 | konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/exceptions/NotAuthorizedResponseException.java:18-30 — before extracting anything, compare `konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/exceptions/BadRequestResponseException.java` and `konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/exceptions/NotAuthorizedResponseException.java` as WHOLE FILES: 90% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/exceptions/BadRequestResponseException.java:34` calls `BadRequestResponseException` and `konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/exceptions/NotAuthorizedResponseException.java:32` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (13 lines × 2) konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/DeviceFirmwareUpdateRestController.java:86— konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/DeviceFirmwareUpdateRestController.java:86-98 | konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/DeviceFirmwareUpdateRestController.java:120-132 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/ApplicationDocumentStoreServiceImpl.java:118— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/ApplicationDocumentStoreServiceImpl.java:118-130 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/ApplicationDocumentStoreServiceImpl.java:147-159 — 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 `konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/ApplicationDocumentStoreServiceImpl.java:118` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (13 lines × 2) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceFirmwareUpdateServiceImpl.java:84— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceFirmwareUpdateServiceImpl.java:84-96 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceFirmwareUpdateServiceImpl.java:115-127 — 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 `konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceFirmwareUpdateServiceImpl.java:84` 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (13 lines × 2) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/PrivateStorageServiceImpl.java:173— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/PrivateStorageServiceImpl.java:173-185 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/PrivateStorageServiceImpl.java:236-248 — 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 `konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/PrivateStorageServiceImpl.java:173` 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 (13 lines × 2) konker.registry.services.storage.cassandra/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/EventRepositoryCassandraImpl.java:533— konker.registry.services.storage.cassandra/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/EventRepositoryCassandraImpl.java:533-545 | konker.registry.services.storage.cassandra/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/EventRepositoryCassandraImpl.java:630-642 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/model/RestDestination.java:127— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/model/RestDestination.java:127-139 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceConfigSetupServiceImpl.java:103-116 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (6 lines × 2) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/HealthAlertServiceImpl.java:300— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/HealthAlertServiceImpl.java:300-305 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/HealthAlertServiceImpl.java:488-493 — 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 `konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/HealthAlertServiceImpl.java:300` 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) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/TransformationServiceImpl.java:84— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/TransformationServiceImpl.java:84-89 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/TransformationServiceImpl.java:184-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 `konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/TransformationServiceImpl.java:84` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (6 lines × 2) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/model/DeviceModel.java:81— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/model/DeviceModel.java:81-86 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/model/Gateway.java:78-83 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/model/Gateway.java:75` calls `getTenant`, `put`, `getCode` and `konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/model/DeviceModel.java:79` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (6 lines × 2) konker.registry.idm.resourceserver/src/main/java/com/konkerlabs/platform/registry/idm/services/OAuthClientDetailsService.java:104— konker.registry.idm.resourceserver/src/main/java/com/konkerlabs/platform/registry/idm/services/OAuthClientDetailsService.java:104-109 | konker.security/src/main/java/com/konkerlabs/platform/security/managers/PasswordManager.java:219-224 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (6 lines × 2) konker.registry.api/src/main/java/com/konkerlabs/platform/registry/KonkerRegistryApiApplication.java:13— konker.registry.api/src/main/java/com/konkerlabs/platform/registry/KonkerRegistryApiApplication.java:13-18 | konker.registry.router/src/main/java/com/konkerlabs/platform/registry/KonkerRegistryDataRouterApplication.java:13-19 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (6 lines × 2) konker.registry.data/src/main/java/com/konkerlabs/platform/registry/data/upload/AwsUploadRepository.java:60— konker.registry.data/src/main/java/com/konkerlabs/platform/registry/data/upload/AwsUploadRepository.java:60-65 | konker.registry.web/src/main/java/com/konkerlabs/platform/registry/business/repositories/upload/AwsUploadRepository.java:66-71 — before extracting anything, compare `konker.registry.data/src/main/java/com/konkerlabs/platform/registry/data/upload/AwsUploadRepository.java` and `konker.registry.web/src/main/java/com/konkerlabs/platform/registry/business/repositories/upload/AwsUploadRepository.java` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 65 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 (6 lines × 2) REDACTED:10— REDACTED:10-15 | REDACTED:73-78 — 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.
Stateful singleton: EventRepositoryCassandraEtlImpl konker.registry.cassandra-etl/src/main/java/org/konker/registry/cassandraetl/repositories/EventRepositoryCassandraEtlImpl.java:25— `EventRepositoryCassandraEtlImpl` is a singleton (@Repository: the container shares one instance across every request thread) but mutates instance state outside any lock (insertIncomingMap; e.g. `insertIncomingMap` in `getInsertIncomingPreparedStatement` at line 63).
Stateful singleton: EqualizeCassandraTablesService konker.registry.cassandra-etl/src/main/java/org/konker/registry/cassandraetl/services/EqualizeCassandraTablesService.java:28— `EqualizeCassandraTablesService` is a singleton (@Service: the container shares one instance across every request thread) but mutates instance state outside any lock (maxSize; e.g. `maxSize` in `process` at line 74).
Stateful singleton: HttpGatewayImpl konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/integration/gateway/HttpGatewayImpl.java:22— `HttpGatewayImpl` is a singleton (@Component: the container shares one instance across every request thread) but mutates instance state outside any lock (defaultHeaders; e.g. `defaultHeaders` in `setUp` at line 98).
Stateful singleton: JedisTaskService konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/services/JedisTaskService.java:22— `JedisTaskService` is a singleton (@Service: the container shares one instance across every request thread) but mutates instance state outside any lock (response; e.g. `response` in `subscribeToChannel` at line 43).
Stateful singleton: UserServiceImpl konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/UserServiceImpl.java:35— `UserServiceImpl` is a singleton (@Service: the container shares one instance across every request thread) but mutates instance state outside any lock (passwordManager; e.g. `passwordManager` in `encodePassword` at line 581).
Stateful singleton: EventRepositoryCassandraImpl konker.registry.services.storage.cassandra/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/EventRepositoryCassandraImpl.java:34— `EventRepositoryCassandraImpl` is a singleton (@Repository: the container shares one instance across every request thread) but mutates instance state outside any lock (selectStatementCache, insertIncomingMap, insertOutgoingMap; e.g. `selectStatementCache` in `doFindBy` at line 265).
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×6
Members sharing a duplicated core (4 members, 50+ identical tokens) konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/services/publishers/EventPublisherAmazonKinesis.java:36— konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/services/publishers/EventPublisherAmazonKinesis.java:36-84 | konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/services/publishers/EventPublisherDevice.java:56-91 | konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/services/publishers/EventPublisherModelLocation.java:73-136 | konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/services/publishers/EventPublisherRest.java:58-113 — 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) konker.registry.data/src/main/java/com/konkerlabs/platform/registry/integration/endpoints/DeviceEventRestEndpoint.java:232— konker.registry.data/src/main/java/com/konkerlabs/platform/registry/integration/endpoints/DeviceEventRestEndpoint.java:232-264 | konker.registry.data/src/main/java/com/konkerlabs/platform/registry/integration/endpoints/DeviceEventRestEndpoint.java:271-309 | konker.registry.data/src/main/java/com/konkerlabs/platform/registry/integration/endpoints/DeviceEventRestEndpoint.java:329-383 | konker.registry.data/src/main/java/com/konkerlabs/platform/registry/integration/endpoints/DeviceEventRestEndpoint.java:390-440 — 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) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/audit/KonkerLogger.java:341— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/audit/KonkerLogger.java:341-352 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/audit/KonkerLogger.java:442-453 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/audit/KonkerLogger.java:499-510 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/audit/KonkerLogger.java:533-544 — 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) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceFirmwareServiceImpl.java:139— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceFirmwareServiceImpl.java:139-180 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceRegisterServiceImpl.java:747-776 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/GatewayServiceImpl.java:300-341 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/TenantLogServiceImpl.java:30-56 — 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) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/HealthAlertServiceImpl.java:157— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/HealthAlertServiceImpl.java:157-215 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/HealthAlertServiceImpl.java:218-258 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/HealthAlertServiceImpl.java:326-358 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/HealthAlertServiceImpl.java:362-399 — 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) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/LocationSearchServiceImpl.java:40— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/LocationSearchServiceImpl.java:40-72 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/LocationSearchServiceImpl.java:83-107 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/LocationSearchServiceImpl.java:184-209 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/LocationSearchServiceImpl.java:212-237 — 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 (12 corresponding lines) · ×6
Edited copy of a member (12 corresponding lines) REDACTED:292— REDACTED:292-303 | REDACTED:310-321 — 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) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/ApplicationServiceImpl.java:288— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/ApplicationServiceImpl.java:288-299 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceModelServiceImpl.java:303-317 — 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) konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/integration/converters/CBorJsonConverter.java:24— konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/integration/converters/CBorJsonConverter.java:24-35 | konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/integration/converters/CBorJsonConverter.java:38-49 — 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) konker.registry.idm.resourceserver/src/main/java/com/konkerlabs/platform/registry/idm/services/OAuthClientDetailsService.java:357— konker.registry.idm.resourceserver/src/main/java/com/konkerlabs/platform/registry/idm/services/OAuthClientDetailsService.java:357-368 | konker.registry.idm.resourceserver/src/main/java/com/konkerlabs/platform/registry/idm/services/OAuthClientDetailsService.java:371-382 — 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) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/audit/KonkerLogger.java:516— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/audit/KonkerLogger.java:516-527 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/audit/KonkerLogger.java:546-557 — 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) konker.utilities/src/main/java/com/konkerlabs/platform/utilities/parsers/json/JsonParsingServiceImpl.java:44— konker.utilities/src/main/java/com/konkerlabs/platform/utilities/parsers/json/JsonParsingServiceImpl.java:44-57 | konker.utilities/src/main/java/com/konkerlabs/platform/utilities/parsers/json/JsonParsingServiceImpl.java:60-71 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (15 lines × 2) konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/AbstractRestController.java:84— konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/AbstractRestController.java:84-98 | konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/DeviceCustomDataRestController.java:149-163 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/AbstractRestController.java:84` 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. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (15 lines × 2) konker.registry.cassandra-etl/src/main/java/org/konker/registry/cassandraetl/repositories/EventRepositoryCassandraEtlImpl.java:97— konker.registry.cassandra-etl/src/main/java/org/konker/registry/cassandraetl/repositories/EventRepositoryCassandraEtlImpl.java:97-111 | konker.registry.services.storage.cassandra/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/EventRepositoryCassandraImpl.java:248-262 — before extracting anything, compare `konker.registry.cassandra-etl/src/main/java/org/konker/registry/cassandraetl/repositories/EventRepositoryCassandraEtlImpl.java` and `konker.registry.services.storage.cassandra/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/EventRepositoryCassandraImpl.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 47 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `konker.registry.cassandra-etl/src/main/java/org/konker/registry/cassandraetl/repositories/EventRepositoryCassandraEtlImpl.java:97` 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. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (15 lines × 2) konker.registry.data/src/main/java/com/konkerlabs/platform/registry/integration/endpoints/DeviceEventRestEndpoint.java:233— konker.registry.data/src/main/java/com/konkerlabs/platform/registry/integration/endpoints/DeviceEventRestEndpoint.java:233-247 | konker.registry.data/src/main/java/com/konkerlabs/platform/registry/integration/endpoints/DeviceEventRestEndpoint.java:393-407 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `konker.registry.data/src/main/java/com/konkerlabs/platform/registry/integration/endpoints/DeviceEventRestEndpoint.java:391` calls `info` and `konker.registry.data/src/main/java/com/konkerlabs/platform/registry/integration/endpoints/DeviceEventRestEndpoint.java:232` 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 (15 lines × 2) konker.registry.data/src/main/java/com/konkerlabs/platform/registry/integration/endpoints/DeviceEventRestEndpoint.java:274— konker.registry.data/src/main/java/com/konkerlabs/platform/registry/integration/endpoints/DeviceEventRestEndpoint.java:274-288 | konker.registry.data/src/main/java/com/konkerlabs/platform/registry/integration/endpoints/DeviceEventRestEndpoint.java:330-344 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (15 lines × 2) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/GatewayServiceImpl.java:102— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/GatewayServiceImpl.java:102-116 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/GatewayServiceImpl.java:210-224 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15 lines × 2) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/ApplicationDocumentStoreServiceImpl.java:194— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/ApplicationDocumentStoreServiceImpl.java:194-208 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceCustomDataServiceImpl.java:189-203 — 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 3) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/audit/KonkerLogger.java:253— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/audit/KonkerLogger.java:253-259 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/audit/KonkerLogger.java:266-272 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/audit/KonkerLogger.java:279-285 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 3) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceConfigSetupServiceImpl.java:47— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceConfigSetupServiceImpl.java:47-53 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceConfigSetupServiceImpl.java:289-295 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceConfigSetupServiceImpl.java:317-323 — 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 `konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceConfigSetupServiceImpl.java:47` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 3) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceFirmwareUpdateServiceImpl.java:72— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceFirmwareUpdateServiceImpl.java:72-78 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceFirmwareUpdateServiceImpl.java:103-109 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceFirmwareUpdateServiceImpl.java:157-163 — 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 `konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceFirmwareUpdateServiceImpl.java:72` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 3) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/HealthAlertServiceImpl.java:269— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/HealthAlertServiceImpl.java:269-275 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/HealthAlertServiceImpl.java:293-299 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/HealthAlertServiceImpl.java:405-411 — 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 `konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/HealthAlertServiceImpl.java:269` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 3) konker.registry.services.storage.cassandra/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/EventRepositoryCassandraImpl.java:310— konker.registry.services.storage.cassandra/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/EventRepositoryCassandraImpl.java:310-316 | konker.registry.services.storage.cassandra/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/EventRepositoryCassandraImpl.java:320-326 | konker.registry.services.storage.cassandra/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/EventRepositoryCassandraImpl.java:328-334 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (7 lines × 3) konker.registry.services.storage.cassandra/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/EventRepositoryCassandraImpl.java:522— konker.registry.services.storage.cassandra/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/EventRepositoryCassandraImpl.java:522-528 | konker.registry.services.storage.cassandra/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/EventRepositoryCassandraImpl.java:560-566 | konker.registry.services.storage.cassandra/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/EventRepositoryCassandraImpl.java:594-600 — 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 `konker.registry.services.storage.cassandra/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/EventRepositoryCassandraImpl.java:522` 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.
X24 · Document value interpolated into markup unescaped· Untrusted text written into markup unescaped · ×6
Untrusted text written into markup unescaped konker.registry.web/src/main/webapp/resources/js/notifications/index.js:89— `Mustache.render($('#notification-template').html(),$.extend({},message,mustacheTranslation))` is text this program did not author, and it is written into the text of an element through the DOM library's `.html()` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped REDACTED:58— `result[0].message` is text this program did not author, and it is written into the text of an element through the DOM library's `.html()` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped REDACTED:189— `data` is text this program did not author, and it is written into the text of an element through the DOM library's `.html()` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js:793— `v==null?"":v` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js:797— `value` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped konker.registry.web/src/main/webapp/resources/konker/scripts/json.formatter.js:30— `unformattedJSON` is text this program did not author, and it is written into the text of an element through the DOM library's `.html()` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
AC6 · Visual & motion safety· Focus outline removed in CSS without a · ×5
Focus outline removed in CSS without a :focus replacement konker.registry.web/src/main/webapp/resources/konker/css/main.css:46— `.btn:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement konker.registry.web/src/main/webapp/resources/konker/css/main.css:875— `.sup-desc-wrap .sup-meta-wrap .sup-title` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement konker.registry.web/src/main/webapp/resources/konker/css/main.css:1351— `.form-control:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement konker.registry.web/src/main/webapp/resources/konker/css/main.css:1576— `.subscribe-box input[type="text"]` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement konker.registry.web/src/main/webapp/resources/konker/css/style.css:53— `.btn-link-1:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
migrate_beat_config_1_x_to_5_0.migrate_tls_settings (cyclomatic 24) konker.registry.api/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py:57— migrate_beat_config_1_x_to_5_0.migrate_tls_settings has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
migrate_beat_config_1_x_to_5_0.migrate_tls_settings (cyclomatic 24) konker.registry.data.processor/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py:57— migrate_beat_config_1_x_to_5_0.migrate_tls_settings has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
migrate_beat_config_1_x_to_5_0.migrate_tls_settings (cyclomatic 24) konker.registry.data/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py:57— migrate_beat_config_1_x_to_5_0.migrate_tls_settings has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
migrate_beat_config_1_x_to_5_0.migrate_tls_settings (cyclomatic 24) konker.registry.router/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py:57— migrate_beat_config_1_x_to_5_0.migrate_tls_settings has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
migrate_beat_config_1_x_to_5_0.migrate_tls_settings (cyclomatic 24) konker.registry.web/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py:57— migrate_beat_config_1_x_to_5_0.migrate_tls_settings has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
migrate_beat_config_1_x_to_5_0.migrate_tls_settings (cognitive 47) konker.registry.api/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py:57— migrate_beat_config_1_x_to_5_0.migrate_tls_settings has cognitive complexity 47 (threshold 15). Drivers by points: loops 7 (23 pts), if/else 10 (22 pts), boolean chains 2 (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.
migrate_beat_config_1_x_to_5_0.migrate_tls_settings (cognitive 47) konker.registry.data.processor/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py:57— migrate_beat_config_1_x_to_5_0.migrate_tls_settings has cognitive complexity 47 (threshold 15). Drivers by points: loops 7 (23 pts), if/else 10 (22 pts), boolean chains 2 (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.
migrate_beat_config_1_x_to_5_0.migrate_tls_settings (cognitive 47) konker.registry.data/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py:57— migrate_beat_config_1_x_to_5_0.migrate_tls_settings has cognitive complexity 47 (threshold 15). Drivers by points: loops 7 (23 pts), if/else 10 (22 pts), boolean chains 2 (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.
migrate_beat_config_1_x_to_5_0.migrate_tls_settings (cognitive 47) konker.registry.router/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py:57— migrate_beat_config_1_x_to_5_0.migrate_tls_settings has cognitive complexity 47 (threshold 15). Drivers by points: loops 7 (23 pts), if/else 10 (22 pts), boolean chains 2 (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.
migrate_beat_config_1_x_to_5_0.migrate_tls_settings (cognitive 47) konker.registry.web/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py:57— migrate_beat_config_1_x_to_5_0.migrate_tls_settings has cognitive complexity 47 (threshold 15). Drivers by points: loops 7 (23 pts), if/else 10 (22 pts), boolean chains 2 (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.
ClassTooLong: TimeZone konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/model/enumerations/TimeZone.java:5— ClassTooLong — 603 significant lines (blank, comment-only and punctuation-only lines excluded), 5 methods. The bar is 400 significant lines; this is 203 over it, 1.51× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: DeviceRegisterServiceImpl konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceRegisterServiceImpl.java:37— ClassTooLong — 511 significant lines (blank, comment-only and punctuation-only lines excluded), 20 methods. The bar is 400 significant lines; this is 111 over it, 1.28× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: UserServiceImpl konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/UserServiceImpl.java:35— ClassTooLong — 462 significant lines (blank, comment-only and punctuation-only lines excluded), 26 methods. The bar is 400 significant lines; this is 62 over it, 1.16× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: EventRepositoryCassandraImpl konker.registry.services.storage.cassandra/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/EventRepositoryCassandraImpl.java:34— ClassTooLong — 449 significant lines (blank, comment-only and punctuation-only lines excluded), 13 methods. The bar is 400 significant lines; this is 49 over it, 1.12× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: HealthAlertServiceImpl konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/HealthAlertServiceImpl.java:24— ClassTooLong — 443 significant lines (blank, comment-only and punctuation-only lines excluded), 15 methods. The bar is 400 significant lines; this is 43 over it, 1.11× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D4 · Code Duplication· Members sharing a duplicated core (5 members, 50+ identical tokens) · ×5
Members sharing a duplicated core (5 members, 50+ identical tokens) konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/ApplicationDocumentStoreRestController.java:145— konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/ApplicationDocumentStoreRestController.java:145-155 | konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/DeviceCredentialRestController.java:101-111 | konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/DeviceCustomDataRestController.java:166-176 | konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/DeviceRestController.java:278-296 | konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/DeviceStatusRestController.java:144-154 — These 5 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 5 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 5 times.
Members sharing a duplicated core (5 members, 50+ identical tokens) konker.registry.api/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py:33— konker.registry.api/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py:33-53 | konker.registry.data.processor/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py:33-53 | konker.registry.data/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py:33-53 | konker.registry.router/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py:33-53 | konker.registry.web/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py:33-53 — These 5 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 5 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 5 times.
Members sharing a duplicated core (5 members, 50+ identical tokens) konker.registry.api/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py:58— konker.registry.api/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py:58-201 | konker.registry.data.processor/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py:58-201 | konker.registry.data/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py:58-201 | konker.registry.router/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py:58-201 | konker.registry.web/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py:58-201 — These 5 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 5 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 5 times.
Members sharing a duplicated core (5 members, 50+ identical tokens) konker.registry.api/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py:207— konker.registry.api/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py:207-232 | konker.registry.data.processor/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py:207-232 | konker.registry.data/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py:207-232 | konker.registry.router/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py:207-232 | konker.registry.web/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py:207-232 — These 5 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 5 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 5 times.
Members sharing a duplicated core (5 members, 50+ identical tokens) konker.registry.api/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py:277— konker.registry.api/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py:277-304 | konker.registry.data.processor/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py:277-304 | konker.registry.data/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py:277-304 | konker.registry.router/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py:277-304 | konker.registry.web/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py:277-304 — These 5 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 5 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 5 times.
D4 · Code Duplication· Edited copy of a member (22 corresponding lines) · ×5
Edited copy of a member (22 corresponding lines) konker.registry.web/src/main/java/com/konkerlabs/platform/registry/web/csv/CsvDownload.java:37— konker.registry.web/src/main/java/com/konkerlabs/platform/registry/web/csv/CsvDownload.java:37-58 | konker.registry.web/src/main/java/com/konkerlabs/platform/registry/web/csv/EventCsvDownload.java:107-130 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (22 corresponding lines) konker.registry.idm.resourceserver/src/main/java/com/konkerlabs/platform/registry/idm/services/OAuthClientDetailsService.java:294— konker.registry.idm.resourceserver/src/main/java/com/konkerlabs/platform/registry/idm/services/OAuthClientDetailsService.java:294-315 | konker.registry.idm.resourceserver/src/main/java/com/konkerlabs/platform/registry/idm/services/OAuthClientDetailsService.java:318-344 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (22 corresponding lines) konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/integration/converters/MessagePackJsonConverter.java:25— konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/integration/converters/MessagePackJsonConverter.java:25-46 | konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/integration/converters/MessagePackJsonConverter.java:49-70 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (22 corresponding lines) REDACTED:180— REDACTED:180-201 | REDACTED:205-229 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (22 corresponding lines) konker.scripts/registry/set_location_device_mode_to_devices.py:17— konker.scripts/registry/set_location_device_mode_to_devices.py:17-39 | konker.scripts/registry/set_location_device_mode_to_devices.py:42-63 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (11 corresponding lines) · ×5
Edited copy of a member (11 corresponding lines) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/AlertTriggerServiceImpl.java:23— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/AlertTriggerServiceImpl.java:23-35 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceRegisterServiceImpl.java:227-237 — 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) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/config/SpringMailConfig.java:71— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/config/SpringMailConfig.java:71-81 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/config/SpringMailConfig.java:83-93 — 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) konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/wrapper/CrudResponseAdvice.java:66— konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/wrapper/CrudResponseAdvice.java:66-76 | konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/wrapper/CrudResponseAdvice.java:95-111 — 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) konker.scripts/registry/users/create_user_roles.py:11— konker.scripts/registry/users/create_user_roles.py:11-21 | konker.scripts/registry/users/create_user_roles.py:24-36 — 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) konker.samples/smart-temperature/dao/act.py:30— konker.samples/smart-temperature/dao/act.py:30-40 | konker.samples/smart-temperature/dao/pid.py:73-90 — 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 (5 lines × 3) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/EventRouteServiceImpl.java:136— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/EventRouteServiceImpl.java:136-144 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/EventRouteServiceImpl.java:339-343 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/EventRouteServiceImpl.java:381-385 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/EventRouteServiceImpl.java:377` calls `ofNullable`, `isPresent`, `error` and `konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/EventRouteServiceImpl.java:337` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (5 lines × 3) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/GatewayServiceImpl.java:108— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/GatewayServiceImpl.java:108-116 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/GatewayServiceImpl.java:190-194 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/GatewayServiceImpl.java:216-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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (5 lines × 3) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/TransformationServiceImpl.java:58— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/TransformationServiceImpl.java:58-62 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/TransformationServiceImpl.java:127-131 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/TransformationServiceImpl.java:152-156 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (5 lines × 3) konker.registry.data.processor/src/main/java/com/konkerlabs/platform/registry/integration/endpoints/ApplicationEventRestEndpoint.java:74— konker.registry.data.processor/src/main/java/com/konkerlabs/platform/registry/integration/endpoints/ApplicationEventRestEndpoint.java:74-78 | konker.registry.data/src/main/java/com/konkerlabs/platform/registry/integration/endpoints/DeviceEventRestEndpoint.java:145-149 | konker.registry.data/src/main/java/com/konkerlabs/platform/registry/integration/endpoints/GatewayEventRestEndpoint.java:101-105 — 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (5 lines × 3) konker.registry.data.processor/src/main/java/com/konkerlabs/platform/registry/integration/endpoints/ApplicationEventRestEndpoint.java:99— konker.registry.data.processor/src/main/java/com/konkerlabs/platform/registry/integration/endpoints/ApplicationEventRestEndpoint.java:99-103 | konker.registry.data/src/main/java/com/konkerlabs/platform/registry/integration/endpoints/GatewayEventRestEndpoint.java:116-120 | konker.registry.data/src/main/java/com/konkerlabs/platform/registry/integration/endpoints/GatewayEventRestEndpoint.java:184-188 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Low contrast colour pair in CSS (3.4:1) konker.registry.web/src/main/webapp/resources/konker/css/style2.css:249— `.btn-theme02:hover, .btn-theme02:focus, .btn-theme02:active, .btn-theme02.active, .open .dropdown-toggle.btn-theme02` sets color: #fff on background-color: #967adc — 3.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (3.4:1) konker.registry.web/src/main/webapp/resources/bootstrap/css/bootstrap.css:3182— `.btn-success:focus, .btn-success.focus` sets color: #fff on background-color: #449d44 — 3.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (3.4:1) konker.registry.web/src/main/webapp/resources/bootstrap/css/bootstrap.css:3187— `.btn-success:hover` sets color: #fff on background-color: #449d44 — 3.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (3.4:1) konker.registry.web/src/main/webapp/resources/bootstrap/css/bootstrap.css:3194— `.btn-success:active, .btn-success.active, .open > .dropdown-toggle.btn-success` sets color: #fff on background-color: #449d44 — 3.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
D4 · Code Duplication· Edited copy of a member (16 corresponding lines) · ×4
Edited copy of a member (16 corresponding lines) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/AlertTriggerServiceImpl.java:39— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/AlertTriggerServiceImpl.java:39-54 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/AlertTriggerServiceImpl.java:57-72 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (16 corresponding lines) konker.registry.idm.resourceserver/src/main/java/com/konkerlabs/platform/registry/idm/services/MongoTokenStore.java:105— konker.registry.idm.resourceserver/src/main/java/com/konkerlabs/platform/registry/idm/services/MongoTokenStore.java:105-120 | konker.registry.idm.resourceserver/src/main/java/com/konkerlabs/platform/registry/idm/services/MongoTokenStore.java:133-148 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (16 corresponding lines) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/storage/repositories/PrivateStorageRepository.java:163— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/storage/repositories/PrivateStorageRepository.java:163-180 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/storage/repositories/PrivateStorageRepository.java:182-197 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (16 corresponding lines) konker.scripts/registry/dao/registry.py:234— konker.scripts/registry/dao/registry.py:234-249 | konker.scripts/registry/dao/registry.py:252-267 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (15 corresponding lines) · ×4
Edited copy of a member (15 corresponding lines) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/EventSchemaServiceImpl.java:291— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/EventSchemaServiceImpl.java:291-305 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/EventSchemaServiceImpl.java:308-325 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) REDACTED:57— REDACTED:57-71 | REDACTED:103-117 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) REDACTED:100— REDACTED:100-115 | REDACTED:162-176 — 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) konker.registry.idm.resourceserver/src/main/java/com/konkerlabs/platform/registry/idm/services/MongoTokenStore.java:168— konker.registry.idm.resourceserver/src/main/java/com/konkerlabs/platform/registry/idm/services/MongoTokenStore.java:168-183 | konker.registry.idm.resourceserver/src/main/java/com/konkerlabs/platform/registry/idm/services/MongoTokenStore.java:201-215 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (9 lines × 3) konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/DeviceModelRestController.java:169— konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/DeviceModelRestController.java:169-177 | konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/DeviceRestController.java:207-215 | konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/GatewayRestController.java:209-217 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
Duplicated block (9 lines × 3) konker.registry.data.processor/src/main/java/com/konkerlabs/platform/registry/integration/endpoints/ApplicationEventRestEndpoint.java:107— konker.registry.data.processor/src/main/java/com/konkerlabs/platform/registry/integration/endpoints/ApplicationEventRestEndpoint.java:107-115 | konker.registry.data/src/main/java/com/konkerlabs/platform/registry/integration/endpoints/DeviceEventRestEndpoint.java:173-181 | konker.registry.data/src/main/java/com/konkerlabs/platform/registry/integration/endpoints/DeviceEventRestEndpoint.java:217-225 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `konker.registry.data.processor/src/main/java/com/konkerlabs/platform/registry/integration/endpoints/ApplicationEventRestEndpoint.java:107` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 3) konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/IncomingEventsRestController.java:122— konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/IncomingEventsRestController.java:122-130 | konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/OutgoingEventsRestController.java:95-103 | konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/SendEventsRestController.java:96-104 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
Duplicated block (9 lines × 3) konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/DeviceConfigRestController.java:176— konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/DeviceConfigRestController.java:176-184 | konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/LocationRestController.java:382-390 | konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/RestDestinationController.java:193-202 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Note first that the copies are not typed on the same thing: `Validations` names `com.konkerlabs.platform.registry.business.model.Location.Validations` in one and `com.konkerlabs.platform.registry.business.model.RestDestination.Validations` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Off the main sequence: konker.security — konker.security: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: konker.registry.services.storage.cassandra — konker.registry.services.storage.cassandra: abstractness 0.00, instability 0.13, distance 0.88 — zone of pain — concrete and depended on by 7 project(s), so it's rigid to change.
Off the main sequence: konker.registry.services.storage.mongodb — konker.registry.services.storage.mongodb: abstractness 0.00, instability 0.13, distance 0.88 — zone of pain — concrete and depended on by 7 project(s), so it's rigid to change.
Off the main sequence: konker.utilities — konker.utilities: abstractness 0.27, instability 0.00, distance 0.73 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Swallowed exception (empty catch) konker.registry.web/src/main/webapp/resources/konker/scripts/json.formatter.js:18— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) REDACTED:52— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) REDACTED:1801— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) konker.registry.idm.resourceserver/src/main/java/com/konkerlabs/platform/registry/idm/security/OauthClientDetailsContextResolver.java:32— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Low contrast colour pair in CSS (1.9:1) konker.registry.web/src/main/webapp/resources/konker/css/create-account.css:129— `.btn-menu a:hover` sets color: #90161d on background-color: #e30613 — 1.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (1.9:1) konker.registry.web/src/main/webapp/resources/konker/css/style2.css:140— `.table-hover > tbody > tr:hover td` sets color: #fff on background-color: #50c8ea — 1.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (1.9:1) konker.registry.web/src/main/webapp/resources/konker/css/style2.css:412— `.profile-info.dropdown .dropdown-menu li a:hover` sets color: #FFF on background-color: #50c8ea — 1.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (2.4:1) konker.registry.web/src/main/webapp/resources/konker/css/style2.css:264— `.btn-theme03:hover, .btn-theme03:focus, .btn-theme03:active, .btn-theme03.active, .open .dropdown-toggle.btn-theme03` sets color: #fff on background-color: #37bc9b — 2.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (2.4:1) konker.registry.web/src/main/webapp/resources/konker/css/style2.css:1192— `.ds h3` sets color: #ffffff on background-color: #ff865c — 2.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (2.4:1) konker.registry.web/src/main/webapp/resources/konker/css/style2.css:2167— `.btn-twitter:hover, .btn-twitter:focus, .btn-twitter:active, .btn-twitter.active, .open .dropdown-toggle.btn-twitter` sets color: #fff on background-color: #2bb4e8 — 2.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (2.5:1) konker.registry.web/src/main/webapp/resources/bootstrap/css/bootstrap.css:3176— `.btn-success` sets color: #fff on background-color: #5cb85c — 2.5:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (2.5:1) konker.registry.web/src/main/webapp/resources/bootstrap/css/bootstrap.css:3229— `.btn-success .badge` sets color: #5cb85c on background-color: #fff — 2.5:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (2.5:1) konker.registry.web/src/main/webapp/resources/bootstrap/css/bootstrap.css:3251— `.btn-info:active, .btn-info.active, .open > .dropdown-toggle.btn-info` sets color: #fff on background-color: #31b0d5 — 2.5:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
FileTooLong: scripts/d3.js konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js— FileTooLong — 7480 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 6980 over it, 14.96× 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: enumerations/TimeZone.java konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/model/enumerations/TimeZone.java— FileTooLong — 605 significant lines (blank, comment-only and punctuation-only lines excluded), about 100% of them inside a single declaration: TimeZone (5-620). The bar is 500 significant lines; this is 105 over it, 1.21× 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: services/DeviceRegisterServiceImpl.java konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceRegisterServiceImpl.java— FileTooLong — 544 significant lines (blank, comment-only and punctuation-only lines excluded), about 94% of them inside a single declaration: DeviceRegisterServiceImpl (37-794). The bar is 500 significant lines; this is 44 over it, 1.09× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
TooManyMethods: KonkerLogger konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/audit/KonkerLogger.java:24— TooManyMethods — 97 methods. The bar is 30 methods; this is 67 over it, 3.23× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: OauthClientDetails konker.registry.idm.resourceserver/src/main/java/com/konkerlabs/platform/registry/business/model/OauthClientDetails.java:22— TooManyMethods — 58 methods. The bar is 30 methods; this is 28 over it, 1.93× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: KonkerLoggerContext konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/audit/KonkerLoggerContext.java:21— TooManyMethods — 38 methods. The bar is 30 methods; this is 8 over it, 1.27× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D4 · Code Duplication· Edited copy of a member (24 corresponding lines) · ×3
Edited copy of a member (24 corresponding lines) konker.registry.data.processor/src/main/java/com/konkerlabs/platform/registry/integration/endpoints/ApplicationEventRestEndpoint.java:85— konker.registry.data.processor/src/main/java/com/konkerlabs/platform/registry/integration/endpoints/ApplicationEventRestEndpoint.java:85-115 | konker.registry.data/src/main/java/com/konkerlabs/platform/registry/integration/endpoints/DeviceEventRestEndpoint.java:158-181 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (24 corresponding lines) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/LocationServiceImpl.java:250— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/LocationServiceImpl.java:250-273 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/LocationServiceImpl.java:275-302 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (24 corresponding lines) REDACTED:237— REDACTED:237-260 | REDACTED:137-160 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (21 corresponding lines) · ×3
Edited copy of a member (21 corresponding lines) konker.security/src/main/java/com/konkerlabs/platform/security/crypto/BCrypt.java:544— konker.security/src/main/java/com/konkerlabs/platform/security/crypto/BCrypt.java:544-564 | konker.security/src/main/java/com/konkerlabs/platform/security/crypto/BCrypt.java:573-597 — 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) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/ApplicationDocumentStoreServiceImpl.java:116— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/ApplicationDocumentStoreServiceImpl.java:116-141 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/ApplicationDocumentStoreServiceImpl.java:145-165 — 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) konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/DeviceCredentialRestController.java:46— konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/DeviceCredentialRestController.java:46-68 | konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/DeviceCredentialRestController.java:78-98 — 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 (19 corresponding lines) · ×3
Edited copy of a member (19 corresponding lines) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/api/UserNotificationServiceImpl.java:80— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/api/UserNotificationServiceImpl.java:80-98 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/api/UserNotificationServiceImpl.java:122-145 — 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) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceCustomDataServiceImpl.java:115— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceCustomDataServiceImpl.java:115-139 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceCustomDataServiceImpl.java:143-161 — 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) konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/GatewayRestController.java:252— konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/GatewayRestController.java:252-272 | konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/UserRestController.java:186-204 — 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 (10 corresponding lines) · ×3
Edited copy of a member (10 corresponding lines) konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/config/RedisConfig.java:32— konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/config/RedisConfig.java:32-41 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/config/RedisCacheConfig.java:37-47 — 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) REDACTED:119— REDACTED:119-128 | REDACTED:145-155 — 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) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/ApplicationServiceImpl.java:160— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/ApplicationServiceImpl.java:160-169 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/LocationSearchServiceImpl.java:109-123 — 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 (14 corresponding lines) · ×3
Edited copy of a member (14 corresponding lines) konker.registry.idm.resourceserver/src/main/java/com/konkerlabs/platform/registry/idm/services/MongoTokenStore.java:228— konker.registry.idm.resourceserver/src/main/java/com/konkerlabs/platform/registry/idm/services/MongoTokenStore.java:228-241 | konker.registry.idm.resourceserver/src/main/java/com/konkerlabs/platform/registry/idm/services/MongoTokenStore.java:244-257 — 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) konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/DeviceConfigRestController.java:55— konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/DeviceConfigRestController.java:55-68 | konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/RestDestinationController.java:52-65 — 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) konker.registry.web/src/main/java/com/konkerlabs/platform/registry/web/services/UploadServiceImpl.java:47— konker.registry.web/src/main/java/com/konkerlabs/platform/registry/web/services/UploadServiceImpl.java:47-60 | konker.registry.web/src/main/java/com/konkerlabs/platform/registry/web/services/UploadServiceImpl.java:81-94 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (16 lines × 2) konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/IncomingEventsRestController.java:85— konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/IncomingEventsRestController.java:85-100 | konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/OutgoingEventsRestController.java:67-82 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/IncomingEventsRestController.java:82` calls `ofNullable`, `getParentUser`, `orElseGet` and `konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/OutgoingEventsRestController.java:65` 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 (16 lines × 2) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/ApplicationDocumentStoreServiceImpl.java:37— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/ApplicationDocumentStoreServiceImpl.java:37-52 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/ApplicationDocumentStoreServiceImpl.java:77-92 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (16 lines × 2) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceConfigSetupServiceImpl.java:66— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceConfigSetupServiceImpl.java:66-81 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceConfigSetupServiceImpl.java:121-136 — 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 `konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceConfigSetupServiceImpl.java:66` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12–13 lines × 2) konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/PrivateStorageRestController.java:113— konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/PrivateStorageRestController.java:113-124 | konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/PrivateStorageRestController.java:157-169 — 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 `konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/PrivateStorageRestController.java: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 (12–13 lines × 2) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/ApplicationServiceImpl.java:225— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/ApplicationServiceImpl.java:225-237 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/ApplicationServiceImpl.java:303-314 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12–13 lines × 2) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/HealthAlertServiceImpl.java:159— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/HealthAlertServiceImpl.java:159-171 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/HealthAlertServiceImpl.java:364-375 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/HealthAlertServiceImpl.java:159` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
AC3 · Page structure· Data table has no header cells · ×2
Data table has no header cells konker.registry.web/src/main/webapp/views/destinations/rest/form.html:97— A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
Data table has no header cells konker.registry.web/src/main/webapp/views/destinations/rest/show.html:63— A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
Low contrast colour pair in CSS (3.3:1) konker.registry.web/src/main/webapp/resources/konker/css/form-elements.css:5— `input[type="text"], input[type="password"], textarea, textarea.form-control` sets color: #888 on background-color: #f8f8f8 — 3.3:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (3.3:1) konker.registry.web/src/main/webapp/resources/bootstrap/css/bootstrap.css:3264— `.btn-info:active:hover, .btn-info.active:hover, .open > .dropdown-toggle.btn-info:hover, .btn-info:active:focus, .btn-info.active:focus, .open > .dropdown-toggle.btn-info:focus, .btn-info:active.focus, .btn-info.active.focus, .open > .dropdown-toggle.btn-info.focus` sets color: #fff on background-color: #269abc — 3.3:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (3.9:1) konker.registry.web/src/main/webapp/resources/konker/css/style2.css:43— `body` sets color: #797979 on background-color: #f2f2f2 — 3.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (3.9:1) konker.registry.web/src/main/webapp/resources/bootstrap/css/bootstrap.css:5431— `a.list-group-item-danger:hover, button.list-group-item-danger:hover, a.list-group-item-danger:focus, button.list-group-item-danger:focus` sets color: #a94442 on background-color: #ebcccc — 3.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (4.3:1) konker.registry.web/src/main/webapp/resources/konker/css/style2.css:279— `.btn-theme04:hover, .btn-theme04:focus, .btn-theme04:active, .btn-theme04.active, .open .dropdown-toggle.btn-theme04` sets color: #fff on background-color: #da4453 — 4.3:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (4.3:1) konker.registry.web/src/main/webapp/resources/bootstrap/css/bootstrap.css:5402— `a.list-group-item-warning:hover, button.list-group-item-warning:hover, a.list-group-item-warning:focus, button.list-group-item-warning:focus` sets color: #8a6d3b on background-color: #faf2cc — 4.3:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (1.6:1) konker.registry.web/src/main/webapp/resources/konker/css/style2.css:754— `ul.sidebar-menu li a.active, ul.sidebar-menu li a:hover, ul.sidebar-menu li a:focus` sets color: #fff on background-color: #68dff0 — 1.6:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (1.6:1) konker.registry.web/src/main/webapp/resources/konker/css/style2.css:924— `.dropdown-menu.extended li p.green` sets color: #fff on background-color: #68dff0 — 1.6:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (1.8:1) konker.registry.web/src/main/webapp/resources/konker/css/style2.css:929— `.dropdown-menu.extended li p.yellow` sets color: #fff on background-color: #fcb322 — 1.8:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (1.8:1) konker.registry.web/src/main/webapp/resources/konker/css/style2.css:1966— `.has-switch span.switch-right` sets color: #ffffff on background-color: #bdc3c7 — 1.8:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (3.0:1) konker.registry.web/src/main/webapp/resources/konker/css/style2.css:2031— `.login-form .login-form-heading` sets color: #888 on background-color: #ececec — 3.0:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (3.0:1) konker.registry.web/src/main/webapp/resources/konker/css/style2.css:2098— `#failogin .alert-danger` sets color: #FFF on background-color: #f6676b — 3.0:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
D4 · Code Duplication· Members sharing a duplicated core (7 members, 50+ identical tokens) · ×2
Members sharing a duplicated core (7 members, 50+ identical tokens) konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/DeviceRestController.java:133— konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/DeviceRestController.java:133-188 | konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/LocationRestController.java:58-86 | konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/LocationRestController.java:97-123 | konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/LocationRestController.java:134-160 | konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/LocationRestController.java:172-209 | konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/LocationRestController.java:222-275 | konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/LocationRestController.java:350-379 — These 7 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 7 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 7 times.
Members sharing a duplicated core (7 members, 50+ identical tokens) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/AlertTriggerServiceImpl.java:177— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/AlertTriggerServiceImpl.java:177-189 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/ApplicationDocumentStoreServiceImpl.java:167-192 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceConfigSetupServiceImpl.java:261-284 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceCustomDataServiceImpl.java:164-187 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceFirmwareUpdateServiceImpl.java:218-237 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceFirmwareUpdateServiceImpl.java:240-259 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/PrivateStorageServiceImpl.java:334-354 — These 7 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 7 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 7 times.
D4 · Code Duplication· Edited copy of a member (36 corresponding lines) · ×2
Edited copy of a member (36 corresponding lines) konker.registry.data/src/main/java/com/konkerlabs/platform/registry/integration/endpoints/GatewayEventRestEndpoint.java:111— konker.registry.data/src/main/java/com/konkerlabs/platform/registry/integration/endpoints/GatewayEventRestEndpoint.java:111-146 | konker.registry.data/src/main/java/com/konkerlabs/platform/registry/integration/endpoints/GatewayEventRestEndpoint.java:176-217 — These two members are one piece of code written twice and then edited apart: 36 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (36 corresponding lines) konker.scripts/registry/dao/registry.py:270— konker.scripts/registry/dao/registry.py:270-305 | konker.scripts/registry/dao/registry.py:308-347 — These two members are one piece of code written twice and then edited apart: 36 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (31 corresponding lines) · ×2
Edited copy of a member (31 corresponding lines) REDACTED:91— REDACTED:91-121 | REDACTED:161-193 — 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.
Edited copy of a member (31 corresponding lines) konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/IncomingEventsRestController.java:78— konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/IncomingEventsRestController.java:78-119 | konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/OutgoingEventsRestController.java:62-92 — 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 (32 corresponding lines) · ×2
Edited copy of a member (32 corresponding lines) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceConfigSetupServiceImpl.java:64— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceConfigSetupServiceImpl.java:64-101 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceConfigSetupServiceImpl.java:119-150 — These two members are one piece of code written twice and then edited apart: 32 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (32 corresponding lines) konker.registry.services.storage.cassandra/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/EventRepositoryCassandraImpl.java:513— konker.registry.services.storage.cassandra/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/EventRepositoryCassandraImpl.java:513-551 | konker.registry.services.storage.cassandra/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/EventRepositoryCassandraImpl.java:553-584 — These two members are one piece of code written twice and then edited apart: 32 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 25+ corresponding lines) · ×2
Edited copies of one member (3 members, 25+ corresponding lines) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceConfigSetupServiceImpl.java:287— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceConfigSetupServiceImpl.java:287-311 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceConfigSetupServiceImpl.java:315-339 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/LocationSearchServiceImpl.java:265-295 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 25 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 25+ corresponding lines) konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/DeviceFirmwareUpdateRestController.java:48— konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/DeviceFirmwareUpdateRestController.java:48-74 | konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/DeviceFirmwareUpdateRestController.java:84-108 | konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/DeviceFirmwareUpdateRestController.java:118-144 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 25 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, 20+ corresponding lines) · ×2
Edited copies of one member (3 members, 20+ corresponding lines) konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/config/S3BucketConfig.java:23— konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/config/S3BucketConfig.java:23-42 | konker.registry.web/src/main/java/com/konkerlabs/platform/registry/config/CdnConfig.java:25-44 | konker.registry.web/src/main/java/com/konkerlabs/platform/registry/config/DeviceS3Config.java:23-42 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 20 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 20+ corresponding lines) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/EventSchemaServiceImpl.java:197— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/EventSchemaServiceImpl.java:197-219 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/EventSchemaServiceImpl.java:222-241 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/EventSchemaServiceImpl.java:243-265 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 20 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (20 corresponding lines) · ×2
Edited copy of a member (20 corresponding lines) konker.registry.idm.resourceserver/src/main/java/com/konkerlabs/platform/registry/idm/services/OAuthClientDetailsService.java:125— konker.registry.idm.resourceserver/src/main/java/com/konkerlabs/platform/registry/idm/services/OAuthClientDetailsService.java:125-145 | konker.registry.idm.resourceserver/src/main/java/com/konkerlabs/platform/registry/idm/services/OAuthClientDetailsService.java:148-167 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (20 corresponding lines) konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/AlertTriggerRestController.java:63— konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/AlertTriggerRestController.java:63-82 | konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/EventRouteRestController.java:141-160 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (18 corresponding lines) · ×2
Edited copy of a member (18 corresponding lines) konker.registry.services.storage.cassandra/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/EventRepositoryCassandraImpl.java:470— konker.registry.services.storage.cassandra/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/EventRepositoryCassandraImpl.java:470-491 | konker.registry.services.storage.cassandra/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/EventRepositoryCassandraImpl.java:494-511 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (18 corresponding lines) konker.registry.web/src/main/java/com/konkerlabs/platform/registry/idm/web/controllers/AccountClientsController.java:140— konker.registry.web/src/main/java/com/konkerlabs/platform/registry/idm/web/controllers/AccountClientsController.java:140-157 | konker.registry.web/src/main/java/com/konkerlabs/platform/registry/idm/web/controllers/AccountClientsController.java:164-181 — 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, 22+ corresponding lines) · ×2
Edited copies of one member (3 members, 22+ corresponding lines) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/EventRouteServiceImpl.java:327— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/EventRouteServiceImpl.java:327-348 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/GatewayServiceImpl.java:178-200 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/GatewayServiceImpl.java:203-233 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 22 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 22+ corresponding lines) konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/DeviceFirmwareRestController.java:71— konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/DeviceFirmwareRestController.java:71-96 | konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/DeviceModelRestController.java:128-149 | konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/GatewayRestController.java:170-191 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 22 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 (17 corresponding lines) · ×2
Edited copy of a member (17 corresponding lines) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/model/DeviceModel.java:76— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/model/DeviceModel.java:76-92 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/model/Location.java:81-97 — 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) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/config/RedisCacheConfig.java:115— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/config/RedisCacheConfig.java:115-134 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/config/RedisCacheConfig.java:163-179 — 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) · ×2
Edited copy of a member (9 corresponding lines) konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/integration/processors/DeviceEventProcessor.java:90— konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/integration/processors/DeviceEventProcessor.java:90-100 | konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/integration/processors/DeviceEventProcessor.java:111-119 — 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) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/model/AlertTrigger.java:55— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/model/AlertTrigger.java:55-63 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/model/HealthAlert.java:102-110 — 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 (13 corresponding lines) · ×2
Edited copy of a member (13 corresponding lines) konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/ApplicationRestController.java:236— konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/ApplicationRestController.java:236-249 | konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/DeviceModelRestController.java:212-224 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) konker.registry.data.processor/src/main/java/com/konkerlabs/platform/registry/KonkerRegistryDataProcessorApplication.java:14— konker.registry.data.processor/src/main/java/com/konkerlabs/platform/registry/KonkerRegistryDataProcessorApplication.java:14-26 | konker.registry.data/src/main/java/com/konkerlabs/platform/registry/KonkerRegistryDataApplication.java:14-26 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 8+ corresponding lines) · ×2
Edited copies of one member (4 members, 8+ corresponding lines) REDACTED:182— REDACTED:182-190 | REDACTED:73-80 | REDACTED:66-74 | REDACTED:69-77 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
Edited copies of one member (4 members, 8+ corresponding lines) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/config/HealthAlertsConfig.java:16— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/config/HealthAlertsConfig.java:16-24 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/config/PasswordUserConfig.java:16-23 | konker.registry.web/src/main/java/com/konkerlabs/platform/registry/config/EnvironmentConfig.java:19-26 | konker.registry.web/src/main/java/com/konkerlabs/platform/registry/config/HotjarConfig.java:20-29 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (8 corresponding lines) · ×2
Edited copy of a member (8 corresponding lines) konker.registry.web/src/main/java/com/konkerlabs/platform/registry/config/AmazonConfig.java:17— konker.registry.web/src/main/java/com/konkerlabs/platform/registry/config/AmazonConfig.java:17-24 | konker.registry.web/src/main/java/com/konkerlabs/platform/registry/config/WebConfig.java:19-26 — 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) konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/model/DeviceModelVO.java:48— konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/model/DeviceModelVO.java:48-55 | konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/model/DeviceVO.java:43-52 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (18 lines × 2) konker.registry.cassandra-etl/src/main/java/org/konker/registry/cassandraetl/services/EventsCassandraToMongoService.java:40— konker.registry.cassandra-etl/src/main/java/org/konker/registry/cassandraetl/services/EventsCassandraToMongoService.java:40-57 | konker.registry.cassandra-etl/src/main/java/org/konker/registry/cassandraetl/services/EventsMongoToCassandraService.java:40-57 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. 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 (18 lines × 2) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/RestDestinationServiceImpl.java:155— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/RestDestinationServiceImpl.java:155-172 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/RestDestinationServiceImpl.java:238-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 `konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/RestDestinationServiceImpl.java:155` 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (15–16 lines × 2) konker.registry.idm.resourceserver/src/main/java/com/konkerlabs/platform/registry/idm/services/OAuthClientDetailsService.java:130— konker.registry.idm.resourceserver/src/main/java/com/konkerlabs/platform/registry/idm/services/OAuthClientDetailsService.java:130-145 | konker.registry.idm.resourceserver/src/main/java/com/konkerlabs/platform/registry/idm/services/OAuthClientDetailsService.java:153-167 — 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 `konker.registry.idm.resourceserver/src/main/java/com/konkerlabs/platform/registry/idm/services/OAuthClientDetailsService.java:130` 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 (15–16 lines × 2) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/TransformationServiceImpl.java:92— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/TransformationServiceImpl.java:92-107 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/TransformationServiceImpl.java:193-207 — 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 `konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/TransformationServiceImpl.java:92` 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (14 lines × 3) konker.registry.cassandra-etl/src/main/java/org/konker/registry/cassandraetl/repositories/EventRepositoryCassandraEtlImpl.java:67— konker.registry.cassandra-etl/src/main/java/org/konker/registry/cassandraetl/repositories/EventRepositoryCassandraEtlImpl.java:67-80 | konker.registry.services.storage.cassandra/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/EventRepositoryCassandraImpl.java:159-172 | konker.registry.services.storage.cassandra/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/EventRepositoryCassandraImpl.java:218-231 — before extracting anything, compare `konker.registry.cassandra-etl/src/main/java/org/konker/registry/cassandraetl/repositories/EventRepositoryCassandraEtlImpl.java` and `konker.registry.services.storage.cassandra/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/EventRepositoryCassandraImpl.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 47 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `konker.registry.cassandra-etl/src/main/java/org/konker/registry/cassandraetl/repositories/EventRepositoryCassandraEtlImpl.java:67` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 3) konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/config/S3BucketConfig.java:29— konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/config/S3BucketConfig.java:29-42 | konker.registry.web/src/main/java/com/konkerlabs/platform/registry/config/CdnConfig.java:31-44 | konker.registry.web/src/main/java/com/konkerlabs/platform/registry/config/DeviceS3Config.java:29-42 — 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 `konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/config/S3BucketConfig.java:29` 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 (14 lines × 2) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/HealthAlertServiceImpl.java:336— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/HealthAlertServiceImpl.java:336-349 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/HealthAlertServiceImpl.java:377-390 — 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 `konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/HealthAlertServiceImpl.java:336` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (14 lines × 2) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/storage/repositories/PrivateStorageRepository.java:167— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/storage/repositories/PrivateStorageRepository.java:167-180 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/storage/repositories/PrivateStorageRepository.java:184-197 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/storage/repositories/PrivateStorageRepository.java:167` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 3) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/config/MongoAuditConfig.java:53— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/config/MongoAuditConfig.java:53-64 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/config/MongoBillingConfig.java:59-70 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/config/MongoConfig.java:62-73 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/config/MongoAuditConfig.java:53` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 3) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/config/MongoAuditConfig.java:87— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/config/MongoAuditConfig.java:87-98 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/config/MongoBillingConfig.java:93-104 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/config/MongoConfig.java:91-102 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (10–11 lines × 3) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/ApplicationDocumentStoreServiceImpl.java:88— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/ApplicationDocumentStoreServiceImpl.java:88-98 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/ApplicationDocumentStoreServiceImpl.java:123-133 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/ApplicationDocumentStoreServiceImpl.java:152-161 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10–11 lines × 3) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceModelServiceImpl.java:241— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceModelServiceImpl.java:241-251 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceModelServiceImpl.java:321-330 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceModelServiceImpl.java:358-367 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11 lines × 3) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/LocationServiceImpl.java:58— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/LocationServiceImpl.java:58-68 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/LocationServiceImpl.java:189-199 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/LocationServiceImpl.java:361-371 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11 lines × 3) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/config/RedisCacheConfig.java:124— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/config/RedisCacheConfig.java:124-134 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/config/RedisCacheConfig.java:146-156 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/config/RedisCacheConfig.java:169-179 — 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 `konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/config/RedisCacheConfig.java:124` 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–11 lines × 2) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/EventRouteServiceImpl.java:84— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/EventRouteServiceImpl.java:84-92 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/EventRouteServiceImpl.java:155-165 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/EventRouteServiceImpl.java:84` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (9–11 lines × 2) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/GatewayServiceImpl.java:54— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/GatewayServiceImpl.java:54-62 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/GatewayServiceImpl.java:124-134 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/GatewayServiceImpl.java:54` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (9 lines × 4) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/LocationSearchServiceImpl.java:42— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/LocationSearchServiceImpl.java:42-50 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/LocationSearchServiceImpl.java:85-93 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/LocationSearchServiceImpl.java:186-194 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/LocationSearchServiceImpl.java:214-222 — 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 4) konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/ApplicationDocumentStoreRestController.java:147— konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/ApplicationDocumentStoreRestController.java:147-155 | konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/DeviceCredentialRestController.java:103-111 | konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/DeviceCustomDataRestController.java:168-176 | konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/DeviceStatusRestController.java:146-154 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 4 call sites, so a change lands once. 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 (8 lines × 3) konker.registry.cassandra-etl/src/main/java/org/konker/registry/cassandraetl/repositories/EventRepositoryCassandraEtlImpl.java:97— konker.registry.cassandra-etl/src/main/java/org/konker/registry/cassandraetl/repositories/EventRepositoryCassandraEtlImpl.java:97-104 | konker.registry.services.storage.cassandra/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/EventRepositoryCassandraImpl.java:198-205 | konker.registry.services.storage.cassandra/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/EventRepositoryCassandraImpl.java:248-255 — before extracting anything, compare `konker.registry.cassandra-etl/src/main/java/org/konker/registry/cassandraetl/repositories/EventRepositoryCassandraEtlImpl.java` and `konker.registry.services.storage.cassandra/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/EventRepositoryCassandraImpl.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 47 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 3) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/ApplicationServiceImpl.java:56— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/ApplicationServiceImpl.java:56-63 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceModelServiceImpl.java:52-59 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/HealthAlertServiceImpl.java:521-528 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/ApplicationServiceImpl.java: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 (8–9 lines × 2) konker.registry.data/src/main/java/com/konkerlabs/platform/registry/integration/endpoints/DeviceEventRestEndpoint.java:302— konker.registry.data/src/main/java/com/konkerlabs/platform/registry/integration/endpoints/DeviceEventRestEndpoint.java:302-309 | konker.registry.data/src/main/java/com/konkerlabs/platform/registry/integration/endpoints/DeviceEventRestEndpoint.java:375-383 — 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 `konker.registry.data/src/main/java/com/konkerlabs/platform/registry/integration/endpoints/DeviceEventRestEndpoint.java:302` 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) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/model/EventRoute.java:179— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/model/EventRoute.java:179-186 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/model/EventRoute.java:204-212 — 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 `konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/model/EventRoute.java:179` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `validations` to `Map<String, Object[]>` in one and `Map<String,Object[]>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (7 lines × 4) konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/services/publishers/EventPublisherAmazonKinesis.java:37— konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/services/publishers/EventPublisherAmazonKinesis.java:37-43 | konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/services/publishers/EventPublisherDevice.java:57-63 | konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/services/publishers/EventPublisherModelLocation.java:74-80 | konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/services/publishers/EventPublisherRest.java:59-65 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 4 call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/services/publishers/EventPublisherDevice.java:64` calls `ofNullable`, `get`, `filter` and `konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/services/publishers/EventPublisherAmazonKinesis.java:44` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (7 lines × 4) konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/config/RabbitMQDataConfig.java:22— konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/config/RabbitMQDataConfig.java:22-30 | konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/config/RabbitMQDataConfig.java:33-41 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/config/RabbitMQConfig.java:99-107 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/config/RabbitMQConfig.java:110-116 — 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Low cohesion: KonkerLoggingEvent (LCOM4 5) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/audit/KonkerLoggingEvent.java:15— KonkerLoggingEvent's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: RabbitMQConfig (LCOM4 4) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/config/RabbitMQConfig.java:25— RabbitMQConfig's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Duplicated block (6 lines × 2 locations) konker.registry.web/src/main/webapp/resources/js/notifications/index.js:89— konker.registry.web/src/main/webapp/resources/js/notifications/index.js:89 · konker.registry.web/src/main/webapp/resources/js/notifications/index.js:96 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (6 lines × 2 locations) konker.registry.web/src/main/webapp/resources/js/users/form.js:39— konker.registry.web/src/main/webapp/resources/js/users/form.js:39 · konker.registry.web/src/main/webapp/resources/js/users/form.js:52 — 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.
Dead file (~59 LoC) konker.registry.web/src/main/webapp/resources/js/input-eye.js— no import path from any entry point (2 application, 0 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~59 LoC) konker.registry.web/src/main/webapp/resources/js/users/form.js— no import path from any entry point (2 application, 0 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~28 LoC) konker.registry.web/src/main/webapp/resources/konker/scripts/scripts.js— no import path from any entry point (2 application, 0 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~28 LoC) REDACTED— no import path from any entry point (2 application, 0 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Low contrast colour pair in CSS (2.8:1) konker.registry.web/src/main/webapp/resources/konker/css/main.css:1387— `#subscribe form input` sets color: #999999 on background-color: #ffffff — 2.8:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (4.0:1) konker.registry.web/src/main/webapp/resources/konker/css/main.css:1579— `.subscribe-box input[type="submit"]` sets color: #fff on background-color: #4676fa — 4.0:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (3.8:1) konker.registry.web/src/main/webapp/resources/konker/css/style2.css:135— `table.table thead` sets color: #fff on background-color: #2e8dac — 3.8:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (3.6:1) konker.registry.web/src/main/webapp/resources/konker/css/style2.css:234— `.btn-theme:hover, .btn-theme:focus, .btn-theme:active, .btn-theme.active, .open .dropdown-toggle.btn-theme` sets color: #fff on background-color: #5986de — 3.6:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (1.4:1) konker.registry.web/src/main/webapp/resources/konker/css/style2.css:372— `ul.top-menu > li > .logout` sets color: #f2f2f2 on background-color: #68dff0 — 1.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (4.4:1) konker.registry.web/src/main/webapp/resources/konker/css/style2.css:2152— `.btn-facebook:hover, .btn-facebook:focus, .btn-facebook:active, .btn-facebook.active, .open .dropdown-toggle.btn-facebook` sets color: #fff on background-color: #2775e2 — 4.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (2.3:1) konker.registry.web/src/main/webapp/resources/bootstrap/css/bootstrap.css:3308— `.btn-warning:active, .btn-warning.active, .open > .dropdown-toggle.btn-warning` sets color: #fff on background-color: #ec971f — 2.3:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (4.2:1) konker.registry.web/src/main/webapp/resources/bootstrap/css/bootstrap.css:5344— `a.list-group-item-success:hover, button.list-group-item-success:hover, a.list-group-item-success:focus, button.list-group-item-success:focus` sets color: #3c763d on background-color: #d0e9c6 — 4.2:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (4.1:1) konker.registry.web/src/main/webapp/resources/bootstrap/css/bootstrap.css:5373— `a.list-group-item-info:hover, button.list-group-item-info:hover, a.list-group-item-info:focus, button.list-group-item-info:focus` sets color: #31708f on background-color: #c4e3f3 — 4.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
d3.d3.svg.brush (cyclomatic 79) konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js:9089— d3.d3.svg.brush has cyclomatic complexity 79 (threshold 15). Most of this is not in the body itself: 11 of the 79 points are its own statements and the rest belongs to 15 function items inside it that branch (a function literal at line 9315, brushstart::brushmove, brushstart::move1, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest. This file is where this pass's cyclomatic complexity CONCENTRATES: konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js holds 22 of the 36 methods over the threshold — including the worst — and 363 of the 467 points over it (78%), 17.3× the next-largest file (konker.registry.services.storage.cassandra/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/EventRepositoryCassandraImpl.java at 21). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
d3.d3.layout.force (cyclomatic 61) konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js:6228— d3.d3.layout.force has cyclomatic complexity 61 (threshold 15). Most of this is not in the body itself: 1 of the 61 points is its own statement and the rest belongs to 16 function literals inside it that branch (lines 6385, 6251, 6231, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest. This file is where this pass's cyclomatic complexity CONCENTRATES: konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js holds 22 of the 36 methods over the threshold — including the worst — and 363 of the 467 points over it (78%), 17.3× the next-largest file (konker.registry.services.storage.cassandra/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/EventRepositoryCassandraImpl.java at 21). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
d3.d3.layout.treemap (cyclomatic 52) konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js:7252— d3.d3.layout.treemap has cyclomatic complexity 52 (threshold 15). Most of this is not in the body itself: 1 of the 52 points is its own statement and the rest belongs to 13 function items inside it that branch (squarify, position, stickify, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest. This file is where this pass's cyclomatic complexity CONCENTRATES: konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js holds 22 of the 36 methods over the threshold — including the worst — and 363 of the 467 points over it (78%), 17.3× the next-largest file (konker.registry.services.storage.cassandra/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/EventRepositoryCassandraImpl.java at 21). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
d3.d3_geo_clipExtent (cyclomatic 49) konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js:3698— d3.d3_geo_clipExtent has cyclomatic complexity 49 (threshold 15). Most of this is not in the body itself: 1 of the 49 points is its own statement and the rest belongs to 10 function items inside it that branch (a function literal at line 3778, a function literal at line 3730, a function literal at line 3745, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest. This file is where this pass's cyclomatic complexity CONCENTRATES: konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js holds 22 of the 36 methods over the threshold — including the worst — and 363 of the 467 points over it (78%), 17.3× the next-largest file (konker.registry.services.storage.cassandra/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/EventRepositoryCassandraImpl.java at 21). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
d3.d3_geo_clipCircle (cyclomatic 43) konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js:3530— d3.d3_geo_clipCircle has cyclomatic complexity 43 (threshold 15). Most of this is not in the body itself: 2 of the 43 points are its own statements and the rest belongs to 5 function items inside it that branch (a function literal at line 3543, intersect, code, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest. This file is where this pass's cyclomatic complexity CONCENTRATES: konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js holds 22 of the 36 methods over the threshold — including the worst — and 363 of the 467 points over it (78%), 17.3× the next-largest file (konker.registry.services.storage.cassandra/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/EventRepositoryCassandraImpl.java at 21). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
d3.d3.behavior.zoom (cyclomatic 41) konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js:1305— d3.d3.behavior.zoom has cyclomatic complexity 41 (threshold 15). Most of this is not in the body itself: 7 of the 41 points are its own statements and the rest belongs to 21 function items inside it that branch (touchstarted::moved, touchstarted::started, touchstarted::ended, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest. This file is where this pass's cyclomatic complexity CONCENTRATES: konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js holds 22 of the 36 methods over the threshold — including the worst — and 363 of the 467 points over it (78%), 17.3× the next-largest file (konker.registry.services.storage.cassandra/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/EventRepositoryCassandraImpl.java at 21). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
EventRepositoryCassandraImpl.getQuery (cyclomatic 36) konker.registry.services.storage.cassandra/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/EventRepositoryCassandraImpl.java:369— EventRepositoryCassandraImpl.getQuery has cyclomatic complexity 36 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
d3.d3_geom_clipLine.<returned closure> (cyclomatic 35) konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js:3627— d3.d3_geom_clipLine.<returned closure> has cyclomatic complexity 35 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This file is where this pass's cyclomatic complexity CONCENTRATES: konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js holds 22 of the 36 methods over the threshold — including the worst — and 363 of the 467 points over it (78%), 17.3× the next-largest file (konker.registry.services.storage.cassandra/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/EventRepositoryCassandraImpl.java at 21). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
d3.d3.svg.arc.arc (cyclomatic 33) konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js:7975— d3.d3.svg.arc.arc has cyclomatic complexity 33 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This file is where this pass's cyclomatic complexity CONCENTRATES: konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js holds 22 of the 36 methods over the threshold — including the worst — and 363 of the 467 points over it (78%), 17.3× the next-largest file (konker.registry.services.storage.cassandra/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/EventRepositoryCassandraImpl.java at 21). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
d3.d3.layout.tree (cyclomatic 30) konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js:7045— d3.d3.layout.tree has cyclomatic complexity 30 (threshold 15). Most of this is not in the body itself: 1 of the 30 points is its own statement and the rest belongs to 8 function items inside it that branch (apportion, firstWalk, wrapTree, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest. This file is where this pass's cyclomatic complexity CONCENTRATES: konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js holds 22 of the 36 methods over the threshold — including the worst — and 363 of the 467 points over it (78%), 17.3× the next-largest file (konker.registry.services.storage.cassandra/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/EventRepositoryCassandraImpl.java at 21). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
d3.d3_xhr (cyclomatic 29) konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js:1934— d3.d3_xhr has cyclomatic complexity 29 (threshold 15). Most of this is not in the body itself: 10 of the 29 points are its own statements and the rest belongs to 5 function items inside it that branch (a function literal at line 1988, respond, a function literal at line 1963, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest. This file is where this pass's cyclomatic complexity CONCENTRATES: konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js holds 22 of the 36 methods over the threshold — including the worst — and 363 of the 467 points over it (78%), 17.3× the next-largest file (konker.registry.services.storage.cassandra/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/EventRepositoryCassandraImpl.java at 21). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
d3.d3_locale_numberFormat.<returned closure> (cyclomatic 29) konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js:2223— d3.d3_locale_numberFormat.<returned closure> has cyclomatic complexity 29 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions. This file is where this pass's cyclomatic complexity CONCENTRATES: konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js holds 22 of the 36 methods over the threshold — including the worst — and 363 of the 467 points over it (78%), 17.3× the next-largest file (konker.registry.services.storage.cassandra/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/EventRepositoryCassandraImpl.java at 21). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
mustache.parseTemplate (cyclomatic 29) konker.registry.web/src/main/webapp/resources/konker/scripts/mustache.js:105— mustache.parseTemplate has cyclomatic complexity 29 (threshold 15). Of this number, 23 points are the body's own statements and 6 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
d3.d3.geom.quadtree.quadtree (cyclomatic 24) konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js:5562— d3.d3.geom.quadtree.quadtree has cyclomatic complexity 24 (threshold 15). Of this number, 16 points are the body's own statements and 8 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This is NOT this file's highest cyclomatic complexity: d3.d3.dsv (cyclomatic 26) 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. This file is where this pass's cyclomatic complexity CONCENTRATES: konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js holds 22 of the 36 methods over the threshold — including the worst — and 363 of the 467 points over it (78%), 17.3× the next-largest file (konker.registry.services.storage.cassandra/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/EventRepositoryCassandraImpl.java at 21). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
LocationServiceImpl.updateSubtree (cyclomatic 22) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/LocationServiceImpl.java:358— LocationServiceImpl.updateSubtree has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
d3.d3_geom_voronoiConnectEdge (cyclomatic 22) konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js:5129— d3.d3_geom_voronoiConnectEdge has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This is NOT this file's highest cyclomatic complexity: d3.d3.dsv (cyclomatic 26) 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. This file is where this pass's cyclomatic complexity CONCENTRATES: konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js holds 22 of the 36 methods over the threshold — including the worst — and 363 of the 467 points over it (78%), 17.3× the next-largest file (konker.registry.services.storage.cassandra/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/EventRepositoryCassandraImpl.java at 21). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
d3.d3.layout.chord (cyclomatic 22) konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js:6115— d3.d3.layout.chord has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 2 of the 22 points are its own statements and the rest belongs to 8 function items inside it that branch (relayout, a function literal at line 6212, a function literal at line 6188, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest. This is NOT this file's highest cyclomatic complexity: d3.d3.dsv (cyclomatic 26) 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. This file is where this pass's cyclomatic complexity CONCENTRATES: konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js holds 22 of the 36 methods over the threshold — including the worst — and 363 of the 467 points over it (78%), 17.3× the next-largest file (konker.registry.services.storage.cassandra/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/EventRepositoryCassandraImpl.java at 21). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
d3.d3_selectionPrototype.data (cyclomatic 21) konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js:830— d3.d3_selectionPrototype.data has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 7 of the 21 points are its own statements and the rest belongs to one function item inside it that branches (bind). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest. This is NOT this file's highest cyclomatic complexity: d3.d3.dsv (cyclomatic 26) 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. This file is where this pass's cyclomatic complexity CONCENTRATES: konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js holds 22 of the 36 methods over the threshold — including the worst — and 363 of the 467 points over it (78%), 17.3× the next-largest file (konker.registry.services.storage.cassandra/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/EventRepositoryCassandraImpl.java at 21). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
d3.d3_locale_numberFormat.<returned closure>.<returned closure> (cyclomatic 21) konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js:2274— d3.d3_locale_numberFormat.<returned closure>.<returned closure> has cyclomatic complexity 21 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This is NOT this file's highest cyclomatic complexity: d3.d3.dsv (cyclomatic 26) 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. This file is where this pass's cyclomatic complexity CONCENTRATES: konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js holds 22 of the 36 methods over the threshold — including the worst — and 363 of the 467 points over it (78%), 17.3× the next-largest file (konker.registry.services.storage.cassandra/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/EventRepositoryCassandraImpl.java at 21). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
EventRoute.applyValidations (cyclomatic 20) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/model/EventRoute.java:85— EventRoute.applyValidations has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
d3.d3_geom_voronoiCloseCells (cyclomatic 19) konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js:5039— d3.d3_geom_voronoiCloseCells has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This is NOT this file's highest cyclomatic complexity: d3.d3.dsv (cyclomatic 26) 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. This file is where this pass's cyclomatic complexity CONCENTRATES: konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js holds 22 of the 36 methods over the threshold — including the worst — and 363 of the 467 points over it (78%), 17.3× the next-largest file (konker.registry.services.storage.cassandra/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/EventRepositoryCassandraImpl.java at 21). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
EventsMigrationApplication.run (cyclomatic 18) konker.registry.cassandra-etl/src/main/java/org/konker/registry/cassandraetl/EventsMigrationApplication.java:44— EventsMigrationApplication.run has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
EventRouteServiceImpl.applyRouteActorValidations (cyclomatic 18) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/EventRouteServiceImpl.java:199— EventRouteServiceImpl.applyRouteActorValidations has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
HealthAlertServiceImpl.basicValidate (cyclomatic 18) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/HealthAlertServiceImpl.java:583— HealthAlertServiceImpl.basicValidate has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
EventRepositoryMongoImpl.doFindBy (cyclomatic 17) konker.registry.services.storage.mongodb/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/EventRepositoryMongoImpl.java:118— EventRepositoryMongoImpl.doFindBy has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
d3.d3_geo_pointInPolygon (cyclomatic 17) konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js:3501— d3.d3_geo_pointInPolygon has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This is NOT this file's highest cyclomatic complexity: d3.d3.dsv (cyclomatic 26) 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. This file is where this pass's cyclomatic complexity CONCENTRATES: konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js holds 22 of the 36 methods over the threshold — including the worst — and 363 of the 467 points over it (78%), 17.3× the next-largest file (konker.registry.services.storage.cassandra/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/EventRepositoryCassandraImpl.java at 21). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
d3.d3_transitionNode (cyclomatic 17) konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js:8905— d3.d3_transitionNode has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 3 of the 17 points are its own statements and the rest belongs to 5 function items inside it that branch (start, tick, a function literal at line 8935, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest. This is NOT this file's highest cyclomatic complexity: d3.d3.dsv (cyclomatic 26) 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. This file is where this pass's cyclomatic complexity CONCENTRATES: konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js holds 22 of the 36 methods over the threshold — including the worst — and 363 of the 467 points over it (78%), 17.3× the next-largest file (konker.registry.services.storage.cassandra/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/EventRepositoryCassandraImpl.java at 21). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
d3.d3_time_scale (cyclomatic 17) konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js:9430— d3.d3_time_scale has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 4 of the 17 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 9465, tickMethod, a function literal at line 9448, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest. This is NOT this file's highest cyclomatic complexity: d3.d3.dsv (cyclomatic 26) 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. This file is where this pass's cyclomatic complexity CONCENTRATES: konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js holds 22 of the 36 methods over the threshold — including the worst — and 363 of the 467 points over it (78%), 17.3× the next-largest file (konker.registry.services.storage.cassandra/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/EventRepositoryCassandraImpl.java at 21). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
AbstractEventRestEndpoint.subscribeForEvents (cyclomatic 16) konker.registry.data/src/main/java/com/konkerlabs/platform/registry/integration/endpoints/AbstractEventRestEndpoint.java:39— AbstractEventRestEndpoint.subscribeForEvents has cyclomatic complexity 16 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
d3.d3.extent (cyclomatic 16) konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js:86— d3.d3.extent has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This is NOT this file's highest cyclomatic complexity: d3.d3.dsv (cyclomatic 26) 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. This file is where this pass's cyclomatic complexity CONCENTRATES: konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js holds 22 of the 36 methods over the threshold — including the worst — and 363 of the 467 points over it (78%), 17.3× the next-largest file (konker.registry.services.storage.cassandra/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/EventRepositoryCassandraImpl.java at 21). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
d3.d3_layout_packSiblings (cyclomatic 16) konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js:6950— d3.d3_layout_packSiblings has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This is NOT this file's highest cyclomatic complexity: d3.d3.dsv (cyclomatic 26) 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. This file is where this pass's cyclomatic complexity CONCENTRATES: konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js holds 22 of the 36 methods over the threshold — including the worst — and 363 of the 467 points over it (78%), 17.3× the next-largest file (konker.registry.services.storage.cassandra/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/EventRepositoryCassandraImpl.java at 21). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
d3.d3.geom.quadtree.quadtree (cognitive 65) konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js:5562— d3.d3.geom.quadtree.quadtree has cognitive complexity 65 (threshold 15). Drivers by points: if/else 27 (55 pts), loops 3 (8 pts), boolean chains 2 (nesting depth added 33). Of this number, 49 points are the body's own statements and 16 belong to 2 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js holds 30 of the 59 methods over the threshold — including the worst — and 532 of the 871 points over it (61%), 13.3× the next-largest file (konker.registry.web/src/main/webapp/resources/konker/scripts/mustache.js at 40). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
d3.d3_geom_voronoiCloseCells (cognitive 62) konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js:5039— d3.d3_geom_voronoiCloseCells has cognitive complexity 62 (threshold 15). Drivers by points: ternaries 8 (48 pts), boolean chains 6, if/else 2 (5 pts), loops 2 (3 pts) (nesting depth added 44). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function. This file is where this pass's cognitive complexity CONCENTRATES: konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js holds 30 of the 59 methods over the threshold — including the worst — and 532 of the 871 points over it (61%), 13.3× the next-largest file (konker.registry.web/src/main/webapp/resources/konker/scripts/mustache.js at 40). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
d3.d3.svg.arc.arc (cognitive 61) konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js:7975— d3.d3.svg.arc.arc has cognitive complexity 61 (threshold 15). Drivers by points: if/else 25 (39 pts), ternaries 7 (18 pts), boolean chains 4 (nesting depth added 25). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js holds 30 of the 59 methods over the threshold — including the worst — and 532 of the 871 points over it (61%), 13.3× the next-largest file (konker.registry.web/src/main/webapp/resources/konker/scripts/mustache.js at 40). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
d3.d3.svg.brush (cognitive 57) konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js:9089— d3.d3.svg.brush has cognitive complexity 57 (threshold 15). Drivers by points: if/else 27 (34 pts), boolean chains 16, ternaries 6 (7 pts) (nesting depth added 8). Most of this is not in the body itself: 10 of the 57 points are its own statements and the rest belongs to 15 function items inside it that branch (brushstart::brushmove, brushstart::move1, brushstart, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest. This file is where this pass's cognitive complexity CONCENTRATES: konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js holds 30 of the 59 methods over the threshold — including the worst — and 532 of the 871 points over it (61%), 13.3× the next-largest file (konker.registry.web/src/main/webapp/resources/konker/scripts/mustache.js at 40). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
d3.d3_geom_clipLine.<returned closure> (cognitive 50) konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js:3627— d3.d3_geom_clipLine.<returned closure> has cognitive complexity 50 (threshold 15). Drivers by points: if/else 30 (46 pts), boolean chains 4 (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. This file is where this pass's cognitive complexity CONCENTRATES: konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js holds 30 of the 59 methods over the threshold — including the worst — and 532 of the 871 points over it (61%), 13.3× the next-largest file (konker.registry.web/src/main/webapp/resources/konker/scripts/mustache.js at 40). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
d3.d3_geom_voronoiConnectEdge (cognitive 49) konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js:5129— d3.d3_geom_voronoiConnectEdge has cognitive complexity 49 (threshold 15). Drivers by points: if/else 24 (47 pts), boolean chains 2 (nesting depth added 23). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js holds 30 of the 59 methods over the threshold — including the worst — and 532 of the 871 points over it (61%), 13.3× the next-largest file (konker.registry.web/src/main/webapp/resources/konker/scripts/mustache.js at 40). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
mustache.parseTemplate (cognitive 48) konker.registry.web/src/main/webapp/resources/konker/scripts/mustache.js:105— mustache.parseTemplate has cognitive complexity 48 (threshold 15). Drivers by points: if/else 21 (36 pts), boolean chains 6, loops 3 (6 pts) (nesting depth added 18). Of this number, 40 points are the body's own statements and 8 belong to 2 function items inside it that branch. 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.
d3.d3_geo_clipCircle (cognitive 46) konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js:3530— d3.d3_geo_clipCircle has cognitive complexity 46 (threshold 15). Drivers by points: if/else 22 (27 pts), boolean chains 12, ternaries 5 (7 pts) (nesting depth added 7). Most of this is not in the body itself: 1 of the 46 points is its own statement and the rest belongs to 5 function items inside it that branch (a function literal at line 3543, intersect, code, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest. This file is where this pass's cognitive complexity CONCENTRATES: konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js holds 30 of the 59 methods over the threshold — including the worst — and 532 of the 871 points over it (61%), 13.3× the next-largest file (konker.registry.web/src/main/webapp/resources/konker/scripts/mustache.js at 40). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
d3.d3_layout_packSiblings (cognitive 46) konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js:6950— d3.d3_layout_packSiblings has cognitive complexity 46 (threshold 15). Drivers by points: if/else 10 (30 pts), loops 4 (13 pts), boolean chains 3 (nesting depth added 29). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function. This file is where this pass's cognitive complexity CONCENTRATES: konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js holds 30 of the 59 methods over the threshold — including the worst — and 532 of the 871 points over it (61%), 13.3× the next-largest file (konker.registry.web/src/main/webapp/resources/konker/scripts/mustache.js at 40). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
d3.d3.extent (cognitive 40) konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js:86— d3.d3.extent has cognitive complexity 40 (threshold 15). Drivers by points: if/else 10 (30 pts), loops 4 (8 pts), boolean chains 2 (nesting depth added 24). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js holds 30 of the 59 methods over the threshold — including the worst — and 532 of the 871 points over it (61%), 13.3× the next-largest file (konker.registry.web/src/main/webapp/resources/konker/scripts/mustache.js at 40). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
EventRepositoryCassandraImpl.getQuery (cognitive 38) konker.registry.services.storage.cassandra/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/EventRepositoryCassandraImpl.java:369— EventRepositoryCassandraImpl.getQuery has cognitive complexity 38 (threshold 15). Drivers by points: if/else 26 (28 pts), boolean chains 10 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
d3.d3_geo_clipPolygon (cognitive 38) konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js:3237— d3.d3_geo_clipPolygon has cognitive complexity 38 (threshold 15). Drivers by points: if/else 10 (20 pts), loops 7 (18 pts) (nesting depth added 21). Of this number, 34 points are the body's own statements and 4 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js holds 30 of the 59 methods over the threshold — including the worst — and 532 of the 871 points over it (61%), 13.3× the next-largest file (konker.registry.web/src/main/webapp/resources/konker/scripts/mustache.js at 40). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
d3.d3_selectionPrototype.data::bind (cognitive 34) konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js:841— d3.d3_selectionPrototype.data::bind has cognitive complexity 34 (threshold 15). Drivers by points: if/else 10 (21 pts), loops 6 (12 pts), boolean chains 1 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js holds 30 of the 59 methods over the threshold — including the worst — and 532 of the 871 points over it (61%), 13.3× the next-largest file (konker.registry.web/src/main/webapp/resources/konker/scripts/mustache.js at 40). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
d3.d3.layout.tree (cognitive 34) konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js:7045— d3.d3.layout.tree has cognitive complexity 34 (threshold 15). Drivers by points: if/else 13 (21 pts), boolean chains 7, loops 3 (5 pts), ternaries 1 (nesting depth added 10). None of this is in the body itself: all 34 points belong to 8 function items inside it that branch (apportion, firstWalk, wrapTree, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest. This file is where this pass's cognitive complexity CONCENTRATES: konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js holds 30 of the 59 methods over the threshold — including the worst — and 532 of the 871 points over it (61%), 13.3× the next-largest file (konker.registry.web/src/main/webapp/resources/konker/scripts/mustache.js at 40). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
d3.d3.behavior.zoom (cognitive 32) konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js:1305— d3.d3.behavior.zoom has cognitive complexity 32 (threshold 15). Drivers by points: if/else 16 (20 pts), loops 4 (6 pts), boolean chains 5, ternaries 1 (nesting depth added 6). Most of this is not in the body itself: 4 of the 32 points are its own statements and the rest belongs to 21 function items inside it that branch (touchstarted::moved, touchstarted::started, touchstarted::ended, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest. This file is where this pass's cognitive complexity CONCENTRATES: konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js holds 30 of the 59 methods over the threshold — including the worst — and 532 of the 871 points over it (61%), 13.3× the next-largest file (konker.registry.web/src/main/webapp/resources/konker/scripts/mustache.js at 40). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
d3.d3_selectionPrototype.classed (cognitive 27) konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js:681— d3.d3_selectionPrototype.classed has cognitive complexity 27 (threshold 15). Drivers by points: if/else 6 (17 pts), loops 3 (10 pts) (nesting depth added 18). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function. This file is where this pass's cognitive complexity CONCENTRATES: konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js holds 30 of the 59 methods over the threshold — including the worst — and 532 of the 871 points over it (61%), 13.3× the next-largest file (konker.registry.web/src/main/webapp/resources/konker/scripts/mustache.js at 40). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
d3.d3.min (cognitive 26) konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js:52— d3.d3.min has cognitive complexity 26 (threshold 15). Drivers by points: if/else 6 (14 pts), loops 4 (8 pts), boolean chains 4 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (d3.d3.max) 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. This file is where this pass's cognitive complexity CONCENTRATES: konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js holds 30 of the 59 methods over the threshold — including the worst — and 532 of the 871 points over it (61%), 13.3× the next-largest file (konker.registry.web/src/main/webapp/resources/konker/scripts/mustache.js at 40). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
d3.d3.max (cognitive 26) konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js:69— d3.d3.max has cognitive complexity 26 (threshold 15). Drivers by points: if/else 6 (14 pts), loops 4 (8 pts), boolean chains 4 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (d3.d3.min) 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. This file is where this pass's cognitive complexity CONCENTRATES: konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js holds 30 of the 59 methods over the threshold — including the worst — and 532 of the 871 points over it (61%), 13.3× the next-largest file (konker.registry.web/src/main/webapp/resources/konker/scripts/mustache.js at 40). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
d3.d3_geo_pointInPolygon (cognitive 26) konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js:3501— d3.d3_geo_pointInPolygon has cognitive complexity 26 (threshold 15). Drivers by points: if/else 5 (15 pts), boolean chains 5, loops 2 (3 pts), ternaries 1 (3 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js holds 30 of the 59 methods over the threshold — including the worst — and 532 of the 871 points over it (61%), 13.3× the next-largest file (konker.registry.web/src/main/webapp/resources/konker/scripts/mustache.js at 40). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
EventRouteServiceImpl.applyRouteActorValidations (cognitive 25) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/EventRouteServiceImpl.java:199— EventRouteServiceImpl.applyRouteActorValidations has cognitive complexity 25 (threshold 15). Drivers by points: if/else 12 (24 pts), match/switch 1 (nesting depth added 12). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
LocationServiceImpl.updateSubtree (cognitive 25) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/LocationServiceImpl.java:358— LocationServiceImpl.updateSubtree has cognitive complexity 25 (threshold 15). Drivers by points: if/else 9 (13 pts), loops 7, boolean chains 5 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
KonkerLoggerAppender.enrich (cognitive 25) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/audit/KonkerLoggerAppender.java:61— KonkerLoggerAppender.enrich has cognitive complexity 25 (threshold 15). Drivers by points: if/else 6 (18 pts), boolean chains 4, loops 1 (3 pts) (nesting depth added 14). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
d3.d3.layout.treemap::squarify (cognitive 25) konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js:7261— d3.d3.layout.treemap::squarify has cognitive complexity 25 (threshold 15). Drivers by points: ternaries 4 (14 pts), if/else 4 (7 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 14). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function. This file is where this pass's cognitive complexity CONCENTRATES: konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js holds 30 of the 59 methods over the threshold — including the worst — and 532 of the 871 points over it (61%), 13.3× the next-largest file (konker.registry.web/src/main/webapp/resources/konker/scripts/mustache.js at 40). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
EventsMigrationApplication.run (cognitive 24) konker.registry.cassandra-etl/src/main/java/org/konker/registry/cassandraetl/EventsMigrationApplication.java:44— EventsMigrationApplication.run has cognitive complexity 24 (threshold 15). Drivers by points: if/else 11 (17 pts), boolean chains 6, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
HealthAlertServiceImpl.basicValidate (cognitive 24) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/HealthAlertServiceImpl.java:583— HealthAlertServiceImpl.basicValidate has cognitive complexity 24 (threshold 15). Drivers by points: if/else 15 (22 pts), boolean chains 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
EventRepositoryCassandraImpl.saveEvent (cognitive 24) konker.registry.services.storage.cassandra/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/EventRepositoryCassandraImpl.java:102— EventRepositoryCassandraImpl.saveEvent has cognitive complexity 24 (threshold 15). Drivers by points: ternaries 8 (16 pts), if/else 6 (8 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
EventRouteExecutorImpl.isEventRouteDeviceMatch (cognitive 23) konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/services/routes/EventRouteExecutorImpl.java:135— EventRouteExecutorImpl.isEventRouteDeviceMatch has cognitive complexity 23 (threshold 15). Drivers by points: if/else 11 (19 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GatewayEventProcessor.process (cognitive 23) konker.registry.data/src/main/java/com/konkerlabs/platform/registry/integration/processors/GatewayEventProcessor.java:120— GatewayEventProcessor.process has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (18 pts), ternaries 1 (3 pts), boolean chains 1, loops 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
JsonParsingServiceImpl.addKeys (cognitive 23) konker.utilities/src/main/java/com/konkerlabs/platform/utilities/parsers/json/JsonParsingServiceImpl.java:92— JsonParsingServiceImpl.addKeys has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (15 pts), loops 2 (4 pts), match/switch 1 (2 pts), ternaries 1 (2 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
EventSchemaServiceImpl.findLastIncomingBy (cognitive 22) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/EventSchemaServiceImpl.java:342— EventSchemaServiceImpl.findLastIncomingBy has cognitive complexity 22 (threshold 15). Drivers by points: if/else 5 (13 pts), error handling 2 (5 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
KonkerLoggerContextVO.equals (cognitive 22) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/audit/KonkerLoggerContextVO.java:41— KonkerLoggerContextVO.equals has cognitive complexity 22 (threshold 15). Drivers by points: if/else 11 (22 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
d3.d3_geom_voronoiAddBeach (cognitive 22) konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js:4954— d3.d3_geom_voronoiAddBeach has cognitive complexity 22 (threshold 15). Drivers by points: if/else 11 (20 pts), boolean chains 1, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js holds 30 of the 59 methods over the threshold — including the worst — and 532 of the 871 points over it (61%), 13.3× the next-largest file (konker.registry.web/src/main/webapp/resources/konker/scripts/mustache.js at 40). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
d3.d3_interpolateString (cognitive 22) konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js:5754— d3.d3_interpolateString has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (17 pts), ternaries 2 (3 pts), boolean chains 1, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js holds 30 of the 59 methods over the threshold — including the worst — and 532 of the 871 points over it (61%), 13.3× the next-largest file (konker.registry.web/src/main/webapp/resources/konker/scripts/mustache.js at 40). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
mustache.Context.lookup (cognitive 22) konker.registry.web/src/main/webapp/resources/konker/scripts/mustache.js:373— mustache.Context.lookup has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (15 pts), loops 2 (6 pts), boolean chains 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
d3.d3_locale_numberFormat.<returned closure> (cognitive 21) konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js:2223— d3.d3_locale_numberFormat.<returned closure> has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 10, if/else 8 (10 pts), match/switch 1 (nesting depth added 2). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators. This file is where this pass's cognitive complexity CONCENTRATES: konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js holds 30 of the 59 methods over the threshold — including the worst — and 532 of the 871 points over it (61%), 13.3× the next-largest file (konker.registry.web/src/main/webapp/resources/konker/scripts/mustache.js at 40). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
d3.d3_locale_numberFormat.<returned closure>.<returned closure> (cognitive 20) konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js:2274— d3.d3_locale_numberFormat.<returned closure>.<returned closure> has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (10 pts), ternaries 4 (6 pts), boolean chains 4 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level. This file is where this pass's cognitive complexity CONCENTRATES: konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js holds 30 of the 59 methods over the threshold — including the worst — and 532 of the 871 points over it (61%), 13.3× the next-largest file (konker.registry.web/src/main/webapp/resources/konker/scripts/mustache.js at 40). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
d3.d3_geo_clip.<returned closure> (cognitive 20) konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js:3316— d3.d3_geo_clip.<returned closure> has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11 (16 pts), loops 1 (3 pts), boolean chains 1 (nesting depth added 7). None of this is in the body itself: all 20 points belong to 3 function items inside it that branch (ringEnd, a function literal at line 3329, point). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest. This file is where this pass's cognitive complexity CONCENTRATES: konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js holds 30 of the 59 methods over the threshold — including the worst — and 532 of the 871 points over it (61%), 13.3× the next-largest file (konker.registry.web/src/main/webapp/resources/konker/scripts/mustache.js at 40). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
d3.d3_geom_voronoiAttachCircle (cognitive 20) konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js:5076— d3.d3_geom_voronoiAttachCircle has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 4, loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js holds 30 of the 59 methods over the threshold — including the worst — and 532 of the 871 points over it (61%), 13.3× the next-largest file (konker.registry.web/src/main/webapp/resources/konker/scripts/mustache.js at 40). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
d3.d3.layout.chord::relayout (cognitive 20) konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js:6117— d3.d3.layout.chord::relayout has cognitive complexity 20 (threshold 15). Drivers by points: loops 6 (9 pts), if/else 4 (6 pts), ternaries 1 (4 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js holds 30 of the 59 methods over the threshold — including the worst — and 532 of the 871 points over it (61%), 13.3× the next-largest file (konker.registry.web/src/main/webapp/resources/konker/scripts/mustache.js at 40). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
EventRoute.applyValidations (cognitive 19) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/model/EventRoute.java:85— EventRoute.applyValidations has cognitive complexity 19 (threshold 15). Drivers by points: if/else 14, boolean chains 5. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
d3.d3_geo_clipExtent::corner (cognitive 19) konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js:3821— d3.d3_geo_clipExtent::corner has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 7 (19 pts) (nesting depth added 12). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function. This file is where this pass's cognitive complexity CONCENTRATES: konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js holds 30 of the 59 methods over the threshold — including the worst — and 532 of the 871 points over it (61%), 13.3× the next-largest file (konker.registry.web/src/main/webapp/resources/konker/scripts/mustache.js at 40). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
d3.d3.layout.hierarchy.hierarchy (cognitive 19) konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js:6489— d3.d3.layout.hierarchy.hierarchy has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (11 pts), boolean chains 4, loops 2 (4 pts) (nesting depth added 7). Of this number, 15 points are the body's own statements and 4 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js holds 30 of the 59 methods over the threshold — including the worst — and 532 of the 871 points over it (61%), 13.3× the next-largest file (konker.registry.web/src/main/webapp/resources/konker/scripts/mustache.js at 40). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
d3.d3_transitionNode (cognitive 19) konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js:8905— d3.d3_transitionNode has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (11 pts), boolean chains 6, loops 2 (nesting depth added 2). Most of this is not in the body itself: 2 of the 19 points are its own statements and the rest belongs to 5 function items inside it that branch (start, tick, a function literal at line 8935, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest. This file is where this pass's cognitive complexity CONCENTRATES: konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js holds 30 of the 59 methods over the threshold — including the worst — and 532 of the 871 points over it (61%), 13.3× the next-largest file (konker.registry.web/src/main/webapp/resources/konker/scripts/mustache.js at 40). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
d3.d3.svg.axis.axis (cognitive 19) konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js:8982— d3.d3.svg.axis.axis has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 7 (11 pts), if/else 5, boolean chains 3 (nesting depth added 4). None of this is in the body itself: all 19 points belong to one function literal inside it that branches (line 8983). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest. This file is where this pass's cognitive complexity CONCENTRATES: konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js holds 30 of the 59 methods over the threshold — including the worst — and 532 of the 871 points over it (61%), 13.3× the next-largest file (konker.registry.web/src/main/webapp/resources/konker/scripts/mustache.js at 40). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
EventRouteRestController.getRouteActor (cognitive 18) konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/EventRouteRestController.java:271— EventRouteRestController.getRouteActor has cognitive complexity 18 (threshold 15). Drivers by points: if/else 14 (18 pts) (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
KonkerContextInitializer.findConfigFileURLFromSystemProperties (cognitive 18) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/audit/KonkerContextInitializer.java:56— KonkerContextInitializer.findConfigFileURLFromSystemProperties has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (11 pts), error handling 2 (6 pts), boolean chains 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
KonkerLoggerContext.getLogger (cognitive 18) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/audit/KonkerLoggerContext.java:65— KonkerLoggerContext.getLogger has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (15 pts), loops 1 (3 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DeviceController.addChartObjects (cognitive 18) REDACTED:323— DeviceController.addChartObjects has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (10 pts), boolean chains 4, loops 2, ternaries 1 (2 pts) (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
d3.d3_locale_timeFormat (cognitive 17) konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js:2511— d3.d3_locale_timeFormat has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (8 pts), ternaries 5, boolean chains 3, loops 1 (nesting depth added 4). Most of this is not in the body itself: 1 of the 17 points is its own statement and the rest belongs to 7 function items inside it that branch (d3_time_parse, a function literal at line 2623, d3_time_parseWeekdayAbbrev, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest. This file is where this pass's cognitive complexity CONCENTRATES: konker.registry.web/src/main/webapp/resources/konker/scripts/d3.js holds 30 of the 59 methods over the threshold — including the worst — and 532 of the 871 points over it (61%), 13.3× the next-largest file (konker.registry.web/src/main/webapp/resources/konker/scripts/mustache.js at 40). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
AbstractEventRestEndpoint.subscribeForEvents (cognitive 16) konker.registry.data/src/main/java/com/konkerlabs/platform/registry/integration/endpoints/AbstractEventRestEndpoint.java:39— AbstractEventRestEndpoint.subscribeForEvents has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 8, if/else 5, ternaries 3. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
UserServiceImpl.save (cognitive 16) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/UserServiceImpl.java:203— UserServiceImpl.save has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9, boolean chains 6, ternaries 1. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
KonkerLogger.setLevel (cognitive 16) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/audit/KonkerLogger.java:90— KonkerLogger.setLevel has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (11 pts), loops 1 (4 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
EventRepositoryMongoImpl.doFindBy (cognitive 16) konker.registry.services.storage.mongodb/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/EventRepositoryMongoImpl.java:118— EventRepositoryMongoImpl.doFindBy has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 16. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
EventCsvDownload.createHeader (cognitive 16) konker.registry.web/src/main/java/com/konkerlabs/platform/registry/web/csv/EventCsvDownload.java:107— EventCsvDownload.createHeader has cognitive complexity 16 (threshold 15). Drivers by points: if/else 3 (7 pts), ternaries 1 (5 pts), loops 2 (4 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MethodTooLong: EqualizeCassandraTablesService.process konker.registry.cassandra-etl/src/main/java/org/konker/registry/cassandraetl/services/EqualizeCassandraTablesService.java:74— MethodTooLong — process runs 119 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 19 over it, 1.19× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
D4 · Code Duplication· Near-duplicate member family (3 members, 22 shared lines) · ×1
Near-duplicate member family (3 members, 22 shared lines) konker.registry.cassandra-etl/src/main/java/org/konker/registry/cassandraetl/repositories/EventRepositoryCassandraEtlImpl.java:63— konker.registry.cassandra-etl/src/main/java/org/konker/registry/cassandraetl/repositories/EventRepositoryCassandraEtlImpl.java:63-111 | konker.registry.services.storage.cassandra/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/EventRepositoryCassandraImpl.java:155-212 | konker.registry.services.storage.cassandra/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/EventRepositoryCassandraImpl.java:214-262 — These 3 members are variants of one another: a block of 22 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 3 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 3 times.
Near-duplicate member pair (35 shared lines) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/EventRouteServiceImpl.java:63— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/EventRouteServiceImpl.java:63-111 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/EventRouteServiceImpl.java:114-186 — These two members are variants of one another: 35 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
Near-duplicate member pair (29 shared lines) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/ApplicationServiceImpl.java:52— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/ApplicationServiceImpl.java:52-96 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceModelServiceImpl.java:48-124 — These two members are variants of one another: 29 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication· Members sharing a duplicated core (10 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (10 members, 50+ identical tokens) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/EventRouteCounterServiceImpl.java:92— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/EventRouteCounterServiceImpl.java:92-114 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/EventRouteServiceImpl.java:397-421 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/RestDestinationServiceImpl.java:49-73 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/RestDestinationServiceImpl.java:76-108 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/RestDestinationServiceImpl.java:111-172 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/RestDestinationServiceImpl.java:175-255 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/RestDestinationServiceImpl.java:258-302 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/TransformationServiceImpl.java:57-107 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/TransformationServiceImpl.java:151-207 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/TransformationServiceImpl.java:210-257 — These 10 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 10 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 10 times.
D4 · Code Duplication· Members sharing a duplicated core (9 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (9 members, 50+ identical tokens) konker.registry.web/src/main/java/com/konkerlabs/platform/registry/idm/web/controllers/AccountClientsController.java:191— konker.registry.web/src/main/java/com/konkerlabs/platform/registry/idm/web/controllers/AccountClientsController.java:191-214 | konker.registry.web/src/main/java/com/konkerlabs/platform/registry/idm/web/controllers/AccountClientsController.java:219-243 | konker.registry.web/src/main/java/com/konkerlabs/platform/registry/idm/web/controllers/AccountClientsController.java:265-287 | REDACTED:442-463 | REDACTED:504-537 | REDACTED:542-562 | REDACTED:266-283 | REDACTED:167-185 | konker.registry.web/src/main/java/com/konkerlabs/platform/registry/web/controllers/UserSubscriptionController.java:84-113 — These 9 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 9 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 9 times.
D4 · Code Duplication· Members sharing a duplicated core (6 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (6 members, 50+ identical tokens) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/PrivateStorageServiceImpl.java:48— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/PrivateStorageServiceImpl.java:48-96 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/PrivateStorageServiceImpl.java:113-158 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/PrivateStorageServiceImpl.java:165-197 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/PrivateStorageServiceImpl.java:203-221 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/PrivateStorageServiceImpl.java:228-252 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/PrivateStorageServiceImpl.java:262-303 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
D4 · Code Duplication· Edited copy of a member (62 corresponding lines) · ×1
Edited copy of a member (62 corresponding lines) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/LocationServiceImpl.java:106— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/LocationServiceImpl.java:106-170 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/LocationServiceImpl.java:187-248 — These two members are one piece of code written twice and then edited apart: 62 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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 (30 corresponding lines) · ×1
Edited copy of a member (30 corresponding lines) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceModelServiceImpl.java:320— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceModelServiceImpl.java:320-354 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceModelServiceImpl.java:357-386 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (50 corresponding lines) · ×1
Edited copy of a member (50 corresponding lines) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/UserServiceImpl.java:392— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/UserServiceImpl.java:392-443 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/UserServiceImpl.java:500-549 — These two members are one piece of code written twice and then edited apart: 50 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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) · ×1
Edited copy of a member (25 corresponding lines) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceEventServiceImpl.java:65— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceEventServiceImpl.java:65-98 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceEventServiceImpl.java:154-178 — 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 copies of one member (3 members, 34+ corresponding lines) · ×1
Edited copies of one member (3 members, 34+ corresponding lines) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/KonkerPaymentServiceImpl.java:36— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/KonkerPaymentServiceImpl.java:36-73 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/KonkerPaymentServiceImpl.java:76-109 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/KonkerPaymentServiceImpl.java:112-145 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 34 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, 28+ corresponding lines) · ×1
Edited copies of one member (4 members, 28+ corresponding lines) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/ApplicationDocumentStoreServiceImpl.java:75— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/ApplicationDocumentStoreServiceImpl.java:75-113 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceCustomDataServiceImpl.java:75-112 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceFirmwareUpdateServiceImpl.java:69-96 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceFirmwareUpdateServiceImpl.java:100-127 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 28 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 (33 corresponding lines) · ×1
Edited copy of a member (33 corresponding lines) konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/EventRouteRestController.java:358— konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/EventRouteRestController.java:358-391 | konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/RestDestinationController.java:136-168 — These two members are one piece of code written twice and then edited apart: 33 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (34 corresponding lines) · ×1
Edited copy of a member (34 corresponding lines) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/ApplicationDocumentStoreServiceImpl.java:35— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/ApplicationDocumentStoreServiceImpl.java:35-72 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceCustomDataServiceImpl.java:39-72 — These two members are one piece of code written twice and then edited apart: 34 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 28+ corresponding lines) · ×1
Edited copies of one member (3 members, 28+ corresponding lines) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceEventServiceImpl.java:109— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceEventServiceImpl.java:109-142 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceEventServiceImpl.java:189-226 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceModelServiceImpl.java:391-418 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 28 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 (26 corresponding lines) · ×1
Edited copy of a member (26 corresponding lines) konker.registry.data/src/main/java/com/konkerlabs/platform/registry/data/upload/AwsUploadRepository.java:96— konker.registry.data/src/main/java/com/konkerlabs/platform/registry/data/upload/AwsUploadRepository.java:96-121 | konker.registry.web/src/main/java/com/konkerlabs/platform/registry/business/repositories/upload/AwsUploadRepository.java:148-174 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 27+ corresponding lines) · ×1
Edited copies of one member (3 members, 27+ corresponding lines) konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/DeviceModelRestController.java:161— konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/DeviceModelRestController.java:161-187 | konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/DeviceRestController.java:197-229 | konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/GatewayRestController.java:200-227 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 27 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, 17+ corresponding lines) · ×1
Edited copies of one member (4 members, 17+ corresponding lines) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceFirmwareUpdateServiceImpl.java:130— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceFirmwareUpdateServiceImpl.java:130-150 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceFirmwareUpdateServiceImpl.java:153-170 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceFirmwareUpdateServiceImpl.java:173-189 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceFirmwareUpdateServiceImpl.java:192-212 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 17 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 20+ corresponding lines) · ×1
Edited copies of one member (4 members, 20+ corresponding lines) konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/AbstractRestController.java:28— konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/AbstractRestController.java:28-48 | konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/AbstractRestController.java:50-73 | konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/AbstractRestController.java:75-98 | konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/DeviceCustomDataRestController.java:144-163 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 20 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 (23 corresponding lines) · ×1
Edited copy of a member (23 corresponding lines) konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/ApplicationRestController.java:190— konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/ApplicationRestController.java:190-212 | konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/DeviceStatusRestController.java:83-108 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 12+ corresponding lines) · ×1
Edited copies of one member (4 members, 12+ corresponding lines) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/model/EventRoute.java:126— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/model/EventRoute.java:126-139 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/model/EventRoute.java:174-186 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/model/EventRoute.java:188-199 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/model/EventRoute.java:201-212 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 16+ corresponding lines) · ×1
Edited copies of one member (3 members, 16+ corresponding lines) konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/DeviceConfigRestController.java:79— konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/DeviceConfigRestController.java:79-94 | konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/DeviceConfigRestController.java:107-122 | konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/DeviceConfigRestController.java:156-173 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (6 members, 16+ corresponding lines) · ×1
Edited copies of one member (6 members, 16+ corresponding lines) konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/DeviceCustomDataRestController.java:126— konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/DeviceCustomDataRestController.java:126-142 | konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/DeviceModelRestController.java:194-209 | konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/DeviceRestController.java:260-275 | konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/EventRouteRestController.java:398-413 | konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/GatewayRestController.java:234-249 | konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/RestDestinationController.java:175-190 — These 6 members are one piece of code written 6 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 6 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 17+ corresponding lines) · ×1
Edited copies of one member (3 members, 17+ corresponding lines) konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/PrivateStorageRestController.java:178— konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/PrivateStorageRestController.java:178-196 | konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/PrivateStorageRestController.java:205-221 | konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/PrivateStorageRestController.java:229-248 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 17 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 12+ corresponding lines) · ×1
Edited copies of one member (3 members, 12+ corresponding lines) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/audit/KonkerLogger.java:250— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/audit/KonkerLogger.java:250-262 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/audit/KonkerLogger.java:264-275 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/audit/KonkerLogger.java:277-288 — 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 copy of a member (6 corresponding lines) · ×1
Edited copy of a member (6 corresponding lines) konker.registry.idm.resourceserver/src/main/java/com/konkerlabs/platform/registry/business/model/OauthClientDetails.java:339— konker.registry.idm.resourceserver/src/main/java/com/konkerlabs/platform/registry/business/model/OauthClientDetails.java:339-344 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/model/User.java:81-86 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 11+ corresponding lines) · ×1
Edited copies of one member (4 members, 11+ corresponding lines) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/model/behaviors/DeviceURIDealer.java:12— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/model/behaviors/DeviceURIDealer.java:12-24 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/model/behaviors/RESTDestinationURIDealer.java:12-28 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/api/BaseEventRepositoryImpl.java:160-170 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/api/BaseEventRepositoryImpl.java:172-182 — These 4 members are one piece of code written 4 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 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 10+ corresponding lines) · ×1
Edited copies of one member (3 members, 10+ corresponding lines) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/api/UserNotificationServiceImpl.java:56— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/api/UserNotificationServiceImpl.java:56-65 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/api/UserNotificationServiceImpl.java:68-77 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/api/UserNotificationServiceImpl.java:101-114 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 14+ corresponding lines) · ×1
Edited copies of one member (4 members, 14+ corresponding lines) konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/ApplicationDocumentStoreRestController.java:61— konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/ApplicationDocumentStoreRestController.java:61-74 | konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/ApplicationDocumentStoreRestController.java:84-97 | konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/DeviceCustomDataRestController.java:60-74 | konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/DeviceCustomDataRestController.java:83-97 — 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, 15+ corresponding lines) · ×1
Edited copies of one member (3 members, 15+ corresponding lines) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/LocationTreeUtils.java:104— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/LocationTreeUtils.java:104-122 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/LocationTreeUtils.java:124-142 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/LocationTreeUtils.java:144-158 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 13+ corresponding lines) · ×1
Edited copies of one member (4 members, 13+ corresponding lines) konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/AlertTriggerRestController.java:172— konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/AlertTriggerRestController.java:172-184 | konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/AlertTriggerRestController.java:199-214 | konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/HealthAlertRestController.java:94-113 | konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/HealthAlertRestController.java:209-228 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 14+ corresponding lines) · ×1
Edited copies of one member (3 members, 14+ corresponding lines) konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/integration/gateway/RabbitGateway.java:28— konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/integration/gateway/RabbitGateway.java:28-41 | konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/integration/gateway/RabbitGateway.java:43-56 | konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/integration/gateway/RabbitGateway.java:83-96 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (5 members, 13+ corresponding lines) · ×1
Edited copies of one member (5 members, 13+ corresponding lines) konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/DeviceModelRestController.java:80— konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/DeviceModelRestController.java:80-93 | konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/DeviceRestController.java:111-124 | konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/GatewayRestController.java:72-85 | konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/RestDestinationController.java:75-88 | konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/UserRestController.java:77-89 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 9+ corresponding lines) · ×1
Edited copies of one member (3 members, 9+ corresponding lines) konker.scripts/registry/patches/set_alert_trigger_name.py:9— konker.scripts/registry/patches/set_alert_trigger_name.py:9-19 | konker.scripts/registry/patches/set_device_model_content_type.py:19-27 | konker.scripts/registry/patches/set_rest_dest_type.py:19-27 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 13+ corresponding lines) · ×1
Edited copies of one member (3 members, 13+ corresponding lines) konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/exceptions/BadRequestResponseException.java:18— konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/exceptions/BadRequestResponseException.java:18-32 | konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/exceptions/BadServiceResponseException.java:20-32 | konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/exceptions/NotAuthorizedResponseException.java:16-30 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (4 corresponding lines) · ×1
Edited copy of a member (4 corresponding lines) konker.registry.web/src/main/java/com/konkerlabs/platform/registry/security/TenantContextResolver.java:14— konker.registry.web/src/main/java/com/konkerlabs/platform/registry/security/TenantContextResolver.java:14-17 | konker.registry.web/src/main/java/com/konkerlabs/platform/registry/security/UserContextResolver.java:13-16 — 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.
D4 · Code Duplication· Edited copies of one member (5 members, 3+ corresponding lines) · ×1
Edited copies of one member (5 members, 3+ corresponding lines) konker.registry.api/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py:12— konker.registry.api/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py:12-14 | konker.registry.data.processor/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py:12-14 | konker.registry.data/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py:12-14 | konker.registry.router/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py:12-14 | konker.registry.web/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py:12-14 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 3 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
Duplicated block (27 lines × 2) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/PrivateStorageServiceImpl.java:56— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/PrivateStorageServiceImpl.java:56-82 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/PrivateStorageServiceImpl.java:121-147 — 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 `konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/PrivateStorageServiceImpl.java:56` 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 (3–27 lines × 4) konker.registry.web/src/main/java/com/konkerlabs/platform/registry/web/controllers/RecoverPasswordController.java:167— konker.registry.web/src/main/java/com/konkerlabs/platform/registry/web/controllers/RecoverPasswordController.java:167-193 | konker.registry.web/src/main/java/com/konkerlabs/platform/registry/web/controllers/RecoverPasswordController.java:211-230 | konker.registry.web/src/main/java/com/konkerlabs/platform/registry/web/controllers/RecoverPasswordController.java:245-247 | konker.registry.web/src/main/java/com/konkerlabs/platform/registry/web/controllers/UserSubscriptionController.java:124-126 — 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 `konker.registry.web/src/main/java/com/konkerlabs/platform/registry/web/controllers/RecoverPasswordController.java:167` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `konker.registry.web/src/main/java/com/konkerlabs/platform/registry/web/controllers/RecoverPasswordController.java:167` calls `getMessage`, `getKey`, `getValue` and `konker.registry.web/src/main/java/com/konkerlabs/platform/registry/web/controllers/UserSubscriptionController.java:124` does not — after which the two agree again for 5 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 (26 lines × 2) konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/config/oauth/OAuth2Config.java:73— konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/config/oauth/OAuth2Config.java:73-98 | konker.registry.web/src/main/java/com/konkerlabs/platform/registry/config/OAuth2Config.java:57-82 — before extracting anything, compare `konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/config/oauth/OAuth2Config.java` and `konker.registry.web/src/main/java/com/konkerlabs/platform/registry/config/OAuth2Config.java` as WHOLE FILES: 88% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (19–23 lines × 2) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceEventServiceImpl.java:110— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceEventServiceImpl.java:110-128 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceEventServiceImpl.java:190-212 — 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 `konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceEventServiceImpl.java:110` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (23 lines × 2) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceFirmwareServiceImpl.java:158— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceFirmwareServiceImpl.java:158-180 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/GatewayServiceImpl.java:319-341 — 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 `konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceFirmwareServiceImpl.java:158` 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (22–23 lines × 2) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/EventRouteCounterServiceImpl.java:93— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/EventRouteCounterServiceImpl.java:93-114 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/EventRouteServiceImpl.java:399-421 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (3–22 lines × 4) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceFirmwareServiceImpl.java:143— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceFirmwareServiceImpl.java:143-164 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceRegisterServiceImpl.java:751-772 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/GatewayServiceImpl.java:304-325 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/TenantLogServiceImpl.java:32-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 all 4 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceFirmwareServiceImpl.java:143` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. 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 (20 lines × 2) konker.registry.data/src/main/java/com/konkerlabs/platform/registry/data/upload/AwsUploadRepository.java:69— konker.registry.data/src/main/java/com/konkerlabs/platform/registry/data/upload/AwsUploadRepository.java:69-88 | konker.registry.web/src/main/java/com/konkerlabs/platform/registry/business/repositories/upload/AwsUploadRepository.java:75-94 — before extracting anything, compare `konker.registry.data/src/main/java/com/konkerlabs/platform/registry/data/upload/AwsUploadRepository.java` and `konker.registry.web/src/main/java/com/konkerlabs/platform/registry/business/repositories/upload/AwsUploadRepository.java` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 65 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 `konker.registry.data/src/main/java/com/konkerlabs/platform/registry/data/upload/AwsUploadRepository.java:69` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (18–20 lines × 2) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/EventRouteServiceImpl.java:94— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/EventRouteServiceImpl.java:94-111 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/EventRouteServiceImpl.java:167-186 — 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 `konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/EventRouteServiceImpl.java:94` 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (18–19 lines × 2) konker.registry.data/src/main/java/com/konkerlabs/platform/registry/integration/endpoints/GatewayEventRestEndpoint.java:128— konker.registry.data/src/main/java/com/konkerlabs/platform/registry/integration/endpoints/GatewayEventRestEndpoint.java:128-146 | konker.registry.data/src/main/java/com/konkerlabs/platform/registry/integration/endpoints/GatewayEventRestEndpoint.java:200-217 — 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 `konker.registry.data/src/main/java/com/konkerlabs/platform/registry/integration/endpoints/GatewayEventRestEndpoint.java:128` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (19 lines × 2) konker.registry.data/src/main/java/com/konkerlabs/platform/registry/integration/processors/GatewayEventProcessor.java:100— konker.registry.data/src/main/java/com/konkerlabs/platform/registry/integration/processors/GatewayEventProcessor.java:100-118 | konker.registry.data/src/main/java/com/konkerlabs/platform/registry/integration/processors/GatewayEventProcessor.java:173-191 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `konker.registry.data/src/main/java/com/konkerlabs/platform/registry/integration/processors/GatewayEventProcessor.java:100` 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 (17–18 lines × 2) konker.registry.services.storage.cassandra/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/EventRepositoryCassandraImpl.java:474— konker.registry.services.storage.cassandra/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/EventRepositoryCassandraImpl.java:474-491 | konker.registry.services.storage.cassandra/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/EventRepositoryCassandraImpl.java:495-511 — 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 `konker.registry.services.storage.cassandra/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/EventRepositoryCassandraImpl.java:474` 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 (17 lines × 2) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/LocationTreeUtils.java:106— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/LocationTreeUtils.java:106-122 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/LocationTreeUtils.java:126-142 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (13–16 lines × 2) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/UserServiceImpl.java:290— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/UserServiceImpl.java:290-302 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/UserServiceImpl.java:505-520 — 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 `konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/UserServiceImpl.java:290` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. 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 (27 lines × 3) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/RestDestinationServiceImpl.java:79— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/RestDestinationServiceImpl.java:79-105 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/RestDestinationServiceImpl.java:182-208 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/RestDestinationServiceImpl.java:261-287 — 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 `konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/RestDestinationServiceImpl.java:79` 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) konker.registry.data/src/main/java/com/konkerlabs/platform/registry/data/upload/AwsUploadRepository.java:107— konker.registry.data/src/main/java/com/konkerlabs/platform/registry/data/upload/AwsUploadRepository.java:107-121 | konker.registry.web/src/main/java/com/konkerlabs/platform/registry/business/repositories/upload/AwsUploadRepository.java:161-174 — before extracting anything, compare `konker.registry.data/src/main/java/com/konkerlabs/platform/registry/data/upload/AwsUploadRepository.java` and `konker.registry.web/src/main/java/com/konkerlabs/platform/registry/business/repositories/upload/AwsUploadRepository.java` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 65 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 `konker.registry.data/src/main/java/com/konkerlabs/platform/registry/data/upload/AwsUploadRepository.java:107` 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–14 lines × 2) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceModelServiceImpl.java:244— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceModelServiceImpl.java:244-257 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceModelServiceImpl.java:324-335 — 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 `konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceModelServiceImpl.java:244` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11–14 lines × 2) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/HealthAlertServiceImpl.java:170— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/HealthAlertServiceImpl.java:170-183 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/HealthAlertServiceImpl.java:225-235 — 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 `konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/HealthAlertServiceImpl.java:170` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (15 lines × 3) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/TransformationServiceImpl.java:64— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/TransformationServiceImpl.java:64-78 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/TransformationServiceImpl.java:158-172 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/TransformationServiceImpl.java:214-228 — 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 `konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/TransformationServiceImpl.java:64` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9–13 lines × 2) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/model/behaviors/DeviceURIDealer.java:13— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/model/behaviors/DeviceURIDealer.java:13-21 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/model/behaviors/RESTDestinationURIDealer.java:13-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. Read the line range as the matched WINDOW rather than a finished unit: at `konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/model/behaviors/DeviceURIDealer.java:13` 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 (11–12 lines × 7) konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/DeviceRestController.java:136— konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/DeviceRestController.java:136-147 | konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/LocationRestController.java:60-71 | konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/LocationRestController.java:99-109 | konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/LocationRestController.java:136-146 | konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/LocationRestController.java:175-186 | konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/LocationRestController.java:224-235 | konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/LocationRestController.java:352-362 — there are 7 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 7 sites; resolving a subset leaves the remainder to drift apart. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/LocationRestController.java:112` calls `authorizeGateway`, `builder`, `name` and `konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/LocationRestController.java:364` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (12 lines × 4) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/PrivateStorageServiceImpl.java:49— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/PrivateStorageServiceImpl.java:49-60 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/PrivateStorageServiceImpl.java:114-125 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/PrivateStorageServiceImpl.java:166-177 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/PrivateStorageServiceImpl.java:229-240 — 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11–12 lines × 3) REDACTED:452— REDACTED:452-463 | REDACTED:273-283 | REDACTED:175-185 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:452` 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–12 lines × 2) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/GatewayServiceImpl.java:64— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/GatewayServiceImpl.java:64-73 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/GatewayServiceImpl.java:136-147 — 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 `konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/GatewayServiceImpl.java:64` 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10–11 lines × 2) konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/ApplicationRestController.java:200— konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/ApplicationRestController.java:200-210 | konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/DeviceStatusRestController.java:94-103 — 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 `konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/ApplicationRestController.java:200` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/DeviceStatusRestController.java:105` calls `NotFoundResponseException` and `konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/ApplicationRestController.java:210` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (10 lines × 4) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/audit/KonkerLogger.java:343— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/audit/KonkerLogger.java:343-352 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/audit/KonkerLogger.java:444-453 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/audit/KonkerLogger.java:501-510 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/audit/KonkerLogger.java:535-544 — 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 `konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/audit/KonkerLogger.java:343` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9–10 lines × 3) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceCustomDataServiceImpl.java:88— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceCustomDataServiceImpl.java:88-97 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceCustomDataServiceImpl.java:122-131 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceCustomDataServiceImpl.java:150-158 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7–10 lines × 3) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/HealthAlertServiceImpl.java:176— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/HealthAlertServiceImpl.java:176-185 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/HealthAlertServiceImpl.java:231-237 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/HealthAlertServiceImpl.java:349-355 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9–10 lines × 2) konker.registry.data/src/main/java/com/konkerlabs/platform/registry/data/upload/AwsUploadRepository.java:97— konker.registry.data/src/main/java/com/konkerlabs/platform/registry/data/upload/AwsUploadRepository.java:97-105 | konker.registry.web/src/main/java/com/konkerlabs/platform/registry/business/repositories/upload/AwsUploadRepository.java:149-158 — before extracting anything, compare `konker.registry.data/src/main/java/com/konkerlabs/platform/registry/data/upload/AwsUploadRepository.java` and `konker.registry.web/src/main/java/com/konkerlabs/platform/registry/business/repositories/upload/AwsUploadRepository.java` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 65 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 `konker.registry.data/src/main/java/com/konkerlabs/platform/registry/data/upload/AwsUploadRepository.java:97` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8–9 lines × 3) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceRegisterServiceImpl.java:389— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceRegisterServiceImpl.java:389-397 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceRegisterServiceImpl.java:443-451 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceRegisterServiceImpl.java:505-512 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceRegisterServiceImpl.java:514` calls `findByDomainName`, `getDomainName` and `konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceRegisterServiceImpl.java:399` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (7–9 lines × 2) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/AlertTriggerServiceImpl.java:160— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/AlertTriggerServiceImpl.java:160-168 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/AlertTriggerServiceImpl.java:210-216 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (5–9 lines × 3) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceRegisterServiceImpl.java:454— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceRegisterServiceImpl.java:454-458 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceRegisterServiceImpl.java:521-528 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceRegisterServiceImpl.java:615-623 — 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 `konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceRegisterServiceImpl.java:454` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceRegisterServiceImpl.java:623` calls `error` and `konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceRegisterServiceImpl.java:458` 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 (6–8 lines × 3) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/storage/repositories/FilterEnum.java:102— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/storage/repositories/FilterEnum.java:102-107 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/storage/repositories/FilterEnum.java:123-128 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/storage/repositories/FilterEnum.java:144-151 — 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 `konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/storage/repositories/FilterEnum.java:102` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (6–8 lines × 2) konker.utilities/src/main/java/com/konkerlabs/platform/utilities/expressions/ExpressionEvaluationServiceImpl.java:27— konker.utilities/src/main/java/com/konkerlabs/platform/utilities/expressions/ExpressionEvaluationServiceImpl.java:27-34 | konker.utilities/src/main/java/com/konkerlabs/platform/utilities/expressions/ExpressionEvaluationServiceImpl.java:52-57 — 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 `konker.utilities/src/main/java/com/konkerlabs/platform/utilities/expressions/ExpressionEvaluationServiceImpl.java:27` 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–7 lines × 7) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/AlertTriggerServiceImpl.java:179— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/AlertTriggerServiceImpl.java:179-184 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/ApplicationDocumentStoreServiceImpl.java:169-174 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceConfigSetupServiceImpl.java:263-269 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceCustomDataServiceImpl.java:166-171 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceFirmwareUpdateServiceImpl.java:220-226 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceFirmwareUpdateServiceImpl.java:242-248 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/PrivateStorageServiceImpl.java:335-340 — there are 7 copies across 6 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 7 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/AlertTriggerServiceImpl.java:179` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 6) konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/config/S3BucketConfig.java:28— konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/config/S3BucketConfig.java:28-34 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/config/EmailConfig.java:32-38 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/config/PubServerConfig.java:33-39 | konker.registry.web/src/main/java/com/konkerlabs/platform/registry/config/CdnConfig.java:30-36 | konker.registry.web/src/main/java/com/konkerlabs/platform/registry/config/DeviceS3Config.java:28-34 | konker.registry.web/src/main/java/com/konkerlabs/platform/registry/config/RecaptchaConfig.java:24-30 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 6 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 6 times.
Duplicated block (6 lines × 7) konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/config/S3BucketConfig.java:24— konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/config/S3BucketConfig.java:24-29 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/config/EmailConfig.java:27-32 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/config/PubServerConfig.java:28-33 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/config/RabbitMQConfig.java:47-52 | konker.registry.services.storage.cassandra/src/main/java/com/konkerlabs/platform/registry/business/repositories/config/CassandraRegistryConfig.java:36-41 | konker.registry.web/src/main/java/com/konkerlabs/platform/registry/config/CdnConfig.java:26-31 | konker.registry.web/src/main/java/com/konkerlabs/platform/registry/config/DeviceS3Config.java:24-29 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 7 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 7 times. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (6 lines × 6) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/PrivateStorageServiceImpl.java:51— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/PrivateStorageServiceImpl.java:51-56 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/PrivateStorageServiceImpl.java:116-121 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/PrivateStorageServiceImpl.java:168-173 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/PrivateStorageServiceImpl.java:206-211 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/PrivateStorageServiceImpl.java:231-236 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/PrivateStorageServiceImpl.java:284-289 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/PrivateStorageServiceImpl.java:51` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 5) konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/ApplicationDocumentStoreRestController.java:148— konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/ApplicationDocumentStoreRestController.java:148-153 | konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/DeviceCredentialRestController.java:104-109 | konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/DeviceCustomDataRestController.java:169-174 | konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/DeviceRestController.java:285-290 | konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/DeviceStatusRestController.java:147-152 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 5 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/ApplicationDocumentStoreRestController.java: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 (6 lines × 3) konker.registry.web/src/main/java/com/konkerlabs/platform/registry/config/GoogleAnalyticsConfig.java:19— konker.registry.web/src/main/java/com/konkerlabs/platform/registry/config/GoogleAnalyticsConfig.java:19-24 | konker.registry.web/src/main/java/com/konkerlabs/platform/registry/config/HotjarConfig.java:21-26 | konker.registry.web/src/main/java/com/konkerlabs/platform/registry/config/UTraceConfig.java:19-24 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
Duplicated block (4–6 lines × 3) konker.registry.web/src/main/java/com/konkerlabs/platform/registry/web/controllers/RecoverPasswordController.java:159— konker.registry.web/src/main/java/com/konkerlabs/platform/registry/web/controllers/RecoverPasswordController.java:159-164 | konker.registry.web/src/main/java/com/konkerlabs/platform/registry/web/controllers/RecoverPasswordController.java:207-210 | konker.registry.web/src/main/java/com/konkerlabs/platform/registry/web/controllers/UserSubscriptionController.java:117-122 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `konker.registry.web/src/main/java/com/konkerlabs/platform/registry/web/controllers/RecoverPasswordController.java:159` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `konker.registry.web/src/main/java/com/konkerlabs/platform/registry/web/controllers/RecoverPasswordController.java:164` calls `ofNullable`, `getResult`, `isPresent` and `konker.registry.web/src/main/java/com/konkerlabs/platform/registry/web/controllers/RecoverPasswordController.java:210` does not — after which the two agree again for 5 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (5 lines × 10) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/EventRouteCounterServiceImpl.java:105— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/EventRouteCounterServiceImpl.java:105-109 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/EventRouteServiceImpl.java:411-415 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/RestDestinationServiceImpl.java:62-66 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/RestDestinationServiceImpl.java:93-97 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/RestDestinationServiceImpl.java:142-146 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/RestDestinationServiceImpl.java:196-200 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/RestDestinationServiceImpl.java:275-279 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/TransformationServiceImpl.java:72-76 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/TransformationServiceImpl.java:166-170 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/TransformationServiceImpl.java:222-226 — there are 10 copies across 4 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 10 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/EventRouteCounterServiceImpl.java:105` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/RestDestinationServiceImpl.java:150` calls `setId` and `konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/TransformationServiceImpl.java:80` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (5 lines × 8) konker.registry.web/src/main/java/com/konkerlabs/platform/registry/idm/web/controllers/AccountClientsController.java:201— konker.registry.web/src/main/java/com/konkerlabs/platform/registry/idm/web/controllers/AccountClientsController.java:201-205 | konker.registry.web/src/main/java/com/konkerlabs/platform/registry/idm/web/controllers/AccountClientsController.java:230-234 | konker.registry.web/src/main/java/com/konkerlabs/platform/registry/idm/web/controllers/AccountClientsController.java:275-279 | REDACTED:452-457 | REDACTED:529-533 | REDACTED:552-556 | REDACTED:273-278 | REDACTED:175-180 — there are 8 copies across 4 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 8 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `konker.registry.web/src/main/java/com/konkerlabs/platform/registry/idm/web/controllers/AccountClientsController.java:201` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 5) konker.registry.web/src/main/java/com/konkerlabs/platform/registry/idm/web/controllers/AccountClientsController.java:201— konker.registry.web/src/main/java/com/konkerlabs/platform/registry/idm/web/controllers/AccountClientsController.java:201-205 | konker.registry.web/src/main/java/com/konkerlabs/platform/registry/idm/web/controllers/AccountClientsController.java:230-234 | konker.registry.web/src/main/java/com/konkerlabs/platform/registry/idm/web/controllers/AccountClientsController.java:275-279 | REDACTED:552-556 | konker.registry.web/src/main/java/com/konkerlabs/platform/registry/web/controllers/UserSubscriptionController.java:100-104 — there are 5 copies across 3 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 5 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `konker.registry.web/src/main/java/com/konkerlabs/platform/registry/idm/web/controllers/AccountClientsController.java:201` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 4) konker.registry.data/src/main/java/com/konkerlabs/platform/registry/integration/endpoints/DeviceEventRestEndpoint.java:238— konker.registry.data/src/main/java/com/konkerlabs/platform/registry/integration/endpoints/DeviceEventRestEndpoint.java:238-242 | konker.registry.data/src/main/java/com/konkerlabs/platform/registry/integration/endpoints/DeviceEventRestEndpoint.java:279-283 | konker.registry.data/src/main/java/com/konkerlabs/platform/registry/integration/endpoints/DeviceEventRestEndpoint.java:335-339 | konker.registry.data/src/main/java/com/konkerlabs/platform/registry/integration/endpoints/DeviceEventRestEndpoint.java:398-402 — 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 `konker.registry.data/src/main/java/com/konkerlabs/platform/registry/integration/endpoints/DeviceEventRestEndpoint.java:238` 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 (45 lines × 3) konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/config/BusinessConfig.java:1— konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/config/BusinessConfig.java:1-47 | konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/config/BusinessConfig.java:1-45 | konker.registry.web/src/main/java/com/konkerlabs/platform/registry/config/BusinessConfig.java:1-46 — before extracting anything, compare `konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/config/BusinessConfig.java` and `konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/config/BusinessConfig.java` as WHOLE FILES: 90% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/config/BusinessConfig.java:1` 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 (63 lines × 3) konker.registry.data.processor/src/main/java/com/konkerlabs/platform/registry/data/processor/config/WebMvcConfig.java:1— konker.registry.data.processor/src/main/java/com/konkerlabs/platform/registry/data/processor/config/WebMvcConfig.java:1-63 | konker.registry.data/src/main/java/com/konkerlabs/platform/registry/data/config/WebMvcConfig.java:1-63 | konker.registry.router/src/main/java/com/konkerlabs/platform/registry/router/config/WebMvcConfig.java:1-63 — before extracting anything, compare `konker.registry.data.processor/src/main/java/com/konkerlabs/platform/registry/data/processor/config/WebMvcConfig.java` and `konker.registry.data/src/main/java/com/konkerlabs/platform/registry/data/config/WebMvcConfig.java` as WHOLE FILES: 97% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `konker.registry.data.processor/src/main/java/com/konkerlabs/platform/registry/data/processor/config/WebMvcConfig.java:1` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (35 lines × 3) konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/model/ApplicationDocumentStore.java:1— konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/model/ApplicationDocumentStore.java:1-35 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/model/DeviceCustomData.java:1-35 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/model/DeviceFwUpdate.java:1-42 — before extracting anything, compare `konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/model/ApplicationDocumentStore.java` and `konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/model/DeviceCustomData.java` as WHOLE FILES: 85% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/model/ApplicationDocumentStore.java:1` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 4) konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/services/DeviceLogEventServiceImpl.java:65— konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/services/DeviceLogEventServiceImpl.java:65-77 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceEventServiceImpl.java:40-52 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceRegisterServiceImpl.java:76-88 | konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/EventSchemaServiceImpl.java:103-115 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
Duplicated block (144 lines × 5) konker.registry.api/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py:58— konker.registry.api/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py:58-201 | konker.registry.data.processor/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py:58-201 | konker.registry.data/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py:58-201 | konker.registry.router/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py:58-201 | konker.registry.web/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py:58-201 — before extracting anything, compare `konker.registry.api/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py` and `konker.registry.data.processor/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 261 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 (28 lines × 5) konker.registry.api/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py:277— konker.registry.api/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py:277-304 | konker.registry.data.processor/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py:277-304 | konker.registry.data/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py:277-304 | konker.registry.router/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py:277-304 | konker.registry.web/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py:277-304 — before extracting anything, compare `konker.registry.api/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py` and `konker.registry.data.processor/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 261 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 (26 lines × 5) konker.registry.api/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py:207— konker.registry.api/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py:207-232 | konker.registry.data.processor/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py:207-232 | konker.registry.data/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py:207-232 | konker.registry.router/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py:207-232 | konker.registry.web/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py:207-232 — before extracting anything, compare `konker.registry.api/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py` and `konker.registry.data.processor/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 261 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 (21 lines × 5) konker.registry.api/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py:33— konker.registry.api/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py:33-53 | konker.registry.data.processor/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py:33-53 | konker.registry.data/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py:33-53 | konker.registry.router/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py:33-53 | konker.registry.web/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py:33-53 — before extracting anything, compare `konker.registry.api/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py` and `konker.registry.data.processor/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 261 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 5) konker.registry.api/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py:19— konker.registry.api/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py:19-28 | konker.registry.data.processor/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py:19-28 | konker.registry.data/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py:19-28 | konker.registry.router/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py:19-28 | konker.registry.web/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py:19-28 — before extracting anything, compare `konker.registry.api/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py` and `konker.registry.data.processor/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 261 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (32 lines × 5) konker.registry.api/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py:240— konker.registry.api/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py:240-271 | konker.registry.data.processor/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py:240-271 | konker.registry.data/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py:240-271 | konker.registry.router/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py:240-271 | konker.registry.web/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py:240-271 — before extracting anything, compare `konker.registry.api/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py` and `konker.registry.data.processor/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 261 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.
End-of-life framework: Spring Boot 1 REDACTED:1— REDACTED depends on `org.springframework.boot` at a version that pins Spring Boot 1, and Spring Boot 1.x, open-source support ended 2019-08-01. The constraint cannot admit a different major, so this repository stays on it until the declaration is edited. An end-of-life framework receives no further releases, including security releases.
P12 · CI test-gate honesty· Test suite runs only after the merge · ×1
Test suite runs only after the merge — `REDACTED` run(s) the test suite, but no workflow that runs tests is triggered by a pull request (or a merge queue) — so the suite reports on code that is already on the default branch. A red build there blocks nothing and the only remedy is a revert. Add the pull-request trigger to the workflow that runs your suite so the gate applies before the merge, not after it.
Duplicated block (40 lines × 2 locations) konker.registry.web/src/main/webapp/resources/js/destinations/rest/form.js:72— konker.registry.web/src/main/webapp/resources/js/destinations/rest/form.js:72 · konker.registry.web/src/main/webapp/resources/js/routes/form.js:10 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
Duplicated block (16 lines × 2 locations) konker.registry.web/src/main/webapp/resources/js/users/userdialog.js:23— konker.registry.web/src/main/webapp/resources/js/users/userdialog.js:23 · konker.registry.web/src/main/webapp/resources/js/users/userdialog.js:75 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (10 lines × 2 locations) REDACTED:159— REDACTED:159 · REDACTED:170 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 3 locations) konker.registry.web/src/main/webapp/resources/js/destinations/rest/form.js:42— konker.registry.web/src/main/webapp/resources/js/destinations/rest/form.js:42 · konker.registry.web/src/main/webapp/resources/js/devices/form.js:1 · konker.registry.web/src/main/webapp/resources/js/routes/form.js:76 — the 3 copies are spread across 3 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete.
Duplicated block (8 lines × 2 locations) konker.registry.web/src/main/webapp/resources/konker/scripts/main.js:32— konker.registry.web/src/main/webapp/resources/konker/scripts/main.js:32 · konker.registry.web/src/main/webapp/resources/konker/scripts/main.js:95 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (7 lines × 2 locations) konker.registry.web/src/main/webapp/resources/js/input-eye.js:4— konker.registry.web/src/main/webapp/resources/js/input-eye.js:4 · konker.registry.web/src/main/webapp/resources/js/input-eye.js:14 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2 locations) konker.registry.web/src/main/webapp/resources/js/visualization/graph.js:139— konker.registry.web/src/main/webapp/resources/js/visualization/graph.js:139 · konker.registry.web/src/main/webapp/resources/js/visualization/graph.js:156 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Complex function parseTemplate (cyclomatic 23, cognitive 40) konker.registry.web/src/main/webapp/resources/konker/scripts/mustache.js:105— parseTemplate has cyclomatic complexity 23 and cognitive complexity 40; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Test Coverage — 0% of 30 production file(s) reachable from 0 test file(s) via the import graph — 'production' here is the RESIDUE: every source file left once tests, tooling, generated output, config, declarations and declaration-only modules, fixture corpora, type fixtures, behaviour-free data modules, re-export barrels, registration/constant data modules and service workers are set aside, so the percentage is taken over a smaller denominator than the workspace's file count
Dead file (~313 LoC) REDACTED— no import path from any entry point (2 application, 0 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~204 LoC) konker.registry.web/src/main/webapp/resources/js/clipboard.js/src/clipboard-action.js— no import path from any entry point (2 application, 0 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (konker.registry.web/src/main/webapp/resources/js/clipboard.js/src/clipboard.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~192 LoC) konker.registry.web/src/main/webapp/resources/js/visualization/graph.js— no import path from any entry point (2 application, 0 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~184 LoC) konker.registry.web/src/main/webapp/resources/konker/scripts/wow.js— no import path from any entry point (2 application, 0 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~135 LoC) konker.registry.web/src/main/webapp/resources/js/clipboard.js/src/clipboard.js— no import path from any entry point (2 application, 0 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~133 LoC) konker.registry.web/src/main/webapp/resources/konker/scripts/main.js— no import path from any entry point (2 application, 0 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~121 LoC) konker.registry.web/src/main/webapp/resources/js/transformations/form.js— no import path from any entry point (2 application, 0 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~120 LoC) konker.registry.web/src/main/webapp/resources/js/destinations/rest/form.js— no import path from any entry point (2 application, 0 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~108 LoC) konker.registry.web/src/main/webapp/resources/js/users/userdialog.js— no import path from any entry point (2 application, 0 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~86 LoC) konker.registry.web/src/main/webapp/resources/js/routes/form.js— no import path from any entry point (2 application, 0 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~80 LoC) REDACTED— no import path from any entry point (2 application, 0 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~72 LoC) konker.registry.web/src/main/webapp/resources/js/visualization/outlier.js— no import path from any entry point (2 application, 0 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~66 LoC) konker.registry.web/src/main/webapp/resources/js/payment/checkout.js— no import path from any entry point (2 application, 0 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~42 LoC) konker.registry.web/src/main/webapp/resources/konker/scripts/menu.js— no import path from any entry point (2 application, 0 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~41 LoC) konker.registry.web/src/main/webapp/resources/js/devices/index.js— no import path from any entry point (2 application, 0 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~39 LoC) konker.registry.web/src/main/webapp/resources/js/notifications/status.js— no import path from any entry point (2 application, 0 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~37 LoC) REDACTED— no import path from any entry point (2 application, 0 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~34 LoC) konker.registry.web/src/main/webapp/resources/konker/scripts/json.formatter.js— no import path from any entry point (2 application, 0 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~23 LoC) konker.registry.web/src/main/webapp/resources/js/payment/plans.js— no import path from any entry point (2 application, 0 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~22 LoC) konker.registry.web/src/main/webapp/resources/js/enrichment/form.js— no import path from any entry point (2 application, 0 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~17 LoC) konker.registry.web/src/main/webapp/resources/js/devices/password.js— no import path from any entry point (2 application, 0 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~11 LoC) konker.registry.web/src/main/webapp/resources/js/devices/form.js— no import path from any entry point (2 application, 0 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~3 LoC) konker.registry.web/src/main/webapp/resources/js/global.js— no import path from any entry point (2 application, 0 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~1 LoC) konker.registry.web/src/main/webapp/resources/js/panel/index.js— no import path from any entry point (2 application, 0 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Third-party script without Subresource Integrity konker.registry.web/src/main/webapp/views/devices/events.html:260— `https://developers.google.com/maps/documentation/javascript/examples/markerclusterer/markerclusterer.js` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. The URL also names no version, so it resolves to whatever that origin serves at fetch time — the executed bytes can change with nobody touching this repository. 4 such include(s) across the repository's markup.
No direct assertions: shouldCreateAlertTrigger konker.registry.api/src/test/java/com/konkerlabs/platform/registry/api/test/web/controller/AlertTriggerRestControllerTest.java:210— No conventional assertion call was detected, and 258 of 267 tests in `konker.registry.api` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: shouldEditAlertTrigger konker.registry.api/src/test/java/com/konkerlabs/platform/registry/api/test/web/controller/AlertTriggerRestControllerTest.java:182— No conventional assertion call was detected, and 258 of 267 tests in `konker.registry.api` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: shouldListAlertTrigger konker.registry.api/src/test/java/com/konkerlabs/platform/registry/api/test/web/controller/AlertTriggerRestControllerTest.java:129— No conventional assertion call was detected, and 258 of 267 tests in `konker.registry.api` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: shouldReadAlertTrigger konker.registry.api/src/test/java/com/konkerlabs/platform/registry/api/test/web/controller/AlertTriggerRestControllerTest.java:260— No conventional assertion call was detected, and 258 of 267 tests in `konker.registry.api` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: shouldRemoveAlertTrigger konker.registry.api/src/test/java/com/konkerlabs/platform/registry/api/test/web/controller/AlertTriggerRestControllerTest.java:237— No conventional assertion call was detected, and 258 of 267 tests in `konker.registry.api` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: shouldReturnInternalErrorWhenListAlertTrigger konker.registry.api/src/test/java/com/konkerlabs/platform/registry/api/test/web/controller/AlertTriggerRestControllerTest.java:162— No conventional assertion call was detected, and 258 of 267 tests in `konker.registry.api` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: shouldCreateDevice konker.registry.api/src/test/java/com/konkerlabs/platform/registry/api/test/web/controller/ApplicationDocumentStoreRestControllerTest.java:152— No conventional assertion call was detected, and 258 of 267 tests in `konker.registry.api` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: shouldDeleteDevice konker.registry.api/src/test/java/com/konkerlabs/platform/registry/api/test/web/controller/ApplicationDocumentStoreRestControllerTest.java:230— No conventional assertion call was detected, and 258 of 267 tests in `konker.registry.api` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: shouldReadDevice konker.registry.api/src/test/java/com/konkerlabs/platform/registry/api/test/web/controller/ApplicationDocumentStoreRestControllerTest.java:98— No conventional assertion call was detected, and 258 of 267 tests in `konker.registry.api` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: shouldReadWithWrongApplication konker.registry.api/src/test/java/com/konkerlabs/platform/registry/api/test/web/controller/ApplicationDocumentStoreRestControllerTest.java:114— No conventional assertion call was detected, and 258 of 267 tests in `konker.registry.api` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: shouldTryCreateDeviceWithBadRequest konker.registry.api/src/test/java/com/konkerlabs/platform/registry/api/test/web/controller/ApplicationDocumentStoreRestControllerTest.java:171— No conventional assertion call was detected, and 258 of 267 tests in `konker.registry.api` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: shouldTryDeleteDeviceWithInternalError konker.registry.api/src/test/java/com/konkerlabs/platform/registry/api/test/web/controller/ApplicationDocumentStoreRestControllerTest.java:267— No conventional assertion call was detected, and 258 of 267 tests in `konker.registry.api` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: shouldTryDeleteNonexistentEventRoute konker.registry.api/src/test/java/com/konkerlabs/platform/registry/api/test/web/controller/ApplicationDocumentStoreRestControllerTest.java:285— No conventional assertion call was detected, and 258 of 267 tests in `konker.registry.api` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: shouldTryDeleteWithWrongApplication konker.registry.api/src/test/java/com/konkerlabs/platform/registry/api/test/web/controller/ApplicationDocumentStoreRestControllerTest.java:248— No conventional assertion call was detected, and 258 of 267 tests in `konker.registry.api` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: shouldTryReadDeviceWithBadRequest konker.registry.api/src/test/java/com/konkerlabs/platform/registry/api/test/web/controller/ApplicationDocumentStoreRestControllerTest.java:133— No conventional assertion call was detected, and 258 of 267 tests in `konker.registry.api` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: shouldTryUpdateDeviceWithInternalError konker.registry.api/src/test/java/com/konkerlabs/platform/registry/api/test/web/controller/ApplicationDocumentStoreRestControllerTest.java:210— No conventional assertion call was detected, and 258 of 267 tests in `konker.registry.api` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: shouldUpdateDevice konker.registry.api/src/test/java/com/konkerlabs/platform/registry/api/test/web/controller/ApplicationDocumentStoreRestControllerTest.java:192— No conventional assertion call was detected, and 258 of 267 tests in `konker.registry.api` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: shouldCreateApplication konker.registry.api/src/test/java/com/konkerlabs/platform/registry/api/test/web/controller/ApplicationRestControllerTest.java:296— No conventional assertion call was detected, and 258 of 267 tests in `konker.registry.api` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: shouldDeleteApplication konker.registry.api/src/test/java/com/konkerlabs/platform/registry/api/test/web/controller/ApplicationRestControllerTest.java:395— No conventional assertion call was detected, and 258 of 267 tests in `konker.registry.api` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: shouldDeleteHealthAlertFromApplication konker.registry.api/src/test/java/com/konkerlabs/platform/registry/api/test/web/controller/ApplicationRestControllerTest.java:506— No conventional assertion call was detected, and 258 of 267 tests in `konker.registry.api` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: shouldListApplications konker.registry.api/src/test/java/com/konkerlabs/platform/registry/api/test/web/controller/ApplicationRestControllerTest.java:161— No conventional assertion call was detected, and 258 of 267 tests in `konker.registry.api` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: shouldReadApplicationByName konker.registry.api/src/test/java/com/konkerlabs/platform/registry/api/test/web/controller/ApplicationRestControllerTest.java:223— No conventional assertion call was detected, and 258 of 267 tests in `konker.registry.api` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: shouldReadDefaultApplicationByName konker.registry.api/src/test/java/com/konkerlabs/platform/registry/api/test/web/controller/ApplicationRestControllerTest.java:248— No conventional assertion call was detected, and 258 of 267 tests in `konker.registry.api` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: shouldReturnInternalErrorWhenDeleteApplication konker.registry.api/src/test/java/com/konkerlabs/platform/registry/api/test/web/controller/ApplicationRestControllerTest.java:412— No conventional assertion call was detected, and 258 of 267 tests in `konker.registry.api` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: shouldReturnInternalErrorWhenListApplications konker.registry.api/src/test/java/com/konkerlabs/platform/registry/api/test/web/controller/ApplicationRestControllerTest.java:204— No conventional assertion call was detected, and 258 of 267 tests in `konker.registry.api` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
Orphaned file konker.security/src/main/java/com/konkerlabs/platform/security/crypto/BCrypt.java:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/HealthAlertServiceImpl.java:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file konker.registry.services.storage.cassandra/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/EventRepositoryCassandraImpl.java:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file REDACTED:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/audit/KonkerLogger.java:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file konker.registry.data/src/main/java/com/konkerlabs/platform/registry/integration/endpoints/DeviceEventRestEndpoint.java:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/LocationServiceImpl.java:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file konker.registry.idm.resourceserver/src/main/java/com/konkerlabs/platform/registry/idm/services/OAuthClientDetailsService.java:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/EventRouteRestController.java:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/EventRouteServiceImpl.java:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceModelServiceImpl.java:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file konker.scripts/registry/users/migrate_user_roles.py:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/PrivateStorageServiceImpl.java:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/EventSchemaServiceImpl.java:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/LocationRestController.java:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceConfigSetupServiceImpl.java:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file konker.registry.web/src/main/java/com/konkerlabs/platform/registry/idm/web/controllers/AccountClientsController.java:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file konker.registry.web/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file konker.registry.router/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file konker.registry.data.processor/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file konker.registry.data/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file konker.registry.api/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/RestDestinationServiceImpl.java:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file konker.registry.services.storage.mongodb/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/EventRepositoryMongoImpl.java:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file konker.registry.data/src/main/java/com/konkerlabs/platform/registry/integration/endpoints/GatewayEventRestEndpoint.java:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Interpolated log message defeats structured logging konker.registry.services.storage.cassandra/src/main/java/com/konkerlabs/platform/registry/business/repositories/config/CassandraRegistryConfig.java:57— `warn` at line 57 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/config/MongoPrivateStorageConfig.java:123— `info` at line 123 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/config/MongoPrivateStorageConfig.java:125— `info` at line 125 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/UserServiceImpl.java:179— `info` at line 179 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/UserServiceImpl.java:185— `error` at line 185 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging konker.registry.data.processor/src/main/java/com/konkerlabs/platform/registry/integration/endpoints/DeviceConfigRabbitEndpoint.java:50— `debug` at line 50 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging konker.registry.data.processor/src/main/java/com/konkerlabs/platform/registry/integration/endpoints/DeviceEventRabbitEndpoint.java:34— `debug` at line 34 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/services/DeviceLogEventServiceImpl.java:147— `warn` at line 147 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/services/DeviceLogEventServiceImpl.java:174— `warn` at line 174 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/services/DeviceLogEventServiceImpl.java:192— `warn` at line 192 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/services/DeviceLogEventServiceImpl.java:209— `warn` at line 209 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/services/DeviceLogEventServiceImpl.java:216— `warn` at line 216 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/services/DeviceLogEventServiceImpl.java:226— `warn` at line 226 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/services/DeviceLogEventServiceImpl.java:232— `warn` at line 232 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/services/routes/EventRouteExecutorImpl.java:127— `error` at line 127 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/services/routes/EventRouteExecutorImpl.java:223— `debug` at line 223 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/services/routes/EventRouteExecutorImpl.java:230— `debug` at line 230 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/services/publishers/EventPublisherAmazonKinesis.java:77— `info` at line 77 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/services/publishers/EventPublisherDevice.java:85— `debug` at line 85 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/services/publishers/EventPublisherRest.java:108— `debug` at line 108 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/security/KonkerBasicAuthenticationFilter.java:61— `warn` at line 61 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/security/KonkerBasicAuthenticationFilter.java:69— `warn` at line 69 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/security/KonkerBasicAuthenticationFilter.java:75— `warn` at line 75 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/integration/processors/DeviceEventProcessor.java:149— `info` at line 149 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/integration/processors/DeviceEventProcessor.java:161— `error` at line 161 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, 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 level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Duplicated predicate konker.registry.web/src/main/java/com/konkerlabs/platform/registry/web/controllers/RecoverPasswordController.java:163— `!Optional.ofNullable(serviceResponse).isPresent() || !Optional.ofNullable(serviceResponse.getResult()).isPresent()` appears character-identically in 2 files — konker.registry.web/src/main/java/com/konkerlabs/platform/registry/web/controllers/RecoverPasswordController.java, konker.registry.web/src/main/java/com/konkerlabs/platform/registry/web/controllers/UserSubscriptionController.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/config/MongoAuditConfig.java:87— `!StringUtils.isEmpty(getUsername()) && !StringUtils.isEmpty(getPassword())` appears character-identically in 4 files — konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/config/MongoAuditConfig.java, konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/config/MongoBillingConfig.java, konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/config/MongoConfig.java, konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/config/MongoPrivateStorageConfig.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceEventServiceImpl.java:66— `Optional.ofNullable(user.getApplication()).isPresent() && !application.equals(user.getApplication())` appears character-identically in 3 files — konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceEventServiceImpl.java, konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/GatewayServiceImpl.java, konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/PrivateStorageServiceImpl.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/UserRestController.java:113— `Optional.ofNullable(userForm.getPassword()).isPresent() && !userForm.getPassword().isEmpty()` appears character-identically in 2 files — konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/UserRestController.java, konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/web/controller/UserSubscriptionRestController.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/model/DeviceModel.java:84— `getName() != null && !regex.matcher(getName()).matches()` appears character-identically in 3 files — konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/model/DeviceModel.java, konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/model/Gateway.java, konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/model/Location.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/model/Device.java:99— `getName() == null || getName().isEmpty()` appears character-identically in 4 files — konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/model/Device.java, konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/model/DeviceModel.java, konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/model/EventRoute.java, konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/model/Gateway.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate konker.registry.data.processor/src/main/java/com/konkerlabs/platform/registry/integration/endpoints/DeviceConfigRabbitEndpoint.java:53— `properties == null || properties.getHeaders().isEmpty()` appears character-identically in 2 files — konker.registry.data.processor/src/main/java/com/konkerlabs/platform/registry/integration/endpoints/DeviceConfigRabbitEndpoint.java, konker.registry.data.processor/src/main/java/com/konkerlabs/platform/registry/integration/endpoints/DeviceEventRabbitEndpoint.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/exceptions/BadRequestResponseException.java:20— `serviceResponse != null && serviceResponse.getResponseMessages() != null` appears character-identically in 2 files — konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/exceptions/BadRequestResponseException.java, konker.registry.api/src/main/java/com/konkerlabs/platform/registry/api/exceptions/NotAuthorizedResponseException.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate konker.registry.web/src/main/java/com/konkerlabs/platform/registry/web/controllers/RecoverPasswordController.java:180— `serviceResponse.getResult().getIsExpired() || !validToken.getResult()` appears character-identically in 2 files — konker.registry.web/src/main/java/com/konkerlabs/platform/registry/web/controllers/RecoverPasswordController.java, konker.registry.web/src/main/java/com/konkerlabs/platform/registry/web/controllers/UserSubscriptionController.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/AlertTriggerServiceImpl.java:26— `validationsResponse != null && !validationsResponse.isOk()` appears character-identically in 5 files — konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/AlertTriggerServiceImpl.java, konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/ApplicationDocumentStoreServiceImpl.java, konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceConfigSetupServiceImpl.java, konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceCustomDataServiceImpl.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate REDACTED:9— `typeof define === 'function' && define.amd` appears character-identically in 3 files — REDACTED, REDACTED, konker.registry.web/src/main/webapp/resources/konker/scripts/mustache.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate konker.registry.api/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py:133— `len(line_start) > 0 and line_start[0] == '#'` appears character-identically in 5 files — konker.registry.api/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py, konker.registry.data.processor/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py, konker.registry.data/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py, konker.registry.router/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate konker.registry.api/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py:151— `setting is not None and line_indent <= indent` appears character-identically in 5 files — konker.registry.api/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py, konker.registry.data.processor/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py, konker.registry.data/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py, konker.registry.router/docker-resources/nginx/filebeat/scripts/migrate_beat_config_1_x_to_5_0.py. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
P10 · Library API & versioning· Implementation type on the public API · ×11
Implementation type on the public API konker.registry.cassandra-etl/src/main/java/org/konker/registry/cassandraetl/repositories/EventRepositoryCassandraEtlImpl.java:25— 1 public type in `org.konker.registry.cassandraetl.repositories` is marked as implementation by its own namespace, folder or name: `EventRepositoryCassandraEtlImpl` (konker.registry.cassandra-etl/src/main/java/org/konker/registry/cassandraetl/repositories/EventRepositoryCassandraEtlImpl.java:25, name ends in `Impl`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers.
Implementation type on the public API konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/integration/gateway/HttpGatewayImpl.java:22— 1 public type in `com.konkerlabs.platform.registry.data.core.integration.gateway` is marked as implementation by its own namespace, folder or name: `HttpGatewayImpl` (konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/integration/gateway/HttpGatewayImpl.java:22, name ends in `Impl`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers.
Implementation type on the public API konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/services/DeviceLogEventServiceImpl.java:41— 1 public type in `com.konkerlabs.platform.registry.data.core.services` is marked as implementation by its own namespace, folder or name: `DeviceLogEventServiceImpl` (konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/services/DeviceLogEventServiceImpl.java:41, name ends in `Impl`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers.
Implementation type on the public API konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/services/routes/EventRouteExecutorImpl.java:33— 2 public types in `com.konkerlabs.platform.registry.data.core.services.routes` are marked as implementation by their own namespace, folder or name: `EventRouteExecutorImpl` (konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/services/routes/EventRouteExecutorImpl.java:33, name ends in `Impl`), `EventTransformationServiceImpl` (konker.registry.data.core/src/main/java/com/konkerlabs/platform/registry/data/core/services/routes/EventTransformationServiceImpl.java:30, name ends in `Impl`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers.
Implementation type on the public API konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/api/BaseEventRepositoryImpl.java:15— 1 public type in `com.konkerlabs.platform.registry.business.repositories.events.api` is marked as implementation by its own namespace, folder or name: `BaseEventRepositoryImpl` (konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/api/BaseEventRepositoryImpl.java:15, name ends in `Impl`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers.
Implementation type on the public API konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/AlertTriggerServiceImpl.java:14— 28 public types in `com.konkerlabs.platform.registry.business.services` are marked as implementation by their own namespace, folder or name: `AlertTriggerServiceImpl` (konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/AlertTriggerServiceImpl.java:14, name ends in `Impl`), `ApplicationDocumentStoreServiceImpl` (konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/ApplicationDocumentStoreServiceImpl.java:27, name ends in `Impl`), `ApplicationServiceImpl` (konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/ApplicationServiceImpl.java:27, name ends in `Impl`), `DeviceConfigSetupServiceImpl` (konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceConfigSetupServiceImpl.java:36, name ends in `Impl`), `DeviceCustomDataServiceImpl` (konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceCustomDataServiceImpl.java:30, name ends in `Impl`), `DeviceEventServiceImpl` (konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceEventServiceImpl.java:25, name ends in `Impl`), `DeviceFirmwareServiceImpl` (konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceFirmwareServiceImpl.java:32, name ends in `Impl`), `DeviceFirmwareUpdateServiceImpl` (konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceFirmwareUpdateServiceImpl.java:24, name ends in `Impl`), and 20 more. While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers.
Implementation type on the public API konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/api/UserNotificationServiceImpl.java:29— 1 public type in `com.konkerlabs.platform.registry.business.services.api` is marked as implementation by its own namespace, folder or name: `UserNotificationServiceImpl` (konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/api/UserNotificationServiceImpl.java:29, name ends in `Impl`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers.
Implementation type on the public API konker.registry.services.storage.cassandra/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/EventRepositoryCassandraImpl.java:34— 2 public types in `com.konkerlabs.platform.registry.business.repositories.events` are marked as implementation by their own namespace, folder or name: `EventRepositoryCassandraImpl` (konker.registry.services.storage.cassandra/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/EventRepositoryCassandraImpl.java:34, name ends in `Impl`), `EventRepositoryMongoImpl` (konker.registry.services.storage.mongodb/src/main/java/com/konkerlabs/platform/registry/business/repositories/events/EventRepositoryMongoImpl.java:34, name ends in `Impl`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers.
Implementation type on the public API konker.registry.web/src/main/java/com/konkerlabs/platform/registry/web/services/AvatarServiceImpl.java:32— 3 public types in `com.konkerlabs.platform.registry.web.services` are marked as implementation by their own namespace, folder or name: `AvatarServiceImpl` (konker.registry.web/src/main/java/com/konkerlabs/platform/registry/web/services/AvatarServiceImpl.java:32, name ends in `Impl`), `CaptchaServiceImpl` (konker.registry.web/src/main/java/com/konkerlabs/platform/registry/web/services/CaptchaServiceImpl.java:23, name ends in `Impl`), `UploadServiceImpl` (konker.registry.web/src/main/java/com/konkerlabs/platform/registry/web/services/UploadServiceImpl.java:19, name ends in `Impl`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers.
Implementation type on the public API konker.utilities/src/main/java/com/konkerlabs/platform/utilities/expressions/ExpressionEvaluationServiceImpl.java:23— 1 public type in `com.konkerlabs.platform.utilities.expressions` is marked as implementation by its own namespace, folder or name: `ExpressionEvaluationServiceImpl` (konker.utilities/src/main/java/com/konkerlabs/platform/utilities/expressions/ExpressionEvaluationServiceImpl.java:23, name ends in `Impl`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers.
Implementation type on the public API konker.utilities/src/main/java/com/konkerlabs/platform/utilities/parsers/json/JsonParsingServiceImpl.java:23— 1 public type in `com.konkerlabs.platform.utilities.parsers.json` is marked as implementation by its own namespace, folder or name: `JsonParsingServiceImpl` (konker.utilities/src/main/java/com/konkerlabs/platform/utilities/parsers/json/JsonParsingServiceImpl.java:23, name ends in `Impl`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers.
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×3
Projects may be oversized for their cohesion REDACTED:1— `konker.registry.web` (18209 LoC, 118 module-visible types across 35 directories) overshoots its size bounds. 3 of 19 build unit(s) (Maven, Python) overshoot their size bounds, lowering Project Cohesion to 7.3/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.
Projects may be oversized for their cohesion REDACTED:1— `konker.registry.services.core` (15538 LoC, 267 module-visible types across 20 directories) overshoots its size bounds. 3 of 19 build unit(s) (Maven, Python) overshoot their size bounds, lowering Project Cohesion to 7.3/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.
Projects may be oversized for their cohesion REDACTED:1— `konker.registry.api` (6959 LoC, 96 module-visible types across 11 directories) overshoots its size bounds. 3 of 19 build unit(s) (Maven, Python) overshoot their size bounds, lowering Project Cohesion to 7.3/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.
D34 · Knowledge Freshness· Most significant orphaned file · ×3
Most significant orphaned file konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/model/enumerations/TimeZone.java:1— One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
Most significant orphaned file konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/DeviceRegisterServiceImpl.java:1— One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
Most significant orphaned file konker.registry.services.core/src/main/java/com/konkerlabs/platform/registry/business/services/UserServiceImpl.java:1— One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
No ADRs found konker.scripts/registry/setup.py:4— 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 `konker.scripts/registry/setup.py` makes this repository a deployable product (line 4).
Dormant codebase — 193 of 193 significant files have no living knowledge — the codebase as a whole is dormant, not 193 separate risks. Counted over 193 of the 512 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over. Re-engage owners or document before change.
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.
No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
M2 · Architecture documentation· No architecture diagram/doc · ×1
No architecture diagram/doc — No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
Logging is not universal — Only 12/15 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `konker.samples/rest-json-enrichment`, `konker.samples/rest-json-transformation`, `konker.samples/smart-temperature`.
No SAST — No static application security testing detected. For this repository's stack, add spotbugs with find-sec-bugs (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 1 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
No dependency-update automation REDACTED:37— `REDACTED` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`.
No changelog — No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
No security response headers detected REDACTED:1— 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.)
X5 · Nullable reference types· Java packages are not null-marked everywhere · ×1
Java packages are not null-marked everywhere — 0/97 of this repository's Java package directories are under a non-null default: a `package-info.java` declaring `@NullMarked` (JSpecify) or `@NonNullApi`, `@ParametersAreNonnullByDefault`, `@NonNullByDefault`, `@DefaultQualifier(NonNull.class)`; a `module-info.java` declaring `@NullMarked`; every type in it `@NullMarked`; or a build that runs NullAway with the package in `AnnotatedPackages`, or the Checker Framework's `NullnessChecker`. Elsewhere every reference admits null and no checker warns on the dereference that throws a `NullPointerException`.
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
runtime-hardening: not applicable — 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 01a1e859-24bd-72a3-8e48-0a186912df18 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 261 · Warnings: 795 · Recommendations: 681 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 17-11-2026 @ 07:11 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.