Public report of jufeng98/java-master, 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, 08:53 UTC · Survey ID cd_85bb90469cd24f8caf8b19f3be6e47c4
jufeng98/java-master
Measured 17 November 2026, 08:50 UTC, at code version ca0bcd5
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 large codebase: 110,202 lines of product code in 30 projects, tests not counted · Estimated rebuild effort: about 0.7 person-years · Weakest lens: Production Readiness, 20.5
Findings by how serious they are
524 critical1045 serious656 minor
15 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, 08:50 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 ▸
75of 75 dimensions measured by tools.
1984of 2225 findings point to an exact file and line, so you can open each one in the code. The other 241 concern the repository as a whole, such as missing documentation.
75dimensions across 7 lenses, read from 110,202 lines of product code in 30 projects.
jufeng98/java-master is rated At risk because critical security findings are open, most of them in the packages it uses. Its score is held back because we found no working pipeline that builds or tests changes to the code and it has packages under a licence on your banned list. It scores 31.7 out of 100, which the At risk rating leaves unchanged.
Production Readiness, at 20.5, is the weakest lens and counts most in the score. The best first step is replacing the six packages under a banned licence, worth about 9.5 points. Fixing the two passwords or keys in the code's history comes next, worth about 6.4 points. Raising Production Readiness to 70 would lift the score to about 41.1.
448 known security holes in the packages the code depends on can be used by attackers. Eight weaknesses in the code could be used by an attacker, and twenty-two controls can't be used without a mouse. Updating the vulnerable packages, fixing the weaknesses the scanner points to and making the controls work with a keyboard would close these risks. The four unsafe settings in infrastructure or container files need changing to safe values. The three passwords or keys in the code's history and the password or key in the code need replacing, with the old ones switched off. The ten uses of packages that aren't listed need adding to the project's list of dependencies.
The product code is 110,202 lines, about €100,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 Production Readiness rose from 20.5 to 70, the lowest score rated Strong, the score would rise from 31.7 to about 41.1.
Code composition: what the lines of code are
Product code 94%Tests 6%
Rebuild cost: about €100,000 · Estimate
Cost to rebuild
€33,000 to €170,000, for 552 to 1,752 hours of work, about 0.7 person-years for 1 to 2 engineers
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.7 at a score of 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
Large: 110,202 lines of product code
What it is not
Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.
How the estimate is made: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Resolve the 6 Banned license finding(s) in License Compliance.
Resolve the 2 REDACTED finding(s) in REDACTED Scanning — start with REDACTED (2).
Raises the score by about 6.4 points · Low effort · REDACTED Scanning
3
Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED.
Raises the score by about 4.6 points · Low effort · REDACTED Scanning
Diagnosis: what the measurements show together
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
Where the investment is most exposed · Value at risk
This code would cost about €100,000 to build again, about 0.7 person-years of work. Its weakest lens is Production Readiness, at 20.5 (Critical). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
If you do one thing first · First action
Resolve the 6 Banned license finding(s) in License Compliance. Of all the actions in this report, it raises the score most for the work it takes: about 9.5 points for low effort, because it clears the 6 License Compliance findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 6.4 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 4% to 9% on every change.
How this is estimated: It rests on an assumption 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. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Code Duplication · Cohesion (LCOM4)
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.
312 modules, with 218 dependencies between them. 3 loops run through 11 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 272 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.
org.javamaster.b2c.bytecode.attribute uses org.javamaster.b2c.bytecode, so a change to org.javamaster.b2c.bytecode can break org.javamaster.b2c.bytecode.attribute, while a change to org.javamaster.b2c.bytecode.attribute can't break org.javamaster.b2c.bytecode.
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.
org.javamaster.b2c.core.mapper uses org.javamaster.b2c.core.entity, so a change to org.javamaster.b2c.core.entity can break org.javamaster.b2c.core.mapper, while a change to org.javamaster.b2c.core.mapper can't break org.javamaster.b2c.core.entity.
Position
Below the diagonal: org.javamaster.b2c.core.mapper uses a module listed above it, which is the healthy direction.
org.javamaster.b2c.core.mapper uses org.javamaster.b2c.core.enums, so a change to org.javamaster.b2c.core.enums can break org.javamaster.b2c.core.mapper, while a change to org.javamaster.b2c.core.mapper can't break org.javamaster.b2c.core.enums.
Position
Below the diagonal: org.javamaster.b2c.core.mapper uses a module listed above it, which is the healthy direction.
org.javamaster.b2c.core.mapper uses org.javamaster.b2c.core.model, so a change to org.javamaster.b2c.core.model can break org.javamaster.b2c.core.mapper, while a change to org.javamaster.b2c.core.mapper can't break org.javamaster.b2c.core.model.
Position
Below the diagonal: org.javamaster.b2c.core.mapper uses a module listed above it, which is the healthy direction.
org.javamaster.b2c.core.model.vo uses org.javamaster.b2c.core.entity, so a change to org.javamaster.b2c.core.entity can break org.javamaster.b2c.core.model.vo, while a change to org.javamaster.b2c.core.model.vo can't break org.javamaster.b2c.core.entity.
Position
Below the diagonal: org.javamaster.b2c.core.model.vo uses a module listed above it, which is the healthy direction.
org.javamaster.b2c.core.model.vo uses org.javamaster.b2c.core.enums, so a change to org.javamaster.b2c.core.enums can break org.javamaster.b2c.core.model.vo, while a change to org.javamaster.b2c.core.model.vo can't break org.javamaster.b2c.core.enums.
Position
Below the diagonal: org.javamaster.b2c.core.model.vo uses a module listed above it, which is the healthy direction.
org.javamaster.b2c.core.model.vo uses org.javamaster.b2c.core.model, so a change to org.javamaster.b2c.core.model can break org.javamaster.b2c.core.model.vo, while a change to org.javamaster.b2c.core.model.vo can't break org.javamaster.b2c.core.model.
Position
Below the diagonal: org.javamaster.b2c.core.model.vo uses a module listed above it, which is the healthy direction.
19→23 org.javamaster.invocationlab.admin.service.creation.entity uses org.javamaster.invocationlab.admin.service.creationpart of a loop✕
Connections
1 pair of types, where a type in org.javamaster.invocationlab.admin.service.creation.entity uses a type in org.javamaster.invocationlab.admin.service.creation.
org.javamaster.invocationlab.admin.service.creation.entity uses org.javamaster.invocationlab.admin.service.creation, so a change to org.javamaster.invocationlab.admin.service.creation can break org.javamaster.invocationlab.admin.service.creation.entity, while a change to org.javamaster.invocationlab.admin.service.creation.entity can't break org.javamaster.invocationlab.admin.service.creation.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→28 org.javamaster.invocationlab.admin.service.creation.entity uses org.javamaster.invocationlab.admin.servicepart of a loop✕
Connections
2 pairs of types, where a type in org.javamaster.invocationlab.admin.service.creation.entity uses a type in org.javamaster.invocationlab.admin.service.
org.javamaster.invocationlab.admin.service.creation.entity uses org.javamaster.invocationlab.admin.service, so a change to org.javamaster.invocationlab.admin.service can break org.javamaster.invocationlab.admin.service.creation.entity, while a change to org.javamaster.invocationlab.admin.service.creation.entity can't break org.javamaster.invocationlab.admin.service.
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.
org.javamaster.spring.swagger.controller uses org.javamaster.spring.swagger.model, so a change to org.javamaster.spring.swagger.model can break org.javamaster.spring.swagger.controller, while a change to org.javamaster.spring.swagger.controller can't break org.javamaster.spring.swagger.model.
Position
Below the diagonal: org.javamaster.spring.swagger.controller uses a module listed above it, which is the healthy direction.
org.javamaster.b2c.bytecode uses org.javamaster.b2c.bytecode.attribute, so a change to org.javamaster.b2c.bytecode.attribute can break org.javamaster.b2c.bytecode, while a change to org.javamaster.b2c.bytecode can't break org.javamaster.b2c.bytecode.attribute.
Position
Below the diagonal: org.javamaster.b2c.bytecode uses a module listed above it, which is the healthy direction.
org.javamaster.b2c.core.service uses org.javamaster.b2c.core.entity, so a change to org.javamaster.b2c.core.entity can break org.javamaster.b2c.core.service, while a change to org.javamaster.b2c.core.service can't break org.javamaster.b2c.core.entity.
Position
Below the diagonal: org.javamaster.b2c.core.service uses a module listed above it, which is the healthy direction.
org.javamaster.b2c.core.service uses org.javamaster.b2c.core.model.vo, so a change to org.javamaster.b2c.core.model.vo can break org.javamaster.b2c.core.service, while a change to org.javamaster.b2c.core.service can't break org.javamaster.b2c.core.model.vo.
Position
Below the diagonal: org.javamaster.b2c.core.service uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in org.javamaster.invocationlab.admin.service.creation uses a type in org.javamaster.invocationlab.admin.service.repository.redis.
org.javamaster.invocationlab.admin.service.creation uses org.javamaster.invocationlab.admin.service.repository.redis, so a change to org.javamaster.invocationlab.admin.service.repository.redis can break org.javamaster.invocationlab.admin.service.creation, while a change to org.javamaster.invocationlab.admin.service.creation can't break org.javamaster.invocationlab.admin.service.repository.redis.
Position
Below the diagonal: org.javamaster.invocationlab.admin.service.creation uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in org.javamaster.invocationlab.admin.service.creation uses a type in org.javamaster.invocationlab.admin.service.creation.entity.
org.javamaster.invocationlab.admin.service.creation uses org.javamaster.invocationlab.admin.service.creation.entity, so a change to org.javamaster.invocationlab.admin.service.creation.entity can break org.javamaster.invocationlab.admin.service.creation, while a change to org.javamaster.invocationlab.admin.service.creation can't break org.javamaster.invocationlab.admin.service.creation.entity.
Position
Below the diagonal: org.javamaster.invocationlab.admin.service.creation uses a module listed above it, which is the healthy direction.
23→28 org.javamaster.invocationlab.admin.service.creation uses org.javamaster.invocationlab.admin.servicepart of a loop✕
Connections
4 pairs of types, where a type in org.javamaster.invocationlab.admin.service.creation uses a type in org.javamaster.invocationlab.admin.service.
org.javamaster.invocationlab.admin.service.creation uses org.javamaster.invocationlab.admin.service, so a change to org.javamaster.invocationlab.admin.service can break org.javamaster.invocationlab.admin.service.creation, while a change to org.javamaster.invocationlab.admin.service.creation can't break org.javamaster.invocationlab.admin.service.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
23→34 org.javamaster.invocationlab.admin.service.creation uses org.javamaster.invocationlab.admin.service.mavenpart of a loop✕
Connections
1 pair of types, where a type in org.javamaster.invocationlab.admin.service.creation uses a type in org.javamaster.invocationlab.admin.service.maven.
org.javamaster.invocationlab.admin.service.creation uses org.javamaster.invocationlab.admin.service.maven, so a change to org.javamaster.invocationlab.admin.service.maven can break org.javamaster.invocationlab.admin.service.creation, while a change to org.javamaster.invocationlab.admin.service.creation can't break org.javamaster.invocationlab.admin.service.maven.
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 org.javamaster.invocationlab.admin.service.invocation.entity uses a type in org.javamaster.invocationlab.admin.service.creation.entity.
org.javamaster.invocationlab.admin.service.invocation.entity uses org.javamaster.invocationlab.admin.service.creation.entity, so a change to org.javamaster.invocationlab.admin.service.creation.entity can break org.javamaster.invocationlab.admin.service.invocation.entity, while a change to org.javamaster.invocationlab.admin.service.invocation.entity can't break org.javamaster.invocationlab.admin.service.creation.entity.
Position
Below the diagonal: org.javamaster.invocationlab.admin.service.invocation.entity uses a module listed above it, which is the healthy direction.
24→27 org.javamaster.invocationlab.admin.service.invocation.entity uses org.javamaster.invocationlab.admin.service.invocationpart of a loop✕
Connections
1 pair of types, where a type in org.javamaster.invocationlab.admin.service.invocation.entity uses a type in org.javamaster.invocationlab.admin.service.invocation.
org.javamaster.invocationlab.admin.service.invocation.entity uses org.javamaster.invocationlab.admin.service.invocation, so a change to org.javamaster.invocationlab.admin.service.invocation can break org.javamaster.invocationlab.admin.service.invocation.entity, while a change to org.javamaster.invocationlab.admin.service.invocation.entity can't break org.javamaster.invocationlab.admin.service.invocation.
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.
org.javamaster.b2c.core.controller uses org.javamaster.b2c.core.entity, so a change to org.javamaster.b2c.core.entity can break org.javamaster.b2c.core.controller, while a change to org.javamaster.b2c.core.controller can't break org.javamaster.b2c.core.entity.
Position
Below the diagonal: org.javamaster.b2c.core.controller uses a module listed above it, which is the healthy direction.
org.javamaster.b2c.core.controller uses org.javamaster.b2c.core.model, so a change to org.javamaster.b2c.core.model can break org.javamaster.b2c.core.controller, while a change to org.javamaster.b2c.core.controller can't break org.javamaster.b2c.core.model.
Position
Below the diagonal: org.javamaster.b2c.core.controller uses a module listed above it, which is the healthy direction.
org.javamaster.b2c.core.controller uses org.javamaster.b2c.core.model.vo, so a change to org.javamaster.b2c.core.model.vo can break org.javamaster.b2c.core.controller, while a change to org.javamaster.b2c.core.controller can't break org.javamaster.b2c.core.model.vo.
Position
Below the diagonal: org.javamaster.b2c.core.controller uses a module listed above it, which is the healthy direction.
org.javamaster.b2c.core.controller uses org.javamaster.b2c.core.service, so a change to org.javamaster.b2c.core.service can break org.javamaster.b2c.core.controller, while a change to org.javamaster.b2c.core.controller can't break org.javamaster.b2c.core.service.
Position
Below the diagonal: org.javamaster.b2c.core.controller uses a module listed above it, which is the healthy direction.
org.javamaster.b2c.core.service.impl uses org.javamaster.b2c.core.entity, so a change to org.javamaster.b2c.core.entity can break org.javamaster.b2c.core.service.impl, while a change to org.javamaster.b2c.core.service.impl can't break org.javamaster.b2c.core.entity.
Position
Below the diagonal: org.javamaster.b2c.core.service.impl uses a module listed above it, which is the healthy direction.
org.javamaster.b2c.core.service.impl uses org.javamaster.b2c.core.mapper, so a change to org.javamaster.b2c.core.mapper can break org.javamaster.b2c.core.service.impl, while a change to org.javamaster.b2c.core.service.impl can't break org.javamaster.b2c.core.mapper.
Position
Below the diagonal: org.javamaster.b2c.core.service.impl uses a module listed above it, which is the healthy direction.
org.javamaster.b2c.core.service.impl uses org.javamaster.b2c.core.model.vo, so a change to org.javamaster.b2c.core.model.vo can break org.javamaster.b2c.core.service.impl, while a change to org.javamaster.b2c.core.service.impl can't break org.javamaster.b2c.core.model.vo.
Position
Below the diagonal: org.javamaster.b2c.core.service.impl uses a module listed above it, which is the healthy direction.
org.javamaster.b2c.core.service.impl uses org.javamaster.b2c.core.service, so a change to org.javamaster.b2c.core.service can break org.javamaster.b2c.core.service.impl, while a change to org.javamaster.b2c.core.service.impl can't break org.javamaster.b2c.core.service.
Position
Below the diagonal: org.javamaster.b2c.core.service.impl uses a module listed above it, which is the healthy direction.
org.javamaster.invocationlab.admin.service.invocation uses org.javamaster.invocationlab.admin.model.dto, so a change to org.javamaster.invocationlab.admin.model.dto can break org.javamaster.invocationlab.admin.service.invocation, while a change to org.javamaster.invocationlab.admin.service.invocation can't break org.javamaster.invocationlab.admin.model.dto.
Position
Below the diagonal: org.javamaster.invocationlab.admin.service.invocation uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in org.javamaster.invocationlab.admin.service.invocation uses a type in org.javamaster.invocationlab.admin.service.creation.entity.
org.javamaster.invocationlab.admin.service.invocation uses org.javamaster.invocationlab.admin.service.creation.entity, so a change to org.javamaster.invocationlab.admin.service.creation.entity can break org.javamaster.invocationlab.admin.service.invocation, while a change to org.javamaster.invocationlab.admin.service.invocation can't break org.javamaster.invocationlab.admin.service.creation.entity.
Position
Below the diagonal: org.javamaster.invocationlab.admin.service.invocation uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in org.javamaster.invocationlab.admin.service.invocation uses a type in org.javamaster.invocationlab.admin.service.invocation.entity.
org.javamaster.invocationlab.admin.service.invocation uses org.javamaster.invocationlab.admin.service.invocation.entity, so a change to org.javamaster.invocationlab.admin.service.invocation.entity can break org.javamaster.invocationlab.admin.service.invocation, while a change to org.javamaster.invocationlab.admin.service.invocation can't break org.javamaster.invocationlab.admin.service.invocation.entity.
Position
Below the diagonal: org.javamaster.invocationlab.admin.service.invocation uses a module listed above it, which is the healthy direction.
27→28 org.javamaster.invocationlab.admin.service.invocation uses org.javamaster.invocationlab.admin.servicepart of a loop✕
Connections
1 pair of types, where a type in org.javamaster.invocationlab.admin.service.invocation uses a type in org.javamaster.invocationlab.admin.service.
org.javamaster.invocationlab.admin.service.invocation uses org.javamaster.invocationlab.admin.service, so a change to org.javamaster.invocationlab.admin.service can break org.javamaster.invocationlab.admin.service.invocation, while a change to org.javamaster.invocationlab.admin.service.invocation can't break org.javamaster.invocationlab.admin.service.
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.
org.javamaster.invocationlab.admin.service uses org.javamaster.invocationlab.admin.enums, so a change to org.javamaster.invocationlab.admin.enums can break org.javamaster.invocationlab.admin.service, while a change to org.javamaster.invocationlab.admin.service can't break org.javamaster.invocationlab.admin.enums.
Position
Below the diagonal: org.javamaster.invocationlab.admin.service uses a module listed above it, which is the healthy direction.
36 pairs of types, where a type in org.javamaster.invocationlab.admin.service uses a type in org.javamaster.invocationlab.admin.model.erd. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
org.javamaster.invocationlab.admin.service uses org.javamaster.invocationlab.admin.model.erd, so a change to org.javamaster.invocationlab.admin.model.erd can break org.javamaster.invocationlab.admin.service, while a change to org.javamaster.invocationlab.admin.service can't break org.javamaster.invocationlab.admin.model.erd.
Position
Below the diagonal: org.javamaster.invocationlab.admin.service uses a module listed above it, which is the healthy direction.
org.javamaster.invocationlab.admin.service uses org.javamaster.invocationlab.admin.model.redis, so a change to org.javamaster.invocationlab.admin.model.redis can break org.javamaster.invocationlab.admin.service, while a change to org.javamaster.invocationlab.admin.service can't break org.javamaster.invocationlab.admin.model.redis.
Position
Below the diagonal: org.javamaster.invocationlab.admin.service uses a module listed above it, which is the healthy direction.
org.javamaster.invocationlab.admin.service uses org.javamaster.invocationlab.admin.service.registry, so a change to org.javamaster.invocationlab.admin.service.registry can break org.javamaster.invocationlab.admin.service, while a change to org.javamaster.invocationlab.admin.service can't break org.javamaster.invocationlab.admin.service.registry.
Position
Below the diagonal: org.javamaster.invocationlab.admin.service uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in org.javamaster.invocationlab.admin.service uses a type in org.javamaster.invocationlab.admin.service.repository.redis.
org.javamaster.invocationlab.admin.service uses org.javamaster.invocationlab.admin.service.repository.redis, so a change to org.javamaster.invocationlab.admin.service.repository.redis can break org.javamaster.invocationlab.admin.service, while a change to org.javamaster.invocationlab.admin.service can't break org.javamaster.invocationlab.admin.service.repository.redis.
Position
Below the diagonal: org.javamaster.invocationlab.admin.service uses a module listed above it, which is the healthy direction.
org.javamaster.invocationlab.admin.service uses org.javamaster.invocationlab.admin.service.creation, so a change to org.javamaster.invocationlab.admin.service.creation can break org.javamaster.invocationlab.admin.service, while a change to org.javamaster.invocationlab.admin.service can't break org.javamaster.invocationlab.admin.service.creation.
Position
Below the diagonal: org.javamaster.invocationlab.admin.service uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in org.javamaster.invocationlab.admin.service uses a type in org.javamaster.invocationlab.admin.service.invocation.entity.
org.javamaster.invocationlab.admin.service uses org.javamaster.invocationlab.admin.service.invocation.entity, so a change to org.javamaster.invocationlab.admin.service.invocation.entity can break org.javamaster.invocationlab.admin.service, while a change to org.javamaster.invocationlab.admin.service can't break org.javamaster.invocationlab.admin.service.invocation.entity.
Position
Below the diagonal: org.javamaster.invocationlab.admin.service uses a module listed above it, which is the healthy direction.
org.javamaster.invocationlab.admin.service uses org.javamaster.invocationlab.admin.service.invocation, so a change to org.javamaster.invocationlab.admin.service.invocation can break org.javamaster.invocationlab.admin.service, while a change to org.javamaster.invocationlab.admin.service can't break org.javamaster.invocationlab.admin.service.invocation.
Position
Below the diagonal: org.javamaster.invocationlab.admin.service uses a module listed above it, which is the healthy direction.
org.javamaster.invocationlab.admin.redis uses org.javamaster.invocationlab.admin.model.redis, so a change to org.javamaster.invocationlab.admin.model.redis can break org.javamaster.invocationlab.admin.redis, while a change to org.javamaster.invocationlab.admin.redis can't break org.javamaster.invocationlab.admin.model.redis.
Position
Below the diagonal: org.javamaster.invocationlab.admin.redis uses a module listed above it, which is the healthy direction.
org.javamaster.invocationlab.admin.redis uses org.javamaster.invocationlab.admin.service, so a change to org.javamaster.invocationlab.admin.service can break org.javamaster.invocationlab.admin.redis, while a change to org.javamaster.invocationlab.admin.redis can't break org.javamaster.invocationlab.admin.service.
Position
Below the diagonal: org.javamaster.invocationlab.admin.redis uses a module listed above it, which is the healthy direction.
org.javamaster.invocationlab.admin.service.context uses org.javamaster.invocationlab.admin.enums, so a change to org.javamaster.invocationlab.admin.enums can break org.javamaster.invocationlab.admin.service.context, while a change to org.javamaster.invocationlab.admin.service.context can't break org.javamaster.invocationlab.admin.enums.
Position
Below the diagonal: org.javamaster.invocationlab.admin.service.context uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in org.javamaster.invocationlab.admin.service.context uses a type in org.javamaster.invocationlab.admin.service.creation.entity.
org.javamaster.invocationlab.admin.service.context uses org.javamaster.invocationlab.admin.service.creation.entity, so a change to org.javamaster.invocationlab.admin.service.creation.entity can break org.javamaster.invocationlab.admin.service.context, while a change to org.javamaster.invocationlab.admin.service.context can't break org.javamaster.invocationlab.admin.service.creation.entity.
Position
Below the diagonal: org.javamaster.invocationlab.admin.service.context uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in org.javamaster.invocationlab.admin.service.context uses a type in org.javamaster.invocationlab.admin.service.creation.
org.javamaster.invocationlab.admin.service.context uses org.javamaster.invocationlab.admin.service.creation, so a change to org.javamaster.invocationlab.admin.service.creation can break org.javamaster.invocationlab.admin.service.context, while a change to org.javamaster.invocationlab.admin.service.context can't break org.javamaster.invocationlab.admin.service.creation.
Position
Below the diagonal: org.javamaster.invocationlab.admin.service.context uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in org.javamaster.invocationlab.admin.service.context uses a type in org.javamaster.invocationlab.admin.service.invocation.entity.
org.javamaster.invocationlab.admin.service.context uses org.javamaster.invocationlab.admin.service.invocation.entity, so a change to org.javamaster.invocationlab.admin.service.invocation.entity can break org.javamaster.invocationlab.admin.service.context, while a change to org.javamaster.invocationlab.admin.service.context can't break org.javamaster.invocationlab.admin.service.invocation.entity.
Position
Below the diagonal: org.javamaster.invocationlab.admin.service.context uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in org.javamaster.invocationlab.admin.service.context uses a type in org.javamaster.invocationlab.admin.service.invocation.
org.javamaster.invocationlab.admin.service.context uses org.javamaster.invocationlab.admin.service.invocation, so a change to org.javamaster.invocationlab.admin.service.invocation can break org.javamaster.invocationlab.admin.service.context, while a change to org.javamaster.invocationlab.admin.service.context can't break org.javamaster.invocationlab.admin.service.invocation.
Position
Below the diagonal: org.javamaster.invocationlab.admin.service.context uses a module listed above it, which is the healthy direction.
org.javamaster.invocationlab.admin.service.context uses org.javamaster.invocationlab.admin.service, so a change to org.javamaster.invocationlab.admin.service can break org.javamaster.invocationlab.admin.service.context, while a change to org.javamaster.invocationlab.admin.service.context can't break org.javamaster.invocationlab.admin.service.
Position
Below the diagonal: org.javamaster.invocationlab.admin.service.context uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in org.javamaster.invocationlab.admin.service.creation.impl uses a type in org.javamaster.invocationlab.admin.service.load.classloader.
org.javamaster.invocationlab.admin.service.creation.impl uses org.javamaster.invocationlab.admin.service.load.classloader, so a change to org.javamaster.invocationlab.admin.service.load.classloader can break org.javamaster.invocationlab.admin.service.creation.impl, while a change to org.javamaster.invocationlab.admin.service.creation.impl can't break org.javamaster.invocationlab.admin.service.load.classloader.
Position
Below the diagonal: org.javamaster.invocationlab.admin.service.creation.impl uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in org.javamaster.invocationlab.admin.service.creation.impl uses a type in org.javamaster.invocationlab.admin.service.creation.entity.
org.javamaster.invocationlab.admin.service.creation.impl uses org.javamaster.invocationlab.admin.service.creation.entity, so a change to org.javamaster.invocationlab.admin.service.creation.entity can break org.javamaster.invocationlab.admin.service.creation.impl, while a change to org.javamaster.invocationlab.admin.service.creation.impl can't break org.javamaster.invocationlab.admin.service.creation.entity.
Position
Below the diagonal: org.javamaster.invocationlab.admin.service.creation.impl uses a module listed above it, which is the healthy direction.
6 pairs of types, where a type in org.javamaster.invocationlab.admin.service.creation.impl uses a type in org.javamaster.invocationlab.admin.service.creation.
org.javamaster.invocationlab.admin.service.creation.impl uses org.javamaster.invocationlab.admin.service.creation, so a change to org.javamaster.invocationlab.admin.service.creation can break org.javamaster.invocationlab.admin.service.creation.impl, while a change to org.javamaster.invocationlab.admin.service.creation.impl can't break org.javamaster.invocationlab.admin.service.creation.
Position
Below the diagonal: org.javamaster.invocationlab.admin.service.creation.impl uses a module listed above it, which is the healthy direction.
org.javamaster.invocationlab.admin.service.creation.impl uses org.javamaster.invocationlab.admin.service, so a change to org.javamaster.invocationlab.admin.service can break org.javamaster.invocationlab.admin.service.creation.impl, while a change to org.javamaster.invocationlab.admin.service.creation.impl can't break org.javamaster.invocationlab.admin.service.
Position
Below the diagonal: org.javamaster.invocationlab.admin.service.creation.impl uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in org.javamaster.invocationlab.admin.service.invocation.impl uses a type in org.javamaster.invocationlab.admin.model.dto.
org.javamaster.invocationlab.admin.service.invocation.impl uses org.javamaster.invocationlab.admin.model.dto, so a change to org.javamaster.invocationlab.admin.model.dto can break org.javamaster.invocationlab.admin.service.invocation.impl, while a change to org.javamaster.invocationlab.admin.service.invocation.impl can't break org.javamaster.invocationlab.admin.model.dto.
Position
Below the diagonal: org.javamaster.invocationlab.admin.service.invocation.impl uses a module listed above it, which is the healthy direction.
5 pairs of types, where a type in org.javamaster.invocationlab.admin.service.invocation.impl uses a type in org.javamaster.invocationlab.admin.service.invocation.entity.
org.javamaster.invocationlab.admin.service.invocation.impl uses org.javamaster.invocationlab.admin.service.invocation.entity, so a change to org.javamaster.invocationlab.admin.service.invocation.entity can break org.javamaster.invocationlab.admin.service.invocation.impl, while a change to org.javamaster.invocationlab.admin.service.invocation.impl can't break org.javamaster.invocationlab.admin.service.invocation.entity.
Position
Below the diagonal: org.javamaster.invocationlab.admin.service.invocation.impl uses a module listed above it, which is the healthy direction.
8 pairs of types, where a type in org.javamaster.invocationlab.admin.service.invocation.impl uses a type in org.javamaster.invocationlab.admin.service.invocation.
org.javamaster.invocationlab.admin.service.invocation.impl uses org.javamaster.invocationlab.admin.service.invocation, so a change to org.javamaster.invocationlab.admin.service.invocation can break org.javamaster.invocationlab.admin.service.invocation.impl, while a change to org.javamaster.invocationlab.admin.service.invocation.impl can't break org.javamaster.invocationlab.admin.service.invocation.
Position
Below the diagonal: org.javamaster.invocationlab.admin.service.invocation.impl uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in org.javamaster.invocationlab.admin.service.invocation.impl uses a type in org.javamaster.invocationlab.admin.service.
org.javamaster.invocationlab.admin.service.invocation.impl uses org.javamaster.invocationlab.admin.service, so a change to org.javamaster.invocationlab.admin.service can break org.javamaster.invocationlab.admin.service.invocation.impl, while a change to org.javamaster.invocationlab.admin.service.invocation.impl can't break org.javamaster.invocationlab.admin.service.
Position
Below the diagonal: org.javamaster.invocationlab.admin.service.invocation.impl uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in org.javamaster.invocationlab.admin.service.load.impl uses a type in org.javamaster.invocationlab.admin.service.load.classloader.
org.javamaster.invocationlab.admin.service.load.impl uses org.javamaster.invocationlab.admin.service.load.classloader, so a change to org.javamaster.invocationlab.admin.service.load.classloader can break org.javamaster.invocationlab.admin.service.load.impl, while a change to org.javamaster.invocationlab.admin.service.load.impl can't break org.javamaster.invocationlab.admin.service.load.classloader.
Position
Below the diagonal: org.javamaster.invocationlab.admin.service.load.impl uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in org.javamaster.invocationlab.admin.service.load.impl uses a type in org.javamaster.invocationlab.admin.service.creation.
org.javamaster.invocationlab.admin.service.load.impl uses org.javamaster.invocationlab.admin.service.creation, so a change to org.javamaster.invocationlab.admin.service.creation can break org.javamaster.invocationlab.admin.service.load.impl, while a change to org.javamaster.invocationlab.admin.service.load.impl can't break org.javamaster.invocationlab.admin.service.creation.
Position
Below the diagonal: org.javamaster.invocationlab.admin.service.load.impl uses a module listed above it, which is the healthy direction.
org.javamaster.invocationlab.admin.service.load.impl uses org.javamaster.invocationlab.admin.service, so a change to org.javamaster.invocationlab.admin.service can break org.javamaster.invocationlab.admin.service.load.impl, while a change to org.javamaster.invocationlab.admin.service.load.impl can't break org.javamaster.invocationlab.admin.service.
Position
Below the diagonal: org.javamaster.invocationlab.admin.service.load.impl uses a module listed above it, which is the healthy direction.
org.javamaster.invocationlab.admin.service.maven uses org.javamaster.invocationlab.admin.service, so a change to org.javamaster.invocationlab.admin.service can break org.javamaster.invocationlab.admin.service.maven, while a change to org.javamaster.invocationlab.admin.service.maven can't break org.javamaster.invocationlab.admin.service.
Position
Below the diagonal: org.javamaster.invocationlab.admin.service.maven uses a module listed above it, which is the healthy direction.
org.javamaster.invocationlab.admin.service.scenetest uses org.javamaster.invocationlab.admin.model.dto, so a change to org.javamaster.invocationlab.admin.model.dto can break org.javamaster.invocationlab.admin.service.scenetest, while a change to org.javamaster.invocationlab.admin.service.scenetest can't break org.javamaster.invocationlab.admin.model.dto.
Position
Below the diagonal: org.javamaster.invocationlab.admin.service.scenetest uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in org.javamaster.invocationlab.admin.service.scenetest uses a type in org.javamaster.invocationlab.admin.service.invocation.entity.
org.javamaster.invocationlab.admin.service.scenetest uses org.javamaster.invocationlab.admin.service.invocation.entity, so a change to org.javamaster.invocationlab.admin.service.invocation.entity can break org.javamaster.invocationlab.admin.service.scenetest, while a change to org.javamaster.invocationlab.admin.service.scenetest can't break org.javamaster.invocationlab.admin.service.invocation.entity.
Position
Below the diagonal: org.javamaster.invocationlab.admin.service.scenetest uses a module listed above it, which is the healthy direction.
4 pairs of types, where a type in org.javamaster.invocationlab.admin.service.scenetest uses a type in org.javamaster.invocationlab.admin.service.invocation.
org.javamaster.invocationlab.admin.service.scenetest uses org.javamaster.invocationlab.admin.service.invocation, so a change to org.javamaster.invocationlab.admin.service.invocation can break org.javamaster.invocationlab.admin.service.scenetest, while a change to org.javamaster.invocationlab.admin.service.scenetest can't break org.javamaster.invocationlab.admin.service.invocation.
Position
Below the diagonal: org.javamaster.invocationlab.admin.service.scenetest uses a module listed above it, which is the healthy direction.
org.javamaster.invocationlab.admin.service.scenetest uses org.javamaster.invocationlab.admin.service, so a change to org.javamaster.invocationlab.admin.service can break org.javamaster.invocationlab.admin.service.scenetest, while a change to org.javamaster.invocationlab.admin.service.scenetest can't break org.javamaster.invocationlab.admin.service.
Position
Below the diagonal: org.javamaster.invocationlab.admin.service.scenetest uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in org.javamaster.invocationlab.admin.config uses a type in org.javamaster.invocationlab.admin.service.repository.redis.
org.javamaster.invocationlab.admin.config uses org.javamaster.invocationlab.admin.service.repository.redis, so a change to org.javamaster.invocationlab.admin.service.repository.redis can break org.javamaster.invocationlab.admin.config, while a change to org.javamaster.invocationlab.admin.config can't break org.javamaster.invocationlab.admin.service.repository.redis.
Position
Below the diagonal: org.javamaster.invocationlab.admin.config uses a module listed above it, which is the healthy direction.
org.javamaster.invocationlab.admin.config uses org.javamaster.invocationlab.admin.service.maven, so a change to org.javamaster.invocationlab.admin.service.maven can break org.javamaster.invocationlab.admin.config, while a change to org.javamaster.invocationlab.admin.config can't break org.javamaster.invocationlab.admin.service.maven.
Position
Below the diagonal: org.javamaster.invocationlab.admin.config uses a module listed above it, which is the healthy direction.
org.javamaster.invocationlab.admin.controller uses org.javamaster.invocationlab.admin.model, so a change to org.javamaster.invocationlab.admin.model can break org.javamaster.invocationlab.admin.controller, while a change to org.javamaster.invocationlab.admin.controller can't break org.javamaster.invocationlab.admin.model.
Position
Below the diagonal: org.javamaster.invocationlab.admin.controller uses a module listed above it, which is the healthy direction.
org.javamaster.invocationlab.admin.controller uses org.javamaster.invocationlab.admin.model.dto, so a change to org.javamaster.invocationlab.admin.model.dto can break org.javamaster.invocationlab.admin.controller, while a change to org.javamaster.invocationlab.admin.controller can't break org.javamaster.invocationlab.admin.model.dto.
Position
Below the diagonal: org.javamaster.invocationlab.admin.controller uses a module listed above it, which is the healthy direction.
26 pairs of types, where a type in org.javamaster.invocationlab.admin.controller uses a type in org.javamaster.invocationlab.admin.model.erd. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
org.javamaster.invocationlab.admin.controller uses org.javamaster.invocationlab.admin.model.erd, so a change to org.javamaster.invocationlab.admin.model.erd can break org.javamaster.invocationlab.admin.controller, while a change to org.javamaster.invocationlab.admin.controller can't break org.javamaster.invocationlab.admin.model.erd.
Position
Below the diagonal: org.javamaster.invocationlab.admin.controller uses a module listed above it, which is the healthy direction.
org.javamaster.invocationlab.admin.controller uses org.javamaster.invocationlab.admin.model.redis, so a change to org.javamaster.invocationlab.admin.model.redis can break org.javamaster.invocationlab.admin.controller, while a change to org.javamaster.invocationlab.admin.controller can't break org.javamaster.invocationlab.admin.model.redis.
Position
Below the diagonal: org.javamaster.invocationlab.admin.controller uses a module listed above it, which is the healthy direction.
6 pairs of types, where a type in org.javamaster.invocationlab.admin.controller uses a type in org.javamaster.invocationlab.admin.service.repository.redis.
org.javamaster.invocationlab.admin.controller uses org.javamaster.invocationlab.admin.service.repository.redis, so a change to org.javamaster.invocationlab.admin.service.repository.redis can break org.javamaster.invocationlab.admin.controller, while a change to org.javamaster.invocationlab.admin.controller can't break org.javamaster.invocationlab.admin.service.repository.redis.
Position
Below the diagonal: org.javamaster.invocationlab.admin.controller uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in org.javamaster.invocationlab.admin.controller uses a type in org.javamaster.invocationlab.admin.service.creation.entity.
org.javamaster.invocationlab.admin.controller uses org.javamaster.invocationlab.admin.service.creation.entity, so a change to org.javamaster.invocationlab.admin.service.creation.entity can break org.javamaster.invocationlab.admin.controller, while a change to org.javamaster.invocationlab.admin.controller can't break org.javamaster.invocationlab.admin.service.creation.entity.
Position
Below the diagonal: org.javamaster.invocationlab.admin.controller uses a module listed above it, which is the healthy direction.
org.javamaster.invocationlab.admin.controller uses org.javamaster.invocationlab.admin.service, so a change to org.javamaster.invocationlab.admin.service can break org.javamaster.invocationlab.admin.controller, while a change to org.javamaster.invocationlab.admin.controller can't break org.javamaster.invocationlab.admin.service.
Position
Below the diagonal: org.javamaster.invocationlab.admin.controller uses a module listed above it, which is the healthy direction.
org.javamaster.invocationlab.admin.controller uses org.javamaster.invocationlab.admin.service.scenetest, so a change to org.javamaster.invocationlab.admin.service.scenetest can break org.javamaster.invocationlab.admin.controller, while a change to org.javamaster.invocationlab.admin.controller can't break org.javamaster.invocationlab.admin.service.scenetest.
Position
Below the diagonal: org.javamaster.invocationlab.admin.controller uses a module listed above it, which is the healthy direction.
org.javamaster.invocationlab.admin.service.impl uses org.javamaster.invocationlab.admin.enums, so a change to org.javamaster.invocationlab.admin.enums can break org.javamaster.invocationlab.admin.service.impl, while a change to org.javamaster.invocationlab.admin.service.impl can't break org.javamaster.invocationlab.admin.enums.
Position
Below the diagonal: org.javamaster.invocationlab.admin.service.impl uses a module listed above it, which is the healthy direction.
53 pairs of types, where a type in org.javamaster.invocationlab.admin.service.impl uses a type in org.javamaster.invocationlab.admin.model.erd. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
org.javamaster.invocationlab.admin.service.impl uses org.javamaster.invocationlab.admin.model.erd, so a change to org.javamaster.invocationlab.admin.model.erd can break org.javamaster.invocationlab.admin.service.impl, while a change to org.javamaster.invocationlab.admin.service.impl can't break org.javamaster.invocationlab.admin.model.erd.
Position
Below the diagonal: org.javamaster.invocationlab.admin.service.impl uses a module listed above it, which is the healthy direction.
org.javamaster.invocationlab.admin.service.impl uses org.javamaster.invocationlab.admin.model.redis, so a change to org.javamaster.invocationlab.admin.model.redis can break org.javamaster.invocationlab.admin.service.impl, while a change to org.javamaster.invocationlab.admin.service.impl can't break org.javamaster.invocationlab.admin.model.redis.
Position
Below the diagonal: org.javamaster.invocationlab.admin.service.impl uses a module listed above it, which is the healthy direction.
org.javamaster.invocationlab.admin.service.impl uses org.javamaster.invocationlab.admin.service, so a change to org.javamaster.invocationlab.admin.service can break org.javamaster.invocationlab.admin.service.impl, while a change to org.javamaster.invocationlab.admin.service.impl can't break org.javamaster.invocationlab.admin.service.
Position
Below the diagonal: org.javamaster.invocationlab.admin.service.impl uses a module listed above it, which is the healthy direction.
org.javamaster.invocationlab.admin.service.impl uses org.javamaster.invocationlab.admin.redis, so a change to org.javamaster.invocationlab.admin.redis can break org.javamaster.invocationlab.admin.service.impl, while a change to org.javamaster.invocationlab.admin.service.impl can't break org.javamaster.invocationlab.admin.redis.
Position
Below the diagonal: org.javamaster.invocationlab.admin.service.impl uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in org.javamaster.invocationlab.admin.service.impl.RedisServiceImpl uses a type in org.javamaster.invocationlab.admin.model.erd.
org.javamaster.invocationlab.admin.service.impl.RedisServiceImpl uses org.javamaster.invocationlab.admin.model.erd, so a change to org.javamaster.invocationlab.admin.model.erd can break org.javamaster.invocationlab.admin.service.impl.RedisServiceImpl, while a change to org.javamaster.invocationlab.admin.service.impl.RedisServiceImpl can't break org.javamaster.invocationlab.admin.model.erd.
Position
Below the diagonal: org.javamaster.invocationlab.admin.service.impl.RedisServiceImpl uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in org.javamaster.invocationlab.admin.service.impl.RedisServiceImpl uses a type in org.javamaster.invocationlab.admin.model.redis.
org.javamaster.invocationlab.admin.service.impl.RedisServiceImpl uses org.javamaster.invocationlab.admin.model.redis, so a change to org.javamaster.invocationlab.admin.model.redis can break org.javamaster.invocationlab.admin.service.impl.RedisServiceImpl, while a change to org.javamaster.invocationlab.admin.service.impl.RedisServiceImpl can't break org.javamaster.invocationlab.admin.model.redis.
Position
Below the diagonal: org.javamaster.invocationlab.admin.service.impl.RedisServiceImpl uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in org.javamaster.invocationlab.admin.service.impl.RedisServiceImpl uses a type in org.javamaster.invocationlab.admin.service.
org.javamaster.invocationlab.admin.service.impl.RedisServiceImpl uses org.javamaster.invocationlab.admin.service, so a change to org.javamaster.invocationlab.admin.service can break org.javamaster.invocationlab.admin.service.impl.RedisServiceImpl, while a change to org.javamaster.invocationlab.admin.service.impl.RedisServiceImpl can't break org.javamaster.invocationlab.admin.service.
Position
Below the diagonal: org.javamaster.invocationlab.admin.service.impl.RedisServiceImpl uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in org.javamaster.invocationlab.admin.service.impl.RedisServiceImpl uses a type in org.javamaster.invocationlab.admin.redis.
org.javamaster.invocationlab.admin.service.impl.RedisServiceImpl uses org.javamaster.invocationlab.admin.redis, so a change to org.javamaster.invocationlab.admin.redis can break org.javamaster.invocationlab.admin.service.impl.RedisServiceImpl, while a change to org.javamaster.invocationlab.admin.service.impl.RedisServiceImpl can't break org.javamaster.invocationlab.admin.redis.
Position
Below the diagonal: org.javamaster.invocationlab.admin.service.impl.RedisServiceImpl uses a module listed above it, which is the healthy direction.
org.javamaster.invocationlab.admin.util uses org.javamaster.invocationlab.admin.enums, so a change to org.javamaster.invocationlab.admin.enums can break org.javamaster.invocationlab.admin.util, while a change to org.javamaster.invocationlab.admin.util can't break org.javamaster.invocationlab.admin.enums.
Position
Below the diagonal: org.javamaster.invocationlab.admin.util uses a module listed above it, which is the healthy direction.
org.javamaster.invocationlab.admin.util uses org.javamaster.invocationlab.admin.model.erd, so a change to org.javamaster.invocationlab.admin.model.erd can break org.javamaster.invocationlab.admin.util, while a change to org.javamaster.invocationlab.admin.util can't break org.javamaster.invocationlab.admin.model.erd.
Position
Below the diagonal: org.javamaster.invocationlab.admin.util uses a module listed above it, which is the healthy direction.
org.javamaster.invocationlab.admin.util uses org.javamaster.invocationlab.admin.model.redis, so a change to org.javamaster.invocationlab.admin.model.redis can break org.javamaster.invocationlab.admin.util, while a change to org.javamaster.invocationlab.admin.util can't break org.javamaster.invocationlab.admin.model.redis.
Position
Below the diagonal: org.javamaster.invocationlab.admin.util uses a module listed above it, which is the healthy direction.
org.javamaster.invocationlab.admin.util uses org.javamaster.invocationlab.admin.service, so a change to org.javamaster.invocationlab.admin.service can break org.javamaster.invocationlab.admin.util, while a change to org.javamaster.invocationlab.admin.util can't break org.javamaster.invocationlab.admin.service.
Position
Below the diagonal: org.javamaster.invocationlab.admin.util uses a module listed above it, which is the healthy direction.
org.javamaster.invocationlab.admin.util uses org.javamaster.invocationlab.admin.redis, so a change to org.javamaster.invocationlab.admin.redis can break org.javamaster.invocationlab.admin.util, while a change to org.javamaster.invocationlab.admin.util can't break org.javamaster.invocationlab.admin.redis.
Position
Below the diagonal: org.javamaster.invocationlab.admin.util uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 31.3 · Weak · gated by D2, R10, R7 ·
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A03:2025 — Software Supply Chain Failures
640
High / Critical
A05:2025 — Injection
28
High / Critical
A07:2025 — Authentication Failures
9
High / Critical
A02:2025 — Security Misconfiguration
9
High / Critical
A08:2025 — Software or Data Integrity Failures
1
Medium
Roadmap
Top priorities: Resolve the 6 Banned license finding(s) in License Compliance; Resolve the 2 REDACTED finding(s) in REDACTED Scanning — start with REDACTED (2); Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 6 Banned license finding(s) in License Compliance.
Run what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.
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 — 524
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 — 1045
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 — 656
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 15
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 75 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 — 75 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, 1984 of 2225 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: the Java/Kotlin half could not be measured — the JUnit suite ran, but the analyzer could not read its coverage for 5 of its 7 build(s), so a figure over the rest would be a part of the suite. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo.
D12 Dependency Hygiene — 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. Currency was graded against Maven Central, but whether an artifact is DEPRECATED is not: Maven Central publishes no deprecation marker, exactly as rubygems.org does not. Whether one is UNMAINTAINED is not graded either — no registry publishes a maintenance status, and release age does not stand in for one. Two of this dimension's four signals are therefore unread on a Gradle tree, and its score reflects currency alone.
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 286 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 236 of the 1001 production source files in this repository: 715 are under the ~2,400-byte size floor this dimension measures over, and the remaining 50 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. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 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 — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is a COLLECTOR gap, not an environment fault: no published-package marker D22 reads admitted any project here, so this ecosystem's public API has no collector, and the remedy is to write one — no change to the scan image can close it.
D24 Comment Value — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. D24 compares a comment's words with the identifiers, literals and constructs of the code it annotates, using English function-word and rationale lexicons. Comments in another script or language were left unread rather than counted as clean.
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.
D27 Navigability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `spring-embed-arthas/src/main/webapp/index.js`, `spring-embed-arthas/src/main/webapp/vue.js`, `tools-manage/invocationlab-admin-21/build.gradle.kts`, `tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/redis/TripleFunction.kt`, `tools-manage/invocationlab-admin/src/main/resources/public/invocationlab-erd-online-view/1177.23fe5a99.async.js`, … (+12 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
AC6 Visual & motion safety — 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. Visual & motion safety could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository. Engine failure: ArgumentOutOfRangeException: startIndex cannot be larger than length of string. (Parameter 'startIndex').
AX1 Captive dependencies — 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.
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.
ED5 Idempotency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check decides whether a handler's mutation is safe to re-run by recognising its persistence writes (a database save, a repository write, an event publish) and its guards. Those markers are .NET member names, so in this repository's language a write such as `repository.save(order)` is not recognised and a same-named call on an unrelated library type could be. The handlers were found; their idempotency was neither confirmed nor ruled out.
P8 Schema migrations — 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. The schema may be created by a runner, a deploy script or a config file outside what this check reads, so an absence here is our blind spot rather than a missing migration strategy. The card abstains instead of scoring. You can widen what we reach: if the schema is created and evolved by a tool this check does not name, naming it lets us teach the detector to read it.
R10 Code Duplication — 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. 219 further occurrence(s) are not listed individually; the score already reflects all 259.
R2 Cyclomatic Complexity — 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. 45 further occurrence(s) are not listed individually; the score already reflects all 85.
R7 Dead Code — 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. 250 further occurrence(s) are not listed individually; the score already reflects all 290.
R8 Dependency Hygiene — 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. 3 further occurrence(s) are not listed individually; the score already reflects all 43.
X1 Async correctness — 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.
X27 Collection changed while being enumerated — 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.
Repo exclusion declarations: 55 pattern(s) declared (.gitattributes linguist-generated/vendored, .editorconfig generated_code) excluded 0 source file(s) from code-quality scoring. Declarations are the repo's own visible statement that a tree is machine-written or vendored — auditable in any diff, honored by GitHub the same way.
Limitations & what we did not check
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.
D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
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.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
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.
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".
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.
169 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was (anonymous) at 188. A further 4 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 vue.eventsMixin at 18 — they are counted neither in the figure above nor in this dimension's score. 2 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/util/ClassUtils.kt (ClassUtils.isPrimitive at 16), tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/util/ClassUtils.java (ClassUtils.isPrimitive at 16). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
+ 102 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 4 bodies over 120 down to 120 or less in Cyclomatic Complexity — start with (anonymous) (cyclomatic 188), (anonymous) (cyclomatic 145), useVersionStore.useVersionStore (cyclomatic 144). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 4 together lifts Cyclomatic Complexity from 4.6 to about 5.2/10, projected with the scoring formula itself and assuming each lands exactly at 120; 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.
+ 137 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 4 bodies over 120 down to 120 or less in Cognitive Complexity — start with useVersionStore.useVersionStore (cognitive 216), (anonymous) (cognitive 183), G6Relation._renderRelation (cognitive 173). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 4 together lifts Cognitive Complexity from 3.0 to about 4.1/10, projected with the scoring formula itself and assuming each lands exactly at 120; a cleaner split scores higher.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes7.7 / 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 35 FunctionTooLong finding(s) in God Classes — start with REDACTED (9), json2code.ts (3), REDACTED (2). — One of this dimension's main actionable groups (35 warning-level).
Resolve the 15 TooManyMethods finding(s) in God Classes — start with MenusExample.java, ExamsExample.java, MicrowebsiteExamExample.java. — One of this dimension's main actionable groups (15 warning-level).
Resolve the 9 FileTooLong finding(s) in God Classes — start with index.js, vue.js, g6.js. — One of this dimension's main actionable groups (9 warning-level).
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How much of the production code is copy-pasted: the share of production lines inside a reported copy (every copy of a duplicated block or of an edited member, each line once), 10 at none and 0 at a quarter of the lines.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), scored on the share of production lines inside a reported copy (each line once; 10 at none, 0 at a quarter). Deterministic.
56 duplicated block group(s) detected. 4.7 % of the production lines (5,228 of 110,202) are in a reported copy. A further 64 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. Measured on part of this repository only: .tsx (29% of production source) was not exposed to THIS dimension's token comparison and is not in this count; duplication there is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream.
Edited copy of a member (11 corresponding lines) · ×6tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/controller/RpcPostmanServiceCreationController.java:96
Edited copy of a member (10 corresponding lines) · ×6REDACTED:66
+ 52 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 10 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with RedisUtils.java (2), SetRedisStrategy.kt, MySqlDbServiceImpl.kt. — One of this dimension's main actionable groups (10 warning-level).
Resolve the 6 Edited copy of a member (11 corresponding lines) finding(s) in Code Duplication — start with RpcPostmanServiceCreationController.java, FieldInfo.java, RedisUtils.java. — One of this dimension's main actionable groups (6 warning-level).
Resolve the 6 Edited copy of a member (10 corresponding lines) finding(s) in Code Duplication — start with RedisServiceImpl.java (3), REDACTED, MySqlDbServiceImpl.java. — One of this dimension's main actionable groups (6 warning-level).
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling9.5 / 10Stronggated by 2 serious findings✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
30 production modules (Gradle+Maven+npm), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; edges a convention plugin adds from buildSrc or build-logic are not visible there; 2 module(s) off the main sequence, with abstractness counted on 27 of the 30 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
Off the main sequence: redis-spring-boot-starter · ×2
What to do
Resolve the 2 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
D11 · Test Reliability10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the tests pass reliably, with no flakiness.
Method: Suite re-run N times within tiered wall-clock budgets (unit to e2e); tests failing non-deterministically across runs flagged; guarded tests retried when #if guards detected.
What it measures: Whether dependencies are current, not deprecated, and not bloated. Known vulnerabilities are D30's.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (capped-linear for deprecation, prerelease and outdated) per KLoC. Known-vulnerable packages are D30's and are not charged here (rubric-2026.11.2). Exhaustive.
This repository's Gradle dependency graph was RESOLVED BY A BUILD, across every subproject rather than the root alone: 226 artifact(s) resolved, 226 of them gradable against Maven Central, and 207 behind a shipped release. Where a version was requested and a different one won conflict resolution, the RESOLVED version is what is graded — grading the request would recommend an upgrade already applied. Known CVEs in the same graph are a separate question again, reported under D30.
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.
1 secret(s) detected. 2 password hash(es) are listed to check and are not counted as leaked credentials.
REDACTED
REDACTED
What to do
Resolve the 2 REDACTED finding(s) in REDACTED Scanning — start with REDACTED (2). — One of this dimension's main actionable groups (2 recommendation-level).
Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Detailed fixes: d13_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
6 of 108 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 28 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. 81 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. 3 of them resolve to no licence at all on Central, even through their parent POMs; that is missing data, not a violation, and none of them is charged. A further 4 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.
Banned license: mysql:mysql-connector-java · ×6
What to do
Resolve the 6 Banned license finding(s) in License Compliance. — One of this dimension's main actionable groups (6 issue-level).
Detailed fixes: d14_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
5 deducted task-comment markers across 65040 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 5 TodoComment finding(s) in Explicit Debt — start with useVersionStore.tsx (2), MongoDbServiceImpl.java, ConstantInvokeDynamicInfo.java. — One of this dimension's main actionable groups (5 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.
0 of 1 documentation facets pass in full; short on: F2 example. 6 document(s) read across 32 unit(s).
Documentation: no build, run or usage exampletools-manage/invocationlab-erd-online-view/README.md:1
What to do
Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d19_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D20 · ADR Quality0.0 / 10Critical✓ Tool-verified
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: 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 REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d20_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether names — types, methods, variables — are clear and consistent.
Method: Seven vocabulary-free rules (N1-N7) mine each naming convention from the repository and flag a name that breaks a convention its structural peers in the same unit follow; production C# and TypeScript, each its own population. Deterministic, no model, no sample. Advisory.
5 naming inconsistencies among 159 declarations measured against a convention their peers follow.
`postgreSQL` spells `SQL` where 36 names in the project spell it `Sql`tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/model/erd/ApplyBean.kt:28
`PostgreSQLBean` spells `SQL` where 36 names in the project spell it `Sql`tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/model/erd/ApplyBean.kt:56
`groupID` spells `ID` where 126 names in the project spell it `Id`tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/service/GAV.kt:8
`artifactID` spells `ID` where 126 names in the project spell it `Id`tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/service/GAV.kt:9
`PostgreSQLBean` spells `SQL` where 45 names in the project spell it `Sql`tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/model/erd/ApplyBean.java:53
What to do
Resolve the 1 `postgreSQL` spells `SQL` where 36 names in the project spell it `Sql` finding(s) in Naming Consistency — start with ApplyBean.kt. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 `PostgreSQLBean` spells `SQL` where 36 names in the project spell it… finding(s) in Naming Consistency — start with ApplyBean.kt. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 `groupID` spells `ID` where 126 names in the project spell it `Id` finding(s) in Naming Consistency — start with GAV.kt. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d21_recommendation.md · top locations in Appendix A, every location in findings.md.
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 95 judged comments only repeat the code they sit on (3.2 %). 456 comment(s) in another language or script were not judged.
redundant comment · ×3REDACTED:138
doc comments repeat the names · ×2tools-manage/invocationlab-erd-online-view/src/global.tsx:87
What to do
Resolve the 3 redundant comment finding(s) in Comment Value — start with REDACTED (2), FieldMultiSelect.tsx. — One of this dimension's main actionable groups (3 recommendation-level).
Detailed fixes: d24_recommendation.md · top locations in Appendix A, every location in findings.md.
3 of 28 build units (Gradle, Maven, npm) 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, REDACTED, build.gradle.kts. — 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: 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.
5 finding(s): 0 critical, 3 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
REDACTED
REDACTED
REDACTED
What to do
Resolve the 3 REDACTED finding(s) in Secrets (history) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 issue-level).
Resolve the 2 REDACTED finding(s) in Secrets (history) — start with REDACTED (2). — One of this dimension's main actionable groups (2 recommendation-level).
Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
28 finding(s): 0 critical, 8 high, 17 medium, 3 low. semgrep hit a parse error in 30 file(s) — `b2c-parent/b2c-core/src/main/resources/application.yml`, `b2c-parent/b2c-core/src/script/start.sh` (line 25), `b2c-parent/b2c-core/src/script/start1.sh` (line 29), `b2c-parent/b2c-core/src/script/stop.sh` (line 22), `spring-embed-arthas/src/main/webapp/index.js`, … (+25 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.
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 13 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 issue-level).
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
+ 2 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 341 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (98), REDACTED (81), REDACTED (80). — One of this dimension's main actionable groups (341 issue-level).
Resolve the 96 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (45), REDACTED (26), REDACTED (12). — One of this dimension's main actionable groups (96 issue-level).
Resolve the 8 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (5), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (8 issue-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
Resolve the 4 High IaC finding(s) in IaC & Container Security — start with REDACTED (4). — One of this dimension's main actionable groups (4 issue-level).
Resolve the 3 Low IaC finding(s) in IaC & Container Security — start with REDACTED (3). — One of this dimension's main actionable groups (3 recommendation-level).
Resolve the 2 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-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.
286 of 286 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/AbstractDbService.java. Counted over 286 of the 1001 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Most significant orphaned file · ×3tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/AbstractDbService.java:1
Dormant codebase
What to do
Resolve the 283 Orphaned file finding(s) in Knowledge Freshness — start with REDACTED (21), RedisServiceImpl.java (2), REDACTED (2). — One of this dimension's main actionable groups (283 recommendation-level).
Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with AbstractDbService.java, AbstractDbService.kt, useVersionStore.tsx. — 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.
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.
Resolve the 1 Malicious package finding(s) in Malicious Dependencies — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d43_recommendation.md · top locations in Appendix A, every location in findings.md.
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 21 platform declaration(s) and 180 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 2b2c-parent/pom.xml: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 alternatives3.7 / 10Weak✓ 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. (×7) — tools-manage/invocationlab-admin-21/src/main/resources/erd.vm:120, tools-manage/invocationlab-admin/src/main/resources/erd.vm:119, tools-manage/invocationlab-erd-online-view/src/components/Header/ProjectHeader/index.tsx:14, …
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 & labels4.4 / 10Weak✓ 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. — spring-embed-arthas/src/main/webapp/vue.js:8535
A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label. — spring-embed-arthas/src/main/webapp/vue.js:11861
This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed. (×14) — tools-manage/invocationlab-erd-online-view/src/components/LeftContent/DesignLeftContent/component/MetaDataSearch.tsx:256, tools-manage/invocationlab-erd-online-view/src/components/LeftContent/DesignLeftContent/component/MetaDataSearch.tsx:258, tools-manage/invocationlab-erd-online-view/src/components/LeftContent/DesignLeftContent/component/MetaDataSearch.tsx:260, …
This UI-library field component has no label / aria-label / aria-labelledby / id, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id alone, wherever it is set, names nothing until a label points at it). The text inside it does not stand in for one: these compound APIs render a trigger with role="combobox" (or role="button"), and those roles take their name from the AUTHOR, not from their content — so the words on screen never reach the accessibility tree as a name. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed. (×4) — tools-manage/invocationlab-erd-online-view/src/components/LeftContent/DesignLeftContent/component/MetaDataSearch.tsx:265, tools-manage/invocationlab-erd-online-view/src/pages/design/query/index.tsx:327, tools-manage/invocationlab-erd-online-view/src/pages/design/query/index.tsx:351, …
This UI-library field component has no label / aria-label / aria-labelledby / id at this call site, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id, even one the component sets on what it renders, names nothing until a label points at it) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed. (×10) — tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/AesContextMenu.tsx:107, tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/AesContextMenu.tsx:113, tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/ConstructSqlForm.tsx:356, …
This <svg> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label. — tools-manage/invocationlab-rpcpostman-view/src/components/Hamburger/index.vue:0
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. (×2) — tools-manage/invocationlab-rpcpostman-view/src/views/pages/CreateService.vue:43, tools-manage/invocationlab-rpcpostman-view/src/views/pages/CreateServiceJdk.vue:30
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 structure4.3 / 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.
The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). (×6) — b2c-parent/b2c-scheduled/src/main/resources/templates/task-list.html:2, spring-embed-arthas/src/main/webapp/vue.js:11887, spring-lifecycle/src/main/webapp/WEB-INF/views/welcome.jsp:3, …
No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. (×8) — b2c-parent/b2c-scheduled/src/main/resources/templates/task-list.html:2, spring-embed-arthas/src/main/webapp/arthas-test.html:2, spring-embed-arthas/src/main/webapp/table-column-drag.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). (×5) — b2c-parent/b2c-scheduled/src/main/resources/templates/task-list.html:28, tools-manage/invocationlab-admin-21/src/main/resources/erd.vm:130, tools-manage/invocationlab-admin-21/src/main/resources/erd.vm:161, …
user-scalable=no/0 or a maximum-scale below 2 stops low-vision users zooming to 200%. Remove the zoom restriction from the viewport meta. — tools-manage/invocationlab-admin/src/main/resources/public/invocationlab-erd-online-view/index.html:3
Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one. (×2) — tools-manage/invocationlab-rpcpostman-view/src/views/error-page/401.vue:12, tools-manage/tools-manage-view/src/components/HelloWorld.vue:10
An empty heading appears in the document outline announced with no text. Give the heading text, or remove it if it's decorative. — tools-manage/tools-manage-view/src/components/WelcomeItem.vue:7
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".
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. (×10) — b2c-parent/b2c-scheduled/src/main/resources/templates/task-list.html:47, b2c-parent/b2c-scheduled/src/main/resources/templates/task-list.html:50, b2c-parent/b2c-scheduled/src/main/resources/templates/task-list.html:53, …
A click handler on a plain element with no role and no tabindex: even where another element's key handler can reach it, assistive tech can neither focus it nor announce what it is. Use a <button>, or add role + tabIndex={0}. — tools-manage/invocationlab-erd-online-view/src/components/HeaderSearch/index.tsx:51
A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler. (×2) — tools-manage/invocationlab-erd-online-view/src/components/NoticeIcon/NoticeList.tsx:93, tools-manage/invocationlab-erd-online-view/src/components/NoticeIcon/NoticeList.tsx:98
This <span> binds double-click and nothing else. No click, no key handler, and no tabIndex={0}, so it cannot even take focus. Nothing synthesises a double-click from the keyboard: Enter and Space fire a single click, and only on a native <button> or <a href>. So this behaviour has no keyboard path at all. Expose the same action on a real control, or add role + tabIndex={0} + a key handler alongside the double-click. (×6) — tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/ExplainResult.tsx:27, tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/QueryHistory.tsx:33, tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/QueryHistory.tsx:43, …
A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler. (×9) — tools-manage/invocationlab-rpcpostman-view/src/components/BackToTop/index.vue:3, tools-manage/invocationlab-rpcpostman-view/src/components/Hamburger/index.vue:0, tools-manage/invocationlab-rpcpostman-view/src/views/layout/Layout.vue:3, …
The repo's own CSS styles .el-icon-caret-bottom with `cursor: pointer`, so this <i> 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. (×3) — tools-manage/invocationlab-rpcpostman-view/src/views/layout/components/Navbar.vue:17, tools-manage/invocationlab-rpcpostman-view/src/views/layout/components/Navbar.vue:0, tools-manage/invocationlab-rpcpostman-view/src/views/layout/components/Navbar.vue:29
The repo's own CSS styles .user-avatar 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. — tools-manage/invocationlab-rpcpostman-view/src/views/layout/components/Navbar.vue:28
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 · 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.
`DubboInvoker` is a singleton (@Service: the container shares one instance across every request thread) but mutates instance state outside any lock (cachedReference; e.g. `cachedReference` in `getOrCreateService` at line 51). — tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/service/invocation/impl/DubboInvoker.kt:28
`DynamicPrintTask` is a singleton (@Component: the container shares one instance across every request thread) but mutates instance state outside any lock (i; e.g. `i` in `execute` at line 19). — b2c-parent/b2c-scheduled/src/main/java/org/javamaster/b2c/scheduled/task/DynamicPrintTask.java:12
`DynamicPrintTask1` is a singleton (@Component: the container shares one instance across every request thread) but mutates instance state outside any lock (i; e.g. `i` in `execute` at line 19). — b2c-parent/b2c-scheduled/src/main/java/org/javamaster/b2c/scheduled/task/DynamicPrintTask1.java:12
`DynamicPrintTask2` is a singleton (@Component: the container shares one instance across every request thread) but mutates instance state outside any lock (i; e.g. `i` in `execute` at line 19). — b2c-parent/b2c-scheduled/src/main/java/org/javamaster/b2c/scheduled/task/DynamicPrintTask2.java:12
`DubboInvoker` is a singleton (@Service: the container shares one instance across every request thread) but mutates instance state outside any lock (cachedReference; e.g. `cachedReference` in `getOrCreateService` at line 53). — tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/invocation/impl/DubboInvoker.java:30
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.
`IModulesDispatchSlice` declares 17 required operations: `addModule`, `renameModule`, `removeModule`, `updateModule`, `copyModule`, `cutModule`, `pastModule`, `refreshModule`, `updateRelation`, `setCurrentModule`, `updateAllModules`, `getOriginalModules`, `getModuleEntityTree`, `getModuleEntityFieldTree`, `setExpandedKey`, `setExpandedKeys`, `getExpandedKeys`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — tools-manage/invocationlab-erd-online-view/src/store/project/modulesSlice.tsx:35
`IProfileDispatchSlice` declares 24 required operations: `addDefaultFields`, `removeDefaultFields`, `updateDefaultFields`, `updateDefaultFieldsType`, `updateSqlConfig`, `addDbs`, `removeDbs`, `updateDbs`, `updateAllDbs`, `setCurrentDbKey`, `setDefaultDb`, `updateWordTemplateConfig`, `updateProfile`, `getCurrentDBName`, `getCurrentDBData`, `setProfileSliceState`, `dbReverseParse`, `checkField`, `getAllTable`, `saveSelectedRowKeys`, `getSelectedEntity`, `importReverseTable`, `getDefaultFields`, `downloadWordTemplate`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — tools-manage/invocationlab-erd-online-view/src/store/project/profileSlice.tsx:15
`ErdOnlineProjectService` declares 17 abstract methods: `createProject`, `delRecordsVoFromGroupUsers`, `deleteProject`, `eraseSensitiveInfo`, `exportErd`, `findRecordsVoByProjectId`, `getDefaultDb`, `getProjectBasicInfo`, `getProjectDetail`, `getProjectList`, `refreshProjectModule`, `resumeSensitiveInfo`, `saveProject`, `saveRecordsVoToGroupUsers`, `sortModule`, `statistic`, `updateProjectBasicInfo`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/ErdOnlineProjectService.java:24
`ErdOnlineProjectService` declares 17 abstract methods: `statistic`, `getProjectList`, `saveRecordsVoToGroupUsers`, `delRecordsVoFromGroupUsers`, `findRecordsVoByProjectId`, `getProjectDetail`, `eraseSensitiveInfo`, `resumeSensitiveInfo`, `getDefaultDb`, `createProject`, `deleteProject`, `updateProjectBasicInfo`, `saveProject`, `refreshProjectModule`, `getProjectBasicInfo`, `exportErd`, `sortModule`. Counted over its public functions with no body, once per name; default-bodied functions and properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/service/ErdOnlineProjectService.kt:12
What to do
Split fat interfaces into focused role-interfaces so clients depend only on what they use.
Other · Code Health — Unreviewed-generation residue in this repository's JavaScript/TypeScript: functions whose whole body still throws a "not implemented" error, and placeholder text (lorem ipsum, changeme/replace_me…) left in strings and JSX 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 JavaScript/TypeScript: functions that only throw a "not implemented" error, functions that take inputs and return a constant or do nothing, async functions that never await, 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.
`getInitialState` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — tools-manage/invocationlab-erd-online-view/src/app.tsx:8
A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead. (×23) — tools-manage/invocationlab-erd-online-view/src/access.ts:1, tools-manage/invocationlab-erd-online-view/src/components/JExcel/index.tsx:1, tools-manage/invocationlab-erd-online-view/src/pages/JExcel/index.tsx:1, …
What to do
Finish or delete the unfinished stubs (functions that throw "not implemented", or whose body is empty or a bare constant) — they are dead surface that looks live.
Clear the softer debt: re-enable or delete skipped tests, decide whether each empty function is a deliberate no-op (and say so in a comment), and replace blanket `eslint-disable` / `@ts-nocheck` with targeted, justified suppressions.
Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
The root README is 102 words, against a bar of 120. Of the three newcomer-critical sections this check looks for by heading, in the README and in the repository documents it links, it found no a build/run or getting-started section, no an architecture or project-map section. Sections are matched on HEADING text only, so material written under a heading this check does not recognise — or with no heading at all — is not seen and this row may understate what the document covers. — README.md:1
What to do
Expand the README with getting-started, architecture overview and a project map.
Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.
Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.
tools-manage/tools-manage-view/README.md names Vue 3, but the manifest declares `vue` 2.5.17. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — tools-manage/tools-manage-view/README.md:4
What to do
Reconcile the README with reality: tools-manage/tools-manage-view/README.md names Vue 3, but the manifest declares `vue` 2.5.17.
Do you agree with this assessment?
P1 · CI/CD gates0.0 / 10Critical✓ Tool-verified
Readiness · Readiness — Whether an automated pipeline builds and tests every change.
Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.
No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.
What to do
Add a CI workflow that builds and runs the test suite on every push/PR.
Only 16/22 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `b2c-parent/b2c-classloader`, `b2c-parent/b2c-mybatis`, `spring-transactional`, `springboot-autoconfiguration`, `tools-manage/invocationlab-erd-online-view` and 1 more.
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) — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 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:52
What to do
Run what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add 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.
What to do
Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
Readiness · Readiness — Whether 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.
`urlopen(` 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:57
`@FeignClient` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. (×3) — spring-swagger/src/main/java/org/javamaster/spring/swagger/feign/UserFeignService.java:16, tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/feign/SsoFeignService.kt:9, tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/feign/SsoFeignService.java:13
`.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. (×4) — tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/service/maven/Maven.kt:100, tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/util/FileUtils.kt:17, tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/maven/Maven.java:117, …
What to do
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.
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).
Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.
Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from each language's code model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
Do you agree with this assessment?
R1 · Type Safety6.9 / 10Adequate✓ 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.
252 typed · 112 plain JS — the untyped files are spring-embed-arthas/src/main/webapp/index.js, spring-embed-arthas/src/main/webapp/table-column-drag.js, tools-manage/invocationlab-admin-21/src/main/resources/script/propertyOperation.js, tools-manage/invocationlab-admin-21/src/main/resources/script/sendWrapper.js, REDACTED, tools-manage/invocationlab-admin/src/main/resources/script/propertyOperation.js (+106 more). 4 production file(s) opt out entirely with @ts-nocheck · 77 @ts-ignore suppression(s); the opted-out files are tools-manage/invocationlab-erd-online-view/src/access.ts, tools-manage/invocationlab-erd-online-view/src/components/JExcel/index.tsx, tools-manage/invocationlab-erd-online-view/src/pages/JExcel/index.tsx, tools-manage/invocationlab-erd-online-view/src/utils/json2code.ts.
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.
tools-manage/invocationlab-admin/src/main/resources/public/invocationlab-erd-online-view/ and tools-manage/invocationlab-erd-online-view/public/ are near-verbatim copies of each other: 50 files are byte-identical under the same relative paths (~1.2 MB; the trees hold 127 and 50 files). That is one structural fact, not 50 local ones: every edit made to one tree and not the other drifts silently, which is the failure whole-tree forks guarantee. Pick one tree as the single source and produce the other from it (generated, copied at build or release time, or re-exported) — or, if the copy is a stale snapshot nothing produces any more, delete it. Check first whether the copy is a deliberately published deliverable (a template consumers copy verbatim, a released sample frozen at a version); where it is, keep it produced from the source tree rather than edited in place. — tools-manage/invocationlab-admin/src/main/resources/public/invocationlab-erd-online-view/project.json:1
27 duplicated blocks under tools-manage/invocationlab-erd-online-view/src/ have copies in at least two of the sibling directories components, pages, services, store, utils — 24 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 27 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 27 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 27 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — tools-manage/invocationlab-erd-online-view/src/components/dialog/export/ExportDDL.tsx:1
10 duplicated blocks under tools-manage/invocationlab-erd-online-view/src/components/dialog/ have copies in at least two of the sibling directories dataType, database, entity, module, query, version — 9 of them are reported below, and 1 is counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 10 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 10 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 10 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — tools-manage/invocationlab-erd-online-view/src/components/dialog/entity/AddEntity.tsx:12
6 duplicated blocks under tools-manage/invocationlab-erd-online-view/src/layouts/ have copies in at least two of the sibling directories DesignLayout, GroupLayout, HomeLayout — 5 of them are reported below, and 1 is counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 6 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 6 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 6 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — tools-manage/invocationlab-erd-online-view/src/layouts/DesignLayout/index.tsx:85
5 duplicated blocks under tools-manage/ have copies in at least two of the sibling directories invocationlab-admin, invocationlab-admin-21, invocationlab-erd-online-view, invocationlab-rpcpostman-view, tools-manage-view — 4 of them are reported below, and 1 is counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 5 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 5 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 5 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — REDACTED:320
REDACTED:320 · tools-manage/tools-manage-view/src/views/RedisManageView.vue:243 — the two spans are one implementation copied and then locally edited — 1491 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — REDACTED:320
tools-manage/invocationlab-erd-online-view/src/components/dialog/export/ExportDDL.tsx:1 · tools-manage/invocationlab-erd-online-view/src/pages/design/export/component/ExportDDL.tsx:1 — these 2 files are line-for-line copies of one another — 155 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — tools-manage/invocationlab-erd-online-view/src/components/dialog/export/ExportDDL.tsx:1
REDACTED:22 · tools-manage/invocationlab-erd-online-view/src/pages/design/setting/component/DatabaseSetUp.tsx:20 — the two spans are one implementation copied and then locally edited — 894 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — REDACTED:22
tools-manage/invocationlab-admin-21/src/main/resources/script/propertyOperation.js:1 · tools-manage/invocationlab-admin/src/main/resources/script/propertyOperation.js:1 — these 2 files are line-for-line copies of one another — 112 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — tools-manage/invocationlab-admin-21/src/main/resources/script/propertyOperation.js:1
tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/ConstructSqlForm.tsx:199 · tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/ConstructSqlFormMongoDB.tsx:185 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/ConstructSqlForm.tsx:199
tools-manage/invocationlab-erd-online-view/src/pages/project/group/index.tsx:1 · tools-manage/invocationlab-erd-online-view/src/pages/project/person/index.tsx:1 — these 2 files are line-for-line copies of one another — 94 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — tools-manage/invocationlab-erd-online-view/src/pages/project/group/index.tsx:1
tools-manage/invocationlab-erd-online-view/src/components/dialog/import/ReverseDatabase.tsx:12 · tools-manage/invocationlab-erd-online-view/src/pages/design/import/component/ReverseDatabase.tsx:9 — the two spans are one implementation copied and then locally edited — 573 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — tools-manage/invocationlab-erd-online-view/src/components/dialog/import/ReverseDatabase.tsx:12
tools-manage/invocationlab-erd-online-view/src/pages/project/group/index.tsx:1 · tools-manage/invocationlab-erd-online-view/src/pages/project/recent/index.tsx:1 — these 2 files are line-for-line copies of one another — 85 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — tools-manage/invocationlab-erd-online-view/src/pages/project/group/index.tsx:1
tools-manage/invocationlab-erd-online-view/src/layouts/DesignLayout/index.tsx:85 · tools-manage/invocationlab-erd-online-view/src/layouts/GroupLayout/index.tsx:20 — the two spans are one implementation copied and then locally edited — 461 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — tools-manage/invocationlab-erd-online-view/src/layouts/DesignLayout/index.tsx:85
tools-manage/invocationlab-erd-online-view/src/pages/design/relation/g6.js:489 · tools-manage/invocationlab-erd-online-view/src/utils/relation2file.js:161 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — tools-manage/invocationlab-erd-online-view/src/pages/design/relation/g6.js:489
tools-manage/invocationlab-erd-online-view/src/components/dialog/database/AddDatabase.tsx:13 · tools-manage/invocationlab-erd-online-view/src/components/dialog/database/RenameDatabase.tsx:12 — the two spans are one implementation copied and then locally edited — 415 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — tools-manage/invocationlab-erd-online-view/src/components/dialog/database/AddDatabase.tsx:13
REDACTED:234 · tools-manage/invocationlab-erd-online-view/src/pages/design/setting/component/DatabaseSetUp.tsx:147 — the two spans are one implementation copied and then locally edited — 334 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — REDACTED:234
tools-manage/invocationlab-erd-online-view/src/components/dialog/entity/AddEntity.tsx:12 · tools-manage/invocationlab-erd-online-view/src/components/dialog/module/AddModule.tsx:13 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — tools-manage/invocationlab-erd-online-view/src/components/dialog/entity/AddEntity.tsx:12
tools-manage/invocationlab-erd-online-view/src/pages/design/relation/g6.js:110 · tools-manage/invocationlab-erd-online-view/src/utils/relation2file.js:6 — the two spans are one implementation copied and then locally edited — 563 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — tools-manage/invocationlab-erd-online-view/src/pages/design/relation/g6.js:110
tools-manage/invocationlab-erd-online-view/src/components/dialog/import/ReverseERD.tsx:43 · tools-manage/invocationlab-erd-online-view/src/components/dialog/import/ReversePdMan.tsx:35 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — tools-manage/invocationlab-erd-online-view/src/components/dialog/import/ReverseERD.tsx:43
tools-manage/invocationlab-erd-online-view/src/components/dialog/dataType/AddDataType.tsx:66 · tools-manage/invocationlab-erd-online-view/src/components/dialog/dataType/RenameDataType.tsx:92 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — tools-manage/invocationlab-erd-online-view/src/components/dialog/dataType/AddDataType.tsx:66
tools-manage/invocationlab-erd-online-view/src/pages/design/relation/g6.js:651 · tools-manage/invocationlab-erd-online-view/src/utils/relation2file.js:323 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — tools-manage/invocationlab-erd-online-view/src/pages/design/relation/g6.js:651
tools-manage/invocationlab-erd-online-view/src/components/JExcel/index.tsx:62 · tools-manage/invocationlab-erd-online-view/src/pages/JExcel/index.tsx:87 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — tools-manage/invocationlab-erd-online-view/src/components/JExcel/index.tsx:62
tools-manage/invocationlab-erd-online-view/src/store/version/useVersionStore.tsx:149 · tools-manage/invocationlab-erd-online-view/src/utils/dbversionutils.js:42 — the two spans are one implementation copied and then locally edited — 454 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — tools-manage/invocationlab-erd-online-view/src/store/version/useVersionStore.tsx:149
spring-embed-arthas/src/main/webapp/index.js:17126 · spring-embed-arthas/src/main/webapp/index.js:17206 — the two spans are one implementation copied and then locally edited — 663 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — spring-embed-arthas/src/main/webapp/index.js:17126
tools-manage/invocationlab-erd-online-view/src/utils/generatehtml.js:4 · tools-manage/invocationlab-erd-online-view/src/utils/markdown.js:4 — the two spans are one implementation copied and then locally edited — 595 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — tools-manage/invocationlab-erd-online-view/src/utils/generatehtml.js:4
tools-manage/invocationlab-erd-online-view/src/pages/design/import/component/ReverseERD.tsx:79 · tools-manage/invocationlab-erd-online-view/src/pages/design/import/component/ReversePdMan.tsx:33 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — tools-manage/invocationlab-erd-online-view/src/pages/design/import/component/ReverseERD.tsx:79
tools-manage/invocationlab-erd-online-view/src/components/dialog/project/AddProject.tsx:61 · tools-manage/invocationlab-erd-online-view/src/components/dialog/project/RenameProject.tsx:37 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — tools-manage/invocationlab-erd-online-view/src/components/dialog/project/AddProject.tsx:61
tools-manage/invocationlab-erd-online-view/src/pages/design/relation/g6.js:800 · tools-manage/invocationlab-erd-online-view/src/utils/relation2file.js:461 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — tools-manage/invocationlab-erd-online-view/src/pages/design/relation/g6.js:800
tools-manage/invocationlab-erd-online-view/copyDistToPublic.js:4 · tools-manage/invocationlab-rpcpostman-view/copyDistToPublic.js:4 · tools-manage/tools-manage-view/copyDistToPublic.js:4 — 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. — tools-manage/invocationlab-erd-online-view/copyDistToPublic.js:4
tools-manage/invocationlab-erd-online-view/src/components/dialog/version/InitVersion.tsx:72 · tools-manage/invocationlab-erd-online-view/src/components/dialog/version/RebuildVersion.tsx:33 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — tools-manage/invocationlab-erd-online-view/src/components/dialog/version/InitVersion.tsx:72
tools-manage/invocationlab-rpcpostman-view/src/views/pages/CreateService.vue:88 · tools-manage/invocationlab-rpcpostman-view/src/views/pages/CreateServiceJdk.vue:76 — the two spans are one implementation copied and then locally edited — 233 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — tools-manage/invocationlab-rpcpostman-view/src/views/pages/CreateService.vue:88
tools-manage/invocationlab-erd-online-view/src/components/dialog/import/ReversePdMan.tsx:13 · tools-manage/invocationlab-erd-online-view/src/pages/design/import/component/ReversePdMan.tsx:9 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — tools-manage/invocationlab-erd-online-view/src/components/dialog/import/ReversePdMan.tsx:13
tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/ConstructSqlForm.tsx:409 · tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/ConstructSqlFormMongoDB.tsx:396 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/ConstructSqlForm.tsx:409
tools-manage/invocationlab-erd-online-view/src/store/version/useVersionStore.tsx:289 · tools-manage/invocationlab-erd-online-view/src/store/version/useVersionStore.tsx:995 — 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. — tools-manage/invocationlab-erd-online-view/src/store/version/useVersionStore.tsx:289
tools-manage/invocationlab-erd-online-view/src/components/dialog/version/AddVersion.tsx:61 · tools-manage/invocationlab-erd-online-view/src/components/dialog/version/RenameVersion.tsx:62 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — tools-manage/invocationlab-erd-online-view/src/components/dialog/version/AddVersion.tsx:61
tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/ConstructSqlForm.tsx:58 · tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/ConstructSqlFormMongoDB.tsx:56 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/ConstructSqlForm.tsx:58
spring-embed-arthas/src/main/webapp/index.js:5993 · spring-embed-arthas/src/main/webapp/index.js:6271 — the two spans are one implementation copied and then locally edited — 275 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — spring-embed-arthas/src/main/webapp/index.js:5993
tools-manage/invocationlab-erd-online-view/src/layouts/GroupLayout/index.tsx:76 · tools-manage/invocationlab-erd-online-view/src/layouts/HomeLayout/index.tsx:70 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — tools-manage/invocationlab-erd-online-view/src/layouts/GroupLayout/index.tsx:76
tools-manage/invocationlab-erd-online-view/src/pages/design/relation/g6.js:615 · tools-manage/invocationlab-erd-online-view/src/utils/relation2file.js:287 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — tools-manage/invocationlab-erd-online-view/src/pages/design/relation/g6.js:615
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 · Architecture — Conformance to the detected frontend architecture layout (feature-sliced / layered src) plus cross-package deep-import rules (D-386).
Method: Conformance to the detected frontend layout (feature-sliced / layered src) plus cross-package deep-import rules, over the module graph. Deterministic.
tools-manage/invocationlab-erd-online-view/src/components/CodeEditor/index.tsx:18 imports react-ace/src/types, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — tools-manage/invocationlab-erd-online-view/src/components/CodeEditor/index.tsx:18
tools-manage/invocationlab-erd-online-view/src/components/Menu/index.tsx:17 imports @blueprintjs/core/src/common/props, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — tools-manage/invocationlab-erd-online-view/src/components/Menu/index.tsx:17
tools-manage/invocationlab-erd-online-view/src/components/TableTransfer/index.tsx:4 imports antd/lib/transfer, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — tools-manage/invocationlab-erd-online-view/src/components/TableTransfer/index.tsx:4
tools-manage/invocationlab-erd-online-view/src/components/dialog/database/AddDatabase.tsx:8 imports antd/lib/radio/interface, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — tools-manage/invocationlab-erd-online-view/src/components/dialog/database/AddDatabase.tsx:8
tools-manage/invocationlab-erd-online-view/src/components/dialog/database/PreviewDatabase.tsx:6 imports antd/lib/radio/interface, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — tools-manage/invocationlab-erd-online-view/src/components/dialog/database/PreviewDatabase.tsx:6
tools-manage/invocationlab-erd-online-view/src/components/dialog/database/RenameDatabase.tsx:7 imports antd/lib/radio/interface, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — tools-manage/invocationlab-erd-online-view/src/components/dialog/database/RenameDatabase.tsx:7
tools-manage/invocationlab-erd-online-view/src/components/dialog/export/ExportDDL.tsx:20 imports antd/lib/radio/interface, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — tools-manage/invocationlab-erd-online-view/src/components/dialog/export/ExportDDL.tsx:20
tools-manage/invocationlab-erd-online-view/src/pages/design/export/component/ExportDDL.tsx:16 imports antd/lib/radio/interface, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — tools-manage/invocationlab-erd-online-view/src/pages/design/export/component/ExportDDL.tsx:16
tools-manage/invocationlab-erd-online-view/src/pages/design/table/component/table/TableObjectList.tsx:3 imports @blueprintjs/core/src/common/index, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — tools-manage/invocationlab-erd-online-view/src/pages/design/table/component/table/TableObjectList.tsx:3
tools-manage/invocationlab-erd-online-view/src/pages/project/group/component/GroupPermission.tsx:3 imports antd/lib/checkbox/Group, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — tools-manage/invocationlab-erd-online-view/src/pages/project/group/component/GroupPermission.tsx:3
tools-manage/invocationlab-erd-online-view/src/services/crud.ts:1 imports antd/lib/table/interface, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — tools-manage/invocationlab-erd-online-view/src/services/crud.ts:1
tools-manage/invocationlab-erd-online-view/src/store/query/useQueryStore.tsx:2 imports antd/lib/tree, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — tools-manage/invocationlab-erd-online-view/src/store/query/useQueryStore.tsx:2
tools-manage/invocationlab-rpcpostman-view/src/main.js:42 imports element-ui/lib/locale/lang/zh-CN, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — tools-manage/invocationlab-rpcpostman-view/src/main.js:42
tools-manage/invocationlab-rpcpostman-view/src/main.js:51 imports element-ui/lib/transitions/collapse-transition, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — tools-manage/invocationlab-rpcpostman-view/src/main.js:51
What to do
Fix the listed violations: import through public entries (package exports / slice index), never reach into another layer or package's internals.
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.
access has cyclomatic complexity 71 and cognitive complexity 70; 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 sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. 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. — tools-manage/invocationlab-erd-online-view/src/access.ts:11
n has cyclomatic complexity 36 and cognitive complexity 35; 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 sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. 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. — spring-embed-arthas/src/main/webapp/index.js:8078
getColumnValueOfType has cyclomatic complexity 35 and cognitive complexity 54; 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. — tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/ConstructSqlForm.tsx:151
(anonymous) has cyclomatic complexity 34 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. — spring-embed-arthas/src/main/webapp/index.js:13219
Parser has cyclomatic complexity 33 and cognitive complexity 74; 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. — tools-manage/invocationlab-erd-online-view/src/components/CodeEditor/parser/lexter.js:27
exports has cyclomatic complexity 28 and cognitive complexity 31; 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. — spring-embed-arthas/src/main/webapp/index.js:1480
parse has cyclomatic complexity 27 and cognitive complexity 25; 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 sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. 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. — spring-embed-arthas/src/main/webapp/index.js:9035
a has cyclomatic complexity 26 and cognitive complexity 27; 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. — spring-embed-arthas/src/main/webapp/index.js:1153
n has cyclomatic complexity 25 and cognitive complexity 21; 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 sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. 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. — spring-embed-arthas/src/main/webapp/index.js:2818
draw has cyclomatic complexity 24 and cognitive complexity 22; 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 sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. 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. (×2) — tools-manage/invocationlab-erd-online-view/src/pages/design/relation/g6.js:692, tools-manage/invocationlab-erd-online-view/src/utils/relation2file.js:362
n has cyclomatic complexity 24 and cognitive complexity 21; 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 sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. 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. — spring-embed-arthas/src/main/webapp/index.js:3955
e has cyclomatic complexity 23 and cognitive complexity 20; 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 sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. 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. — spring-embed-arthas/src/main/webapp/index.js:13471
s has cyclomatic complexity 22 and cognitive complexity 35; 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. — spring-embed-arthas/src/main/webapp/index.js:11903
showChanges has cyclomatic complexity 22 and cognitive complexity 30; 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. — tools-manage/invocationlab-erd-online-view/src/store/version/useVersionStore.tsx:499
divideTokens has cyclomatic complexity 21 and cognitive complexity 38; 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. — tools-manage/invocationlab-erd-online-view/src/components/CodeEditor/parser/select.js:45
fromString has cyclomatic complexity 21 and cognitive complexity 29; 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. — spring-embed-arthas/src/main/webapp/index.js:1640
getCellClasses has cyclomatic complexity 21 and cognitive complexity 19; 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 sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. 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. — spring-embed-arthas/src/main/webapp/index.js:10009
parseOneSource has cyclomatic complexity 20 and cognitive complexity 44; 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. — REDACTED:144
updateElsHeight has cyclomatic complexity 20 and cognitive complexity 29; 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. — spring-embed-arthas/src/main/webapp/index.js:7280
(anonymous) has cyclomatic complexity 20 and cognitive complexity 25; 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. — tools-manage/invocationlab-erd-online-view/src/pages/design/relation/g6.js:1007
(anonymous) has cyclomatic complexity 20 and cognitive complexity 21; 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. — tools-manage/invocationlab-erd-online-view/src/utils/json2code.ts:255
n has cyclomatic complexity 19 and cognitive complexity 17; 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 sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. 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. — spring-embed-arthas/src/main/webapp/index.js:12335
n has cyclomatic complexity 19 and cognitive complexity 14; 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 sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. 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. (×2) — spring-embed-arthas/src/main/webapp/index.js:6836, spring-embed-arthas/src/main/webapp/index.js:15911
(anonymous) has cyclomatic complexity 19 and cognitive complexity 11; 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 sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. 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. — spring-embed-arthas/src/main/webapp/index.js:470
(anonymous) has cyclomatic complexity 19 and cognitive complexity 9; 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 sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. 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. — tools-manage/invocationlab-erd-online-view/src/pages/design/table/component/table/TableCodeShow.tsx:59
i has cyclomatic complexity 18 and cognitive complexity 38; 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. — spring-embed-arthas/src/main/webapp/index.js:6851
createPopper has cyclomatic complexity 18 and cognitive complexity 16; 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 sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. 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. — spring-embed-arthas/src/main/webapp/index.js:425
n has cyclomatic complexity 18 and cognitive complexity 16; 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 sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. 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. — spring-embed-arthas/src/main/webapp/index.js:9059
doOpen has cyclomatic complexity 17 and cognitive complexity 19; 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. — spring-embed-arthas/src/main/webapp/index.js:686
n has cyclomatic complexity 17 and cognitive complexity 15; 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 sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. 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. — spring-embed-arthas/src/main/webapp/index.js:11417
(anonymous) has cyclomatic complexity 17 and cognitive complexity 14; 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 sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. 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. — spring-embed-arthas/src/main/webapp/index.js:12082
handleQueryChange has cyclomatic complexity 16 and cognitive complexity 21; 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. — spring-embed-arthas/src/main/webapp/index.js:2311
handleClick has cyclomatic complexity 15 and cognitive complexity 27; 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. — spring-embed-arthas/src/main/webapp/index.js:10044
keydown has cyclomatic complexity 15 and cognitive complexity 26; 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. — spring-embed-arthas/src/main/webapp/index.js:16734
b has cyclomatic complexity 15 and cognitive complexity 16; 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. — spring-embed-arthas/src/main/webapp/index.js:14605
created has cyclomatic complexity 15 and cognitive complexity 14; 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 sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. 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. — spring-embed-arthas/src/main/webapp/index.js:8418
(anonymous) has cyclomatic complexity 15 and cognitive complexity 14; 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 sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. 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. — spring-embed-arthas/src/main/webapp/index.js:9970
s has cyclomatic complexity 15 and cognitive complexity 13; 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 sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. 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. — spring-embed-arthas/src/main/webapp/index.js:2792
Do you agree with this assessment?
R3 · Large Files8.4 / 10Strong✓ 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.
spring-embed-arthas/src/main/webapp/index.js has 17677 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — spring-embed-arthas/src/main/webapp/index.js:1
tools-manage/invocationlab-erd-online-view/src/pages/design/relation/g6.js has 1546 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — tools-manage/invocationlab-erd-online-view/src/pages/design/relation/g6.js:1
tools-manage/invocationlab-erd-online-view/src/store/version/useVersionStore.tsx has 1041 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — tools-manage/invocationlab-erd-online-view/src/store/version/useVersionStore.tsx:1
tools-manage/invocationlab-rpcpostman-view/src/views/pages/AccessService.vue has 907 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — tools-manage/invocationlab-rpcpostman-view/src/views/pages/AccessService.vue:1
tools-manage/invocationlab-erd-online-view/src/utils/json2code.ts has 841 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — tools-manage/invocationlab-erd-online-view/src/utils/json2code.ts:1
tools-manage/invocationlab-rpcpostman-view/src/views/pages/CaseManage.vue has 804 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — tools-manage/invocationlab-rpcpostman-view/src/views/pages/CaseManage.vue:1
REDACTED has 735 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
tools-manage/invocationlab-rpcpostman-view/src/views/pages/KafkaManage.vue has 640 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — tools-manage/invocationlab-rpcpostman-view/src/views/pages/KafkaManage.vue:1
tools-manage/tools-manage-view/src/views/RedisManageView.vue has 589 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — tools-manage/tools-manage-view/src/views/RedisManageView.vue:1
tools-manage/invocationlab-erd-online-view/src/utils/relation2file.js has 567 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — tools-manage/invocationlab-erd-online-view/src/utils/relation2file.js:1
tools-manage/invocationlab-erd-online-view/src/pages/design/query/index.tsx has 459 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — tools-manage/invocationlab-erd-online-view/src/pages/design/query/index.tsx:1
tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/ConstructSqlForm.tsx has 445 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/ConstructSqlForm.tsx:1
tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/ConstructSqlFormMongoDB.tsx has 435 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/ConstructSqlFormMongoDB.tsx:1
What to do
Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
React / JS · Readiness — How outdated the npm dependencies are (a maturity signal). JS/npm CVEs are scored separately in D30 (JS/npm Dependency Vulnerabilities).
Method: npm dependency staleness from manifest/registry metadata (a maturity signal; JS/npm CVEs are scored separately in D30, which answers dependency vulnerabilities for every ecosystem). Deterministic.
Do you agree with this assessment?
R6 · Tooling10.0 / 10Exemplary✓ Tool-verified
React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each REDACTED script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.
Method: REDACTED scanned for test/lint/typecheck script wiring. Deterministic presence check.
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 31 application, 13 tooling and 11 test entry point(s) detected in this repo. Gate removals on `npm run build` — an undetected custom entry would make these reachable.
no import path from any entry point (31 application, 13 tooling, 11 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (tools-manage/invocationlab-erd-online-view/src/pages/design/relation/index.tsx) — 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 — tools-manage/invocationlab-erd-online-view/src/pages/design/relation/g6.js
no import path from any entry point (31 application, 13 tooling, 11 test roots considered), but 8 in-repo import(s) from 8 other file(s) do name it (tools-manage/invocationlab-erd-online-view/src/components/dialog/version/AddVersion.tsx, tools-manage/invocationlab-erd-online-view/src/components/dialog/version/CompareVersion.tsx, tools-manage/invocationlab-erd-online-view/src/components/dialog/version/InitVersion.tsx and 5 more) — 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 — tools-manage/invocationlab-erd-online-view/src/store/version/useVersionStore.tsx
no import path from any entry point (31 application, 13 tooling, 11 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 (×14) — tools-manage/invocationlab-rpcpostman-view/src/views/pages/AccessService.vue, tools-manage/invocationlab-rpcpostman-view/src/views/pages/CaseManage.vue, tools-manage/invocationlab-erd-online-view/src/pages/design/relation/erd.ts, …
no import path from any entry point (31 application, 13 tooling, 11 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (tools-manage/invocationlab-erd-online-view/src/pages/design/table/index.tsx) — 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 — tools-manage/invocationlab-erd-online-view/src/pages/design/query/index.tsx
no import path from any entry point (31 application, 13 tooling, 11 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (tools-manage/invocationlab-erd-online-view/src/pages/design/query/index.tsx) — 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 (×3) — tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/ConstructSqlForm.tsx, tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/ConstructSqlFormMongoDB.tsx, tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/QueryResult.tsx
no import path from any entry point (31 application, 13 tooling, 11 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (tools-manage/invocationlab-erd-online-view/src/components/CodeEditor/parser/sqlParser.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 — tools-manage/invocationlab-erd-online-view/src/components/CodeEditor/parser/select.js
no import path from any entry point (31 application, 13 tooling, 11 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (tools-manage/invocationlab-erd-online-view/src/components/Menu/index.tsx) — 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 (×2) — REDACTED, tools-manage/invocationlab-erd-online-view/src/components/dialog/export/ExportDDL.tsx
no import path from any entry point (31 application, 13 tooling, 11 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (tools-manage/invocationlab-erd-online-view/src/pages/project/group/component/GroupSetting.tsx) — 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 — tools-manage/invocationlab-erd-online-view/src/pages/project/group/component/GroupPermission.tsx
no import path from any entry point (31 application, 13 tooling, 11 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (tools-manage/invocationlab-erd-online-view/src/components/CodeEditor/parser/select.js, REDACTED, tools-manage/invocationlab-erd-online-view/src/components/CodeEditor/parser/sqlParser.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 — tools-manage/invocationlab-erd-online-view/src/components/CodeEditor/parser/lexter.js
no import path from any entry point (31 application, 13 tooling, 11 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (tools-manage/invocationlab-erd-online-view/src/components/CodeEditor/parser/select.js, tools-manage/invocationlab-erd-online-view/src/components/CodeEditor/parser/sqlParser.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 — REDACTED
no import path from any entry point (31 application, 13 tooling, 11 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (tools-manage/invocationlab-erd-online-view/src/components/LeftContent/DesignLeftContent/index.tsx) — 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 — tools-manage/invocationlab-erd-online-view/src/components/LeftContent/DesignLeftContent/component/MetaDataSearch.tsx
no import path from any entry point (31 application, 13 tooling, 11 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (tools-manage/invocationlab-erd-online-view/src/components/LeftContent/DesignLeftContent/index.tsx, tools-manage/invocationlab-erd-online-view/src/pages/design/table/component/table/TableObjectList.tsx) — 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 — tools-manage/invocationlab-erd-online-view/src/components/LeftContent/DesignLeftContent/component/DataTable.tsx
no import path from any entry point (31 application, 13 tooling, 11 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (tools-manage/invocationlab-erd-online-view/src/pages/design/setting/component/DefaultField.tsx, tools-manage/invocationlab-erd-online-view/src/pages/design/table/component/table/TableIndexEdit.tsx, tools-manage/invocationlab-erd-online-view/src/pages/design/table/component/table/TableInfoEdit.tsx) — 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 — tools-manage/invocationlab-erd-online-view/src/pages/JExcel/index.tsx
no import path from any entry point (31 application, 13 tooling, 11 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (tools-manage/invocationlab-erd-online-view/src/components/LeftContent/QueryLeftContent/component/QueryTree.tsx, tools-manage/invocationlab-erd-online-view/src/layouts/GroupLayout/index.tsx, tools-manage/invocationlab-erd-online-view/src/layouts/HomeLayout/index.tsx) — 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 — tools-manage/invocationlab-erd-online-view/src/layouts/DesignLayout/index.tsx
no import path from any entry point (31 application, 13 tooling, 11 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (tools-manage/invocationlab-erd-online-view/src/pages/design/index.tsx) — 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 — tools-manage/invocationlab-erd-online-view/src/pages/design/version/index.tsx
no import path from any entry point (31 application, 13 tooling, 11 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (tools-manage/invocationlab-erd-online-view/src/components/dialog/setup/DefaultSetUp.tsx) — 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 — tools-manage/invocationlab-erd-online-view/src/components/dialog/setup/DefaultField.tsx
no import path from any entry point (31 application, 13 tooling, 11 test roots considered), but 8 in-repo import(s) from 8 other file(s) do name it (tools-manage/invocationlab-erd-online-view/src/components/dialog/database/AddDatabase.tsx, tools-manage/invocationlab-erd-online-view/src/components/dialog/database/PreviewDatabase.tsx, tools-manage/invocationlab-erd-online-view/src/components/dialog/database/RenameDatabase.tsx and 5 more) — 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 — tools-manage/invocationlab-erd-online-view/src/components/CodeEditor/index.tsx
no import path from any entry point (31 application, 13 tooling, 11 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (tools-manage/invocationlab-erd-online-view/src/components/Menu/index.tsx, tools-manage/invocationlab-erd-online-view/src/pages/design/version/index.tsx) — 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 — tools-manage/invocationlab-erd-online-view/src/components/dialog/version/CompareVersion.tsx
no import path from any entry point (31 application, 13 tooling, 11 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (tools-manage/invocationlab-erd-online-view/src/components/LeftContent/DesignLeftContent/component/DataDomain.tsx) — 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 — tools-manage/invocationlab-erd-online-view/src/components/dialog/database/RenameDatabase.tsx
no import path from any entry point (31 application, 13 tooling, 11 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (tools-manage/invocationlab-erd-online-view/src/pages/design/table/component/table/TableCodeShow.tsx) — 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 — tools-manage/invocationlab-erd-online-view/src/utils/dbversionutils.js
no import path from any entry point (31 application, 13 tooling, 11 test roots considered), but 11 in-repo import(s) from 11 other file(s) do name it (tools-manage/invocationlab-erd-online-view/src/components/Header/DesignHeader/index.tsx, tools-manage/invocationlab-erd-online-view/src/components/dialog/export/ExportDDL.tsx, tools-manage/invocationlab-erd-online-view/src/components/dialog/export/ExportHTML.tsx and 8 more) — 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 — tools-manage/invocationlab-erd-online-view/src/components/Menu/index.tsx
no import path from any entry point (31 application, 13 tooling, 11 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (tools-manage/invocationlab-erd-online-view/src/layouts/DesignLayout/index.tsx) — 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 — tools-manage/invocationlab-erd-online-view/src/layouts/DesignLayout/_defaultProps.tsx
no import path from any entry point (31 application, 13 tooling, 11 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (tools-manage/invocationlab-erd-online-view/src/components/dialog/database/RenameDatabase.tsx) — 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 — tools-manage/invocationlab-erd-online-view/src/components/dialog/database/PreviewDatabase.tsx
What to do
Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
React / JS · Readiness — npm dependency truthfulness (D-386): unused dependencies, imports not declared anywhere, and type-/test-only packages shipped as production deps.
Method: npm dependency truthfulness: unused dependencies, imports declared nowhere, and type-/test-only packages shipped as production deps — from the manifest + import graph. Deterministic.
Imported but not declared in any reachable REDACTED — installs work only by hoisting accident. (×10) — spring-embed-arthas/src/main/webapp/index.js:2, tools-manage/invocationlab-erd-online-view/.eslintrc.js:2, tools-manage/invocationlab-erd-online-view/tests/PuppeteerEnvironment.js:2, …
Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×23) — REDACTED:56, REDACTED:63, REDACTED:64, …
Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×7) — REDACTED:25, REDACTED:18, REDACTED:29, …
What to do
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
Do you agree with this assessment?
R9 · Circular Imports3.7 / 10Weak✓ Tool-verified
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.
`http://libs.baidu.com/jquery/2.0.0/jquery.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. 2 such include(s) across the repository's markup. — REDACTED:6
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 `nginx.conf` 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.) — tools-manage/invocationlab-erd-online-view/ci/conf/nginx.conf:66
`product` is set explicitly here. The OWASP Secure Headers Project lists it among the response headers to REMOVE: it names the server, framework or tooling behind the application, which is exactly what an attacker looks up known exploits for. (No deduction on this card.) — tools-manage/invocationlab-admin/src/main/resources/public/invocationlab-rpcpostman-view/static/js/chunk-libs.783b4dbe.js: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.
Stop sending `product`: delete the write, and suppress the framework's own copy where it has one (Kestrel `AddServerHeader = false`, Express `app.disable('x-powered-by')` / `helmet.hidePoweredBy()`, nginx `server_tokens off`, IIS `<requestFiltering removeServerHeader="true" />`).
Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.
Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.
Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.
Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.
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.
Do you agree with this assessment?
X17 · Uncapped recursion over a caller-supplied document2.7 / 10Weak✓ Tool-verified
Other · Security — Whether a walk that recurses through a JSON/XML tree handed in by its caller bounds how deep it will go — an uncapped walk lets the document's nesting choose the stack depth, and the resulting StackOverflowException cannot be caught.
Method: Roslyn syntax + semantics: methods that take a JSON/XML document node and call themselves with a child of it, reachable from an externally-callable member of the same type that accepts a document, checked for any depth parameter, descent counter or threaded arithmetic anywhere in the walk. On a repository with no .NET source it reads TypeScript off the engine’s own token stream (test, vendored, generated and minified paths and `.d.ts` not) with the same rule: a function or method with a parameter typed as a document value — `unknown`, `any`, `object`, `Record<string, unknown|any>`, a JSON alias (`JsonValue`, `JSONObject`, …) or a DOM node global the file does not rebind — that calls itself (bare, or through `this` for a method, or hands itself to a call over the value as in `value.map(walk)`) with something it took out of that value and never through an ancestor accessor such as `closest()` or `parentElement`, that is exported or reached from an exported function (a public method of the same exported class) taking such a value, and that names no depth, level, nesting, recursion, remaining or budget anywhere and threads no `+`/`-` arithmetic through a self-call. Plain JavaScript is not read: with no annotation nothing tells a parsed document from a tree the code built itself. Deterministic, provable per finding. Advisory.
`convertRowToDoc` is not private, takes a value from its caller (line 262) and hands it on to `convertValue`, which calls itself at line 311 with a piece of `oldValue` — and nowhere in the walk is a depth or nesting counter compared with a bound, nor is the parser that builds the document given a nesting limit in this file. The walk therefore spends one stack frame (more through a lambda or a stream) per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes; javac turns no recursive call into a loop. On the JVM's default 1 MB thread stack a recursive walk throws `StackOverflowError` from about 500–2,000 levels on a cold first call and 6,000–17,000 once warmed up (OpenJDK 21 and 25). org.json, the W3C DOM, dom4j and StAX set no nesting limit of their own, Jackson before 2.15 none and 2.15+ 1,000 — on a cold JVM past the point the walk fails — and a `Map<String, Object>` tree is as deep as whatever built it. `StackOverflowError` is an `Error`, not an `Exception`: a `catch (Exception e)` around the call does not stop it, and the request or the thread dies with it. Thread a depth argument through `convertValue` and reject the value past a fixed maximum, configure the parser's nesting limit (`StreamReadConstraints.maxNestingDepth`, SnakeYAML's `setNestingDepthLimit`), or rewrite the descent with an explicit stack. — tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/MongoDbServiceImpl.java:311
`getTableColumns` is not private, takes a value from its caller (line 322) and hands it on to `convertToColumns`, which calls itself at line 348 with a piece of `value` (and at line 362) — and nowhere in the walk is a depth or nesting counter compared with a bound, nor is the parser that builds the document given a nesting limit in this file. The walk therefore spends one stack frame (more through a lambda or a stream) per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes; javac turns no recursive call into a loop. On the JVM's default 1 MB thread stack a recursive walk throws `StackOverflowError` from about 500–2,000 levels on a cold first call and 6,000–17,000 once warmed up (OpenJDK 21 and 25). org.json, the W3C DOM, dom4j and StAX set no nesting limit of their own, Jackson before 2.15 none and 2.15+ 1,000 — on a cold JVM past the point the walk fails — and a `Map<String, Object>` tree is as deep as whatever built it. `StackOverflowError` is an `Error`, not an `Exception`: a `catch (Exception e)` around the call does not stop it, and the request or the thread dies with it. Thread a depth argument through `convertToColumns` and reject the value past a fixed maximum, configure the parser's nesting limit (`StreamReadConstraints.maxNestingDepth`, SnakeYAML's `setNestingDepthLimit`), or rewrite the descent with an explicit stack. — tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/MongoDbServiceImpl.java:348
What to do
Each finding names the externally-callable member that accepts the document and the self-call that descends, and states that no depth parameter or counter exists anywhere in the walk. Confirm from the two, then thread a depth argument through the walk and reject documents past a fixed maximum, or rewrite it with an explicit stack.
Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.
Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. 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 async functions that make a cancellable request accept or pass on an AbortSignal (adoption curve).
Method: Roslyn scan: every async method (excluding framework-fixed overrides/Blazor handlers) checked for CancellationToken parameter presence. Deterministic, adoption percentage. 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 question: every named async function that itself makes a request an AbortSignal can cancel (global `fetch`, axios and its file-local instances, ky, ofetch) counts, and it is compliant when its parameters or body name a signal or it hands one of its own parameters to the request as options; signatures a framework fixes (JSX event handlers, route and lifecycle exports, request-first handlers, `override`, `'use server'` modules, TanStack `mutationFn`) are exempt unless they take a signal. Deterministic, adoption percentage.
Only 0/1 async functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
`client` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — tools-manage/invocationlab-erd-online-view/src/store/api/client.js:4
What to do
Thread an AbortSignal through async functions that make requests, so the work stops when its caller gives up.
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 unescaped5.3 / 10Adequate✓ 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.
`e.content:r.textContent=e.content` 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. — spring-embed-arthas/src/main/webapp/index.js:3202
`n` is text this program did not author, and it is written into a quoted attribute value 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. — spring-embed-arthas/src/main/webapp/index.js:16725
`cur` 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. — spring-embed-arthas/src/main/webapp/vue.js:7640
`html` 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. — spring-embed-arthas/src/main/webapp/vue.js:9216
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?
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.
`.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it. (×13) — tools-manage/tools-manage-view/src/views/RedisManageView.vue:393, tools-manage/tools-manage-view/src/views/RedisManageView.vue:465, tools-manage/tools-manage-view/src/views/RedisManageView.vue:495, …
`catch (e: Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×2) — tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/util/AesUtils.kt:21, tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/util/AesUtils.kt:36
`catch (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×3) — tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/util/AesUtils.java:24, tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/util/AesUtils.java:38, b2c-parent/b2c-bytecode/src/main/java/org/javamaster/b2c/bytecode/model/PersonCopy.java:36
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. (×7) — spring-embed-arthas/src/main/webapp/index.js:793, spring-embed-arthas/src/main/webapp/index.js:1068, spring-embed-arthas/src/main/webapp/index.js:12233, …
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 `REDACTED` declares a logger that carries values as fields (pino, pino-http, nestjs-pino, Fastify, winston, bunyan, tslog, LogTape, roarr), whose first deciding argument is a template literal with substitutions; an object-literal fields argument is stepped over, a plain string message clears the call. Python is read the same way: a `debug`/`info`/`warning`/`error`/`exception`/`critical`/`log` call on a logger in a file that imports the standard library’s `logging` or structlog (loguru, which formats at the call, is not judged), whose message is a whole f-string with a non-constant field; a `%`-formatted, `.format()`-ed or concatenated message is not convicted, as in C#. PHP is read the same way: a PSR-3 level call (`emergency`…`debug`, `log`) on a logger (`$logger`, `$this->logger`, Laravel’s `Log::`, `logger()`, `\Drupal::logger()`) in a package whose `composer.json` requires a PSR-3 logger or a framework that hands one out (psr/log, Monolog, Laravel, Symfony, Drupal, CakePHP), or a file that imports one, whose message is a double-quoted string interpolating a variable; a single-quoted message clears the call, and `sprintf` or `.` concatenation is not convicted, as in C#. Dart is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on Sentry’s structured logger (`Sentry.logger`) whose message is a whole string literal interpolating a value (`$name`, `${…}`); the `Sentry.logger.fmt` template API clears the call. Dart that logs only through loggers with one message and no fields (package:logging, package:logger, talker, dart:developer) is not applicable rather than a reach gap. Ruby is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on the console gem’s `Console` (declared by a Gemfile, gemspec or Gemfile.lock, or required) or, where SemanticLogger, Ougai or dry-logger is declared or required, on a receiver named for a logger (`logger`, `@logger`, `Rails.logger`, `log`), whose first deciding argument is, as the whole argument, a double-quoted string interpolating a non-constant value (`#{…}`, `#@ivar`); a plain literal clears the call, keyword arguments are the fields, and a block, `%`-format or `+` concatenation is not convicted. Ruby that logs only through the standard Logger (Rails.logger) is not applicable rather than a reach gap. Deterministic.
`error` at line 26 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, 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 with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/GlobalHandler.kt:26
`error` at line 36 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, 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 with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/GlobalHandler.kt:36
`info` at line 74 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, 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 with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. (×2) — tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/service/registry/impl/ZkRegister.kt:74, tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/config/Initializer.kt:74
`warn` at line 84 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, 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 with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/service/load/impl/JarLocalFileLoader.kt:84
`error` at line 40 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, 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 with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/service/invocation/impl/DubboConverter.kt:40
`info` at line 42 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, 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 with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/service/invocation/impl/DubboInvoker.kt:42
`info` at line 106 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, 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 with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/service/invocation/impl/DubboInvoker.kt:106
`debug` at line 62 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, 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 with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/controller/RpcPostmanProxyController.kt:62
`info` at line 36 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, 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 with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/config/Initializer.kt:36
`info` at line 44 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, 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 with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/config/Initializer.kt:44
`info` at line 78 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, 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 with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/config/Initializer.kt:78
`info` at line 85 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, 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 with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/config/Initializer.kt:85
`info` at line 102 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, 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 with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/config/Initializer.kt:102
`info` at line 109 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, 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 with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/config/Initializer.kt:109
`info` at line 83 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. — tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/registry/impl/ZkRegister.java:83
`warn` at line 94 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. — tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/load/impl/JarLocalFileLoader.java:94
`error` at line 49 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. — tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/invocation/impl/DubboConverter.java:49
`info` at line 44 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) — tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/invocation/impl/DubboInvoker.java:44, REDACTED:44
`info` 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.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) — tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/invocation/impl/DubboInvoker.java:109, REDACTED:109
`debug` at line 64 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. — tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/controller/RpcPostmanProxyController.java:64
`info` at line 51 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. — REDACTED:51
`info` at line 82 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. — REDACTED:82
`info` at line 86 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. — REDACTED:86
`info` at line 93 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. — REDACTED:93
`info` at line 116 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. — REDACTED:116
Other · Code Health — Whether strict null checking is enabled and not undermined by heavy `!` assertion — TypeScript's `strictNullChecks` (which `strict` turns on) is what makes `string` exclude `null` and `undefined`, and the postfix `!` is the operator that silences it.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
1/3 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.
What to do
The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`).
Do you agree with this assessment?
WCAG coverage — what static analysis assessed
Statically assessed 13 of 55 WCAG 2.2 Level A/AA success criteria (24%; ≈26% of the 50 WCAG 2.1 AA criteria for EN 301 549). A further 4 got runtime (rendered axe-core) evidence this scan: 1.4.1, 1.4.3, 1.4.12, 2.4.4. The other 38 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.
Unscored — 6 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.
AXH1 Runtime security headers — 11 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXI1 Runtime container hardening — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility (rendered) — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXS1 Runtime exposed surface — 3 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X10 Duplicated predicate — 25 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 5 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
P6 Release Hygiene — not evidenced — no changelog, version stamp or semver release tag in the repo
Not included — 46 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.
AC6 Visual & motion safety — Visual & motion safety could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository.
AX1 Captive dependencies — AX1 reached only 39% of this repository's production lines — javascript (42,437 lines), typescript (22,575 lines), python (151 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
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
AXA1 Runtime unauthenticated reachability — This run crawled public routes only — it had no logged-in session, so there is no authenticated surface to compare anonymous access against and nothing was measured. This is a statement about this run, not about your application: nothing here says access control is missing, and nothing here says it is present.
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
D10 Test Quality — ~6617 lines of test source are present (.java) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
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.
D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D25 ADR Conformance — no ADRs to check
D27 Navigability — D27 reads resolved call sites in the languages it reads only — this repository's production source is .java, .kt, .py, .ts, .tsx, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D32 Data Compliance (PII/GDPR) — 17 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
D8 Code Coverage — Coverage not measured — Java/Kotlin suite
DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 5 value object(s); 1 repository port(s) loading or saving an aggregate/entity
ED1 Event-Driven — not scored — this repository shows only 1 of the 3 signals this lens looks for (1 event handler(s))
ED5 Idempotency — Not assessed, and this one is on us: 1 command handler(s) or message consumer(s) were found here, but this check does not yet recognise persistence writes in this repository's language. Idempotency was neither confirmed nor ruled out — this is a limit of the analyzer, not a finding about your code.
ES1 Event Sourcing — not scored — this repository shows only 1 of the 3 signals this lens looks for (an Axon event-sourcing framework (@Aggregate/@CommandHandler/@EventSourcingHandler annotations))
P12 CI test-gate honesty — no CI workflow found
P8 Schema migrations — Hibernate is declared, but the schema-migration mechanism could not be identified. Our limit, not a verdict on this repository.
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 tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a REDACTED, 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.
R4 Test Coverage — 11 test file(s) reach none of 274 production file(s) via imports — exercised outside the JS import graph (integration/bundled), not import-reachable
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
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
X27 Collection changed while being enumerated — X27 reached only 40% of this repository's production lines — javascript (42,437 lines), typescript (22,575 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
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.
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.
D30 · Dependency Vulnerabilities· High vulnerability · ×8
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
AC1 · Text alternatives· <img> without a text alternative · ×7
<img> without a text alternative tools-manage/invocationlab-admin-21/src/main/resources/erd.vm:120— 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 tools-manage/invocationlab-admin/src/main/resources/erd.vm:119— 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 tools-manage/invocationlab-erd-online-view/src/components/Header/ProjectHeader/index.tsx:14— 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 tools-manage/invocationlab-rpcpostman-view/src/views/error-page/401.vue:27— 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 tools-manage/invocationlab-rpcpostman-view/src/views/layout/components/Navbar.vue:28— 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 tools-manage/invocationlab-rpcpostman-view/src/views/layout/components/Sidebar/Logo.vue:5— 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 tools-manage/invocationlab-rpcpostman-view/src/views/layout/components/Sidebar/Logo.vue:9— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<html> without a lang b2c-parent/b2c-scheduled/src/main/resources/templates/task-list.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 spring-embed-arthas/src/main/webapp/vue.js:11887— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang spring-lifecycle/src/main/webapp/WEB-INF/views/welcome.jsp:3— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang tools-manage/invocationlab-admin/src/main/resources/public/invocationlab-erd-online-view/index.html:1— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang tools-manage/invocationlab-admin/src/main/resources/public/invocationlab-rpcpostman-view/index.html:1— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang tools-manage/invocationlab-rpcpostman-view/index.html:2— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
AC4 · Keyboard semantics· Click handler on a non-interactive <div> · ×6
Click handler on a non-interactive <div> tools-manage/invocationlab-erd-online-view/src/components/HeaderSearch/index.tsx:51— A click handler on a plain element with no role and no tabindex: even where another element's key handler can reach it, assistive tech can neither focus it nor announce what it is. Use a <button>, or add role + tabIndex={0}.
Click handler on a non-interactive <div> tools-manage/invocationlab-erd-online-view/src/components/NoticeIcon/NoticeList.tsx:93— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> tools-manage/invocationlab-erd-online-view/src/components/NoticeIcon/NoticeList.tsx:98— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> tools-manage/invocationlab-rpcpostman-view/src/components/BackToTop/index.vue:3— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
Click handler on a non-interactive <div> tools-manage/invocationlab-rpcpostman-view/src/views/layout/Layout.vue:3— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
Click handler on a non-interactive <div> tools-manage/invocationlab-rpcpostman-view/src/views/layout/components/Navbar.vue:7— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
AC4 · Keyboard semantics· Double-click handler on a non-interactive <span> · ×6
Double-click handler on a non-interactive <span> tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/ExplainResult.tsx:27— This <span> binds double-click and nothing else. No click, no key handler, and no tabIndex={0}, so it cannot even take focus. Nothing synthesises a double-click from the keyboard: Enter and Space fire a single click, and only on a native <button> or <a href>. So this behaviour has no keyboard path at all. Expose the same action on a real control, or add role + tabIndex={0} + a key handler alongside the double-click.
Double-click handler on a non-interactive <span> tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/QueryHistory.tsx:33— This <span> binds double-click and nothing else. No click, no key handler, and no tabIndex={0}, so it cannot even take focus. Nothing synthesises a double-click from the keyboard: Enter and Space fire a single click, and only on a native <button> or <a href>. So this behaviour has no keyboard path at all. Expose the same action on a real control, or add role + tabIndex={0} + a key handler alongside the double-click.
Double-click handler on a non-interactive <span> tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/QueryHistory.tsx:43— This <span> binds double-click and nothing else. No click, no key handler, and no tabIndex={0}, so it cannot even take focus. Nothing synthesises a double-click from the keyboard: Enter and Space fire a single click, and only on a native <button> or <a href>. So this behaviour has no keyboard path at all. Expose the same action on a real control, or add role + tabIndex={0} + a key handler alongside the double-click.
Double-click handler on a non-interactive <span> tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/QueryResult.tsx:90— This <span> binds double-click and nothing else. No click, no key handler, and no tabIndex={0}, so it cannot even take focus. Nothing synthesises a double-click from the keyboard: Enter and Space fire a single click, and only on a native <button> or <a href>. So this behaviour has no keyboard path at all. Expose the same action on a real control, or add role + tabIndex={0} + a key handler alongside the double-click.
Double-click handler on a non-interactive <span> tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/QueryResult.tsx:95— This <span> binds double-click and nothing else. No click, no key handler, and no tabIndex={0}, so it cannot even take focus. Nothing synthesises a double-click from the keyboard: Enter and Space fire a single click, and only on a native <button> or <a href>. So this behaviour has no keyboard path at all. Expose the same action on a real control, or add role + tabIndex={0} + a key handler alongside the double-click.
Double-click handler on a non-interactive <span> tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/QueryResult.tsx:99— This <span> binds double-click and nothing else. No click, no key handler, and no tabIndex={0}, so it cannot even take focus. Nothing synthesises a double-click from the keyboard: Enter and Space fire a single click, and only on a native <button> or <a href>. So this behaviour has no keyboard path at all. Expose the same action on a real control, or add role + tabIndex={0} + a key handler alongside the double-click.
Banned license: mysql:mysql-connector-java — `mysql:mysql-connector-java` 5.1.18 is published on Maven Central under `GPL-2.0`, which this policy bans, and this repository declares it in a Maven or Gradle manifest. The licence was read from the artifact's POM `<licenses>` block — following `<parent>` where the POM inherits them — and normalised to SPDX before it was judged, because Maven publishes the name as free text (`GNU Affero General Public License v3` is AGPL-3.0). Where a POM lists several licences they are read as a CHOICE, per Maven's own documentation, so this is charged only because EVERY listed licence is banned. Replace the dependency, or record an accepted exception.
Banned license: mysql:mysql-connector-java — `mysql:mysql-connector-java` 5.1.49 is published on Maven Central under `GPL-2.0`, which this policy bans, and this repository declares it in a Maven or Gradle manifest. The licence was read from the artifact's POM `<licenses>` block — following `<parent>` where the POM inherits them — and normalised to SPDX before it was judged, because Maven publishes the name as free text (`GNU Affero General Public License v3` is AGPL-3.0). Where a POM lists several licences they are read as a CHOICE, per Maven's own documentation, so this is charged only because EVERY listed licence is banned. Replace the dependency, or record an accepted exception.
Banned license: com.itextpdf:itextpdf — `com.itextpdf:itextpdf` 5.5.13.3 is published on Maven Central under `AGPL-3.0`, which this policy bans, and this repository declares it in a Maven or Gradle manifest. The licence was read from the artifact's POM `<licenses>` block — following `<parent>` where the POM inherits them — and normalised to SPDX before it was judged, because Maven publishes the name as free text (`GNU Affero General Public License v3` is AGPL-3.0). Where a POM lists several licences they are read as a CHOICE, per Maven's own documentation, so this is charged only because EVERY listed licence is banned. Replace the dependency, or record an accepted exception.
Banned license: com.itextpdf:html2pdf — `com.itextpdf:html2pdf` 4.0.3 is published on Maven Central under `AGPL-3.0`, which this policy bans, and this repository declares it in a Maven or Gradle manifest. The licence was read from the artifact's POM `<licenses>` block — following `<parent>` where the POM inherits them — and normalised to SPDX before it was judged, because Maven publishes the name as free text (`GNU Affero General Public License v3` is AGPL-3.0). Where a POM lists several licences they are read as a CHOICE, per Maven's own documentation, so this is charged only because EVERY listed licence is banned. Replace the dependency, or record an accepted exception.
Banned license: com.itextpdf.tool:xmlworker — `com.itextpdf.tool:xmlworker` 5.5.13.3 is published on Maven Central under `AGPL-3.0`, which this policy bans, and this repository declares it in a Maven or Gradle manifest. The licence was read from the artifact's POM `<licenses>` block — following `<parent>` where the POM inherits them — and normalised to SPDX before it was judged, because Maven publishes the name as free text (`GNU Affero General Public License v3` is AGPL-3.0). Where a POM lists several licences they are read as a CHOICE, per Maven's own documentation, so this is charged only because EVERY listed licence is banned. Replace the dependency, or record an accepted exception.
Banned license: com.itextpdf:itext-asian — `com.itextpdf:itext-asian` 5.2.0 is published on Maven Central under `AGPL-3.0`, which this policy bans, and this repository declares it in a Maven or Gradle manifest. The licence was read from the artifact's POM `<licenses>` block — following `<parent>` where the POM inherits them — and normalised to SPDX before it was judged, because Maven publishes the name as free text (`GNU Affero General Public License v3` is AGPL-3.0). Where a POM lists several licences they are read as a CHOICE, per Maven's own documentation, so this is charged only because EVERY listed licence is banned. Replace the dependency, or record an accepted exception.
AC4 · Keyboard semantics· Clickable element isn't keyboard-operable · ×4
Clickable element isn't keyboard-operable tools-manage/invocationlab-rpcpostman-view/src/views/layout/components/Navbar.vue:17— The repo's own CSS styles .el-icon-caret-bottom with `cursor: pointer`, so this <i> 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 tools-manage/invocationlab-rpcpostman-view/src/views/layout/components/Navbar.vue— The repo's own CSS styles .el-icon-caret-bottom with `cursor: pointer`, so this <i> 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 tools-manage/invocationlab-rpcpostman-view/src/views/layout/components/Navbar.vue:28— The repo's own CSS styles .user-avatar 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 tools-manage/invocationlab-rpcpostman-view/src/views/layout/components/Navbar.vue:29— The repo's own CSS styles .el-icon-caret-bottom with `cursor: pointer`, so this <i> 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.
AC4 · Keyboard semantics· Click handler on a non-interactive <li> · ×4
Click handler on a non-interactive <li> tools-manage/invocationlab-rpcpostman-view/src/views/layout/components/TagsView.vue:19— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
Click handler on a non-interactive <li> tools-manage/invocationlab-rpcpostman-view/src/views/layout/components/TagsView.vue:20— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
Click handler on a non-interactive <li> tools-manage/invocationlab-rpcpostman-view/src/views/layout/components/TagsView.vue:21— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
Click handler on a non-interactive <li> tools-manage/invocationlab-rpcpostman-view/src/views/layout/components/TagsView.vue:22— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
AC2 · Forms & labels· <label> that labels no control · ×2
<label> that labels no control tools-manage/invocationlab-rpcpostman-view/src/views/pages/CreateService.vue:43— 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 tools-manage/invocationlab-rpcpostman-view/src/views/pages/CreateServiceJdk.vue:30— 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 · ×1
<select> without a programmatic label spring-embed-arthas/src/main/webapp/vue.js:8535— 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· Link with no accessible name · ×1
Link with no accessible name spring-embed-arthas/src/main/webapp/vue.js:11861— A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label.
AC2 · Forms & labels· Custom control with no accessible name on <svg> · ×1
Custom control with no accessible name on <svg> tools-manage/invocationlab-rpcpostman-view/src/components/Hamburger/index.vue— This <svg> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.
Viewport restricts zoom tools-manage/invocationlab-admin/src/main/resources/public/invocationlab-erd-online-view/index.html:3— user-scalable=no/0 or a maximum-scale below 2 stops low-vision users zooming to 200%. Remove the zoom restriction from the viewport meta.
AC4 · Keyboard semantics· Click handler on a non-interactive <svg> · ×1
Click handler on a non-interactive <svg> tools-manage/invocationlab-rpcpostman-view/src/components/Hamburger/index.vue— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
AC4 · Keyboard semantics· Click handler on a non-interactive <span> · ×1
Click handler on a non-interactive <span> tools-manage/invocationlab-rpcpostman-view/src/views/layout/components/Navbar.vue:38— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
Unlisted import 'vue' spring-embed-arthas/src/main/webapp/index.js:2— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import '@umijs/fabric' tools-manage/invocationlab-erd-online-view/.eslintrc.js:2— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import 'jest-environment-node' tools-manage/invocationlab-erd-online-view/tests/PuppeteerEnvironment.js:2— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import 'puppeteer' tools-manage/invocationlab-erd-online-view/tests/beforeTest.js:32— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import 'umi' tools-manage/invocationlab-erd-online-view/src/services/swagger/pet.ts:3— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import '@/icons' tools-manage/invocationlab-rpcpostman-view/src/main.js:60— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import '@/styles' tools-manage/invocationlab-rpcpostman-view/src/main.js:55— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import '@/utils' tools-manage/invocationlab-rpcpostman-view/src/main.js:53— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import '@/views' tools-manage/invocationlab-rpcpostman-view/src/router/index.js:6— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import 'hammerjs' tools-manage/invocationlab-rpcpostman-view/src/components/ElImageTouch/index.vue:9— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
FunctionTooLong: ConstructSqlForm.ConstructSqlForm tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/ConstructSqlForm.tsx:22— FunctionTooLong — ConstructSqlForm runs 363 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 263 over it, 3.63× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: index.Query tools-manage/invocationlab-erd-online-view/src/pages/design/query/index.tsx:26— FunctionTooLong — Query runs 358 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 258 over it, 3.58× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: ConstructSqlFormMongoDB.ConstructSqlForm tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/ConstructSqlFormMongoDB.tsx:22— FunctionTooLong — ConstructSqlForm runs 352 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 252 over it, 3.52× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: relation2file.renderRelation tools-manage/invocationlab-erd-online-view/src/utils/relation2file.js:160— FunctionTooLong — renderRelation runs 286 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 186 over it, 2.86× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: QueryResult.QueryResult tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/QueryResult.tsx:25— FunctionTooLong — QueryResult runs 273 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 173 over it, 2.73× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: DatabaseSetUp.DatabaseSetUp tools-manage/invocationlab-erd-online-view/src/pages/design/setting/component/DatabaseSetUp.tsx:23— FunctionTooLong — DatabaseSetUp runs 252 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 152 over it, 2.52× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: DatabaseSetUp.DatabaseSetUp REDACTED:25— FunctionTooLong — DatabaseSetUp runs 241 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 141 over it, 2.41× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: profileSlice.ProfileSlice tools-manage/invocationlab-erd-online-view/src/store/project/profileSlice.tsx:48— FunctionTooLong — ProfileSlice runs 241 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 141 over it, 2.41× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: GroupPermission.GroupPermission tools-manage/invocationlab-erd-online-view/src/pages/project/group/component/GroupPermission.tsx:34— FunctionTooLong — GroupPermission runs 229 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 129 over it, 2.29× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: index.Home tools-manage/invocationlab-erd-online-view/src/pages/project/home/index.tsx:9— FunctionTooLong — Home runs 211 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 111 over it, 2.11× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: MetaDataSearch.MetaDataSearch tools-manage/invocationlab-erd-online-view/src/components/LeftContent/DesignLeftContent/component/MetaDataSearch.tsx:40— FunctionTooLong — MetaDataSearch runs 193 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 93 over it, 1.93× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: json2code.getDemoTemplateData tools-manage/invocationlab-erd-online-view/src/utils/json2code.ts:503— FunctionTooLong — getDemoTemplateData runs 191 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 91 over it, 1.91× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: index.JExcel tools-manage/invocationlab-erd-online-view/src/pages/JExcel/index.tsx:22— FunctionTooLong — JExcel runs 172 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 72 over it, 1.72× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: modulesSlice.ModulesSlice tools-manage/invocationlab-erd-online-view/src/store/project/modulesSlice.tsx:57— FunctionTooLong — ModulesSlice runs 166 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 66 over it, 1.66× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: FieldMultiSelect.FieldMultiSelect tools-manage/invocationlab-erd-online-view/src/pages/design/table/component/table/FieldMultiSelect.tsx:35— FunctionTooLong — FieldMultiSelect runs 165 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 65 over it, 1.65× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: ExportDDL.ExportDDL tools-manage/invocationlab-erd-online-view/src/components/dialog/export/ExportDDL.tsx:25— FunctionTooLong — ExportDDL runs 163 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 63 over it, 1.63× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: index.default tools-manage/invocationlab-erd-online-view/src/pages/login/index.tsx:39— FunctionTooLong — default runs 161 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 61 over it, 1.61× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: CompareVersion.CompareVersion tools-manage/invocationlab-erd-online-view/src/components/dialog/version/CompareVersion.tsx:21— FunctionTooLong — CompareVersion runs 160 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 60 over it, 1.60× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: index.Version tools-manage/invocationlab-erd-online-view/src/pages/design/version/index.tsx:27— FunctionTooLong — Version runs 160 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 60 over it, 1.60× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: json2code.generateUpdateSql tools-manage/invocationlab-erd-online-view/src/utils/json2code.ts:201— FunctionTooLong — generateUpdateSql runs 158 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 58 over it, 1.58× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: exportSlice.ExportSlice tools-manage/invocationlab-erd-online-view/src/store/project/exportSlice.tsx:35— FunctionTooLong — ExportSlice runs 153 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 53 over it, 1.53× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: ExportDDL.ExportDDL tools-manage/invocationlab-erd-online-view/src/pages/design/export/component/ExportDDL.tsx:21— FunctionTooLong — ExportDDL runs 144 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 44 over it, 1.44× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: RenameDatabase.RenameDatabase tools-manage/invocationlab-erd-online-view/src/components/dialog/database/RenameDatabase.tsx:15— FunctionTooLong — RenameDatabase runs 143 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 43 over it, 1.43× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: index.DesignLayout tools-manage/invocationlab-erd-online-view/src/layouts/DesignLayout/index.tsx:84— FunctionTooLong — DesignLayout runs 133 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 33 over it, 1.33× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: index.JExcel tools-manage/invocationlab-erd-online-view/src/components/JExcel/index.tsx:11— FunctionTooLong — JExcel runs 123 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 23 over it, 1.23× 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.
(anonymous)::i (cognitive 38) spring-embed-arthas/src/main/webapp/index.js:6851— (anonymous)::i has cognitive complexity 38 (threshold 15). Drivers by points: ternaries 8 (24 pts), if/else 7 (11 pts), boolean chains 3 (nesting depth added 20). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
(anonymous)::n (cognitive 35) spring-embed-arthas/src/main/webapp/index.js:8078— (anonymous)::n has cognitive complexity 35 (threshold 15). Drivers by points: ternaries 21, boolean chains 14. 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.
(anonymous)::validate::(anonymous)::s (cognitive 35) spring-embed-arthas/src/main/webapp/index.js:11903— (anonymous)::validate::(anonymous)::s has cognitive complexity 35 (threshold 15). Drivers by points: ternaries 4 (11 pts), if/else 6 (10 pts), boolean chains 9, loops 2 (5 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
(anonymous)::exports (cognitive 31) spring-embed-arthas/src/main/webapp/index.js:1480— (anonymous)::exports has cognitive complexity 31 (threshold 15). Drivers by points: boolean chains 15, ternaries 5 (9 pts), if/else 3 (4 pts), loops 1 (3 pts) (nesting depth added 7). 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.
(anonymous)::v::fromString (cognitive 29) spring-embed-arthas/src/main/webapp/index.js:1640— (anonymous)::v::fromString has cognitive complexity 29 (threshold 15). Drivers by points: ternaries 5 (12 pts), if/else 7 (9 pts), boolean chains 8 (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.
(anonymous)::setData (cognitive 29) spring-embed-arthas/src/main/webapp/index.js:6998— (anonymous)::setData has cognitive complexity 29 (threshold 15). Drivers by points: if/else 7 (15 pts), ternaries 4 (9 pts), boolean chains 3, loops 1 (2 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
(anonymous)::u::updateElsHeight (cognitive 29) spring-embed-arthas/src/main/webapp/index.js:7280— (anonymous)::u::updateElsHeight has cognitive complexity 29 (threshold 15). Drivers by points: ternaries 7 (16 pts), boolean chains 7, if/else 4 (6 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.
(anonymous)::value (cognitive 28) spring-embed-arthas/src/main/webapp/index.js:10371— (anonymous)::value has cognitive complexity 28 (threshold 15). Drivers by points: if/else 7 (13 pts), ternaries 3 (13 pts), boolean chains 2 (nesting depth added 16). 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.
(anonymous)::a (cognitive 27) spring-embed-arthas/src/main/webapp/index.js:1153— (anonymous)::a has cognitive complexity 27 (threshold 15). Drivers by points: boolean chains 13, ternaries 8 (13 pts), loops 1 (nesting depth added 5). 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.
(anonymous)::handleClick (cognitive 27) spring-embed-arthas/src/main/webapp/index.js:10044— (anonymous)::handleClick has cognitive complexity 27 (threshold 15). Drivers by points: ternaries 4 (14 pts), if/else 6 (9 pts), boolean chains 4 (nesting depth added 13). 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.
(anonymous)::render::(anonymous)::(anonymous)::keydown (cognitive 26) spring-embed-arthas/src/main/webapp/index.js:16734— (anonymous)::render::(anonymous)::(anonymous)::keydown has cognitive complexity 26 (threshold 15). Drivers by points: if/else 8 (13 pts), ternaries 3 (9 pts), boolean chains 4 (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.
(anonymous)::(anonymous)::parse (cognitive 25) spring-embed-arthas/src/main/webapp/index.js:9035— (anonymous)::(anonymous)::parse has cognitive complexity 25 (threshold 15). Drivers by points: boolean chains 20, if/else 3, ternaries 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.
(anonymous)::handleQueryChange (cognitive 21) spring-embed-arthas/src/main/webapp/index.js:2311— (anonymous)::handleQueryChange has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 9, ternaries 3 (7 pts), if/else 3 (5 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
(anonymous)::n (cognitive 21) spring-embed-arthas/src/main/webapp/index.js:2818— (anonymous)::n has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 12, boolean chains 9. 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.
(anonymous)::n (cognitive 21) spring-embed-arthas/src/main/webapp/index.js:3955— (anonymous)::n has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 11, boolean chains 10. 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.
(anonymous)::u::updateColumnsWidth (cognitive 21) spring-embed-arthas/src/main/webapp/index.js:7305— (anonymous)::u::updateColumnsWidth has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (12 pts), ternaries 2 (7 pts), boolean chains 2 (nesting depth added 10). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
(anonymous)::f::e (cognitive 20) spring-embed-arthas/src/main/webapp/index.js:13471— (anonymous)::f::e has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 14, if/else 3, ternaries 1 (2 pts), loops 1 (nesting depth added 1). 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.
(anonymous)::doOpen (cognitive 19) spring-embed-arthas/src/main/webapp/index.js:686— (anonymous)::doOpen has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 13, if/else 2 (3 pts), ternaries 1 (3 pts) (nesting depth added 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.
(anonymous)::getCellClasses (cognitive 19) spring-embed-arthas/src/main/webapp/index.js:10009— (anonymous)::getCellClasses has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 16, 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.
(anonymous)::_dragColumn (cognitive 18) spring-embed-arthas/src/main/webapp/table-column-drag.js:338— (anonymous)::_dragColumn has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 3 (8 pts), if/else 4 (6 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
(anonymous)::exports (cognitive 17) spring-embed-arthas/src/main/webapp/index.js:25— (anonymous)::exports has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 5 (9 pts), boolean chains 7, if/else 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
(anonymous)::o (cognitive 17) spring-embed-arthas/src/main/webapp/index.js:272— (anonymous)::o has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 3 (7 pts), if/else 3 (4 pts), boolean chains 3, loops 1 (3 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
(anonymous)::pagers (cognitive 17) spring-embed-arthas/src/main/webapp/index.js:2089— (anonymous)::pagers has cognitive complexity 17 (threshold 15). Drivers by points: loops 4 (8 pts), boolean chains 5, if/else 4 (nesting depth added 4). 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.
(anonymous)::closeModal (cognitive 17) spring-embed-arthas/src/main/webapp/index.js:2987— (anonymous)::closeModal has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (11 pts), boolean chains 3, loops 1 (3 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
(anonymous)::updateCurrentRow (cognitive 17) spring-embed-arthas/src/main/webapp/index.js:7219— (anonymous)::updateCurrentRow has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (10 pts), boolean chains 4, loops 1 (3 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
(anonymous)::n (cyclomatic 36) spring-embed-arthas/src/main/webapp/index.js:8078— (anonymous)::n 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. This file is where this pass's cyclomatic complexity CONCENTRATES: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
(anonymous)::exports (cyclomatic 28) spring-embed-arthas/src/main/webapp/index.js:1480— (anonymous)::exports has cyclomatic complexity 28 (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. This file is where this pass's cyclomatic complexity CONCENTRATES: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
(anonymous)::(anonymous)::parse (cyclomatic 27) spring-embed-arthas/src/main/webapp/index.js:9035— (anonymous)::(anonymous)::parse has cyclomatic complexity 27 (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. This file is where this pass's cyclomatic complexity CONCENTRATES: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
(anonymous)::a (cyclomatic 26) spring-embed-arthas/src/main/webapp/index.js:1153— (anonymous)::a has cyclomatic complexity 26 (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. This file is where this pass's cyclomatic complexity CONCENTRATES: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
(anonymous)::n (cyclomatic 25) spring-embed-arthas/src/main/webapp/index.js:2818— (anonymous)::n has cyclomatic complexity 25 (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. This file is where this pass's cyclomatic complexity CONCENTRATES: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
(anonymous)::n (cyclomatic 24) spring-embed-arthas/src/main/webapp/index.js:3955— (anonymous)::n has cyclomatic complexity 24 (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. This file is where this pass's cyclomatic complexity CONCENTRATES: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
(anonymous)::f::e (cyclomatic 23) spring-embed-arthas/src/main/webapp/index.js:13471— (anonymous)::f::e has cyclomatic complexity 23 (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. This file is where this pass's cyclomatic complexity CONCENTRATES: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
(anonymous)::validate::(anonymous)::s (cyclomatic 22) spring-embed-arthas/src/main/webapp/index.js:11903— (anonymous)::validate::(anonymous)::s 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 file is where this pass's cyclomatic complexity CONCENTRATES: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
(anonymous)::v::fromString (cyclomatic 21) spring-embed-arthas/src/main/webapp/index.js:1640— (anonymous)::v::fromString has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This file is where this pass's cyclomatic complexity CONCENTRATES: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
(anonymous)::getCellClasses (cyclomatic 21) spring-embed-arthas/src/main/webapp/index.js:10009— (anonymous)::getCellClasses has cyclomatic complexity 21 (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. This file is where this pass's cyclomatic complexity CONCENTRATES: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
(anonymous)::u::updateElsHeight (cyclomatic 20) spring-embed-arthas/src/main/webapp/index.js:7280— (anonymous)::u::updateElsHeight has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This file is where this pass's cyclomatic complexity CONCENTRATES: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
(anonymous)::n (cyclomatic 19) spring-embed-arthas/src/main/webapp/index.js:6836— (anonymous)::n has cyclomatic complexity 19 (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. This file is where this pass's cyclomatic complexity CONCENTRATES: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
(anonymous)::n (cyclomatic 19) spring-embed-arthas/src/main/webapp/index.js:12335— (anonymous)::n has cyclomatic complexity 19 (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. This file is where this pass's cyclomatic complexity CONCENTRATES: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
(anonymous)::n (cyclomatic 19) spring-embed-arthas/src/main/webapp/index.js:15911— (anonymous)::n has cyclomatic complexity 19 (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. This file is where this pass's cyclomatic complexity CONCENTRATES: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
(anonymous)::createPopper (cyclomatic 18) spring-embed-arthas/src/main/webapp/index.js:425— (anonymous)::createPopper has cyclomatic complexity 18 (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. This file is where this pass's cyclomatic complexity CONCENTRATES: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
(anonymous)::i (cyclomatic 18) spring-embed-arthas/src/main/webapp/index.js:6851— (anonymous)::i has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This file is where this pass's cyclomatic complexity CONCENTRATES: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
(anonymous)::n (cyclomatic 18) spring-embed-arthas/src/main/webapp/index.js:9059— (anonymous)::n has cyclomatic complexity 18 (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. This file is where this pass's cyclomatic complexity CONCENTRATES: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
(anonymous)::doOpen (cyclomatic 17) spring-embed-arthas/src/main/webapp/index.js:686— (anonymous)::doOpen has cyclomatic complexity 17 (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. This file is where this pass's cyclomatic complexity CONCENTRATES: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
(anonymous)::n (cyclomatic 17) spring-embed-arthas/src/main/webapp/index.js:11417— (anonymous)::n has cyclomatic complexity 17 (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. This file is where this pass's cyclomatic complexity CONCENTRATES: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
(anonymous)::handleQueryChange (cyclomatic 16) spring-embed-arthas/src/main/webapp/index.js:2311— (anonymous)::handleQueryChange 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 file is where this pass's cyclomatic complexity CONCENTRATES: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
Swallowed exception (empty catch) tools-manage/tools-manage-view/src/views/RedisManageView.vue:393— `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) tools-manage/tools-manage-view/src/views/RedisManageView.vue:465— `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) tools-manage/tools-manage-view/src/views/RedisManageView.vue:495— `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) tools-manage/tools-manage-view/src/views/RedisManageView.vue:535— `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) tools-manage/tools-manage-view/src/views/RedisManageView.vue:558— `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) tools-manage/invocationlab-rpcpostman-view/src/views/pages/AccessService.vue:834— `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) tools-manage/invocationlab-rpcpostman-view/src/views/pages/KafkaManage.vue:443— `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) tools-manage/invocationlab-rpcpostman-view/src/views/pages/KafkaManage.vue:533— `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) REDACTED:483— `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) REDACTED:563— `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) REDACTED:594— `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) REDACTED:634— `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) REDACTED:657— `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) spring-embed-arthas/src/main/webapp/index.js:793— 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) spring-embed-arthas/src/main/webapp/index.js:1068— 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) spring-embed-arthas/src/main/webapp/index.js:12233— 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) spring-embed-arthas/src/main/webapp/index.js:13216— 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) spring-embed-arthas/src/main/webapp/vue.js:557— 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) spring-embed-arthas/src/main/webapp/vue.js:7659— 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) spring-embed-arthas/src/main/webapp/vue.js:7681— 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.
TooManyMethods: GeneratedCriteria b2c-parent/b2c-mybatis/src/main/java/org/javamaster/b2c/mybatis/entity/MenusExample.java:72— TooManyMethods — 121 methods. The bar is 30 methods; this is 91 over it, 4.03× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: GeneratedCriteria b2c-parent/b2c-mybatis/src/main/java/org/javamaster/b2c/mybatis/entity/ExamsExample.java:72— TooManyMethods — 99 methods. The bar is 30 methods; this is 69 over it, 3.30× 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: GeneratedCriteria b2c-parent/b2c-core/src/main/java/org/javamaster/b2c/core/entity/MicrowebsiteExamExample.java:70— TooManyMethods — 71 methods. The bar is 30 methods; this is 41 over it, 2.37× 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: GeneratedCriteria b2c-parent/b2c-core/src/main/java/org/javamaster/b2c/core/entity/SysRememberMeExample.java:71— TooManyMethods — 61 methods. The bar is 30 methods; this is 31 over it, 2.03× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: AbstractDbService tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/AbstractDbService.java:100— TooManyMethods — 51 methods. The bar is 30 methods; this is 21 over it, 1.70× 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: AbstractDbService tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/service/impl/AbstractDbService.kt:69— TooManyMethods — 49 methods. The bar is 30 methods; this is 19 over it, 1.63× 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: GeneratedCriteria b2c-parent/b2c-core/src/main/java/org/javamaster/b2c/core/entity/SysUserExample.java:70— TooManyMethods — 47 methods. The bar is 30 methods; this is 17 over it, 1.57× 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: G6Relation tools-manage/invocationlab-erd-online-view/src/pages/design/relation/g6.js:18— TooManyMethods — 47 methods. The bar is 30 methods; this is 17 over it, 1.57× 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: GeneratedCriteria b2c-parent/b2c-core/src/main/java/org/javamaster/b2c/core/entity/MicrowebsiteExamUserExample.java:70— TooManyMethods — 35 methods. The bar is 30 methods; this is 5 over it, 1.17× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: GeneratedCriteria b2c-parent/b2c-core/src/main/java/org/javamaster/b2c/core/entity/SysAuthorityExample.java:70— TooManyMethods — 35 methods. The bar is 30 methods; this is 5 over it, 1.17× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: GeneratedCriteria b2c-parent/b2c-core/src/main/java/org/javamaster/b2c/core/entity/SysGroupAuthorityExample.java:70— TooManyMethods — 35 methods. The bar is 30 methods; this is 5 over it, 1.17× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: GeneratedCriteria b2c-parent/b2c-core/src/main/java/org/javamaster/b2c/core/entity/SysGroupExample.java:70— TooManyMethods — 35 methods. The bar is 30 methods; this is 5 over it, 1.17× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: GeneratedCriteria b2c-parent/b2c-core/src/main/java/org/javamaster/b2c/core/entity/SysGroupUserExample.java:70— TooManyMethods — 35 methods. The bar is 30 methods; this is 5 over it, 1.17× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: ErdOnlineProjectServiceImpl tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/ErdOnlineProjectServiceImpl.java:102— TooManyMethods — 35 methods. The bar is 30 methods; this is 5 over it, 1.17× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: ErdOnlineProjectServiceImpl tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/service/impl/ErdOnlineProjectServiceImpl.kt:69— TooManyMethods — 32 methods. The bar is 30 methods; this is 2 over it, 1.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Boundary violation [package:third-party-deep-import] tools-manage/invocationlab-erd-online-view/src/components/CodeEditor/index.tsx:18— tools-manage/invocationlab-erd-online-view/src/components/CodeEditor/index.tsx:18 imports react-ace/src/types, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] tools-manage/invocationlab-erd-online-view/src/components/Menu/index.tsx:17— tools-manage/invocationlab-erd-online-view/src/components/Menu/index.tsx:17 imports @blueprintjs/core/src/common/props, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] tools-manage/invocationlab-erd-online-view/src/components/TableTransfer/index.tsx:4— tools-manage/invocationlab-erd-online-view/src/components/TableTransfer/index.tsx:4 imports antd/lib/transfer, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] tools-manage/invocationlab-erd-online-view/src/components/dialog/database/AddDatabase.tsx:8— tools-manage/invocationlab-erd-online-view/src/components/dialog/database/AddDatabase.tsx:8 imports antd/lib/radio/interface, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] tools-manage/invocationlab-erd-online-view/src/components/dialog/database/PreviewDatabase.tsx:6— tools-manage/invocationlab-erd-online-view/src/components/dialog/database/PreviewDatabase.tsx:6 imports antd/lib/radio/interface, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] tools-manage/invocationlab-erd-online-view/src/components/dialog/database/RenameDatabase.tsx:7— tools-manage/invocationlab-erd-online-view/src/components/dialog/database/RenameDatabase.tsx:7 imports antd/lib/radio/interface, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] tools-manage/invocationlab-erd-online-view/src/components/dialog/export/ExportDDL.tsx:20— tools-manage/invocationlab-erd-online-view/src/components/dialog/export/ExportDDL.tsx:20 imports antd/lib/radio/interface, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] tools-manage/invocationlab-erd-online-view/src/pages/design/export/component/ExportDDL.tsx:16— tools-manage/invocationlab-erd-online-view/src/pages/design/export/component/ExportDDL.tsx:16 imports antd/lib/radio/interface, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] tools-manage/invocationlab-erd-online-view/src/pages/design/table/component/table/TableObjectList.tsx:3— tools-manage/invocationlab-erd-online-view/src/pages/design/table/component/table/TableObjectList.tsx:3 imports @blueprintjs/core/src/common/index, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] tools-manage/invocationlab-erd-online-view/src/pages/project/group/component/GroupPermission.tsx:3— tools-manage/invocationlab-erd-online-view/src/pages/project/group/component/GroupPermission.tsx:3 imports antd/lib/checkbox/Group, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] tools-manage/invocationlab-erd-online-view/src/services/crud.ts:1— tools-manage/invocationlab-erd-online-view/src/services/crud.ts:1 imports antd/lib/table/interface, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] tools-manage/invocationlab-erd-online-view/src/store/query/useQueryStore.tsx:2— tools-manage/invocationlab-erd-online-view/src/store/query/useQueryStore.tsx:2 imports antd/lib/tree, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] tools-manage/invocationlab-rpcpostman-view/src/main.js:42— tools-manage/invocationlab-rpcpostman-view/src/main.js:42 imports element-ui/lib/locale/lang/zh-CN, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] tools-manage/invocationlab-rpcpostman-view/src/main.js:51— tools-manage/invocationlab-rpcpostman-view/src/main.js:51 imports element-ui/lib/transitions/collapse-transition, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
AC2 · Forms & labels· <Select> field component without a label · ×11
<Select> field component without a label tools-manage/invocationlab-erd-online-view/src/components/LeftContent/DesignLeftContent/component/MetaDataSearch.tsx:265— This UI-library field component has no label / aria-label / aria-labelledby / id, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id alone, wherever it is set, names nothing until a label points at it). The text inside it does not stand in for one: these compound APIs render a trigger with role="combobox" (or role="button"), and those roles take their name from the AUTHOR, not from their content — so the words on screen never reach the accessibility tree as a name. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<Select> field component without a label tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/ConstructSqlForm.tsx:311— This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<Select> field component without a label tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/ConstructSqlForm.tsx:337— This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<Select> field component without a label tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/ConstructSqlForm.tsx:371— This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<Select> field component without a label tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/ConstructSqlForm.tsx:393— This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<Select> field component without a label tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/ConstructSqlFormMongoDB.tsx:305— This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<Select> field component without a label tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/ConstructSqlFormMongoDB.tsx:331— This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<Select> field component without a label tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/ConstructSqlFormMongoDB.tsx:387— This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<Select> field component without a label tools-manage/invocationlab-erd-online-view/src/pages/design/query/index.tsx:327— This UI-library field component has no label / aria-label / aria-labelledby / id, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id alone, wherever it is set, names nothing until a label points at it). The text inside it does not stand in for one: these compound APIs render a trigger with role="combobox" (or role="button"), and those roles take their name from the AUTHOR, not from their content — so the words on screen never reach the accessibility tree as a name. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<Select> field component without a label tools-manage/invocationlab-erd-online-view/src/pages/design/query/index.tsx:351— This UI-library field component has no label / aria-label / aria-labelledby / id, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id alone, wherever it is set, names nothing until a label points at it). The text inside it does not stand in for one: these compound APIs render a trigger with role="combobox" (or role="button"), and those roles take their name from the AUTHOR, not from their content — so the words on screen never reach the accessibility tree as a name. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<Select> field component without a label tools-manage/invocationlab-erd-online-view/src/pages/design/query/index.tsx:359— This UI-library field component has no label / aria-label / aria-labelledby / id, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id alone, wherever it is set, names nothing until a label points at it). The text inside it does not stand in for one: these compound APIs render a trigger with role="combobox" (or role="button"), and those roles take their name from the AUTHOR, not from their content — so the words on screen never reach the accessibility tree as a name. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
AXH1 · Runtime security headers· Runtime security header not set · ×11
Runtime security header not set: content-security-policy — The live app's responses did not include content-security-policy (restricts the sources a page may load — mitigates XSS/injection). Observed by booting the app in-sandbox — advisory evidence for AppSec / CRA / NIS2 runtime secure-defaults. Set it at your reverse proxy or in the app.
Runtime security header not set: cross-origin-embedder-policy — The live app's responses did not include cross-origin-embedder-policy (recommended by the OWASP Secure Headers Project (value: require-corp)). Observed by booting the app in-sandbox — advisory evidence for AppSec / CRA / NIS2 runtime secure-defaults. Set it at your reverse proxy or in the app.
Runtime security header not set: cross-origin-opener-policy — The live app's responses did not include cross-origin-opener-policy (recommended by the OWASP Secure Headers Project (value: same-origin)). Observed by booting the app in-sandbox — advisory evidence for AppSec / CRA / NIS2 runtime secure-defaults. Set it at your reverse proxy or in the app.
Runtime security header not set: cross-origin-resource-policy — The live app's responses did not include cross-origin-resource-policy (recommended by the OWASP Secure Headers Project (value: same-origin)). Observed by booting the app in-sandbox — advisory evidence for AppSec / CRA / NIS2 runtime secure-defaults. Set it at your reverse proxy or in the app.
Runtime security header not set: permissions-policy — The live app's responses did not include permissions-policy (restricts powerful browser features (camera, geolocation, …)). Observed by booting the app in-sandbox — advisory evidence for AppSec / CRA / NIS2 runtime secure-defaults. Set it at your reverse proxy or in the app.
Runtime security header not set: referrer-policy — The live app's responses did not include referrer-policy (limits referrer leakage to third parties). Observed by booting the app in-sandbox — advisory evidence for AppSec / CRA / NIS2 runtime secure-defaults. Set it at your reverse proxy or in the app.
Runtime security header not set: strict-transport-security — The live app's responses did not include strict-transport-security (forces HTTPS on subsequent requests — mitigates downgrade/MITM). Observed by booting the app in-sandbox — advisory evidence for AppSec / CRA / NIS2 runtime secure-defaults. Set it at your reverse proxy or in the app.
Runtime security header not set: x-content-type-options — The live app's responses did not include x-content-type-options (stops MIME-sniffing (expects 'nosniff')). Observed by booting the app in-sandbox — advisory evidence for AppSec / CRA / NIS2 runtime secure-defaults. Set it at your reverse proxy or in the app.
Runtime security header not set: x-dns-prefetch-control — The live app's responses did not include x-dns-prefetch-control (recommended by the OWASP Secure Headers Project (value: off)). Observed by booting the app in-sandbox — advisory evidence for AppSec / CRA / NIS2 runtime secure-defaults. Set it at your reverse proxy or in the app.
Runtime security header not set: x-frame-options — The live app's responses did not include x-frame-options (blocks clickjacking via framing (or use CSP frame-ancestors)). Observed by booting the app in-sandbox — advisory evidence for AppSec / CRA / NIS2 runtime secure-defaults. Set it at your reverse proxy or in the app.
Runtime security header not set: x-permitted-cross-domain-policies — The live app's responses did not include x-permitted-cross-domain-policies (recommended by the OWASP Secure Headers Project (value: none)). Observed by booting the app in-sandbox — advisory evidence for AppSec / CRA / NIS2 runtime secure-defaults. Set it at your reverse proxy or in the app.
AC2 · Forms & labels· <Input> field component without a label · ×10
<Input> field component without a label tools-manage/invocationlab-erd-online-view/src/components/LeftContent/DesignLeftContent/component/MetaDataSearch.tsx:256— This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<Input> field component without a label tools-manage/invocationlab-erd-online-view/src/components/LeftContent/DesignLeftContent/component/MetaDataSearch.tsx:258— This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<Input> field component without a label tools-manage/invocationlab-erd-online-view/src/components/LeftContent/DesignLeftContent/component/MetaDataSearch.tsx:260— This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<Input> field component without a label tools-manage/invocationlab-erd-online-view/src/components/LeftContent/DesignLeftContent/component/MetaDataSearch.tsx:262— This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<Input> field component without a label tools-manage/invocationlab-erd-online-view/src/components/LeftContent/DesignLeftContent/index.tsx:26— This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<Input> field component without a label tools-manage/invocationlab-erd-online-view/src/components/LeftContent/QueryLeftContent/index.tsx:23— This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<Input> field component without a label tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/ConstructSqlForm.tsx:356— This UI-library field component has no label / aria-label / aria-labelledby / id at this call site, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id, even one the component sets on what it renders, names nothing until a label points at it) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<Input> field component without a label tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/ConstructSqlFormMongoDB.tsx:350— This UI-library field component has no label / aria-label / aria-labelledby / id at this call site, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id, even one the component sets on what it renders, names nothing until a label points at it) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<Input> field component without a label tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/InputContextMenu.tsx:102— This UI-library field component has no label / aria-label / aria-labelledby / id at this call site, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id, even one the component sets on what it renders, names nothing until a label points at it) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<Input> field component without a label tools-manage/invocationlab-erd-online-view/src/pages/project/group/component/AddUser.tsx:89— This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
AC4 · Keyboard semantics· Anchor without href · ×10
Anchor without href b2c-parent/b2c-scheduled/src/main/resources/templates/task-list.html:47— 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 b2c-parent/b2c-scheduled/src/main/resources/templates/task-list.html:50— 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 b2c-parent/b2c-scheduled/src/main/resources/templates/task-list.html:53— 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 tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/QueryResult.tsx:138— 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 tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/QueryResult.tsx:150— 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 tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/QueryResult.tsx:164— 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 tools-manage/invocationlab-erd-online-view/src/pages/login/index.tsx:227— 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 tools-manage/invocationlab-rpcpostman-view/src/components/Breadcrumb/index.vue:6— 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 tools-manage/invocationlab-rpcpostman-view/src/views/layout/components/Navbar.vue:10— 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 tools-manage/invocationlab-rpcpostman-view/src/views/layout/components/Navbar.vue:16— 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.
D30 · Dependency Vulnerabilities· Medium vulnerability · ×10
Duplicated block (7 lines × 2) tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/redis/impl/SetRedisStrategy.kt:151— tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/redis/impl/SetRedisStrategy.kt:151-157 | tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/redis/impl/ZSetRedisStrategy.kt:105-111 — before extracting anything, compare `tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/redis/impl/SetRedisStrategy.kt` and `tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/redis/impl/ZSetRedisStrategy.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/redis/impl/SetRedisStrategy.kt:151` 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 (7 lines × 2) tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/service/impl/MySqlDbServiceImpl.kt:26— tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/service/impl/MySqlDbServiceImpl.kt:26-32 | tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/service/impl/PostgreSqlDbServiceImpl.kt:50-56 — 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) tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/handler/WebSocketHandler.kt:53— tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/handler/WebSocketHandler.kt:53-59 | tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/handler/WebSocketHandler.kt:63-69 — both copies are in the same file, so extract the 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 `tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/handler/WebSocketHandler.kt: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 (7 lines × 2) tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/AbstractDbService.java:1081— tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/AbstractDbService.java:1081-1087 | tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/MongoDbServiceImpl.java:765-771 — 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) tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/util/RedisUtils.java:42— tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/util/RedisUtils.java:42-49 | tools-manage/tools-manage-admin/src/main/java/org/javamaster/spring/tools/manage/util/RedisUtils.java:38-44 — before extracting anything, compare `tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/util/RedisUtils.java` and `tools-manage/tools-manage-admin/src/main/java/org/javamaster/spring/tools/manage/util/RedisUtils.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 34 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. Note first that the copies are not typed on the same thing: `ConnectionVo` names `org.javamaster.invocationlab.admin.model.redis.ConnectionVo` in one and `org.javamaster.spring.tools.manage.model.ConnectionVo` 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.
Duplicated block (7 lines × 2) tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/util/RedisUtils.java:82— tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/util/RedisUtils.java:82-88 | tools-manage/tools-manage-admin/src/main/java/org/javamaster/spring/tools/manage/util/RedisUtils.java:78-84 — before extracting anything, compare `tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/util/RedisUtils.java` and `tools-manage/tools-manage-admin/src/main/java/org/javamaster/spring/tools/manage/util/RedisUtils.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 34 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (7 lines × 2) tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/redis/impl/SetRedisDataTypeService.java:145— tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/redis/impl/SetRedisDataTypeService.java:145-151 | tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/redis/impl/ZSetRedisDataTypeService.java:97-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. 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) tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/serializer/BigDecimalToJsonSerializer.java:23— tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/serializer/BigDecimalToJsonSerializer.java:23-29 | tools-manage/tools-manage-admin/src/main/java/org/javamaster/spring/tools/manage/serializer/BigDecimalJsonSerializer.java:20-26 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (7 lines × 2) b2c-parent/b2c-bytecode/src/main/java/org/javamaster/b2c/bytecode/attribute/LocalVariableTableAttribute.java:63— b2c-parent/b2c-bytecode/src/main/java/org/javamaster/b2c/bytecode/attribute/LocalVariableTableAttribute.java:63-69 | b2c-parent/b2c-bytecode/src/main/java/org/javamaster/b2c/bytecode/attribute/LocalVariableTypeTableAttribute.java:63-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.
Duplicated block (7 lines × 2) b2c-parent/b2c-core/src/script/start.py:24— b2c-parent/b2c-core/src/script/start.py:24-30 | REDACTED:66-72 — 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.
FileTooLong: webapp/index.js spring-embed-arthas/src/main/webapp/index.js— FileTooLong — 15322 significant lines (blank, comment-only and punctuation-only lines excluded; the length bar is tripled for a single-responsibility module of 4 or fewer top-level units). The bar is 1500 significant lines; this is 13822 over it, 10.21× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: webapp/vue.js spring-embed-arthas/src/main/webapp/vue.js— FileTooLong — 7082 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 6582 over it, 14.16× 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: relation/g6.js tools-manage/invocationlab-erd-online-view/src/pages/design/relation/g6.js— FileTooLong — 1149 significant lines (blank, comment-only and punctuation-only lines excluded), about 99% of them inside a single declaration: G6Relation (18-1582). The bar is 500 significant lines; this is 649 over it, 2.30× 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: impl/AbstractDbService.kt tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/service/impl/AbstractDbService.kt— FileTooLong — 783 significant lines (blank, comment-only and punctuation-only lines excluded), about 92% of them inside a single declaration: AbstractDbService (69-1108). The bar is 500 significant lines; this is 283 over it, 1.57× 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: impl/AbstractDbService.java tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/AbstractDbService.java— FileTooLong — 779 significant lines (blank, comment-only and punctuation-only lines excluded), about 88% of them inside a single declaration: AbstractDbService (100-1100). The bar is 500 significant lines; this is 279 over it, 1.56× 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: version/useVersionStore.tsx tools-manage/invocationlab-erd-online-view/src/store/version/useVersionStore.tsx— FileTooLong — 769 significant lines (blank, comment-only and punctuation-only lines excluded), about 91% of them inside a single declaration: useVersionStore (81-1046). The bar is 500 significant lines; this is 269 over it, 1.54× 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: utils/json2code.ts tools-manage/invocationlab-erd-online-view/src/utils/json2code.ts— FileTooLong — 642 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 142 over it, 1.28× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: impl/MongoDbServiceImpl.java tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/MongoDbServiceImpl.java— FileTooLong — 552 significant lines (blank, comment-only and punctuation-only lines excluded), about 88% of them inside a single declaration: MongoDbServiceImpl (78-789). The bar is 500 significant lines; this is 52 over it, 1.10× 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: impl/ErdOnlineProjectServiceImpl.java tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/ErdOnlineProjectServiceImpl.java— FileTooLong — 517 significant lines (blank, comment-only and punctuation-only lines excluded), about 82% of them inside a single declaration: ErdOnlineProjectServiceImpl (102-679). The bar is 500 significant lines; this is 17 over it, 1.03× 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.
AC3 · Page structure· Page without a main landmark · ×8
Page without a main landmark b2c-parent/b2c-scheduled/src/main/resources/templates/task-list.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 spring-embed-arthas/src/main/webapp/arthas-test.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 spring-embed-arthas/src/main/webapp/table-column-drag.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 spring-embed-arthas/src/main/webapp/vue.js:11887— 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 REDACTED: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 spring-lifecycle/src/main/webapp/WEB-INF/views/welcome.jsp:3— 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 tools-manage/invocationlab-admin-21/src/main/resources/erd.vm:1— 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 tools-manage/invocationlab-admin/src/main/resources/erd.vm:1— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
ClassTooLong: G6Relation tools-manage/invocationlab-erd-online-view/src/pages/design/relation/g6.js:18— ClassTooLong — 1136 significant lines (blank, comment-only and punctuation-only lines excluded), 47 methods. The bar is 400 significant lines; this is 736 over it, 2.84× 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: AbstractDbService tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/service/impl/AbstractDbService.kt:69— ClassTooLong — 718 significant lines (blank, comment-only and punctuation-only lines excluded), 49 methods. The bar is 400 significant lines; this is 318 over it, 1.80× 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: useVersionStore tools-manage/invocationlab-erd-online-view/src/store/version/useVersionStore.tsx:1— ClassTooLong — 697 significant lines (blank, comment-only and punctuation-only lines excluded), 3 methods. The bar is 400 significant lines; this is 297 over it, 1.74× 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: AbstractDbService tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/AbstractDbService.java:100— ClassTooLong — 684 significant lines (blank, comment-only and punctuation-only lines excluded), 51 methods. The bar is 400 significant lines; this is 284 over it, 1.71× 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: MongoDbServiceImpl tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/MongoDbServiceImpl.java:78— ClassTooLong — 483 significant lines (blank, comment-only and punctuation-only lines excluded), 27 methods. The bar is 400 significant lines; this is 83 over it, 1.21× 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: MenusExample b2c-parent/b2c-mybatis/src/main/java/org/javamaster/b2c/mybatis/entity/MenusExample.java:12— ClassTooLong — 452 significant lines (blank, comment-only and punctuation-only lines excluded), 11 methods. The bar is 400 significant lines; this is 52 over it, 1.13× 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: ErdOnlineProjectServiceImpl tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/ErdOnlineProjectServiceImpl.java:102— ClassTooLong — 423 significant lines (blank, comment-only and punctuation-only lines excluded), 35 methods. The bar is 400 significant lines; this is 23 over it, 1.06× 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: ErdOnlineProjectServiceImpl tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/service/impl/ErdOnlineProjectServiceImpl.kt:69— ClassTooLong — 414 significant lines (blank, comment-only and punctuation-only lines excluded), 32 methods. The bar is 400 significant lines; this is 14 over it, 1.04× 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.
Outbound HTTP without resilience REDACTED:57— `urlopen(` 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 spring-swagger/src/main/java/org/javamaster/spring/swagger/feign/UserFeignService.java:16— `@FeignClient` 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 tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/feign/SsoFeignService.kt:9— `@FeignClient` 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 tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/service/maven/Maven.kt:100— `.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 tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/util/FileUtils.kt:17— `.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 tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/feign/SsoFeignService.java:13— `@FeignClient` 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 tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/maven/Maven.java:117— `.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 tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/util/FileUtils.java:23— `.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.
(anonymous) (cognitive 16) spring-embed-arthas/src/main/webapp/index.js:730— (anonymous) has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 8, if/else 4 (6 pts), loops 1, ternaries 1 (nesting depth added 2). None of this is in the body itself: all 16 points belong to 5 function items inside it that branch (t, m, n, …). 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.
(anonymous) (cognitive 16) spring-embed-arthas/src/main/webapp/index.js:966— (anonymous) has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 9, ternaries 7. Most of this is not in the body itself: 4 of the 16 points are its own statements and the rest belongs to 5 function items inside it that branch (a function literal at line 982, a function literal at line 977, n, …). 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.
(anonymous) (cognitive 16) spring-embed-arthas/src/main/webapp/index.js:2611— (anonymous) has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 8, ternaries 6 (7 pts), loops 1 (nesting depth added 1). Most of this is not in the body itself: 2 of the 16 points are its own statements and the rest belongs to 5 function items inside it that branch ((anonymous)::t, a function literal at line 2622, a function literal at line 2616, …). 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.
(anonymous) (cognitive 16) spring-embed-arthas/src/main/webapp/index.js:3508— (anonymous) has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 7 (9 pts), boolean chains 6, if/else 1 (nesting depth added 2). None of this is in the body itself: all 16 points belong to 8 function items inside it that branch (render, update, n, …). 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.
(anonymous) (cognitive 16) spring-embed-arthas/src/main/webapp/index.js:6833— (anonymous) has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 11, ternaries 5. None of this is in the body itself: all 16 points belong to 2 function items inside it that branch (n, getEventType). 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.
(anonymous) (cognitive 16) spring-embed-arthas/src/main/webapp/index.js:15064— (anonymous) has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 10, boolean chains 5, if/else 1. None of this is in the body itself: all 16 points belong to 10 function items inside it that branch (a function literal at line 15071, n::(anonymous)::keydown, n, …). 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.
(anonymous) (cognitive 16) REDACTED:121— (anonymous) has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 4 (nesting depth added 5). Of this number, 13 points are the body's own statements and 3 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.
D4 · Code Duplication· Edited copy of a member (11 corresponding lines) · ×6
Edited copy of a member (11 corresponding lines) tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/controller/RpcPostmanServiceCreationController.java:96— tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/controller/RpcPostmanServiceCreationController.java:96-112 | tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/controller/RpcPostmanServiceCreationController.java:144-154 — 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) b2c-parent/b2c-bytecode/src/main/java/org/javamaster/b2c/bytecode/FieldInfo.java:55— b2c-parent/b2c-bytecode/src/main/java/org/javamaster/b2c/bytecode/FieldInfo.java:55-65 | b2c-parent/b2c-bytecode/src/main/java/org/javamaster/b2c/bytecode/MethodInfo.java:47-57 — 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) tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/util/RedisUtils.java:58— tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/util/RedisUtils.java:58-68 | tools-manage/tools-manage-admin/src/main/java/org/javamaster/spring/tools/manage/util/RedisUtils.java:54-64 — 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) tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/controller/RpcPostmanServiceCreationController.kt:94— tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/controller/RpcPostmanServiceCreationController.kt:94-110 | tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/controller/RpcPostmanServiceCreationController.kt:148-158 — 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) tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/enums/ProjectType.java:18— tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/enums/ProjectType.java:18-28 | tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/enums/RegisterCenterType.java:18-28 — 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) tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/enums/ProjectType.kt:14— tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/enums/ProjectType.kt:14-24 | tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/enums/RegisterCenterType.kt:14-24 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (10 corresponding lines) · ×6
Edited copy of a member (10 corresponding lines) REDACTED:66— REDACTED:66-75 | REDACTED:89-100 — 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) tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/MySqlDbServiceImpl.java:22— tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/MySqlDbServiceImpl.java:22-31 | tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/PostgreSqlDbServiceImpl.java:26-36 — 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) tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/RedisServiceImpl.java:60— tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/RedisServiceImpl.java:60-76 | tools-manage/tools-manage-admin/src/main/java/org/javamaster/spring/tools/manage/service/impl/RedisServiceImpl.java:468-477 — 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) tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/RedisServiceImpl.java:79— tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/RedisServiceImpl.java:79-89 | tools-manage/tools-manage-admin/src/main/java/org/javamaster/spring/tools/manage/service/impl/RedisServiceImpl.java:65-74 — 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) tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/service/impl/MySqlDbServiceImpl.kt:15— tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/service/impl/MySqlDbServiceImpl.kt:15-24 | tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/service/impl/PostgreSqlDbServiceImpl.kt:18-28 — 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) tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/RedisServiceImpl.java:92— tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/RedisServiceImpl.java:92-103 | tools-manage/tools-manage-admin/src/main/java/org/javamaster/spring/tools/manage/service/impl/RedisServiceImpl.java:77-86 — 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.
Duplicated block (5 lines × 2) tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/serializer/BigIntegerToJsonSerializer.kt:30— tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/serializer/BigIntegerToJsonSerializer.kt:30-34 | tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/serializer/LongToJsonSerializer.kt:29-33 — 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 `tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/serializer/BigIntegerToJsonSerializer.kt:30` 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 first that the copies are not typed on the same thing: the declarations holding them bind `value` to `BigInteger?` in one and `Long?` 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) b2c-parent/b2c-core/src/main/java/org/javamaster/b2c/core/config/DatabaseConfig.java:80— b2c-parent/b2c-core/src/main/java/org/javamaster/b2c/core/config/DatabaseConfig.java:80-84 | b2c-parent/b2c-core/src/main/java/org/javamaster/b2c/core/jackson/EnumBaseModule.java:23-27 — 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 `b2c-parent/b2c-core/src/main/java/org/javamaster/b2c/core/config/DatabaseConfig.java:80` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/config/MvcConfig.java:101— tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/config/MvcConfig.java:101-106 | tools-manage/tools-manage-admin/src/main/java/org/javamaster/spring/tools/manage/config/RedisConfig.java:83-87 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (5 lines × 2) tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/redis/impl/SetRedisDataTypeService.java:108— tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/redis/impl/SetRedisDataTypeService.java:108-113 | tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/redis/impl/StringRedisDataTypeService.java:77-81 — 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 (5 lines × 2) tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/serializer/BigIntegerToJsonSerializer.java:32— tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/serializer/BigIntegerToJsonSerializer.java:32-36 | tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/serializer/LongToJsonSerializer.java:31-35 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Note first that the copies are not typed on the same thing: the declarations holding them bind `value` to `BigInteger` in one and `Long` 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) REDACTED:198— REDACTED:198-202 | REDACTED:239-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 `REDACTED:198` 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, `REDACTED:203` calls `getElementsByTagName`, `getLength` and `REDACTED:244` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (8 lines × 2) tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/service/impl/RedisServiceImpl.kt:228— tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/service/impl/RedisServiceImpl.kt:228-235 | tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/service/impl/RedisServiceImpl.kt:263-270 — both copies are in the same file, so extract the 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) tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/redis/RedisHelper.java:88— tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/redis/RedisHelper.java:88-95 | tools-manage/tools-manage-admin/src/main/java/org/javamaster/spring/tools/manage/service/impl/RedisServiceImpl.java:138-145 — 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 `tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/redis/RedisHelper.java:88` 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: `ScanParams` names `redis.clients.jedis.ScanParams` in one and `redis.clients.jedis.params.ScanParams` 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.
Duplicated block (8 lines × 2) tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/RedisServiceImpl.java:239— tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/RedisServiceImpl.java:239-246 | tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/RedisServiceImpl.java:275-282 — both copies are in the same file, so extract the 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) tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/handler/WebSocketHandler.java:59— tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/handler/WebSocketHandler.java:59-66 | tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/handler/WebSocketHandler.java:71-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. 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 × 2) tools-manage/tools-manage-admin/src/main/java/org/javamaster/spring/tools/manage/service/impl/RedisServiceImpl.java:380— tools-manage/tools-manage-admin/src/main/java/org/javamaster/spring/tools/manage/service/impl/RedisServiceImpl.java:380-387 | tools-manage/tools-manage-admin/src/main/java/org/javamaster/spring/tools/manage/service/impl/RedisServiceImpl.java:442-449 — both copies are in the same file, so extract the 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 `tools-manage/tools-manage-admin/src/main/java/org/javamaster/spring/tools/manage/service/impl/RedisServiceImpl.java:380` 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) tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/config/MvcConfig.java:76— tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/config/MvcConfig.java:76-83 | tools-manage/tools-manage-admin/src/main/java/org/javamaster/spring/tools/manage/config/MvcConfig.java:28-35 — 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.
AC3 · Page structure· Data table has no header cells · ×5
Data table has no header cells b2c-parent/b2c-scheduled/src/main/resources/templates/task-list.html:28— 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 tools-manage/invocationlab-admin-21/src/main/resources/erd.vm:130— 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 tools-manage/invocationlab-admin-21/src/main/resources/erd.vm:161— 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 tools-manage/invocationlab-admin/src/main/resources/erd.vm:129— 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 tools-manage/invocationlab-admin/src/main/resources/erd.vm:160— 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).
Stateful singleton: DubboInvoker tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/service/invocation/impl/DubboInvoker.kt:28— `DubboInvoker` is a singleton (@Service: the container shares one instance across every request thread) but mutates instance state outside any lock (cachedReference; e.g. `cachedReference` in `getOrCreateService` at line 51).
Stateful singleton: DynamicPrintTask b2c-parent/b2c-scheduled/src/main/java/org/javamaster/b2c/scheduled/task/DynamicPrintTask.java:12— `DynamicPrintTask` is a singleton (@Component: the container shares one instance across every request thread) but mutates instance state outside any lock (i; e.g. `i` in `execute` at line 19).
Stateful singleton: DynamicPrintTask1 b2c-parent/b2c-scheduled/src/main/java/org/javamaster/b2c/scheduled/task/DynamicPrintTask1.java:12— `DynamicPrintTask1` is a singleton (@Component: the container shares one instance across every request thread) but mutates instance state outside any lock (i; e.g. `i` in `execute` at line 19).
Stateful singleton: DynamicPrintTask2 b2c-parent/b2c-scheduled/src/main/java/org/javamaster/b2c/scheduled/task/DynamicPrintTask2.java:12— `DynamicPrintTask2` is a singleton (@Component: the container shares one instance across every request thread) but mutates instance state outside any lock (i; e.g. `i` in `execute` at line 19).
Stateful singleton: DubboInvoker tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/invocation/impl/DubboInvoker.java:30— `DubboInvoker` is a singleton (@Service: the container shares one instance across every request thread) but mutates instance state outside any lock (cachedReference; e.g. `cachedReference` in `getOrCreateService` at line 53).
(anonymous) (cyclomatic 16) spring-embed-arthas/src/main/webapp/index.js:4159— (anonymous) has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 14 function items inside it that branch (visible, destroyed, n, …). 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: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
(anonymous) (cyclomatic 16) spring-embed-arthas/src/main/webapp/index.js:5325— (anonymous) has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 14 function items inside it that branch (itemStyle, n, onMouseEnter, …). 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 file is where this pass's cyclomatic complexity CONCENTRATES: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
(anonymous) (cyclomatic 16) spring-embed-arthas/src/main/webapp/index.js:5894— (anonymous) has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 9 function items inside it that branch (handleKeydown, radioGroupSize, s, …). 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: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
(anonymous) (cyclomatic 16) spring-embed-arthas/src/main/webapp/index.js:6510— (anonymous) has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 2 function items inside it that branch (n, n::keydown). 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 file is where this pass's cyclomatic complexity CONCENTRATES: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
(anonymous) (cyclomatic 16) spring-embed-arthas/src/main/webapp/index.js:14012— (anonymous) has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 16 function items inside it that branch (keydown, typeClass, horizontalClass, …). 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: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
TodoComment tools-manage/invocationlab-erd-online-view/src/store/version/useVersionStore.tsx:555— // 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 tools-manage/invocationlab-erd-online-view/src/store/version/useVersionStore.tsx:805— // 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 tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/MongoDbServiceImpl.java:634— // 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 b2c-parent/b2c-bytecode/src/main/java/org/javamaster/b2c/bytecode/tablestructure/ConstantInvokeDynamicInfo.java:22— // 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 b2c-parent/b2c-bytecode/src/main/java/org/javamaster/b2c/bytecode/tablestructure/ConstantMethodHandleInfo.java:22— // 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.
(anonymous) (cognitive 21) spring-embed-arthas/src/main/webapp/index.js:1551— (anonymous) has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (9 pts), loops 3 (7 pts), boolean chains 5 (nesting depth added 7). None of this is in the body itself: all 21 points belong to 4 function items inside it that branch (a function literal at line 1560, i, a function literal at line 1553, …). 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.
(anonymous) (cognitive 21) spring-embed-arthas/src/main/webapp/index.js:7993— (anonymous) has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 9 (10 pts), boolean chains 5, if/else 4, loops 1 (2 pts) (nesting depth added 2). None of this is in the body itself: all 21 points belong to 17 function items inside it that branch (isCellHidden, render, a function literal at line 8012, …). 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.
(anonymous) (cognitive 21) spring-embed-arthas/src/main/webapp/index.js:11387— (anonymous) has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 11, boolean chains 9, if/else 1. Most of this is not in the body itself: 3 of the 21 points are its own statements and the rest belongs to 10 function items inside it that branch (Dialog, a function literal at line 11392, trapFocus, …). 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.
(anonymous) (cognitive 21) spring-embed-arthas/src/main/webapp/index.js:16155— (anonymous) has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 12, ternaries 8, if/else 1. None of this is in the body itself: all 21 points belong to 7 function items inside it that branch (processIndex, translateItem, calculateTranslate, …). 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.
(anonymous) (cognitive 21) spring-embed-arthas/src/main/webapp/index.js:16917— (anonymous) has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 14, ternaries 5, if/else 2. None of this is in the body itself: all 21 points belong to 17 function items inside it that branch (colorSize, value, n, …). 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.
(anonymous) (cognitive 17) spring-embed-arthas/src/main/webapp/index.js:1101— (anonymous) has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 3 (6 pts), boolean chains 5, loops 3 (4 pts), if/else 2 (nesting depth added 4). None of this is in the body itself: all 17 points belong to 8 function items inside it that branch (onScrollableChange, onColumnsChange, tableLayout, …). 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.
(anonymous) (cognitive 17) spring-embed-arthas/src/main/webapp/index.js:7843— (anonymous) has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 12, ternaries 5. None of this is in the body itself: all 17 points belong to 20 function items inside it that branch (set, n, handleSelect, …). 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.
(anonymous) (cognitive 17) spring-embed-arthas/src/main/webapp/index.js:11992— (anonymous) has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (8 pts), boolean chains 5, loops 2 (4 pts) (nesting depth added 6). None of this is in the body itself: all 17 points belong to 2 function items inside it that branch (a function literal at line 11995, exports). 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.
(anonymous) (cognitive 17) spring-embed-arthas/src/main/webapp/index.js:13971— (anonymous) has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 11, loops 2 (3 pts), if/else 2, ternaries 1 (nesting depth added 1). None of this is in the body itself: all 17 points belong to 10 function items inside it that branch (close, e, n, …). 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.
(anonymous) (cognitive 17) spring-embed-arthas/src/main/webapp/index.js:15853— (anonymous) has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 12, boolean chains 5. None of this is in the body itself: all 17 points belong to 16 function items inside it that branch (style, updateStatus, calcProgress, …). 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.
D4 · Code Duplication· Edited copy of a member (13 corresponding lines) · ×5
Edited copy of a member (13 corresponding lines) tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/creation/impl/DubboCreator.java:65— tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/creation/impl/DubboCreator.java:65-77 | tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/creation/impl/EurekaCreator.java:82-97 — 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) tools-manage/tools-manage-admin/src/main/java/org/javamaster/spring/tools/manage/service/impl/RedisServiceImpl.java:379— tools-manage/tools-manage-admin/src/main/java/org/javamaster/spring/tools/manage/service/impl/RedisServiceImpl.java:379-391 | tools-manage/tools-manage-admin/src/main/java/org/javamaster/spring/tools/manage/service/impl/RedisServiceImpl.java:441-453 — 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) tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/service/creation/impl/DubboCreator.kt:42— tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/service/creation/impl/DubboCreator.kt:42-54 | tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/service/creation/impl/EurekaCreator.kt:66-81 — 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) tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/redis/RedisHelper.java:175— tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/redis/RedisHelper.java:175-187 | tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/redis/RedisHelper.java:189-202 — 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) tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/redis/RedisHelper.kt:143— tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/redis/RedisHelper.kt:143-155 | tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/redis/RedisHelper.kt:157-170 — 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.
Duplicated block (11 lines × 2) b2c-parent/b2c-core/src/main/java/org/javamaster/b2c/core/enums/EnumBase.java:23— b2c-parent/b2c-core/src/main/java/org/javamaster/b2c/core/enums/EnumBase.java:23-33 | spring-swagger/src/main/java/org/javamaster/spring/swagger/enums/EnumBase.java:20-30 — before extracting anything, compare `b2c-parent/b2c-core/src/main/java/org/javamaster/b2c/core/enums/EnumBase.java` and `spring-swagger/src/main/java/org/javamaster/spring/swagger/enums/EnumBase.java` as WHOLE FILES: 86% 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 (11 lines × 2) spring-lifecycle/src/main/java/org/javamaster/spring/lifecycle/controller/PortalController.java:27— spring-lifecycle/src/main/java/org/javamaster/spring/lifecycle/controller/PortalController.java:27-37 | springboot-lifecycle/src/main/java/org/javamaster/springboot/lifecycle/controller/PortalController.java:29-39 — before extracting anything, compare `spring-lifecycle/src/main/java/org/javamaster/spring/lifecycle/controller/PortalController.java` and `springboot-lifecycle/src/main/java/org/javamaster/springboot/lifecycle/controller/PortalController.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 (11 lines × 2) tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/AbstractDbService.java:757— tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/AbstractDbService.java:757-767 | tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/MongoDbServiceImpl.java:676-686 — 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 `tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/AbstractDbService.java:757` 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) tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/AbstractDbService.java:1089— tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/AbstractDbService.java:1089-1099 | tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/MongoDbServiceImpl.java:773-783 — 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 `tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/AbstractDbService.java:1089` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) mybatis-generator/src/main/java/org/javamaster/mybatis/generator/plugin/MybatisGeneratorPlugin.java:169— mybatis-generator/src/main/java/org/javamaster/mybatis/generator/plugin/MybatisGeneratorPlugin.java:169-179 | mybatis-generator/src/main/java/org/javamaster/mybatis/generator/plugin/TkMapperPlugin.java:28-38 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. 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.
Swallowed exception (caught, then discarded) tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/util/AesUtils.kt:21— `catch (e: Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/util/AesUtils.kt:36— `catch (e: Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/util/AesUtils.java:24— `catch (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/util/AesUtils.java:38— `catch (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) b2c-parent/b2c-bytecode/src/main/java/org/javamaster/b2c/bytecode/model/PersonCopy.java:36— `catch (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
AC2 · Forms & labels· <TextArea> field component without a label · ×4
<TextArea> field component without a label tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/AesContextMenu.tsx:107— This UI-library field component has no label / aria-label / aria-labelledby / id at this call site, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id, even one the component sets on what it renders, names nothing until a label points at it) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<TextArea> field component without a label tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/AesContextMenu.tsx:113— This UI-library field component has no label / aria-label / aria-labelledby / id at this call site, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id, even one the component sets on what it renders, names nothing until a label points at it) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<TextArea> field component without a label tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/ConstructSqlForm.tsx:464— This UI-library field component has no label / aria-label / aria-labelledby / id at this call site, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id, even one the component sets on what it renders, names nothing until a label points at it) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<TextArea> field component without a label tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/ConstructSqlFormMongoDB.tsx:461— This UI-library field component has no label / aria-label / aria-labelledby / id at this call site, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id, even one the component sets on what it renders, names nothing until a label points at it) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
(anonymous) (cyclomatic 22) spring-embed-arthas/src/main/webapp/index.js:2566— (anonymous) has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 1 of the 22 points is its own statement and the rest belongs to 13 function items inside it that branch ((anonymous)::r, (anonymous)::e, (anonymous)::i, …). 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: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
(anonymous) (cyclomatic 22) spring-embed-arthas/src/main/webapp/index.js:4271— (anonymous) has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 1 of the 22 points is its own statement and the rest belongs to 21 function items inside it that branch (highlight, handleKeyEnter, suggestionVisible, …). 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: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
(anonymous) (cyclomatic 22) spring-embed-arthas/src/main/webapp/index.js:11607— (anonymous) has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 1 of the 22 points is its own statement and the rest belongs to 22 function items inside it that branch (validate, clearValidate, a function literal at line 11679, …). 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: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
(anonymous) (cyclomatic 22) spring-embed-arthas/src/main/webapp/index.js:16917— (anonymous) has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 1 of the 22 points is its own statement and the rest belongs to 17 function items inside it that branch (colorSize, value, n, …). 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: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
(anonymous) (cyclomatic 17) spring-embed-arthas/src/main/webapp/index.js:966— (anonymous) has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 5 of the 17 points are its own statements and the rest belongs to 5 function items inside it that branch (a function literal at line 982, a function literal at line 977, n, …). 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: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
(anonymous) (cyclomatic 17) spring-embed-arthas/src/main/webapp/index.js:13971— (anonymous) has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 1 of the 17 points is its own statement and the rest belongs to 10 function items inside it that branch (e, close, n, …). 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: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
(anonymous) (cyclomatic 17) spring-embed-arthas/src/main/webapp/index.js:14683— (anonymous) 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 8 function items inside it that branch (a function literal at line 14688, gutter, a function literal at line 14713, …). 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: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
(anonymous) (cyclomatic 17) spring-embed-arthas/src/main/webapp/index.js:15064— (anonymous) has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 1 of the 17 points is its own statement and the rest belongs to 10 function items inside it that branch (a function literal at line 15071, n::(anonymous)::keydown, n, …). 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: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
vue.createPatchFunction::hydrate (cognitive 75) spring-embed-arthas/src/main/webapp/vue.js:6354— vue.createPatchFunction::hydrate has cognitive complexity 75 (threshold 15). Drivers by points: if/else 20 (57 pts), boolean chains 10, loops 2 (8 pts) (nesting depth added 43). 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 shape REPEATS in the file: 3 other methods here (vue.createPatchFunction::createElm, vue.createPatchFunction::updateChildren, vue.createPatchFunction::patchVnode) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
vue.createPatchFunction::patchVnode (cognitive 37) spring-embed-arthas/src/main/webapp/vue.js:6259— vue.createPatchFunction::patchVnode has cognitive complexity 37 (threshold 15). Drivers by points: if/else 19 (27 pts), boolean chains 8, 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. This shape REPEATS in the file: 3 other methods here (vue.createPatchFunction::createElm, vue.createPatchFunction::updateChildren, vue.createPatchFunction::hydrate) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
vue.createPatchFunction::updateChildren (cognitive 27) spring-embed-arthas/src/main/webapp/vue.js:6162— vue.createPatchFunction::updateChildren has cognitive complexity 27 (threshold 15). Drivers by points: if/else 14 (22 pts), boolean chains 4, 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 shape REPEATS in the file: 3 other methods here (vue.createPatchFunction::createElm, vue.createPatchFunction::patchVnode, vue.createPatchFunction::hydrate) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
vue.createPatchFunction::createElm (cognitive 16) spring-embed-arthas/src/main/webapp/vue.js:5901— vue.createPatchFunction::createElm has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 3 (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. This shape REPEATS in the file: 3 other methods here (vue.createPatchFunction::updateChildren, vue.createPatchFunction::patchVnode, vue.createPatchFunction::hydrate) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
(anonymous) (cognitive 25) spring-embed-arthas/src/main/webapp/index.js:1047— (anonymous) has cognitive complexity 25 (threshold 15). Drivers by points: boolean chains 8, if/else 5 (7 pts), ternaries 4 (5 pts), loops 3, error handling 1, match/switch 1 (nesting depth added 3). Most of this is not in the body itself: 2 of the 25 points are its own statements and the rest belongs to 5 function items inside it that branch (isFocusable, triggerEvent, focusFirstDescendant, …). 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.
(anonymous) (cognitive 25) spring-embed-arthas/src/main/webapp/index.js:10844— (anonymous) has cognitive complexity 25 (threshold 15). Drivers by points: boolean chains 12, ternaries 11, if/else 2. None of this is in the body itself: all 25 points belong to 25 function items inside it that branch (amPmMode, handleKeydown, value, …). 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.
(anonymous) (cognitive 25) spring-embed-arthas/src/main/webapp/index.js:12643— (anonymous) has cognitive complexity 25 (threshold 15). Drivers by points: boolean chains 16, ternaries 4 (5 pts), if/else 4 (nesting depth added 1). None of this is in the body itself: all 25 points belong to 23 function items inside it that branch (setCurrentName, calcPaneInstances, render, …). 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.
(anonymous) (cognitive 25) spring-embed-arthas/src/main/webapp/index.js:13654— (anonymous) has cognitive complexity 25 (threshold 15). Drivers by points: boolean chains 19, ternaries 6. None of this is in the body itself: all 25 points belong to 23 function items inside it that branch (created, handleClick, n, …). 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.
(anonymous) (cognitive 19) spring-embed-arthas/src/main/webapp/index.js:820— (anonymous) has cognitive complexity 19 (threshold 15). Drivers by points: if/else 4 (9 pts), boolean chains 6, ternaries 2 (3 pts), loops 1 (nesting depth added 6). None of this is in the body itself: all 19 points belong to 5 function items inside it that branch (o, s, removeResizeListener, …). 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.
(anonymous) (cognitive 19) spring-embed-arthas/src/main/webapp/index.js:2566— (anonymous) has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 10, ternaries 8, if/else 1. None of this is in the body itself: all 19 points belong to 13 function items inside it that branch ((anonymous)::r, a function literal at line 2585, a function literal at line 2568, …). 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.
(anonymous) (cognitive 19) spring-embed-arthas/src/main/webapp/index.js:5972— (anonymous) has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 13, ternaries 3, if/else 1 (2 pts), loops 1 (nesting depth added 1). None of this is in the body itself: all 19 points belong to 12 function items inside it that branch (activeStyle, _radioGroup, size, …). 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.
(anonymous) (cognitive 19) spring-embed-arthas/src/main/webapp/index.js:12287— (anonymous) has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 13, ternaries 3, if/else 2, error handling 1. None of this is in the body itself: all 19 points belong to 12 function items inside it that branch (n, regexp, date, …). 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.
(anonymous) (cognitive 18) spring-embed-arthas/src/main/webapp/index.js:466— (anonymous) has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 11, ternaries 4, if/else 1 (2 pts), loops 1 (nesting depth added 1). Most of this is not in the body itself: 2 of the 18 points are its own statements and the rest belongs to 9 function items inside it that branch (a function literal at line 470, unbind, r, …). 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.
(anonymous) (cognitive 18) spring-embed-arthas/src/main/webapp/index.js:11607— (anonymous) has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 10, ternaries 5, if/else 3. None of this is in the body itself: all 18 points belong to 22 function items inside it that branch (clearValidate, validate, s, …). 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.
(anonymous) (cognitive 18) spring-embed-arthas/src/main/webapp/index.js:12173— (anonymous) has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (11 pts), ternaries 2 (4 pts), boolean chains 3 (nesting depth added 6). Most of this is not in the body itself: 1 of the 18 points is its own statement and the rest belongs to 6 function items inside it that branch (d, h, f, …). 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.
(anonymous) (cognitive 18) tools-manage/invocationlab-rpcpostman-view/src/utils/formatting.js:71— (anonymous) has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (10 pts), boolean chains 4, loops 3 (4 pts) (nesting depth added 7). Of this number, 17 points are the body's own statements and 1 belongs 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.
D4 · Code Duplication· Edited copy of a member (8 corresponding lines) · ×4
Edited copy of a member (8 corresponding lines) b2c-parent/b2c-core/src/main/java/org/javamaster/b2c/core/handler/LoginHandler.java:36— b2c-parent/b2c-core/src/main/java/org/javamaster/b2c/core/handler/LoginHandler.java:36-43 | b2c-parent/b2c-core/src/main/java/org/javamaster/b2c/core/handler/LoginHandler.java:46-54 — 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) tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/util/RedisUtils.java:81— tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/util/RedisUtils.java:81-88 | tools-manage/tools-manage-admin/src/main/java/org/javamaster/spring/tools/manage/util/RedisUtils.java:77-84 — 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) tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/redis/impl/ListRedisDataTypeService.java:63— tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/redis/impl/ListRedisDataTypeService.java:63-72 | tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/redis/impl/SetRedisDataTypeService.java:63-70 — 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) tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/redis/impl/HashRedisStrategy.kt:146— tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/redis/impl/HashRedisStrategy.kt:146-154 | tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/redis/impl/ZSetRedisStrategy.kt:74-81 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (9 corresponding lines) · ×4
Edited copy of a member (9 corresponding lines) b2c-parent/b2c-core/src/main/java/org/javamaster/b2c/core/service/impl/IExamServiceImpl.java:40— b2c-parent/b2c-core/src/main/java/org/javamaster/b2c/core/service/impl/IExamServiceImpl.java:40-54 | b2c-parent/b2c-core/src/main/java/org/javamaster/b2c/core/service/impl/IExamServiceImpl.java:57-65 — 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) tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/AppFactory.java:33— tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/AppFactory.java:33-41 | tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/AppFactory.java:65-74 — 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) tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/service/AppFactory.kt:64— tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/service/AppFactory.kt:64-73 | tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/service/AppFactory.kt:77-85 — 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) tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/ErdOnlineProjectServiceImpl.java:372— tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/ErdOnlineProjectServiceImpl.java:372-380 | tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/ErdOnlineProjectServiceImpl.java:382-390 — 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.
X24 · Document value interpolated into markup unescaped· Untrusted text written into markup unescaped · ×4
Untrusted text written into markup unescaped spring-embed-arthas/src/main/webapp/index.js:3202— `e.content:r.textContent=e.content` 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 spring-embed-arthas/src/main/webapp/index.js:16725— `n` is text this program did not author, and it is written into a quoted attribute value 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 spring-embed-arthas/src/main/webapp/vue.js:7640— `cur` 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 spring-embed-arthas/src/main/webapp/vue.js:9216— `html` 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.
AXS1 · Runtime exposed surface· Runtime opened a port the repository does not declare · ×3
Runtime opened a port the repository does not declare: wd-runtime-app 32768->443/udp on 0.0.0.0 — The booted stack published container port 443/udp of service 'wd-runtime-app' as host port 32768, but no ports:/expose:/EXPOSE entry in this repository names it — so it is most likely inherited from a base image. Observed after booting the stack in our sandbox, not read from a manifest. Advisory evidence for CRA Annex I (2)(j) (limit attack surfaces, including external interfaces); we do not assess whether the network it is published onto makes this a risk.
Runtime opened a port the repository does not declare: wd-runtime-app 32769->443/tcp on 0.0.0.0 — The booted stack published container port 443/tcp of service 'wd-runtime-app' as host port 32769, but no ports:/expose:/EXPOSE entry in this repository names it — so it is most likely inherited from a base image. Observed after booting the stack in our sandbox, not read from a manifest. Advisory evidence for CRA Annex I (2)(j) (limit attack surfaces, including external interfaces); we do not assess whether the network it is published onto makes this a risk.
Runtime opened a port the repository does not declare: wd-runtime-app 32770->2019/tcp on 0.0.0.0 — The booted stack published container port 2019/tcp of service 'wd-runtime-app' as host port 32770, but no ports:/expose:/EXPOSE entry in this repository names it — so it is most likely inherited from a base image. Observed after booting the stack in our sandbox, not read from a manifest. Advisory evidence for CRA Annex I (2)(j) (limit attack surfaces, including external interfaces); we do not assess whether the network it is published onto makes this a risk.
(anonymous) (cyclomatic 40) spring-embed-arthas/src/main/webapp/index.js:3363— (anonymous) has cyclomatic complexity 40 (threshold 15). Most of this is not in the body itself: 3 of the 40 points are its own statements and the rest belongs to 21 function items inside it that branch (value, contains, a function literal at line 3368, …). 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: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
(anonymous) (cyclomatic 40) spring-embed-arthas/src/main/webapp/index.js:6074— (anonymous) has cyclomatic complexity 40 (threshold 15). Most of this is not in the body itself: 1 of the 40 points is its own statement and the rest belongs to 16 function items inside it that branch (set, isDisabled, checkboxSize, …). 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: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
(anonymous) (cyclomatic 40) spring-embed-arthas/src/main/webapp/index.js:11251— (anonymous) has cyclomatic complexity 40 (threshold 15). Most of this is not in the body itself: 1 of the 40 points is its own statement and the rest belongs to 25 function items inside it that branch (validate, visible, handleAction, …). 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: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
vue.createPatchFunction::hydrate (cyclomatic 32) spring-embed-arthas/src/main/webapp/vue.js:6354— vue.createPatchFunction::hydrate has cyclomatic complexity 32 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: 2 other methods here (vue.createPatchFunction::updateChildren, vue.createPatchFunction::patchVnode) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
vue.createPatchFunction::patchVnode (cyclomatic 31) spring-embed-arthas/src/main/webapp/vue.js:6259— vue.createPatchFunction::patchVnode has cyclomatic complexity 31 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: 2 other methods here (vue.createPatchFunction::updateChildren, vue.createPatchFunction::hydrate) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
vue.createPatchFunction::updateChildren (cyclomatic 19) spring-embed-arthas/src/main/webapp/vue.js:6162— vue.createPatchFunction::updateChildren 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 shape REPEATS in the file: 2 other methods here (vue.createPatchFunction::patchVnode, vue.createPatchFunction::hydrate) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
(anonymous) (cyclomatic 31) spring-embed-arthas/src/main/webapp/index.js:168— (anonymous) has cyclomatic complexity 31 (threshold 15). Most of this is not in the body itself: 1 of the 31 points is its own statement and the rest belongs to 15 function items inside it that branch (a, valueEquals, getValueByPath, …). 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 file is where this pass's cyclomatic complexity CONCENTRATES: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
(anonymous) (cyclomatic 31) spring-embed-arthas/src/main/webapp/index.js:14485— (anonymous) has cyclomatic complexity 31 (threshold 15). Most of this is not in the body itself: 1 of the 31 points is its own statement and the rest belongs to 13 function items inside it that branch (install::bind, install::i, install::unbind, …). 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: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
(anonymous) (cyclomatic 31) spring-embed-arthas/src/main/webapp/index.js:17571— (anonymous) has cyclomatic complexity 31 (threshold 15). Most of this is not in the body itself: 1 of the 31 points is its own statement and the rest belongs to 33 function items inside it that branch (render, handler, checkedSummary, …). 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: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
(anonymous) (cyclomatic 26) spring-embed-arthas/src/main/webapp/index.js:10844— (anonymous) has cyclomatic complexity 26 (threshold 15). Most of this is not in the body itself: 1 of the 26 points is its own statement and the rest belongs to 25 function items inside it that branch (amPmMode, handleKeydown, value, …). 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: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
(anonymous) (cyclomatic 26) spring-embed-arthas/src/main/webapp/index.js:13654— (anonymous) has cyclomatic complexity 26 (threshold 15). Most of this is not in the body itself: 1 of the 26 points is its own statement and the rest belongs to 23 function items inside it that branch (created, handleClick, n, …). 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: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
(anonymous) (cyclomatic 26) spring-embed-arthas/src/main/webapp/index.js:14739— (anonymous) has cyclomatic complexity 26 (threshold 15). Most of this is not in the body itself: 1 of the 26 points is its own statement and the rest belongs to 27 function items inside it that branch (handleRemove, render, handleStart, …). 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: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
(anonymous) (cyclomatic 25) spring-embed-arthas/src/main/webapp/index.js:466— (anonymous) has cyclomatic complexity 25 (threshold 15). Most of this is not in the body itself: 3 of the 25 points are its own statements and the rest belongs to 9 function items inside it that branch (a function literal at line 470, r, unbind, …). 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: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
(anonymous) (cyclomatic 25) spring-embed-arthas/src/main/webapp/index.js:14270— (anonymous) has cyclomatic complexity 25 (threshold 15). Most of this is not in the body itself: 1 of the 25 points is its own statement and the rest belongs to 26 function items inside it that branch (setPosition, onDragging, s, …). 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: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
(anonymous) (cyclomatic 25) spring-embed-arthas/src/main/webapp/index.js:14577— (anonymous) has cyclomatic complexity 25 (threshold 15). Most of this is not in the body itself: 1 of the 25 points is its own statement and the rest belongs to 9 function items inside it that branch (b, a function literal at line 14590, n, …). 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: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
(anonymous) (cyclomatic 24) spring-embed-arthas/src/main/webapp/index.js:24— (anonymous) has cyclomatic complexity 24 (threshold 15). Most of this is not in the body itself: 1 of the 24 points is its own statement and the rest belongs to 3 function items inside it that branch (exports, exports::c, exports::render). 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 file is where this pass's cyclomatic complexity CONCENTRATES: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
(anonymous) (cyclomatic 24) spring-embed-arthas/src/main/webapp/index.js:12643— (anonymous) has cyclomatic complexity 24 (threshold 15). Most of this is not in the body itself: 1 of the 24 points is its own statement and the rest belongs to 23 function items inside it that branch (setCurrentName, calcPaneInstances, render, …). 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: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
(anonymous) (cyclomatic 24) spring-embed-arthas/src/main/webapp/table-column-drag.js:242— (anonymous) has cyclomatic complexity 24 (threshold 15). Most of this is not in the body itself: 1 of the 24 points is its own statement and the rest belongs to 12 function items inside it that branch (_dragColumn, _handleMouseMove, a function literal at line 274, …). 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.
(anonymous) (cyclomatic 23) spring-embed-arthas/src/main/webapp/index.js:5782— (anonymous) has cyclomatic complexity 23 (threshold 15). Most of this is not in the body itself: 1 of the 23 points is its own statement and the rest belongs to 11 function items inside it that branch (isDisabled, radioSize, tabIndex, …). 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: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
(anonymous) (cyclomatic 23) spring-embed-arthas/src/main/webapp/index.js:11387— (anonymous) has cyclomatic complexity 23 (threshold 15). Most of this is not in the body itself: 4 of the 23 points are its own statements and the rest belongs to 10 function items inside it that branch (Dialog, a function literal at line 11392, trapFocus, …). 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: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
(anonymous) (cyclomatic 23) spring-embed-arthas/src/main/webapp/index.js:16155— (anonymous) has cyclomatic complexity 23 (threshold 15). Most of this is not in the body itself: 1 of the 23 points is its own statement and the rest belongs to 7 function items inside it that branch (processIndex, translateItem, calculateTranslate, …). 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 file is where this pass's cyclomatic complexity CONCENTRATES: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
(anonymous) (cyclomatic 19) spring-embed-arthas/src/main/webapp/index.js:5972— (anonymous) has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 1 of the 19 points is its own statement and the rest belongs to 12 function items inside it that branch (activeStyle, size, isDisabled, …). 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: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
(anonymous) (cyclomatic 19) spring-embed-arthas/src/main/webapp/index.js:6311— (anonymous) has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 1 of the 19 points is its own statement and the rest belongs to 7 function items inside it that branch (n, a function literal at line 6336, a function literal at line 6354, …). 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: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
(anonymous) (cyclomatic 19) spring-embed-arthas/src/main/webapp/index.js:15259— (anonymous) has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 1 of the 19 points is its own statement and the rest belongs to 7 function items inside it that branch (r, n, s, …). 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: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
(anonymous) (cyclomatic 18) spring-embed-arthas/src/main/webapp/index.js:2611— (anonymous) has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 3 of the 18 points are its own statements and the rest belongs to 5 function items inside it that branch ((anonymous)::t, a function literal at line 2622, a function literal at line 2616, …). 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: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
(anonymous) (cyclomatic 18) spring-embed-arthas/src/main/webapp/index.js:7843— (anonymous) has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 1 of the 18 points is its own statement and the rest belongs to 20 function items inside it that branch (set, n, handleSelect, …). 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: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
(anonymous) (cyclomatic 18) spring-embed-arthas/src/main/webapp/index.js:15853— (anonymous) has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 1 of the 18 points is its own statement and the rest belongs to 16 function items inside it that branch (style, updateStatus, calcProgress, …). 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: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
(anonymous) (cognitive 52) spring-embed-arthas/src/main/webapp/index.js:2636— (anonymous) has cognitive complexity 52 (threshold 15). Drivers by points: boolean chains 27, if/else 8 (14 pts), ternaries 5 (9 pts), loops 1 (2 pts) (nesting depth added 11). None of this is in the body itself: all 52 points belong to 29 function items inside it that branch (calcIconOffset, resizeTextarea, showClear, …). 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.
(anonymous) (cognitive 52) spring-embed-arthas/src/main/webapp/index.js:14133— (anonymous) has cognitive complexity 52 (threshold 15). Drivers by points: ternaries 25, boolean chains 18, if/else 7 (8 pts), loops 1 (nesting depth added 1). None of this is in the body itself: all 52 points belong to 31 function items inside it that branch (setValues, onSliderClick, stops, …). 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.
(anonymous) (cognitive 52) spring-embed-arthas/src/main/webapp/index.js:16404— (anonymous) has cognitive complexity 52 (threshold 15). Drivers by points: boolean chains 31, ternaries 14 (15 pts), if/else 4 (6 pts) (nesting depth added 3). None of this is in the body itself: all 52 points belong to 57 function items inside it that branch (handleKeydown, handleInputChange, cascaderSize, …). 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.
(anonymous) (cognitive 50) spring-embed-arthas/src/main/webapp/index.js:62— (anonymous) has cognitive complexity 50 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 13, ternaries 5 (11 pts), loops 3 (5 pts), error handling 1 (4 pts), match/switch 1 (3 pts) (nesting depth added 19). None of this is in the body itself: all 50 points belong to 19 function items inside it that branch (d, n, a function literal at line 70, …). 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.
(anonymous) (cognitive 50) spring-embed-arthas/src/main/webapp/index.js:6614— (anonymous) has cognitive complexity 50 (threshold 15). Drivers by points: boolean chains 26, ternaries 17 (19 pts), if/else 5 (nesting depth added 2). None of this is in the body itself: all 50 points belong to 43 function items inside it that branch (fixedBodyHeight, fixedHeight, a function literal at line 6697, …). 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.
(anonymous) (cognitive 50) spring-embed-arthas/src/main/webapp/index.js:11719— (anonymous) has cognitive complexity 50 (threshold 15). Drivers by points: boolean chains 31, ternaries 9, if/else 7, loops 3. Most of this is not in the body itself: 1 of the 50 points is its own statement and the rest belongs to 28 function items inside it that branch (contentStyle, validate, getRules, …). 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.
D4 · Code Duplication· Edited copy of a member (6 corresponding lines) · ×3
Edited copy of a member (6 corresponding lines) tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/GlobalHandler.java:41— tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/GlobalHandler.java:41-46 | tools-manage/tools-manage-admin/src/main/java/org/javamaster/spring/tools/manage/GlobalHandler.java:18-24 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/redis/impl/HashRedisDataTypeService.java:142— tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/redis/impl/HashRedisDataTypeService.java:142-148 | tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/redis/impl/ZSetRedisDataTypeService.java:74-79 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/redis/impl/HashRedisStrategy.kt:205— tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/redis/impl/HashRedisStrategy.kt:205-210 | tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/redis/impl/ZSetRedisStrategy.kt:165-170 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (10–11 lines × 2) tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/redis/impl/ListRedisStrategy.kt:123— tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/redis/impl/ListRedisStrategy.kt:123-133 | tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/redis/impl/SetRedisStrategy.kt:134-143 — before extracting anything, compare `tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/redis/impl/ListRedisStrategy.kt` and `tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/redis/impl/SetRedisStrategy.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 39 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (10–11 lines × 2) tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/redis/impl/ListRedisDataTypeService.java:125— tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/redis/impl/ListRedisDataTypeService.java:125-135 | tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/redis/impl/SetRedisDataTypeService.java:131-140 — before extracting anything, compare `tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/redis/impl/ListRedisDataTypeService.java` and `tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/redis/impl/SetRedisDataTypeService.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 41 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (10–11 lines × 2) tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/AbstractDbService.java:636— tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/AbstractDbService.java:636-645 | tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/MongoDbServiceImpl.java:213-223 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (10 lines × 2) tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/redis/impl/StringRedisDataTypeService.java:55— tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/redis/impl/StringRedisDataTypeService.java:55-64 | tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/redis/impl/ZSetRedisDataTypeService.java:123-132 — 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 `tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/redis/impl/StringRedisDataTypeService.java:55` 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) tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/redis/RedisHelper.java:131— tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/redis/RedisHelper.java:131-140 | tools-manage/tools-manage-admin/src/main/java/org/javamaster/spring/tools/manage/service/impl/RedisServiceImpl.java:163-172 — 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 `tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/redis/RedisHelper.java:131` 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: `Tree` names `org.javamaster.invocationlab.admin.model.redis.Tree` in one and `org.javamaster.spring.tools.manage.model.Tree` 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.
Duplicated block (10 lines × 2) tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/util/RedisUtils.java:70— tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/util/RedisUtils.java:70-79 | tools-manage/tools-manage-admin/src/main/java/org/javamaster/spring/tools/manage/util/RedisUtils.java:66-75 — before extracting anything, compare `tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/util/RedisUtils.java` and `tools-manage/tools-manage-admin/src/main/java/org/javamaster/spring/tools/manage/util/RedisUtils.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 34 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 (9 lines × 2) tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/controller/RpcPostmanServiceQueryController.java:185— tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/controller/RpcPostmanServiceQueryController.java:185-193 | tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/controller/RpcPostmanServiceQueryController.java:241-249 — both copies are in the same file, so extract the 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) tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/AbstractDbService.java:610— tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/AbstractDbService.java:610-618 | tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/MongoDbServiceImpl.java:528-536 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (9 lines × 2) tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/util/RedisUtils.java:90— tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/util/RedisUtils.java:90-98 | tools-manage/tools-manage-admin/src/main/java/org/javamaster/spring/tools/manage/util/RedisUtils.java:86-94 — before extracting anything, compare `tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/util/RedisUtils.java` and `tools-manage/tools-manage-admin/src/main/java/org/javamaster/spring/tools/manage/util/RedisUtils.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 34 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 (6 lines × 2) tools-manage/tools-manage-admin/src/main/java/org/javamaster/spring/tools/manage/service/impl/RedisServiceImpl.java:257— tools-manage/tools-manage-admin/src/main/java/org/javamaster/spring/tools/manage/service/impl/RedisServiceImpl.java:257-262 | tools-manage/tools-manage-admin/src/main/java/org/javamaster/spring/tools/manage/service/impl/RedisServiceImpl.java:270-275 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `tools-manage/tools-manage-admin/src/main/java/org/javamaster/spring/tools/manage/service/impl/RedisServiceImpl.java:263` calls `setFieldVos` and `tools-manage/tools-manage-admin/src/main/java/org/javamaster/spring/tools/manage/service/impl/RedisServiceImpl.java:276` 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) tools-manage/tools-manage-admin/src/main/java/org/javamaster/spring/tools/manage/service/impl/RedisServiceImpl.java:302— tools-manage/tools-manage-admin/src/main/java/org/javamaster/spring/tools/manage/service/impl/RedisServiceImpl.java:302-307 | tools-manage/tools-manage-admin/src/main/java/org/javamaster/spring/tools/manage/service/impl/RedisServiceImpl.java:327-332 — both copies are in the same file, so extract the 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 `tools-manage/tools-manage-admin/src/main/java/org/javamaster/spring/tools/manage/service/impl/RedisServiceImpl.java:302` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `tools-manage/tools-manage-admin/src/main/java/org/javamaster/spring/tools/manage/service/impl/RedisServiceImpl.java:326` calls `getFieldKey`, `getBytes` and `tools-manage/tools-manage-admin/src/main/java/org/javamaster/spring/tools/manage/service/impl/RedisServiceImpl.java:301` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (6 lines × 2) tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/model/dto/WebApiRspDto.java:32— tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/model/dto/WebApiRspDto.java:32-37 | tools-manage/tools-manage-admin/src/main/java/org/javamaster/spring/tools/manage/model/WebApiRspDto.java:23-28 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. 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.
AC2 · Forms & labels· <DatePicker> field component without a label · ×2
<DatePicker> field component without a label tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/InputContextMenu.tsx:93— This UI-library field component has no label / aria-label / aria-labelledby / id at this call site, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id, even one the component sets on what it renders, names nothing until a label points at it) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<DatePicker> field component without a label tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/InputContextMenu.tsx:96— This UI-library field component has no label / aria-label / aria-labelledby / id at this call site, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id, even one the component sets on what it renders, names nothing until a label points at it) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
(anonymous) (cyclomatic 71) spring-embed-arthas/src/main/webapp/index.js:243— (anonymous) has cyclomatic complexity 71 (threshold 15). Most of this is not in the body itself: 5 of the 71 points are its own statements and the rest belongs to 20 function items inside it that branch (o, a function literal at line 309, s, …). 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: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
(anonymous) (cyclomatic 71) spring-embed-arthas/src/main/webapp/index.js:12082— (anonymous) has cyclomatic complexity 71 (threshold 15). Of this number, 17 points are the body's own statements and 54 belong to 24 function items inside it that branch. 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 cyclomatic complexity CONCENTRATES: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
(anonymous) (cyclomatic 56) spring-embed-arthas/src/main/webapp/index.js:502— (anonymous) has cyclomatic complexity 56 (threshold 15). Most of this is not in the body itself: 1 of the 56 points is its own statement and the rest belongs to 45 function items inside it that branch (getDayCountOfMonth, a function literal at line 571, limitTimeRange, …). 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: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
(anonymous) (cyclomatic 56) spring-embed-arthas/src/main/webapp/index.js:11719— (anonymous) has cyclomatic complexity 56 (threshold 15). Most of this is not in the body itself: 2 of the 56 points are its own statements and the rest belongs to 28 function items inside it that branch (contentStyle, validate, getRules, …). 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: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
(anonymous) (cyclomatic 51) spring-embed-arthas/src/main/webapp/index.js:5119— (anonymous) has cyclomatic complexity 51 (threshold 15). Most of this is not in the body itself: 1 of the 51 points is its own statement and the rest belongs to 40 function items inside it that branch (render, handleClick, handleMouseenter, …). 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: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
(anonymous) (cyclomatic 51) spring-embed-arthas/src/main/webapp/index.js:16404— (anonymous) has cyclomatic complexity 51 (threshold 15). Most of this is not in the body itself: 1 of the 51 points is its own statement and the rest belongs to 57 function items inside it that branch (handleKeydown, handleClickoutside, cascaderSize, …). 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: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
(anonymous) (cyclomatic 44) spring-embed-arthas/src/main/webapp/index.js:5581— (anonymous) has cyclomatic complexity 44 (threshold 15). Most of this is not in the body itself: 1 of the 44 points is its own statement and the rest belongs to 25 function items inside it that branch (handler, setCurrentValue, inputNumberSize, …). 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 file is where this pass's cyclomatic complexity CONCENTRATES: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
(anonymous) (cyclomatic 44) spring-embed-arthas/src/main/webapp/index.js:12757— (anonymous) has cyclomatic complexity 44 (threshold 15). Most of this is not in the body itself: 1 of the 44 points is its own statement and the rest belongs to 29 function items inside it that branch (render, a function literal at line 12860, update, …). 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: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
(anonymous) (cyclomatic 41) spring-embed-arthas/src/main/webapp/index.js:62— (anonymous) has cyclomatic complexity 41 (threshold 15). Most of this is not in the body itself: 1 of the 41 points is its own statement and the rest belongs to 19 function items inside it that branch (r, a function literal at line 70, d, …). 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: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
(anonymous) (cyclomatic 41) spring-embed-arthas/src/main/webapp/index.js:6240— (anonymous) has cyclomatic complexity 41 (threshold 15). Most of this is not in the body itself: 1 of the 41 points is its own statement and the rest belongs to 15 function items inside it that branch (set, isDisabled, isChecked, …). 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: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
(anonymous) (cyclomatic 36) spring-embed-arthas/src/main/webapp/index.js:4860— (anonymous) has cyclomatic complexity 36 (threshold 15). Most of this is not in the body itself: 1 of the 36 points is its own statement and the rest belongs to 36 function items inside it that branch (updateActiveIndex, getColorChannels, handleItemClick, …). 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: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
(anonymous) (cyclomatic 36) spring-embed-arthas/src/main/webapp/index.js:15959— (anonymous) has cyclomatic complexity 36 (threshold 15). Most of this is not in the body itself: 1 of the 36 points is its own statement and the rest belongs to 34 function items inside it that branch (itemInStage, setActiveItem, s, …). 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: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
(anonymous) (cyclomatic 30) spring-embed-arthas/src/main/webapp/index.js:9448— (anonymous) 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 28 function items inside it that branch (scrollDown, modifyDateField, emitSelectRange, …). 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: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
(anonymous) (cyclomatic 30) spring-embed-arthas/src/main/webapp/index.js:15138— (anonymous) 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 20 function items inside it that branch (uploadFiles, a function literal at line 15201, upload, …). 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: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
(anonymous) (cyclomatic 27) spring-embed-arthas/src/main/webapp/index.js:1047— (anonymous) has cyclomatic complexity 27 (threshold 15). Most of this is not in the body itself: 3 of the 27 points are its own statements and the rest belongs to 5 function items inside it that branch (isFocusable, triggerEvent, focusFirstDescendant, …). 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 file is where this pass's cyclomatic complexity CONCENTRATES: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
(anonymous) (cyclomatic 27) spring-embed-arthas/src/main/webapp/index.js:2064— (anonymous) has cyclomatic complexity 27 (threshold 15). Most of this is not in the body itself: 1 of the 27 points is its own statement and the rest belongs to 6 function items inside it that branch (pagers, onPagerClick, onMouseenter, …). 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 file is where this pass's cyclomatic complexity CONCENTRATES: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
(anonymous) (cyclomatic 21) spring-embed-arthas/src/main/webapp/index.js:6153— (anonymous) has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 1 of the 21 points is its own statement and the rest belongs to 7 function items inside it that branch (n, a function literal at line 6193, a function literal at line 6211, …). 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: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
(anonymous) (cyclomatic 21) spring-embed-arthas/src/main/webapp/index.js:12287— (anonymous) has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 1 of the 21 points is its own statement and the rest belongs to 12 function items inside it that branch (n, regexp, date, …). 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 file is where this pass's cyclomatic complexity CONCENTRATES: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
vue.parseHTML::parseEndTag (cyclomatic 18) spring-embed-arthas/src/main/webapp/vue.js:9487— vue.parseHTML::parseEndTag has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: 2 other methods here (vue.parseHTML, vue.parseHTML::handleStartTag) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
vue.parseHTML::handleStartTag (cyclomatic 16) spring-embed-arthas/src/main/webapp/vue.js:9444— vue.parseHTML::handleStartTag 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 shape REPEATS in the file: 2 other methods here (vue.parseHTML, vue.parseHTML::parseEndTag) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared. This is NOT this file's highest cyclomatic complexity: vue.eventsMixin (cyclomatic 18) 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.
AppInterceptor.preHandle (cyclomatic 18) tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/inteceptor/AppInterceptor.kt:34— AppInterceptor.preHandle has cyclomatic complexity 18 (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.
AppInterceptor.preHandle (cyclomatic 18) tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/inteceptor/AppInterceptor.java:71— AppInterceptor.preHandle has cyclomatic complexity 18 (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.
(anonymous) (cognitive 47) spring-embed-arthas/src/main/webapp/index.js:1350— (anonymous) has cognitive complexity 47 (threshold 15). Drivers by points: boolean chains 15, if/else 10 (15 pts), ternaries 12, loops 4 (5 pts) (nesting depth added 6). Most of this is not in the body itself: 2 of the 47 points are its own statements and the rest belongs to 16 function items inside it that branch (orderBy, getRowIdentity, orderBy::l, …). 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.
(anonymous) (cognitive 47) spring-embed-arthas/src/main/webapp/index.js:12757— (anonymous) has cognitive complexity 47 (threshold 15). Drivers by points: boolean chains 19, ternaries 17 (19 pts), if/else 7 (9 pts) (nesting depth added 4). None of this is in the body itself: all 47 points belong to 29 function items inside it that branch (update, render, scrollToActiveTab, …). 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.
(anonymous) (cognitive 43) spring-embed-arthas/src/main/webapp/index.js:3363— (anonymous) has cognitive complexity 43 (threshold 15). Drivers by points: boolean chains 24, ternaries 10 (14 pts), if/else 4 (5 pts) (nesting depth added 5). Most of this is not in the body itself: 2 of the 43 points are its own statements and the rest belongs to 21 function items inside it that branch (value, contains, limitReached, …). 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.
(anonymous) (cognitive 43) spring-embed-arthas/src/main/webapp/index.js:11251— (anonymous) has cognitive complexity 43 (threshold 15). Drivers by points: boolean chains 26, if/else 6 (12 pts), ternaries 5 (nesting depth added 6). None of this is in the body itself: all 43 points belong to 25 function items inside it that branch (validate, visible, icon, …). 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.
(anonymous) (cognitive 36) spring-embed-arthas/src/main/webapp/index.js:4860— (anonymous) has cognitive complexity 36 (threshold 15). Drivers by points: boolean chains 22, ternaries 9, if/else 2, loops 1 (2 pts), error handling 1 (nesting depth added 1). None of this is in the body itself: all 36 points belong to 36 function items inside it that branch (getColorChannels, updateActiveIndex, handleItemClick, …). 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.
(anonymous) (cognitive 36) spring-embed-arthas/src/main/webapp/index.js:15959— (anonymous) has cognitive complexity 36 (threshold 15). Drivers by points: boolean chains 22, ternaries 8 (12 pts), if/else 2 (nesting depth added 4). None of this is in the body itself: all 36 points belong to 34 function items inside it that branch (setActiveItem, itemInStage, s, …). 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.
(anonymous) (cognitive 31) spring-embed-arthas/src/main/webapp/index.js:4548— (anonymous) has cognitive complexity 31 (threshold 15). Drivers by points: boolean chains 16, ternaries 15. None of this is in the body itself: all 31 points belong to 27 function items inside it that branch (handleItemKeyDown, initEvent, handleTriggerKeyDown, …). 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.
(anonymous) (cognitive 31) spring-embed-arthas/src/main/webapp/index.js:9448— (anonymous) has cognitive complexity 31 (threshold 15). Drivers by points: ternaries 12 (13 pts), boolean chains 9, if/else 5 (6 pts), loops 1 (2 pts), match/switch 1 (nesting depth added 3). None of this is in the body itself: all 31 points belong to 28 function items inside it that branch (scrollDown, emitSelectRange, amPm, …). 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.
(anonymous) (cognitive 30) spring-embed-arthas/src/main/webapp/index.js:15138— (anonymous) has cognitive complexity 30 (threshold 15). Drivers by points: boolean chains 18, if/else 6, ternaries 4, loops 1 (2 pts) (nesting depth added 1). None of this is in the body itself: all 30 points belong to 20 function items inside it that branch (a function literal at line 15201, uploadFiles, upload, …). 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.
(anonymous) (cognitive 30) spring-embed-arthas/src/main/webapp/index.js:17571— (anonymous) has cognitive complexity 30 (threshold 15). Drivers by points: boolean chains 17, ternaries 10, if/else 3. None of this is in the body itself: all 30 points belong to 33 function items inside it that branch (render, checkedSummary, n, …). 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.
vue.parseHTML::parseEndTag (cognitive 29) spring-embed-arthas/src/main/webapp/vue.js:9487— vue.parseHTML::parseEndTag has cognitive complexity 29 (threshold 15). Drivers by points: if/else 13 (22 pts), loops 2 (4 pts), boolean chains 3 (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. This shape REPEATS in the file: 2 other methods here (vue.parseHTML, vue.parseHTML::handleStartTag) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
vue.parseHTML::handleStartTag (cognitive 17) spring-embed-arthas/src/main/webapp/vue.js:9444— vue.parseHTML::handleStartTag has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (9 pts), boolean chains 5, ternaries 1 (2 pts), loops 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: 2 other methods here (vue.parseHTML, vue.parseHTML::parseEndTag) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
(anonymous) (cognitive 28) spring-embed-arthas/src/main/webapp/index.js:9353— (anonymous) has cognitive complexity 28 (threshold 15). Drivers by points: boolean chains 16, ternaries 9, if/else 3. None of this is in the body itself: all 28 points belong to 21 function items inside it that branch (value, amPmMode, handleKeydown, …). 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.
(anonymous) (cognitive 28) spring-embed-arthas/src/main/webapp/index.js:14739— (anonymous) has cognitive complexity 28 (threshold 15). Drivers by points: boolean chains 14, ternaries 6 (8 pts), if/else 4 (5 pts), error handling 1 (nesting depth added 3). None of this is in the body itself: all 28 points belong to 27 function items inside it that branch (handleRemove, render, handleStart, …). 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.
(anonymous) (cognitive 26) spring-embed-arthas/src/main/webapp/index.js:11415— (anonymous) has cognitive complexity 26 (threshold 15). Drivers by points: boolean chains 11, ternaries 10, if/else 5. None of this is in the body itself: all 26 points belong to 10 function items inside it that branch (n, n::keydown, n::keydown, …). 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.
(anonymous) (cognitive 26) spring-embed-arthas/src/main/webapp/index.js:14270— (anonymous) has cognitive complexity 26 (threshold 15). Drivers by points: boolean chains 17, ternaries 5 (7 pts), if/else 2 (nesting depth added 2). None of this is in the body itself: all 26 points belong to 26 function items inside it that branch (setPosition, onDragging, s, …). 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.
(anonymous) (cognitive 22) spring-embed-arthas/src/main/webapp/index.js:4271— (anonymous) has cognitive complexity 22 (threshold 15). Drivers by points: boolean chains 15, if/else 3 (4 pts), ternaries 3 (nesting depth added 1). None of this is in the body itself: all 22 points belong to 21 function items inside it that branch (highlight, handleKeyEnter, suggestionVisible, …). 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.
(anonymous) (cognitive 22) spring-embed-arthas/src/main/webapp/index.js:6311— (anonymous) has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 9 (11 pts), boolean chains 7, if/else 4 (nesting depth added 2). None of this is in the body itself: all 22 points belong to 7 function items inside it that branch (n, a function literal at line 6336, a function literal at line 6354, …). 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.
renderRelation::draw (cognitive 22) tools-manage/invocationlab-erd-online-view/src/utils/relation2file.js:362— renderRelation::draw has cognitive complexity 22 (threshold 15). Drivers by points: boolean chains 13, ternaries 8, if/else 1. 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.
renderRelation::getPath (cognitive 19) tools-manage/invocationlab-erd-online-view/src/utils/relation2file.js:185— renderRelation::getPath has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 2, loops 1 (2 pts), ternaries 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.
_renderRelation::draw (cognitive 22) tools-manage/invocationlab-erd-online-view/src/pages/design/relation/g6.js:692— _renderRelation::draw has cognitive complexity 22 (threshold 15). Drivers by points: boolean chains 13, ternaries 8, if/else 1. 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.
_renderRelation::getPath (cognitive 19) tools-manage/invocationlab-erd-online-view/src/pages/design/relation/g6.js:513— _renderRelation::getPath has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 2, loops 1 (2 pts), ternaries 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.
AppInterceptor.preHandle (cognitive 20) tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/inteceptor/AppInterceptor.kt:34— AppInterceptor.preHandle has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (13 pts), boolean chains 6, loops 1 (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.
AppInterceptor.preHandle (cognitive 20) tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/inteceptor/AppInterceptor.java:71— AppInterceptor.preHandle has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (13 pts), boolean chains 6, loops 1 (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.
JarLocalFileLoader.doLoadInterfaceInfoAndInitLoader (cognitive 18) tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/service/load/impl/JarLocalFileLoader.kt:98— JarLocalFileLoader.doLoadInterfaceInfoAndInitLoader has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (9 pts), loops 3 (6 pts), error handling 1 (2 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.
JarLocalFileLoader.doLoadInterfaceInfoAndInitLoader (cognitive 18) tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/load/impl/JarLocalFileLoader.java:108— JarLocalFileLoader.doLoadInterfaceInfoAndInitLoader has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (9 pts), loops 3 (6 pts), error handling 1 (2 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.
propertyOperation.setProp (cognitive 16) tools-manage/invocationlab-admin-21/src/main/resources/script/propertyOperation.js:1— propertyOperation.setProp has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (15 pts), loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: 2 other methods here (propertyOperation.getProp, propertyOperation.getInternalProp) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
propertyOperation.setProp (cognitive 16) tools-manage/invocationlab-admin/src/main/resources/script/propertyOperation.js:1— propertyOperation.setProp has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (15 pts), loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: 2 other methods here (propertyOperation.getProp, propertyOperation.getInternalProp) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
propertyOperation.getProp (cognitive 16) tools-manage/invocationlab-admin-21/src/main/resources/script/propertyOperation.js:49— propertyOperation.getProp has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (15 pts), loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: 2 other methods here (propertyOperation.setProp, propertyOperation.getInternalProp) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
propertyOperation.getProp (cognitive 16) tools-manage/invocationlab-admin/src/main/resources/script/propertyOperation.js:49— propertyOperation.getProp has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (15 pts), loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: 2 other methods here (propertyOperation.setProp, propertyOperation.getInternalProp) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
propertyOperation.getInternalProp (cognitive 16) tools-manage/invocationlab-admin-21/src/main/resources/script/propertyOperation.js:106— propertyOperation.getInternalProp has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (15 pts), loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: 2 other methods here (propertyOperation.setProp, propertyOperation.getProp) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
propertyOperation.getInternalProp (cognitive 16) tools-manage/invocationlab-admin/src/main/resources/script/propertyOperation.js:106— propertyOperation.getInternalProp has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (15 pts), loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: 2 other methods here (propertyOperation.setProp, propertyOperation.getProp) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
ErdOnlineProjectServiceImpl.isModifyTableName (cognitive 16) tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/service/impl/ErdOnlineProjectServiceImpl.kt:472— ErdOnlineProjectServiceImpl.isModifyTableName has cognitive complexity 16 (threshold 15). Drivers by points: if/else 3 (10 pts), loops 3 (6 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.
ErdOnlineProjectServiceImpl.isModifyTableName (cognitive 16) tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/ErdOnlineProjectServiceImpl.java:494— ErdOnlineProjectServiceImpl.isModifyTableName has cognitive complexity 16 (threshold 15). Drivers by points: if/else 3 (10 pts), loops 3 (6 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.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×2
Members sharing a duplicated core (4 members, 50+ identical tokens) tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/redis/impl/ListRedisStrategy.kt:71— tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/redis/impl/ListRedisStrategy.kt:71-95 | tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/redis/impl/SetRedisStrategy.kt:68-100 | tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/redis/impl/StringRedisStrategy.kt:57-80 | tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/redis/impl/ZSetRedisStrategy.kt:133-159 — 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) tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/AbstractDbService.java:411— tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/AbstractDbService.java:411-454 | tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/AbstractDbService.java:518-558 | tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/MongoDbServiceImpl.java:124-210 | tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/MongoDbServiceImpl.java:546-588 — 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 (22 corresponding lines) · ×2
Edited copy of a member (22 corresponding lines) tools-manage/tools-manage-admin/src/main/java/org/javamaster/spring/tools/manage/service/impl/RedisServiceImpl.java:297— tools-manage/tools-manage-admin/src/main/java/org/javamaster/spring/tools/manage/service/impl/RedisServiceImpl.java:297-318 | tools-manage/tools-manage-admin/src/main/java/org/javamaster/spring/tools/manage/service/impl/RedisServiceImpl.java:321-343 — 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) tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/AbstractDbService.java:1076— tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/AbstractDbService.java:1076-1099 | tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/MongoDbServiceImpl.java:762-783 — 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 (14 corresponding lines) · ×2
Edited copy of a member (14 corresponding lines) tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/AbstractDbService.java:635— tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/AbstractDbService.java:635-648 | tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/MongoDbServiceImpl.java:212-226 — 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) tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/KafkaServiceImpl.java:304— tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/KafkaServiceImpl.java:304-317 | tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/KafkaServiceImpl.java:319-337 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 9+ corresponding lines) · ×2
Edited copies of one member (3 members, 9+ corresponding lines) tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/handler/WebSocketHandler.java:45— tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/handler/WebSocketHandler.java:45-54 | tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/handler/WebSocketHandler.java:58-66 | tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/handler/WebSocketHandler.java:70-78 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 9+ corresponding lines) tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/handler/WebSocketHandler.kt:40— tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/handler/WebSocketHandler.kt:40-49 | tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/handler/WebSocketHandler.kt:51-59 | tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/handler/WebSocketHandler.kt:61-69 — 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, 12+ corresponding lines) · ×2
Edited copies of one member (3 members, 12+ corresponding lines) tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/redis/impl/ListRedisDataTypeService.java:124— tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/redis/impl/ListRedisDataTypeService.java:124-137 | tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/redis/impl/SetRedisDataTypeService.java:130-142 | tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/redis/impl/ZSetRedisDataTypeService.java:105-116 — 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.
Edited copies of one member (3 members, 12+ corresponding lines) tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/redis/impl/ListRedisStrategy.kt:122— tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/redis/impl/ListRedisStrategy.kt:122-135 | tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/redis/impl/SetRedisStrategy.kt:133-145 | tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/redis/impl/ZSetRedisStrategy.kt:117-128 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 10+ corresponding lines) · ×2
Edited copies of one member (3 members, 10+ corresponding lines) tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/util/DbUtils.kt:56— tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/util/DbUtils.kt:56-65 | tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/util/DbUtils.kt:68-78 | tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/util/DbUtils.kt:81-92 — 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.
Edited copies of one member (3 members, 10+ corresponding lines) tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/redis/impl/ListRedisStrategy.kt:54— tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/redis/impl/ListRedisStrategy.kt:54-65 | tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/redis/impl/SetRedisStrategy.kt:54-63 | tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/redis/impl/ZSetRedisStrategy.kt:58-68 — 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 copy of a member (12 corresponding lines) · ×2
Edited copy of a member (12 corresponding lines) tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/util/AesUtils.java:16— tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/util/AesUtils.java:16-27 | tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/util/AesUtils.java:30-41 — 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) tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/util/AesUtils.kt:13— tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/util/AesUtils.kt:13-24 | tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/util/AesUtils.kt:28-39 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (4 corresponding lines) · ×2
Edited copy of a member (4 corresponding lines) spring-aop/src/main/java/org/javamaster/spring/aop/aspect/LogAfterThrowingAspect.java:21— spring-aop/src/main/java/org/javamaster/spring/aop/aspect/LogAfterThrowingAspect.java:21-25 | spring-aop/src/main/java/org/javamaster/spring/aop/advice/LogAfterUserServiceThrowingAdvice.java:18-21 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (4 corresponding lines) tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/redis/impl/HashRedisDataTypeService.java:185— tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/redis/impl/HashRedisDataTypeService.java:185-188 | tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/redis/impl/ZSetRedisDataTypeService.java:147-150 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (7 corresponding lines) · ×2
Edited copy of a member (7 corresponding lines) spring-lifecycle/src/main/java/org/javamaster/spring/lifecycle/ContextLoaderBeans/LifecycleBeanPostProcessor.java:22— spring-lifecycle/src/main/java/org/javamaster/spring/lifecycle/ContextLoaderBeans/LifecycleBeanPostProcessor.java:22-28 | spring-lifecycle/src/main/java/org/javamaster/spring/lifecycle/ContextLoaderBeans/LifecycleInstantiationAwareBeanPostProcessor.java:22-28 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) spring-swagger/src/main/java/org/javamaster/spring/swagger/WebMvcConfig.java:38— spring-swagger/src/main/java/org/javamaster/spring/swagger/WebMvcConfig.java:38-44 | tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/serializer/BigIntegerToJsonSerializer.java:22-28 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (18 lines × 2) spring-transactional/src/main/java/org/javamaster/spring/transactional/service/AddressHelper.java:27— spring-transactional/src/main/java/org/javamaster/spring/transactional/service/AddressHelper.java:27-44 | spring-transactional/src/main/java/org/javamaster/spring/transactional/service/impl/AddressServiceImpl.java:138-155 — 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 (18 lines × 2) b2c-parent/b2c-core/src/main/java/org/javamaster/b2c/core/enums/ExamStatusEnum.java:27— b2c-parent/b2c-core/src/main/java/org/javamaster/b2c/core/enums/ExamStatusEnum.java:27-44 | b2c-parent/b2c-core/src/main/java/org/javamaster/b2c/core/enums/ExamTypeEnum.java:25-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. 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.
Off the main sequence: redis-spring-boot-starter — redis-spring-boot-starter: 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: mocklombok-javac — mocklombok-javac: abstractness 0.20, instability 0.00, distance 0.80 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Duplicated block (73 lines × 2 locations) tools-manage/invocationlab-erd-online-view/src/components/dialog/dataType/AddDataType.tsx:66— tools-manage/invocationlab-erd-online-view/src/components/dialog/dataType/AddDataType.tsx:66 · tools-manage/invocationlab-erd-online-view/src/components/dialog/dataType/RenameDataType.tsx:92 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (73 lines × 2 locations) tools-manage/invocationlab-erd-online-view/src/pages/design/relation/g6.js:651— tools-manage/invocationlab-erd-online-view/src/pages/design/relation/g6.js:651 · tools-manage/invocationlab-erd-online-view/src/utils/relation2file.js:323 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (58 lines × 2 locations) tools-manage/invocationlab-erd-online-view/src/components/dialog/project/AddProject.tsx:61— tools-manage/invocationlab-erd-online-view/src/components/dialog/project/AddProject.tsx:61 · tools-manage/invocationlab-erd-online-view/src/components/dialog/project/RenameProject.tsx:37 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (58 lines × 2 locations) tools-manage/invocationlab-erd-online-view/src/pages/design/relation/g6.js:800— tools-manage/invocationlab-erd-online-view/src/pages/design/relation/g6.js:800 · tools-manage/invocationlab-erd-online-view/src/utils/relation2file.js:461 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (32 lines × 2 locations) tools-manage/invocationlab-erd-online-view/src/layouts/GroupLayout/index.tsx:76— tools-manage/invocationlab-erd-online-view/src/layouts/GroupLayout/index.tsx:76 · tools-manage/invocationlab-erd-online-view/src/layouts/HomeLayout/index.tsx:70 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (32 lines × 2 locations) tools-manage/invocationlab-erd-online-view/src/pages/design/relation/g6.js:615— tools-manage/invocationlab-erd-online-view/src/pages/design/relation/g6.js:615 · tools-manage/invocationlab-erd-online-view/src/utils/relation2file.js:287 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases.
Complex function draw (cyclomatic 24, cognitive 22) tools-manage/invocationlab-erd-online-view/src/pages/design/relation/g6.js:692— draw has cyclomatic complexity 24 and cognitive complexity 22; 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 sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function draw (cyclomatic 24, cognitive 22) tools-manage/invocationlab-erd-online-view/src/utils/relation2file.js:362— draw has cyclomatic complexity 24 and cognitive complexity 22; 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 sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. 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.
R2 · Cyclomatic Complexity· Complex function n (cyclomatic 19, cognitive 14) · ×2
Complex function n (cyclomatic 19, cognitive 14) spring-embed-arthas/src/main/webapp/index.js:6836— n has cyclomatic complexity 19 and cognitive complexity 14; 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 sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function n (cyclomatic 19, cognitive 14) spring-embed-arthas/src/main/webapp/index.js:15911— n has cyclomatic complexity 19 and cognitive complexity 14; 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 sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. 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.
Dead file (~247 LoC) tools-manage/invocationlab-erd-online-view/src/components/dialog/export/ExportDDL.tsx— no import path from any entry point (31 application, 13 tooling, 11 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (tools-manage/invocationlab-erd-online-view/src/components/Menu/index.tsx) — 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 (~247 LoC) tools-manage/invocationlab-erd-online-view/src/pages/design/export/component/ExportDDL.tsx— no import path from any entry point (31 application, 13 tooling, 11 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
X17 · Uncapped recursion over a caller-supplied document· Recursive walk over a caller-supplied document has no depth cap · ×2
Recursive walk over a caller-supplied document has no depth cap tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/MongoDbServiceImpl.java:311— `convertRowToDoc` is not private, takes a value from its caller (line 262) and hands it on to `convertValue`, which calls itself at line 311 with a piece of `oldValue` — and nowhere in the walk is a depth or nesting counter compared with a bound, nor is the parser that builds the document given a nesting limit in this file. The walk therefore spends one stack frame (more through a lambda or a stream) per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes; javac turns no recursive call into a loop. On the JVM's default 1 MB thread stack a recursive walk throws `StackOverflowError` from about 500–2,000 levels on a cold first call and 6,000–17,000 once warmed up (OpenJDK 21 and 25). org.json, the W3C DOM, dom4j and StAX set no nesting limit of their own, Jackson before 2.15 none and 2.15+ 1,000 — on a cold JVM past the point the walk fails — and a `Map<String, Object>` tree is as deep as whatever built it. `StackOverflowError` is an `Error`, not an `Exception`: a `catch (Exception e)` around the call does not stop it, and the request or the thread dies with it. Thread a depth argument through `convertValue` and reject the value past a fixed maximum, configure the parser's nesting limit (`StreamReadConstraints.maxNestingDepth`, SnakeYAML's `setNestingDepthLimit`), or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/MongoDbServiceImpl.java:348— `getTableColumns` is not private, takes a value from its caller (line 322) and hands it on to `convertToColumns`, which calls itself at line 348 with a piece of `value` (and at line 362) — and nowhere in the walk is a depth or nesting counter compared with a bound, nor is the parser that builds the document given a nesting limit in this file. The walk therefore spends one stack frame (more through a lambda or a stream) per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes; javac turns no recursive call into a loop. On the JVM's default 1 MB thread stack a recursive walk throws `StackOverflowError` from about 500–2,000 levels on a cold first call and 6,000–17,000 once warmed up (OpenJDK 21 and 25). org.json, the W3C DOM, dom4j and StAX set no nesting limit of their own, Jackson before 2.15 none and 2.15+ 1,000 — on a cold JVM past the point the walk fails — and a `Map<String, Object>` tree is as deep as whatever built it. `StackOverflowError` is an `Error`, not an `Exception`: a `catch (Exception e)` around the call does not stop it, and the request or the thread dies with it. Thread a depth argument through `convertToColumns` and reject the value past a fixed maximum, configure the parser's nesting limit (`StreamReadConstraints.maxNestingDepth`, SnakeYAML's `setNestingDepthLimit`), or rewrite the descent with an explicit stack.
AC2 · Forms & labels· <TimePicker> field component without a label · ×1
<TimePicker> field component without a label tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/InputContextMenu.tsx:99— This UI-library field component has no label / aria-label / aria-labelledby / id at this call site, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id, even one the component sets on what it renders, names nothing until a label points at it) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
AC3 · Page structure· Heading level jumps from h2 to h6 · ×1
Heading level jumps from h2 to h6 tools-manage/invocationlab-rpcpostman-view/src/views/error-page/401.vue:12— Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
AC3 · Page structure· Heading level jumps from h1 to h3 · ×1
Heading level jumps from h1 to h3 tools-manage/tools-manage-view/src/components/HelloWorld.vue:10— Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
Empty <h3> heading tools-manage/tools-manage-view/src/components/WelcomeItem.vue:7— An empty heading appears in the document outline announced with no text. Give the heading text, or remove it if it's decorative.
AXI1 · Runtime container hardening· Container process runs as root · ×1
Container process runs as root: wd-runtime-app — 'wd-runtime-app' (wd-runtime-app:scan) runs as uid 0 — no user was specified, or one resolving to root was. Observed on the running container, which is the only place the answer is settled: an image's own USER, a base image's inherited one and a compose override are all invisible to a REDACTED reader. Advisory evidence for CRA Annex I (2)(b).
AXR1 · Runtime accessibility (rendered)· WCAG 1.4.3 reproducibly failed in a rendered surface · ×1
WCAG 1.4.3 reproducibly failed in a rendered surface — axe-core rule(s) color-contrast failed on: #disclaimer, a:nth-child(3), a[href$="docs/"], a[href$="search"], footer. Runtime evidence (advisory — not scored); fix and re-scan to verify it clears.
AXR1 · Runtime accessibility (rendered)· WCAG 3.1.1 reproducibly failed in a rendered surface · ×1
WCAG 3.1.1 reproducibly failed in a rendered surface — axe-core rule(s) html-has-lang failed on: html. Runtime evidence (advisory — not scored); fix and re-scan to verify it clears.
(anonymous) (cyclomatic 188) spring-embed-arthas/src/main/webapp/index.js:8558— (anonymous) has cyclomatic complexity 188 (threshold 15). Most of this is not in the body itself: 1 of the 188 points is its own statement and the rest belongs to 79 function items inside it that branch (displayValue, handleKeydown, parsedValue, …). 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: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
(anonymous) (cyclomatic 145) spring-embed-arthas/src/main/webapp/index.js:6933— (anonymous) has cyclomatic complexity 145 (threshold 15). Most of this is not in the body itself: 1 of the 145 points is its own statement and the rest belongs to 62 function items inside it that branch (setData, updateAllSelected, updateCurrentRow, …). 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: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
useVersionStore.useVersionStore (cyclomatic 144) tools-manage/invocationlab-erd-online-view/src/store/version/useVersionStore.tsx:82— useVersionStore.useVersionStore has cyclomatic complexity 144 (threshold 15). Most of this is not in the body itself: 1 of the 144 points is its own statement and the rest belongs to 63 function literals inside it that branch (lines 499, 823, 765, …). 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.
G6Relation._renderRelation (cyclomatic 128) tools-manage/invocationlab-erd-online-view/src/pages/design/relation/g6.js:479— G6Relation._renderRelation has cyclomatic complexity 128 (threshold 15). Of this number, 25 points are the body's own statements and 103 belong to 28 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.
(anonymous) (cyclomatic 120) spring-embed-arthas/src/main/webapp/index.js:3028— (anonymous) has cyclomatic complexity 120 (threshold 15). Most of this is not in the body itself: 1 of the 120 points is its own statement and the rest belongs to 55 function items inside it that branch ((anonymous)::arrow, (anonymous)::parse, (anonymous)::value, …). 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: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
(anonymous) (cyclomatic 97) spring-embed-arthas/src/main/webapp/index.js:10277— (anonymous) has cyclomatic complexity 97 (threshold 15). Most of this is not in the body itself: 1 of the 97 points is its own statement and the rest belongs to 53 function items inside it that branch (value, isValidValue, handleRangePick, …). 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: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
(anonymous) (cyclomatic 88) spring-embed-arthas/src/main/webapp/index.js:13248— (anonymous) has cyclomatic complexity 88 (threshold 15). Most of this is not in the body itself: 3 of the 88 points are its own statements and the rest belongs to 53 function items inside it that branch (l::_setCheckedKeys, l::filter::n, a function literal at line 13330, …). 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: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
(anonymous) (cyclomatic 83) spring-embed-arthas/src/main/webapp/index.js:7593— (anonymous) has cyclomatic complexity 83 (threshold 15). Most of this is not in the body itself: 1 of the 83 points is its own statement and the rest belongs to 55 function items inside it that branch (handleMouseMove, handleSortClick, handleFilterClick, …). 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: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
(anonymous) (cyclomatic 80) spring-embed-arthas/src/main/webapp/index.js:8282— (anonymous) has cyclomatic complexity 80 (threshold 15). Most of this is not in the body itself: 1 of the 80 points is its own statement and the rest belongs to 46 function items inside it that branch (created, p, a function literal at line 8460, …). 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: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
(anonymous) (cyclomatic 76) spring-embed-arthas/src/main/webapp/index.js:3586— (anonymous) has cyclomatic complexity 76 (threshold 15). Most of this is not in the body itself: 1 of the 76 points is its own statement and the rest belongs to 66 function items inside it that branch ((anonymous)::o, (anonymous)::f, (anonymous)::unobserve, …). 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: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
(anonymous) (cyclomatic 74) spring-embed-arthas/src/main/webapp/index.js:13038— (anonymous) has cyclomatic complexity 74 (threshold 15). Most of this is not in the body itself: 1 of the 74 points is its own statement and the rest belongs to 44 function items inside it that branch (a function literal at line 13219, a function literal at line 13234, handleKeydown, …). 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: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
access.access (cyclomatic 71) tools-manage/invocationlab-erd-online-view/src/access.ts:11— access.access has cyclomatic complexity 71 (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.
(anonymous) (cyclomatic 65) spring-embed-arthas/src/main/webapp/index.js:9155— (anonymous) has cyclomatic complexity 65 (threshold 15). Most of this is not in the body itself: 1 of the 65 points is its own statement and the rest belongs to 53 function items inside it that branch (handleKeydown, emit, selectionMode, …). 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: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
(anonymous) (cyclomatic 60) spring-embed-arthas/src/main/webapp/index.js:7377— (anonymous) has cyclomatic complexity 60 (threshold 15). Most of this is not in the body itself: 3 of the 60 points are its own statements and the rest belongs to 46 function items inside it that branch (handleCellMouseEnter, getRowClass, a function literal at line 7387, …). 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: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
(anonymous) (cyclomatic 59) spring-embed-arthas/src/main/webapp/index.js:16633— (anonymous) has cyclomatic complexity 59 (threshold 15). Most of this is not in the body itself: 1 of the 59 points is its own statement and the rest belongs to 36 function items inside it that branch (render::(anonymous)::(anonymous)::keydown, a function literal at line 16732, get::e, …). 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: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
relation2file.renderRelation (cyclomatic 58) tools-manage/invocationlab-erd-online-view/src/utils/relation2file.js:160— relation2file.renderRelation has cyclomatic complexity 58 (threshold 15). Of this number, 24 points are the body's own statements and 34 belong to 9 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.
(anonymous) (cyclomatic 57) spring-embed-arthas/src/main/webapp/index.js:1833— (anonymous) has cyclomatic complexity 57 (threshold 15). Most of this is not in the body itself: 1 of the 57 points is its own statement and the rest belongs to 36 function items inside it that branch (getValidCurrentPage, render, internalPageCount, …). 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: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
(anonymous) (cyclomatic 53) spring-embed-arthas/src/main/webapp/index.js:14133— (anonymous) has cyclomatic complexity 53 (threshold 15). Most of this is not in the body itself: 1 of the 53 points is its own statement and the rest belongs to 31 function items inside it that branch (setValues, stops, mounted, …). 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: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
(anonymous) (cyclomatic 52) spring-embed-arthas/src/main/webapp/index.js:6614— (anonymous) 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 43 function items inside it that branch (fixedHeight, a function literal at line 6697, resizeListener, …). 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: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
vue.enter (cyclomatic 50) spring-embed-arthas/src/main/webapp/vue.js:8116— vue.enter has cyclomatic complexity 50 (threshold 15). Of this number, 38 points are the body's own statements and 12 belong to 3 function literals inside it that branch. 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.
(anonymous) (cyclomatic 50) spring-embed-arthas/src/main/webapp/index.js:15608— (anonymous) has cyclomatic complexity 50 (threshold 15). Most of this is not in the body itself: 1 of the 50 points is its own statement and the rest belongs to 26 function items inside it that branch (handleKey, showDecimalIcon, getValueFromMap, …). 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: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
index.Query (cyclomatic 49) tools-manage/invocationlab-erd-online-view/src/pages/design/query/index.tsx:26— index.Query has cyclomatic complexity 49 (threshold 15). Most of this is not in the body itself: 6 of the 49 points are its own statements and the rest belongs to 17 function items inside it that branch (onKeyDown, run, a function literal at line 128, …). 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.
(anonymous) (cyclomatic 46) spring-embed-arthas/src/main/webapp/index.js:2938— (anonymous) has cyclomatic complexity 46 (threshold 15). Most of this is not in the body itself: 2 of the 46 points are its own statements and the rest belongs to 19 function items inside it that branch (openModal, closeModal, a function literal at line 3022, …). 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: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
(anonymous) (cyclomatic 45) spring-embed-arthas/src/main/webapp/index.js:1350— (anonymous) has cyclomatic complexity 45 (threshold 15). Most of this is not in the body itself: 3 of the 45 points are its own statements and the rest belongs to 16 function items inside it that branch (orderBy, a function literal at line 1368, getRowIdentity, …). 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: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
(anonymous) (cyclomatic 43) spring-embed-arthas/src/main/webapp/index.js:11140— (anonymous) has cyclomatic complexity 43 (threshold 15). Most of this is not in the body itself: 3 of the 43 points are its own statements and the rest belongs to 17 function items inside it that branch (g, e, a function literal at line 11150, …). 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: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
(anonymous) (cyclomatic 42) spring-embed-arthas/src/main/webapp/index.js:2636— (anonymous) has cyclomatic complexity 42 (threshold 15). Most of this is not in the body itself: 1 of the 42 points is its own statement and the rest belongs to 29 function items inside it that branch (calcIconOffset, showClear, setCurrentValue, …). 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 file is where this pass's cyclomatic complexity CONCENTRATES: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
vue.parseFilters (cyclomatic 40) spring-embed-arthas/src/main/webapp/vue.js:6829— vue.parseFilters has cyclomatic complexity 40 (threshold 15). Of this number, 39 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
profileSlice.ProfileSlice (cyclomatic 38) tools-manage/invocationlab-erd-online-view/src/store/project/profileSlice.tsx:48— profileSlice.ProfileSlice has cyclomatic complexity 38 (threshold 15). Most of this is not in the body itself: 1 of the 38 points is its own statement and the rest belongs to 19 function literals inside it that branch (lines 259, 178, 74, …). 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.
ConstructSqlFormMongoDB.ConstructSqlForm (cyclomatic 36) tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/ConstructSqlFormMongoDB.tsx:22— ConstructSqlFormMongoDB.ConstructSqlForm has cyclomatic complexity 36 (threshold 15). Most of this is not in the body itself: 1 of the 36 points is its own statement and the rest belongs to 12 function items inside it that branch (getModifiedConditionValue, constructSql, getColumnValueOfType, …). 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.
QueryResult.QueryResult (cyclomatic 36) tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/QueryResult.tsx:25— QueryResult.QueryResult has cyclomatic complexity 36 (threshold 15). Most of this is not in the body itself: 2 of the 36 points are its own statements and the rest belongs to 18 function items inside it that branch (getColumns, a function literal at line 83, a function literal at line 137, …). 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.
json2code.generateUpdateSql (cyclomatic 36) tools-manage/invocationlab-erd-online-view/src/utils/json2code.ts:201— json2code.generateUpdateSql has cyclomatic complexity 36 (threshold 15). Of this number, 19 points are the body's own statements and 17 belong to 7 function items inside it that branch. 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.
ConstructSqlForm.ConstructSqlForm::getColumnValueOfType (cyclomatic 35) tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/ConstructSqlForm.tsx:151— ConstructSqlForm.ConstructSqlForm::getColumnValueOfType 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.
(anonymous) (cyclomatic 34) spring-embed-arthas/src/main/webapp/index.js:11010— (anonymous) has cyclomatic complexity 34 (threshold 15). Most of this is not in the body itself: 1 of the 34 points is its own statement and the rest belongs to 21 function items inside it that branch (mounted, handleDocumentClick, s, …). 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: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
lexter.Parser (cyclomatic 33) tools-manage/invocationlab-erd-online-view/src/components/CodeEditor/parser/lexter.js:27— lexter.Parser 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.
(anonymous) (cyclomatic 33) spring-embed-arthas/src/main/webapp/index.js:5376— (anonymous) has cyclomatic complexity 33 (threshold 15). Most of this is not in the body itself: 1 of the 33 points is its own statement and the rest belongs to 25 function items inside it that branch (render, concatClass, handleClosePopper, …). 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: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
(anonymous) (cyclomatic 32) spring-embed-arthas/src/main/webapp/index.js:4548— (anonymous) has cyclomatic complexity 32 (threshold 15). Most of this is not in the body itself: 1 of the 32 points is its own statement and the rest belongs to 27 function items inside it that branch (handleItemKeyDown, initEvent, handleTriggerKeyDown, …). 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: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
vue.resolveAsyncComponent (cyclomatic 31) spring-embed-arthas/src/main/webapp/vue.js:3618— vue.resolveAsyncComponent has cyclomatic complexity 31 (threshold 15). Of this number, 22 points are the body's own statements and 9 belong to 5 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.
vue.parseHTML (cyclomatic 31) spring-embed-arthas/src/main/webapp/vue.js:9286— vue.parseHTML has cyclomatic complexity 31 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: 2 other methods here (vue.parseHTML::handleStartTag, vue.parseHTML::parseEndTag) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
vue.processAttrs (cyclomatic 30) spring-embed-arthas/src/main/webapp/vue.js:10271— vue.processAttrs has cyclomatic complexity 30 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
TableCodeShow.TableCodeShow (cyclomatic 30) tools-manage/invocationlab-erd-online-view/src/pages/design/table/component/table/TableCodeShow.tsx:20— TableCodeShow.TableCodeShow has cyclomatic complexity 30 (threshold 15). Most of this is not in the body itself: 5 of the 30 points are its own statements and the rest belongs to 4 function items inside it that branch (a function literal at line 59, getTableCode, a function literal at line 23, …). 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.
GroupPermission.GroupPermission (cyclomatic 30) tools-manage/invocationlab-erd-online-view/src/pages/project/group/component/GroupPermission.tsx:34— GroupPermission.GroupPermission has cyclomatic complexity 30 (threshold 15). Most of this is not in the body itself: 3 of the 30 points are its own statements and the rest belongs to 13 function items inside it that branch (firstAllConfig, a function literal at line 143, firstCheckConfig, …). 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.
CompareVersion.CompareVersion (cyclomatic 29) tools-manage/invocationlab-erd-online-view/src/components/dialog/version/CompareVersion.tsx:21— CompareVersion.CompareVersion has cyclomatic complexity 29 (threshold 15). Most of this is not in the body itself: 13 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 115, execSQL, a function literal at line 108, …). 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.
(anonymous) (cyclomatic 29) spring-embed-arthas/src/main/webapp/index.js:9353— (anonymous) has cyclomatic complexity 29 (threshold 15). Most of this is not in the body itself: 1 of the 29 points is its own statement and the rest belongs to 21 function items inside it that branch (value, amPmMode, handleKeydown, …). 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: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
vue.leave (cyclomatic 28) spring-embed-arthas/src/main/webapp/vue.js:8267— vue.leave has cyclomatic complexity 28 (threshold 15). Most of this is not in the body itself: 12 of the 28 points are its own statements and the rest belongs to 3 function items inside it that branch (performLeave, a function literal at line 8311, a function literal at line 8350). 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.
(anonymous) (cyclomatic 28) spring-embed-arthas/src/main/webapp/index.js:10678— (anonymous) has cyclomatic complexity 28 (threshold 15). Most of this is not in the body itself: 1 of the 28 points is its own statement and the rest belongs to 22 function items inside it that branch (items, handleMenuEnter, n, …). 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: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
vue._createElement (cyclomatic 27) spring-embed-arthas/src/main/webapp/vue.js:3363— vue._createElement has cyclomatic complexity 27 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
vue.updateDOMProps (cyclomatic 26) spring-embed-arthas/src/main/webapp/vue.js:7594— vue.updateDOMProps has cyclomatic complexity 26 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
vue.processSlotContent (cyclomatic 26) spring-embed-arthas/src/main/webapp/vue.js:10108— vue.processSlotContent has cyclomatic complexity 26 (threshold 15). Of this number, 25 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
json2code.getTemplateString (cyclomatic 26) tools-manage/invocationlab-erd-online-view/src/utils/json2code.ts:14— json2code.getTemplateString has cyclomatic complexity 26 (threshold 15). Most of this is not in the body itself: 1 of the 26 points is its own statement and the rest belongs to 11 function items inside it that branch (getIndex, a function literal at line 59, join, …). 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.
modulesSlice.ModulesSlice (cyclomatic 25) tools-manage/invocationlab-erd-online-view/src/store/project/modulesSlice.tsx:57— modulesSlice.ModulesSlice has cyclomatic complexity 25 (threshold 15). Most of this is not in the body itself: 1 of the 25 points is its own statement and the rest belongs to 13 function literals inside it that branch (lines 109, 206, 272, …). 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.
vue.genElement (cyclomatic 24) spring-embed-arthas/src/main/webapp/vue.js:10948— vue.genElement 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.
exportSlice.ExportSlice (cyclomatic 24) tools-manage/invocationlab-erd-online-view/src/store/project/exportSlice.tsx:35— exportSlice.ExportSlice has cyclomatic complexity 24 (threshold 15). Most of this is not in the body itself: 1 of the 24 points is its own statement and the rest belongs to 11 function literals inside it that branch (lines 39, 202, 123, …). 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.
renderRelation::draw (cyclomatic 24) tools-manage/invocationlab-erd-online-view/src/utils/relation2file.js:362— renderRelation::draw has cyclomatic complexity 24 (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.
_renderRelation::draw (cyclomatic 24) tools-manage/invocationlab-erd-online-view/src/pages/design/relation/g6.js:692— _renderRelation::draw has cyclomatic complexity 24 (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.
vue.defineReactive$$1 (cyclomatic 22) spring-embed-arthas/src/main/webapp/vue.js:1014— vue.defineReactive$$1 has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 9 of the 22 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 1052, 1039). 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.
vue.addHandler (cyclomatic 22) spring-embed-arthas/src/main/webapp/vue.js:6988— vue.addHandler has cyclomatic complexity 22 (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.
StrUtils.getStringValue (cyclomatic 22) b2c-parent/b2c-bytecode/src/main/java/org/javamaster/b2c/bytecode/utils/StrUtils.java:11— StrUtils.getStringValue 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.
vue.createPatchFunction.patch (cyclomatic 21) spring-embed-arthas/src/main/webapp/vue.js:6458— vue.createPatchFunction.patch has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
vue.genData$2 (cyclomatic 21) spring-embed-arthas/src/main/webapp/vue.js:11099— vue.genData$2 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.
select.divideTokens (cyclomatic 21) tools-manage/invocationlab-erd-online-view/src/components/CodeEditor/parser/select.js:45— select.divideTokens has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
DataTable.DataTable (cyclomatic 21) tools-manage/invocationlab-erd-online-view/src/components/LeftContent/DesignLeftContent/component/DataTable.tsx:141— DataTable.DataTable has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 4 of the 21 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 218, a function literal at line 205, a function literal at line 232, …). 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.
MetaDataSearch.MetaDataSearch (cyclomatic 21) tools-manage/invocationlab-erd-online-view/src/components/LeftContent/DesignLeftContent/component/MetaDataSearch.tsx:40— MetaDataSearch.MetaDataSearch has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 1 of the 21 points is its own statement and the rest belongs to 7 function literals inside it that branch (lines 102, 115, 162, …). 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.
FieldMultiSelect.FieldMultiSelect (cyclomatic 21) tools-manage/invocationlab-erd-online-view/src/pages/design/table/component/table/FieldMultiSelect.tsx:35— FieldMultiSelect.FieldMultiSelect has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 6 of the 21 points are its own statements and the rest belongs to 9 function items inside it that branch (deselectFilm, maybeDeleteCreatedFilmFromArrays, maybeAddCreatedFilmToArrays, …). 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.
sqlParseTool.parseOneSource (cyclomatic 20) REDACTED:144— sqlParseTool.parseOneSource has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
DatabaseSetUp.DatabaseSetUp (cyclomatic 20) tools-manage/invocationlab-erd-online-view/src/pages/design/setting/component/DatabaseSetUp.tsx:23— DatabaseSetUp.DatabaseSetUp has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 7 of the 20 points are its own statements and the rest belongs to 8 function items inside it that branch (a function literal at line 272, a function literal at line 24, a function literal at line 90, …). 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.
(anonymous) (cyclomatic 20) spring-embed-arthas/src/main/webapp/index.js:7993— (anonymous) has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 1 of the 20 points is its own statement and the rest belongs to 17 function items inside it that branch (isCellHidden, render, a function literal at line 8029, …). 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: spring-embed-arthas/src/main/webapp/index.js holds 100 of the 165 methods over the threshold — including the worst — and 2217 of the 3130 points over it (71%), 8.9× the next-largest file (spring-embed-arthas/src/main/webapp/vue.js at 249). 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.
index.DesignLayout (cyclomatic 19) tools-manage/invocationlab-erd-online-view/src/layouts/DesignLayout/index.tsx:84— index.DesignLayout has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 6 of the 19 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 120, 244, 202, …). 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.
vue.normalizeArrayChildren (cyclomatic 18) spring-embed-arthas/src/main/webapp/vue.js:2376— vue.normalizeArrayChildren 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.
vue.normalizeScopedSlots (cyclomatic 18) spring-embed-arthas/src/main/webapp/vue.js:2545— vue.normalizeScopedSlots 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.
vue.parse::closeElement (cyclomatic 18) spring-embed-arthas/src/main/webapp/vue.js:9627— vue.parse::closeElement 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.
ExcelReader.read (cyclomatic 18) handypoi-excel/src/main/java/cn/com/bluemoon/handypoi/excel/resolve/ExcelReader.java:118— ExcelReader.read has cyclomatic complexity 18 (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.
vue.resolveSlots (cyclomatic 17) spring-embed-arthas/src/main/webapp/vue.js:2499— vue.resolveSlots 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: vue.eventsMixin (cyclomatic 18) 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.
vue.bindObjectProps (cyclomatic 17) spring-embed-arthas/src/main/webapp/vue.js:2752— vue.bindObjectProps has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 5 of the 17 points are its own statements and the rest belongs to one function item inside it that branches (loop). 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: vue.eventsMixin (cyclomatic 18) 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.
vue.updateChildComponent (cyclomatic 17) spring-embed-arthas/src/main/webapp/vue.js:4092— vue.updateChildComponent has cyclomatic complexity 17 (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. This is NOT this file's highest cyclomatic complexity: vue.eventsMixin (cyclomatic 18) 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.
vue.updateAttrs (cyclomatic 17) spring-embed-arthas/src/main/webapp/vue.js:6687— vue.updateAttrs 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: vue.eventsMixin (cyclomatic 18) 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.
index.CodeEditor (cyclomatic 17) tools-manage/invocationlab-erd-online-view/src/components/CodeEditor/index.tsx:78— index.CodeEditor has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 8 of the 17 points are its own statements and the rest belongs to 5 function items inside it that branch (resolveSql, a function literal at line 122, a function literal at line 154, …). 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.
DatabaseSetUp.DatabaseSetUp (cyclomatic 17) REDACTED:25— DatabaseSetUp.DatabaseSetUp has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 7 of the 17 points are its own statements and the rest belongs to 7 function items inside it that branch (a function literal at line 26, a function literal at line 88, a function literal at line 174, …). 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.
index.JExcel (cyclomatic 17) tools-manage/invocationlab-erd-online-view/src/pages/JExcel/index.tsx:22— index.JExcel has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 1 of the 17 points is its own statement and the rest belongs to 6 function items inside it that branch (saveValidData, a function literal at line 221, a function literal at line 129, …). 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.
G6Relation._updateEdges (cyclomatic 17) tools-manage/invocationlab-erd-online-view/src/pages/design/relation/g6.js:324— G6Relation._updateEdges has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 1 of the 17 points is its own statement and the rest belongs to 3 function literals inside it that branch (lines 326, 338, 340). 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.
vue.genHandler (cyclomatic 16) spring-embed-arthas/src/main/webapp/vue.js:10804— vue.genHandler 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: vue.eventsMixin (cyclomatic 18) 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.
vue.Vue.$mount (cyclomatic 16) spring-embed-arthas/src/main/webapp/vue.js:11878— vue.Vue.$mount 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: vue.eventsMixin (cyclomatic 18) 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.
projectJsonSlice.ProjectJsonSlice (cyclomatic 16) tools-manage/invocationlab-erd-online-view/src/store/project/projectJsonSlice.tsx:38— projectJsonSlice.ProjectJsonSlice has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 5 function literals inside it that branch (lines 71, 39, 55, …). 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.
RedisServiceImpl.getValue (cyclomatic 16) tools-manage/tools-manage-admin/src/main/java/org/javamaster/spring/tools/manage/service/impl/RedisServiceImpl.java:209— RedisServiceImpl.getValue 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.
useVersionStore.useVersionStore (cognitive 216) tools-manage/invocationlab-erd-online-view/src/store/version/useVersionStore.tsx:82— useVersionStore.useVersionStore has cognitive complexity 216 (threshold 15). Drivers by points: if/else 110 (157 pts), boolean chains 51, ternaries 3 (6 pts), match/switch 2 (nesting depth added 50). None of this is in the body itself: all 216 points belong to 63 function literals inside it that branch (lines 499, 749, 765, …). 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.
(anonymous) (cognitive 183) spring-embed-arthas/src/main/webapp/index.js:8558— (anonymous) has cognitive complexity 183 (threshold 15). Drivers by points: boolean chains 112, ternaries 52, if/else 12 (16 pts), loops 2 (3 pts) (nesting depth added 5). None of this is in the body itself: all 183 points belong to 79 function items inside it that branch (displayValue, handleKeydown, parsedValue, …). 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.
G6Relation._renderRelation (cognitive 173) tools-manage/invocationlab-erd-online-view/src/pages/design/relation/g6.js:479— G6Relation._renderRelation has cognitive complexity 173 (threshold 15). Drivers by points: if/else 65 (108 pts), boolean chains 50, ternaries 10 (13 pts), loops 1 (2 pts) (nesting depth added 47). Of this number, 20 points are the body's own statements and 153 belong to 28 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.
(anonymous) (cognitive 131) spring-embed-arthas/src/main/webapp/index.js:3028— (anonymous) has cognitive complexity 131 (threshold 15). Drivers by points: boolean chains 54, ternaries 37 (47 pts), if/else 20 (24 pts), loops 4 (6 pts) (nesting depth added 16). None of this is in the body itself: all 131 points belong to 55 function items inside it that branch ((anonymous)::parse, (anonymous)::arrow, (anonymous)::value, …). 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.
vue.processAttrs (cognitive 94) spring-embed-arthas/src/main/webapp/vue.js:10271— vue.processAttrs has cognitive complexity 94 (threshold 15). Drivers by points: if/else 24 (86 pts), boolean chains 7, loops 1 (nesting depth added 62). 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.
vue.parseHTML (cognitive 82) spring-embed-arthas/src/main/webapp/vue.js:9286— vue.parseHTML has cognitive complexity 82 (threshold 15). Drivers by points: if/else 43 (112 pts), boolean chains 19, loops 6 (12 pts), ternaries 1 (2 pts) (nesting depth added 76). 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 shape REPEATS in the file: 2 other methods here (vue.parseHTML::handleStartTag, vue.parseHTML::parseEndTag) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
(anonymous) (cognitive 82) spring-embed-arthas/src/main/webapp/index.js:13038— (anonymous) has cognitive complexity 82 (threshold 15). Drivers by points: ternaries 20 (37 pts), boolean chains 29, if/else 14, error handling 1, loops 1 (nesting depth added 17). None of this is in the body itself: all 82 points belong to 44 function items inside it that branch (a function literal at line 13219, a function literal at line 13234, handleKeydown, …). 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.
(anonymous) (cognitive 79) spring-embed-arthas/src/main/webapp/index.js:8282— (anonymous) has cognitive complexity 79 (threshold 15). Drivers by points: boolean chains 52, ternaries 18 (20 pts), if/else 3 (4 pts), loops 3 (nesting depth added 3). None of this is in the body itself: all 79 points belong to 46 function items inside it that branch (created, p, created::renderCell, …). 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.
(anonymous) (cognitive 77) spring-embed-arthas/src/main/webapp/index.js:3586— (anonymous) has cognitive complexity 77 (threshold 15). Drivers by points: boolean chains 42, if/else 15 (18 pts), ternaries 13, loops 4 (nesting depth added 3). None of this is in the body itself: all 77 points belong to 66 function items inside it that branch ((anonymous)::o, (anonymous)::unobserve, (anonymous)::f, …). 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.
(anonymous) (cognitive 76) spring-embed-arthas/src/main/webapp/index.js:9155— (anonymous) has cognitive complexity 76 (threshold 15). Drivers by points: ternaries 24 (31 pts), boolean chains 28, if/else 12 (15 pts), loops 2 (nesting depth added 10). None of this is in the body itself: all 76 points belong to 53 function items inside it that branch (emit, handleTimePick, handleKeydown, …). 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.
Parser (cognitive 74) tools-manage/invocationlab-erd-online-view/src/components/CodeEditor/parser/lexter.js:27— Parser has cognitive complexity 74 (threshold 15). Drivers by points: if/else 16 (37 pts), loops 7 (19 pts), ternaries 4 (12 pts), boolean chains 6 (nesting depth added 41). 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.
vue.createPatchFunction.patch (cognitive 71) spring-embed-arthas/src/main/webapp/vue.js:6458— vue.createPatchFunction.patch has cognitive complexity 71 (threshold 15). Drivers by points: if/else 17 (44 pts), loops 4 (22 pts), ternaries 1 (3 pts), boolean chains 2 (nesting depth added 47). 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.
access.access (cognitive 70) tools-manage/invocationlab-erd-online-view/src/access.ts:11— access.access has cognitive complexity 70 (threshold 15). Drivers by points: boolean chains 69, if/else 1. 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.
relation2file.renderRelation (cognitive 69) tools-manage/invocationlab-erd-online-view/src/utils/relation2file.js:160— relation2file.renderRelation has cognitive complexity 69 (threshold 15). Drivers by points: if/else 22 (32 pts), boolean chains 24, ternaries 9 (11 pts), loops 1 (2 pts) (nesting depth added 13). Of this number, 19 points are the body's own statements and 50 belong to 9 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.
(anonymous) (cognitive 68) spring-embed-arthas/src/main/webapp/index.js:12082— (anonymous) has cognitive complexity 68 (threshold 15). Drivers by points: boolean chains 43, ternaries 8 (10 pts), loops 7 (8 pts), if/else 5 (7 pts) (nesting depth added 5). Most of this is not in the body itself: 14 of the 68 points are its own statements and the rest belongs to 24 function items inside it that branch (X, J, stringify, …). 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.
(anonymous) (cognitive 63) spring-embed-arthas/src/main/webapp/index.js:7377— (anonymous) has cognitive complexity 63 (threshold 15). Drivers by points: boolean chains 29, ternaries 18 (22 pts), if/else 9 (12 pts) (nesting depth added 7). Most of this is not in the body itself: 2 of the 63 points are its own statements and the rest belongs to 46 function items inside it that branch (handleCellMouseEnter, store.states.currentRow, getSpan, …). 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.
(anonymous) (cognitive 58) spring-embed-arthas/src/main/webapp/index.js:15608— (anonymous) has cognitive complexity 58 (threshold 15). Drivers by points: boolean chains 28, ternaries 16 (23 pts), if/else 4 (5 pts), loops 2 (nesting depth added 8). None of this is in the body itself: all 58 points belong to 26 function items inside it that branch (handleKey, setCurrentValue, showDecimalIcon, …). 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.
vue.resolveAsyncComponent (cognitive 56) spring-embed-arthas/src/main/webapp/vue.js:3618— vue.resolveAsyncComponent has cognitive complexity 56 (threshold 15). Drivers by points: if/else 20 (46 pts), boolean chains 6, loops 1 (2 pts), ternaries 1 (2 pts) (nesting depth added 28). Of this number, 41 points are the body's own statements and 15 belong to 5 function items inside it that branch. 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.
(anonymous) (cognitive 56) spring-embed-arthas/src/main/webapp/index.js:1833— (anonymous) has cognitive complexity 56 (threshold 15). Drivers by points: boolean chains 31, ternaries 19 (20 pts), if/else 4 (5 pts) (nesting depth added 2). None of this is in the body itself: all 56 points belong to 36 function items inside it that branch (getValidCurrentPage, render, internalPageCount, …). 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.
vue.parseFilters (cognitive 55) spring-embed-arthas/src/main/webapp/vue.js:6829— vue.parseFilters has cognitive complexity 55 (threshold 15). Drivers by points: if/else 18 (38 pts), boolean chains 7, loops 3 (7 pts), match/switch 1 (3 pts) (nesting depth added 26). Of this number, 54 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ConstructSqlForm.ConstructSqlForm::getColumnValueOfType (cognitive 55) tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/ConstructSqlForm.tsx:151— ConstructSqlForm.ConstructSqlForm::getColumnValueOfType has cognitive complexity 55 (threshold 15). Drivers by points: ternaries 12 (24 pts), if/else 17 (19 pts), boolean chains 6, loops 2 (6 pts) (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
(anonymous) (cognitive 55) spring-embed-arthas/src/main/webapp/index.js:502— (anonymous) has cognitive complexity 55 (threshold 15). Drivers by points: boolean chains 23, ternaries 21, loops 4 (6 pts), if/else 5 (nesting depth added 2). None of this is in the body itself: all 55 points belong to 45 function items inside it that branch (getRangeHours, a function literal at line 571, getDayCountOfMonth, …). 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.
index.Query (cognitive 53) tools-manage/invocationlab-erd-online-view/src/pages/design/query/index.tsx:26— index.Query has cognitive complexity 53 (threshold 15). Drivers by points: if/else 30 (34 pts), boolean chains 18, ternaries 1 (nesting depth added 4). Most of this is not in the body itself: 5 of the 53 points are its own statements and the rest belongs to 17 function items inside it that branch (onKeyDown, run, a function literal at line 80, …). 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.
vue.enter (cognitive 52) spring-embed-arthas/src/main/webapp/vue.js:8116— vue.enter has cognitive complexity 52 (threshold 15). Drivers by points: if/else 14 (21 pts), boolean chains 20, ternaries 9 (10 pts), loops 1 (nesting depth added 8). Of this number, 37 points are the body's own statements and 15 belong to 3 function literals 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.
(anonymous) (cognitive 49) spring-embed-arthas/src/main/webapp/index.js:5119— (anonymous) has cognitive complexity 49 (threshold 15). Drivers by points: boolean chains 33, ternaries 11, if/else 3 (4 pts), loops 1 (nesting depth added 1). None of this is in the body itself: all 49 points belong to 40 function items inside it that branch (render, titleStyle, isFirstLevel, …). 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.
(anonymous) (cognitive 46) spring-embed-arthas/src/main/webapp/index.js:11140— (anonymous) has cognitive complexity 46 (threshold 15). Drivers by points: boolean chains 22, ternaries 14 (19 pts), if/else 3 (4 pts), loops 1 (nesting depth added 6). Most of this is not in the body itself: 2 of the 46 points are its own statements and the rest belongs to 17 function items inside it that branch (g, e, e, …). 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.
ConstructSqlFormMongoDB.ConstructSqlForm (cognitive 45) tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/ConstructSqlFormMongoDB.tsx:22— ConstructSqlFormMongoDB.ConstructSqlForm has cognitive complexity 45 (threshold 15). Drivers by points: if/else 24 (26 pts), boolean chains 9, ternaries 4 (8 pts), loops 1 (2 pts) (nesting depth added 7). None of this is in the body itself: all 45 points belong to 12 function items inside it that branch (getColumnValueOfType, getModifiedConditionValue, constructSql, …). 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.
(anonymous) (cognitive 44) spring-embed-arthas/src/main/webapp/index.js:5581— (anonymous) has cognitive complexity 44 (threshold 15). Drivers by points: boolean chains 29, if/else 9 (10 pts), ternaries 5 (nesting depth added 1). None of this is in the body itself: all 44 points belong to 25 function items inside it that branch (handler, setCurrentValue, inputNumberSize, …). 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.
parseOneSource (cognitive 44) REDACTED:144— parseOneSource has cognitive complexity 44 (threshold 15). Drivers by points: if/else 16 (35 pts), loops 2 (5 pts), boolean chains 4 (nesting depth added 22). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
vue.updateDOMProps (cognitive 43) spring-embed-arthas/src/main/webapp/vue.js:7594— vue.updateDOMProps has cognitive complexity 43 (threshold 15). Drivers by points: if/else 11 (22 pts), loops 4 (8 pts), boolean chains 7, error handling 1 (3 pts), ternaries 1 (3 pts) (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
(anonymous) (cognitive 42) spring-embed-arthas/src/main/webapp/index.js:6240— (anonymous) has cognitive complexity 42 (threshold 15). Drivers by points: boolean chains 25, ternaries 12 (13 pts), if/else 2 (3 pts), loops 1 (nesting depth added 2). None of this is in the body itself: all 42 points belong to 15 function items inside it that branch (set, isDisabled, handleChange, …). 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.
QueryResult.QueryResult (cognitive 41) tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/QueryResult.tsx:25— QueryResult.QueryResult has cognitive complexity 41 (threshold 15). Drivers by points: if/else 28 (31 pts), boolean chains 9, ternaries 1 (nesting depth added 3). Most of this is not in the body itself: 1 of the 41 points is its own statement and the rest belongs to 18 function items inside it that branch (getColumns, a function literal at line 241, a function literal at line 83, …). 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.
(anonymous) (cognitive 41) spring-embed-arthas/src/main/webapp/index.js:6074— (anonymous) has cognitive complexity 41 (threshold 15). Drivers by points: boolean chains 24, ternaries 12 (13 pts), if/else 2 (3 pts), loops 1 (nesting depth added 2). None of this is in the body itself: all 41 points belong to 16 function items inside it that branch (set, isDisabled, checkboxSize, …). 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.
profileSlice.ProfileSlice (cognitive 40) tools-manage/invocationlab-erd-online-view/src/store/project/profileSlice.tsx:48— profileSlice.ProfileSlice has cognitive complexity 40 (threshold 15). Drivers by points: if/else 20 (21 pts), boolean chains 17, ternaries 1 (2 pts) (nesting depth added 2). None of this is in the body itself: all 40 points belong to 19 function literals inside it that branch (lines 259, 74, 178, …). 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.
vue.processSlotContent (cognitive 39) spring-embed-arthas/src/main/webapp/vue.js:10108— vue.processSlotContent has cognitive complexity 39 (threshold 15). Drivers by points: if/else 15 (30 pts), boolean chains 9 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
select.divideTokens (cognitive 38) tools-manage/invocationlab-erd-online-view/src/components/CodeEditor/parser/select.js:45— select.divideTokens has cognitive complexity 38 (threshold 15). Drivers by points: if/else 17 (35 pts), loops 2, boolean chains 1 (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RpcPostmanServiceQueryController.newObj (cognitive 38) tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/controller/RpcPostmanServiceQueryController.kt:237— RpcPostmanServiceQueryController.newObj has cognitive complexity 38 (threshold 15). Drivers by points: if/else 13 (28 pts), error handling 3 (9 pts), loops 1 (nesting depth added 21). 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.
(anonymous) (cognitive 37) spring-embed-arthas/src/main/webapp/index.js:168— (anonymous) has cognitive complexity 37 (threshold 15). Drivers by points: if/else 10 (17 pts), boolean chains 8, loops 6, ternaries 6 (nesting depth added 7). None of this is in the body itself: all 37 points belong to 15 function items inside it that branch (a, valueEquals, getValueByPath, …). 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.
RedisServiceImpl.listKeys (cognitive 36) tools-manage/tools-manage-admin/src/main/java/org/javamaster/spring/tools/manage/service/impl/RedisServiceImpl.java:126— RedisServiceImpl.listKeys has cognitive complexity 36 (threshold 15). Drivers by points: if/else 9 (23 pts), loops 4 (10 pts), error handling 1 (3 pts) (nesting depth added 22). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GroupPermission.GroupPermission (cognitive 34) tools-manage/invocationlab-erd-online-view/src/pages/project/group/component/GroupPermission.tsx:34— GroupPermission.GroupPermission has cognitive complexity 34 (threshold 15). Drivers by points: if/else 15 (16 pts), boolean chains 11, ternaries 5 (7 pts) (nesting depth added 3). Most of this is not in the body itself: 2 of the 34 points are its own statements and the rest belongs to 13 function items inside it that branch (firstAllConfig, a function literal at line 143, firstCheckConfig, …). 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.
modulesSlice.ModulesSlice (cognitive 34) tools-manage/invocationlab-erd-online-view/src/store/project/modulesSlice.tsx:57— modulesSlice.ModulesSlice has cognitive complexity 34 (threshold 15). Drivers by points: if/else 19 (21 pts), boolean chains 8, loops 2 (4 pts), error handling 1 (nesting depth added 4). None of this is in the body itself: all 34 points belong to 13 function literals inside it that branch (lines 109, 206, 272, …). 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.
vue._createElement (cognitive 33) spring-embed-arthas/src/main/webapp/vue.js:3363— vue._createElement has cognitive complexity 33 (threshold 15). Drivers by points: if/else 18 (23 pts), boolean chains 10 (nesting depth added 5). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
(anonymous) (cognitive 33) spring-embed-arthas/src/main/webapp/index.js:5376— (anonymous) has cognitive complexity 33 (threshold 15). Drivers by points: boolean chains 22, ternaries 7 (8 pts), if/else 3 (nesting depth added 1). None of this is in the body itself: all 33 points belong to 25 function items inside it that branch (render, concatClass, handleClosePopper, …). 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.
DataTable.DataTable (cognitive 32) tools-manage/invocationlab-erd-online-view/src/components/LeftContent/DesignLeftContent/component/DataTable.tsx:141— DataTable.DataTable has cognitive complexity 32 (threshold 15). Drivers by points: if/else 10 (15 pts), ternaries 6 (13 pts), boolean chains 4 (nesting depth added 12). Most of this is not in the body itself: 3 of the 32 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 218, a function literal at line 245, a function literal at line 205, …). 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.
(anonymous) (cognitive 32) spring-embed-arthas/src/main/webapp/index.js:14485— (anonymous) has cognitive complexity 32 (threshold 15). Drivers by points: boolean chains 18, ternaries 7 (13 pts), if/else 1 (nesting depth added 6). None of this is in the body itself: all 32 points belong to 13 function items inside it that branch (install::bind, install::i, n, …). 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.
vue.normalizeArrayChildren (cognitive 31) spring-embed-arthas/src/main/webapp/vue.js:2376— vue.normalizeArrayChildren has cognitive complexity 31 (threshold 15). Drivers by points: if/else 11 (25 pts), boolean chains 5, loops 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
vue.leave (cognitive 31) spring-embed-arthas/src/main/webapp/vue.js:8267— vue.leave has cognitive complexity 31 (threshold 15). Drivers by points: if/else 14 (20 pts), boolean chains 10, ternaries 1 (nesting depth added 6). Most of this is not in the body itself: 12 of the 31 points are its own statements and the rest belongs to 3 function items inside it that branch (performLeave, a function literal at line 8350, a function literal at line 8311). 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.
vue.genHandler (cognitive 31) spring-embed-arthas/src/main/webapp/vue.js:10804— vue.genHandler has cognitive complexity 31 (threshold 15). Drivers by points: if/else 11 (19 pts), ternaries 3 (9 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
vue.Vue.$mount (cognitive 31) spring-embed-arthas/src/main/webapp/vue.js:11878— vue.Vue.$mount has cognitive complexity 31 (threshold 15). Drivers by points: if/else 12 (27 pts), boolean chains 4 (nesting depth added 15). 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.
RpcPostmanServiceQueryController.newObj (cognitive 31) tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/controller/RpcPostmanServiceQueryController.java:109— RpcPostmanServiceQueryController.newObj has cognitive complexity 31 (threshold 15). Drivers by points: ternaries 3 (13 pts), if/else 6 (9 pts), error handling 3 (8 pts), loops 1 (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
KafkaServiceImpl.getTopicMsgList (cognitive 30) tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/KafkaServiceImpl.java:418— KafkaServiceImpl.getTopicMsgList has cognitive complexity 30 (threshold 15). Drivers by points: if/else 10 (25 pts), loops 3 (5 pts) (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.
vue.generateCodeFrame (cognitive 29) spring-embed-arthas/src/main/webapp/vue.js:11593— vue.generateCodeFrame has cognitive complexity 29 (threshold 15). Drivers by points: if/else 7 (18 pts), ternaries 1 (5 pts), loops 2 (4 pts), boolean chains 2 (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.
(anonymous) (cognitive 29) spring-embed-arthas/src/main/webapp/index.js:11010— (anonymous) has cognitive complexity 29 (threshold 15). Drivers by points: boolean chains 23, ternaries 6. None of this is in the body itself: all 29 points belong to 21 function items inside it that branch (mounted, handleDocumentClick, s, …). 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.
vue.bindObjectProps (cognitive 28) spring-embed-arthas/src/main/webapp/vue.js:2752— vue.bindObjectProps has cognitive complexity 28 (threshold 15). Drivers by points: if/else 8 (18 pts), boolean chains 7, loops 1 (3 pts) (nesting depth added 12). Most of this is not in the body itself: 10 of the 28 points are its own statements and the rest belongs to one function item inside it that branches (loop). 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.
vue.genElement (cognitive 28) spring-embed-arthas/src/main/webapp/vue.js:10948— vue.genElement has cognitive complexity 28 (threshold 15). Drivers by points: if/else 11 (14 pts), boolean chains 9, ternaries 1 (3 pts), loops 1 (2 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CompareVersion.CompareVersion (cognitive 28) tools-manage/invocationlab-erd-online-view/src/components/dialog/version/CompareVersion.tsx:21— CompareVersion.CompareVersion has cognitive complexity 28 (threshold 15). Drivers by points: ternaries 15 (17 pts), boolean chains 9, if/else 2 (nesting depth added 2). Of this number, 14 points are the body's own statements and 14 belong to 5 function items inside it that branch. 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.
exportSlice.ExportSlice (cognitive 28) tools-manage/invocationlab-erd-online-view/src/store/project/exportSlice.tsx:35— exportSlice.ExportSlice has cognitive complexity 28 (threshold 15). Drivers by points: if/else 13 (14 pts), boolean chains 12, ternaries 1 (2 pts) (nesting depth added 2). None of this is in the body itself: all 28 points belong to 11 function literals inside it that branch (lines 39, 202, 123, …). 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.
json2code.getTemplateString (cognitive 28) tools-manage/invocationlab-erd-online-view/src/utils/json2code.ts:14— json2code.getTemplateString has cognitive complexity 28 (threshold 15). Drivers by points: if/else 11 (15 pts), boolean chains 5, loops 5, ternaries 3 (nesting depth added 4). None of this is in the body itself: all 28 points belong to 11 function items inside it that branch (getIndex, join, each, …). 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.
vue._update (cognitive 27) spring-embed-arthas/src/main/webapp/vue.js:6579— vue._update has cognitive complexity 27 (threshold 15). Drivers by points: if/else 10 (18 pts), loops 4 (7 pts), boolean chains 2 (nesting depth added 11). Of this number, 23 points are the body's own statements and 4 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.
json2code.generateUpdateSql (cognitive 27) tools-manage/invocationlab-erd-online-view/src/utils/json2code.ts:201— json2code.generateUpdateSql has cognitive complexity 27 (threshold 15). Drivers by points: boolean chains 23, if/else 3 (4 pts) (nesting depth added 1). Of this number, 18 points are the body's own statements and 9 belong to 7 function items inside it that branch. 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.
ExcelReader.read (cognitive 27) handypoi-excel/src/main/java/cn/com/bluemoon/handypoi/excel/resolve/ExcelReader.java:118— ExcelReader.read has cognitive complexity 27 (threshold 15). Drivers by points: if/else 18 (22 pts), error handling 4 (5 pts) (nesting depth added 5). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
(anonymous) (cognitive 27) spring-embed-arthas/src/main/webapp/index.js:10678— (anonymous) has cognitive complexity 27 (threshold 15). Drivers by points: boolean chains 13, ternaries 6, if/else 4 (5 pts), loops 2 (3 pts) (nesting depth added 2). None of this is in the body itself: all 27 points belong to 22 function items inside it that branch (items, handleMenuEnter, scrollDown, …). 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.
RedisServiceImpl.getValue (cognitive 26) tools-manage/tools-manage-admin/src/main/java/org/javamaster/spring/tools/manage/service/impl/RedisServiceImpl.java:209— RedisServiceImpl.getValue has cognitive complexity 26 (threshold 15). Drivers by points: if/else 12 (16 pts), ternaries 4 (10 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.
vue.defineReactive$$1 (cognitive 25) spring-embed-arthas/src/main/webapp/vue.js:1014— vue.defineReactive$$1 has cognitive complexity 25 (threshold 15). Drivers by points: if/else 10 (13 pts), boolean chains 10, ternaries 2 (nesting depth added 3). Most of this is not in the body itself: 8 of the 25 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 1052, 1039). 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.
vue.checkNode (cognitive 25) spring-embed-arthas/src/main/webapp/vue.js:11489— vue.checkNode has cognitive complexity 25 (threshold 15). Drivers by points: if/else 9 (19 pts), loops 2 (5 pts), boolean chains 1 (nesting depth added 13). 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.
lexter.vars (cognitive 25) tools-manage/invocationlab-erd-online-view/src/components/CodeEditor/parser/lexter.js:227— lexter.vars has cognitive complexity 25 (threshold 15). Drivers by points: if/else 8 (19 pts), match/switch 2 (4 pts), loops 1 (2 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ExcelWriterImpl.fillFooterInfo (cognitive 25) handypoi-excel/src/main/java/cn/com/bluemoon/handypoi/excel/resolve/ExcelWriter.java:246— ExcelWriterImpl.fillFooterInfo has cognitive complexity 25 (threshold 15). Drivers by points: if/else 7 (16 pts), loops 4 (9 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
vue.resolveInject (cognitive 24) spring-embed-arthas/src/main/webapp/vue.js:2456— vue.resolveInject has cognitive complexity 24 (threshold 15). Drivers by points: if/else 6 (16 pts), loops 2 (5 pts), ternaries 1 (2 pts), boolean chains 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
vue.addHandler (cognitive 24) spring-embed-arthas/src/main/webapp/vue.js:6988— vue.addHandler has cognitive complexity 24 (threshold 15). Drivers by points: if/else 16 (18 pts), boolean chains 4, ternaries 1 (2 pts) (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
(anonymous) (cognitive 24) spring-embed-arthas/src/main/webapp/index.js:6153— (anonymous) has cognitive complexity 24 (threshold 15). Drivers by points: ternaries 10 (12 pts), boolean chains 8, if/else 4 (nesting depth added 2). None of this is in the body itself: all 24 points belong to 7 function items inside it that branch (n, a function literal at line 6193, a function literal at line 6211, …). 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.
vue.parse::closeElement (cognitive 23) spring-embed-arthas/src/main/webapp/vue.js:9627— vue.parse::closeElement has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 8, loops 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DatabaseSetUp.DatabaseSetUp (cognitive 23) tools-manage/invocationlab-erd-online-view/src/pages/design/setting/component/DatabaseSetUp.tsx:23— DatabaseSetUp.DatabaseSetUp has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (10 pts), boolean chains 8, ternaries 4 (5 pts) (nesting depth added 4). Most of this is not in the body itself: 6 of the 23 points are its own statements and the rest belongs to 8 function items inside it that branch (a function literal at line 272, a function literal at line 90, a function literal at line 24, …). 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.
(anonymous) (cognitive 23) spring-embed-arthas/src/main/webapp/index.js:5782— (anonymous) has cognitive complexity 23 (threshold 15). Drivers by points: boolean chains 14, ternaries 6, if/else 1 (2 pts), loops 1 (nesting depth added 1). None of this is in the body itself: all 23 points belong to 11 function items inside it that branch (isDisabled, radioSize, isGroup, …). 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.
sqlParseTool.parseOneWhere (cognitive 22) REDACTED:222— sqlParseTool.parseOneWhere has cognitive complexity 22 (threshold 15). Drivers by points: if/else 16 (22 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
index.DesignLayout (cognitive 22) tools-manage/invocationlab-erd-online-view/src/layouts/DesignLayout/index.tsx:84— index.DesignLayout has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (9 pts), boolean chains 8, ternaries 4 (5 pts) (nesting depth added 3). Most of this is not in the body itself: 5 of the 22 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 120, 202, 244, …). 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.
RedisServiceImpl.addKey (cognitive 22) tools-manage/tools-manage-admin/src/main/java/org/javamaster/spring/tools/manage/service/impl/RedisServiceImpl.java:394— RedisServiceImpl.addKey has cognitive complexity 22 (threshold 15). Drivers by points: if/else 11 (15 pts), loops 2 (6 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.
vue.resolveSlots (cognitive 21) spring-embed-arthas/src/main/webapp/vue.js:2499— vue.resolveSlots has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 7, loops 2 (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.
vue.genData$2 (cognitive 21) spring-embed-arthas/src/main/webapp/vue.js:11099— vue.genData$2 has cognitive complexity 21 (threshold 15). Drivers by points: if/else 18 (19 pts), boolean chains 1, loops 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
MetaDataSearch.MetaDataSearch (cognitive 21) tools-manage/invocationlab-erd-online-view/src/components/LeftContent/DesignLeftContent/component/MetaDataSearch.tsx:40— MetaDataSearch.MetaDataSearch has cognitive complexity 21 (threshold 15). Drivers by points: if/else 14 (15 pts), boolean chains 3, ternaries 3 (nesting depth added 1). None of this is in the body itself: all 21 points belong to 7 function literals inside it that branch (lines 102, 189, 201, …). 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.
StrUtils.getStringValue (cognitive 21) b2c-parent/b2c-bytecode/src/main/java/org/javamaster/b2c/bytecode/utils/StrUtils.java:11— StrUtils.getStringValue has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (15 pts), loops 2, match/switch 1 (2 pts), boolean chains 1, error handling 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.
vue.handleError (cognitive 20) spring-embed-arthas/src/main/webapp/vue.js:1827— vue.handleError has cognitive complexity 20 (threshold 15). Drivers by points: if/else 3 (9 pts), loops 2 (6 pts), error handling 1 (5 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
vue.updateAttrs (cognitive 20) spring-embed-arthas/src/main/webapp/vue.js:6687— vue.updateAttrs has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 6, loops 2 (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.
vue.markStaticRoots (cognitive 20) spring-embed-arthas/src/main/webapp/vue.js:10667— vue.markStaticRoots has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (10 pts), loops 2 (6 pts), boolean chains 4 (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.
InputContextMenu.InputContextMenu (cognitive 20) tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/InputContextMenu.tsx:31— InputContextMenu.InputContextMenu has cognitive complexity 20 (threshold 15). Drivers by points: if/else 14 (15 pts), boolean chains 3, error handling 1 (2 pts) (nesting depth added 2). Most of this is not in the body itself: 7 of the 20 points are its own statements and the rest belongs to 2 function items inside it that branch (handleInputChange, a function literal at line 58). 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.
FieldMultiSelect.FieldMultiSelect (cognitive 20) tools-manage/invocationlab-erd-online-view/src/pages/design/table/component/table/FieldMultiSelect.tsx:35— FieldMultiSelect.FieldMultiSelect has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 9, boolean chains 7, if/else 4. Most of this is not in the body itself: 5 of the 20 points are its own statements and the rest belongs to 9 function items inside it that branch (deselectFilm, maybeDeleteCreatedFilmFromArrays, maybeAddCreatedFilmToArrays, …). 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.
entitiesSlice.EntitiesSlice (cognitive 20) tools-manage/invocationlab-erd-online-view/src/store/project/entitiesSlice.tsx:43— entitiesSlice.EntitiesSlice has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11 (12 pts), boolean chains 5, loops 1 (2 pts), error handling 1 (nesting depth added 2). None of this is in the body itself: all 20 points belong to 7 function literals inside it that branch (lines 109, 46, 96, …). 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.
useTabStore.useTabStore (cognitive 20) tools-manage/invocationlab-erd-online-view/src/store/tab/useTabStore.tsx:43— useTabStore.useTabStore has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (16 pts), boolean chains 4 (nesting depth added 6). None of this is in the body itself: all 20 points belong to 9 function literals inside it that branch (lines 64, 47, 55, …). 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.
(anonymous) (cognitive 20) spring-embed-arthas/src/main/webapp/index.js:15259— (anonymous) has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 11, if/else 3 (4 pts), loops 1 (2 pts), ternaries 2, error handling 1 (nesting depth added 2). None of this is in the body itself: all 20 points belong to 7 function items inside it that branch (r, n, s, …). 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.
vue.renderList (cognitive 19) spring-embed-arthas/src/main/webapp/vue.js:2629— vue.renderList has cognitive complexity 19 (threshold 15). Drivers by points: loops 4 (10 pts), if/else 6 (7 pts), boolean chains 2 (nesting depth added 7). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
vue.createCompileToFunctionFn.compileToFunctions (cognitive 19) spring-embed-arthas/src/main/webapp/vue.js:11659— vue.createCompileToFunctionFn.compileToFunctions has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 5, error handling 1, ternaries 1 (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.
CostTimeTransformer.transform (cognitive 19) java-agent/src/main/java/org/javamaster/java/agent/transformer/CostTimeTransformer.java:29— CostTimeTransformer.transform has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (15 pts), loops 1 (2 pts), boolean chains 1, error handling 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.
MongoDbServiceImpl.execDqlSql (cognitive 19) tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/MongoDbServiceImpl.java:456— MongoDbServiceImpl.execDqlSql has cognitive complexity 19 (threshold 15). Drivers by points: if/else 11 (17 pts), loops 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
parseJoinmap (cognitive 19) tools-manage/invocationlab-erd-online-view/src/components/CodeEditor/parser/select.js:215— parseJoinmap has cognitive complexity 19 (threshold 15). Drivers by points: if/else 4 (10 pts), loops 3 (5 pts), ternaries 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.
vue.looseEqual (cognitive 18) spring-embed-arthas/src/main/webapp/vue.js:296— vue.looseEqual has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (9 pts), boolean chains 7, error handling 1 (2 pts) (nesting depth added 2). 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.
vue.normalizeScopedSlots (cognitive 18) spring-embed-arthas/src/main/webapp/vue.js:2545— vue.normalizeScopedSlots has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (10 pts), boolean chains 4, loops 2 (3 pts), ternaries 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
vue.preTransformNode (cognitive 18) spring-embed-arthas/src/main/webapp/vue.js:10487— vue.preTransformNode has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (13 pts), ternaries 1 (3 pts), boolean chains 2 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
vue.markStatic$1 (cognitive 18) spring-embed-arthas/src/main/webapp/vue.js:10635— vue.markStatic$1 has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (12 pts), loops 2 (5 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.
dataTypeDomainsSlice.DataTypeDomainsSlice (cognitive 18) tools-manage/invocationlab-erd-online-view/src/store/project/dataTypeDomainsSlice.tsx:44— dataTypeDomainsSlice.DataTypeDomainsSlice has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8, boolean chains 5, loops 2 (4 pts), error handling 1 (nesting depth added 2). None of this is in the body itself: all 18 points belong to 6 function literals inside it that branch (lines 106, 93, 45, …). 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.
formatting.CodeMirror.defineExtension("autoFormatRange") (cognitive 18) tools-manage/invocationlab-rpcpostman-view/src/utils/formatting.js:71— formatting.CodeMirror.defineExtension("autoFormatRange") has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (10 pts), boolean chains 4, loops 3 (4 pts) (nesting depth added 7). Of this number, 17 points are the body's own statements and 1 belongs 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.
dragColumn (cognitive 18) spring-embed-arthas/src/main/webapp/table-column-drag.js:193— dragColumn has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 3 (8 pts), if/else 4 (6 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
vue.mergeDataOrFn (cognitive 17) spring-embed-arthas/src/main/webapp/vue.js:1212— vue.mergeDataOrFn has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (9 pts), ternaries 4 (8 pts) (nesting depth added 7). Most of this is not in the body itself: 6 of the 17 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 1237, 1230). 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.
vue.actuallySetSelected (cognitive 17) spring-embed-arthas/src/main/webapp/vue.js:8530— vue.actuallySetSelected has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (15 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.
select.parseColumn (cognitive 17) tools-manage/invocationlab-erd-online-view/src/components/CodeEditor/parser/select.js:115— select.parseColumn has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (15 pts), boolean chains 1, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
select.createObj (cognitive 17) tools-manage/invocationlab-erd-online-view/src/components/CodeEditor/parser/select.js:409— select.createObj has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (16 pts), loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ConvertUtils.numberType (cognitive 17) handypoi-excel/src/main/java/cn/com/bluemoon/handypoi/excel/utils/ConvertUtils.java:46— ConvertUtils.numberType has cognitive complexity 17 (threshold 15). Drivers by points: if/else 15 (16 pts), error handling 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
StringUtils.wordsAndHyphenAndCamelToConstantCase (cognitive 17) mybatis-generator/src/main/java/org/javamaster/mybatis/generator/utils/StringUtils.java:14— StringUtils.wordsAndHyphenAndCamelToConstantCase has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 10, if/else 4 (6 pts), loops 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.
vue.assertProp (cognitive 16) spring-embed-arthas/src/main/webapp/vue.js:1682— vue.assertProp has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (9 pts), boolean chains 5, loops 1 (2 pts) (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
vue.initComputed (cognitive 16) spring-embed-arthas/src/main/webapp/vue.js:4756— vue.initComputed has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (11 pts), boolean chains 2, ternaries 1 (2 pts), loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
vue.genDefaultModel (cognitive 16) spring-embed-arthas/src/main/webapp/vue.js:7422— vue.genDefaultModel has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 6, if/else 5, ternaries 3 (5 pts) (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.
vue.createCompilerCreator.createCompiler.compile (cognitive 16) spring-embed-arthas/src/main/webapp/vue.js:11760— vue.createCompilerCreator.createCompiler.compile has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (10 pts), boolean chains 3, loops 1 (2 pts), ternaries 1 (nesting depth added 6). Of this number, 15 points are the body's own statements and 1 belongs 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.
index.CodeEditor (cognitive 16) tools-manage/invocationlab-erd-online-view/src/components/CodeEditor/index.tsx:78— index.CodeEditor has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 8, if/else 6, error handling 1, loops 1. Most of this is not in the body itself: 7 of the 16 points are its own statements and the rest belongs to 5 function items inside it that branch (resolveSql, a function literal at line 122, a function literal at line 154, …). 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.
request.request.interceptors.response.use() (cognitive 16) REDACTED:121— request.request.interceptors.response.use() has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 4 (nesting depth added 5). Of this number, 13 points are the body's own statements and 3 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.
DatabaseSetUp.DatabaseSetUp (cognitive 16) REDACTED:25— DatabaseSetUp.DatabaseSetUp has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 8, ternaries 4 (5 pts), if/else 3 (nesting depth added 1). Most of this is not in the body itself: 6 of the 16 points are its own statements and the rest belongs to 7 function items inside it that branch (a function literal at line 88, a function literal at line 26, a function literal at line 174, …). 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.
TableCodeShow.TableCodeShow (cognitive 16) tools-manage/invocationlab-erd-online-view/src/pages/design/table/component/table/TableCodeShow.tsx:20— TableCodeShow.TableCodeShow has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 11, if/else 4, ternaries 1. Most of this is not in the body itself: 2 of the 16 points are its own statements and the rest belongs to 4 function items inside it that branch (a function literal at line 59, getTableCode, a function literal at line 23, …). 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.
AbstractDbService.executeDqlSql (cognitive 16) tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/service/impl/AbstractDbService.kt:555— AbstractDbService.executeDqlSql has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 2, loops 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.
MethodTooLong: G6Relation._renderRelation tools-manage/invocationlab-erd-online-view/src/pages/design/relation/g6.js:479— MethodTooLong — _renderRelation runs 582 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 482 over it, 5.82× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
D4 · Code Duplication· Edited copy of a member (21 corresponding lines) · ×1
Edited copy of a member (21 corresponding lines) spring-transactional/src/main/java/org/javamaster/spring/transactional/service/AddressHelper.java:24— spring-transactional/src/main/java/org/javamaster/spring/transactional/service/AddressHelper.java:24-47 | spring-transactional/src/main/java/org/javamaster/spring/transactional/service/impl/AddressServiceImpl.java:132-172 — 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 (53 corresponding lines) · ×1
Edited copy of a member (53 corresponding lines) tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/AbstractDbService.java:719— tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/AbstractDbService.java:719-774 | tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/MongoDbServiceImpl.java:640-692 — These two members are one piece of code written twice and then edited apart: 53 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 35+ corresponding lines) · ×1
Edited copies of one member (3 members, 35+ corresponding lines) tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/redis/impl/ListRedisDataTypeService.java:26— tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/redis/impl/ListRedisDataTypeService.java:26-60 | tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/redis/impl/SetRedisDataTypeService.java:26-60 | tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/redis/impl/ZSetRedisDataTypeService.java:25-60 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 35 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 (15 corresponding lines) · ×1
Edited copy of a member (15 corresponding lines) tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/config/MvcConfig.java:100— tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/config/MvcConfig.java:100-122 | tools-manage/tools-manage-admin/src/main/java/org/javamaster/spring/tools/manage/config/RedisConfig.java:82-96 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 25+ corresponding lines) · ×1
Edited copies of one member (3 members, 25+ corresponding lines) tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/redis/impl/ListRedisDataTypeService.java:75— tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/redis/impl/ListRedisDataTypeService.java:75-99 | tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/redis/impl/SetRedisDataTypeService.java:73-105 | tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/redis/impl/ZSetRedisDataTypeService.java:119-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, 31+ corresponding lines) · ×1
Edited copies of one member (3 members, 31+ corresponding lines) tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/redis/impl/ListRedisStrategy.kt:18— tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/redis/impl/ListRedisStrategy.kt:18-48 | tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/redis/impl/SetRedisStrategy.kt:18-48 | tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/redis/impl/ZSetRedisStrategy.kt:18-52 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 31 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (19 corresponding lines) · ×1
Edited copy of a member (19 corresponding lines) tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/RedisServiceImpl.java:274— tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/RedisServiceImpl.java:274-295 | tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/RedisServiceImpl.java:298-316 — 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 copies of one member (3 members, 20+ corresponding lines) · ×1
Edited copies of one member (3 members, 20+ corresponding lines) tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/KafkaServiceImpl.java:482— tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/KafkaServiceImpl.java:482-501 | tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/KafkaServiceImpl.java:504-524 | tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/KafkaServiceImpl.java:527-547 — 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 (16 corresponding lines) · ×1
Edited copy of a member (16 corresponding lines) tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/util/RedisUtils.java:41— tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/util/RedisUtils.java:41-56 | tools-manage/tools-manage-admin/src/main/java/org/javamaster/spring/tools/manage/util/RedisUtils.java:37-52 — 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 (18 corresponding lines) · ×1
Edited copy of a member (18 corresponding lines) tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/KafkaServiceImpl.java:159— tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/KafkaServiceImpl.java:159-176 | tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/KafkaServiceImpl.java:179-196 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (17 corresponding lines) · ×1
Edited copy of a member (17 corresponding lines) tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/controller/RpcPostmanClusterController.kt:78— tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/controller/RpcPostmanClusterController.kt:78-94 | tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/controller/RpcPostmanClusterController.kt:101-117 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (5 members, 11+ corresponding lines) · ×1
Edited copies of one member (5 members, 11+ corresponding lines) REDACTED:77— REDACTED:77-87 | tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/util/KafkaUtils.java:25-37 | tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/util/KafkaUtils.java:54-67 | tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/util/KafkaUtils.java:85-97 | tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/util/KafkaUtils.java:99-113 — These 5 members are one piece of code written 5 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 5 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 9+ corresponding lines) · ×1
Edited copies of one member (4 members, 9+ corresponding lines) tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/RedisServiceImpl.java:193— tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/RedisServiceImpl.java:193-202 | tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/RedisServiceImpl.java:205-213 | tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/RedisServiceImpl.java:216-224 | tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/RedisServiceImpl.java:227-235 — These 4 members are one piece of code written 4 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 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 8+ corresponding lines) · ×1
Edited copies of one member (3 members, 8+ corresponding lines) b2c-parent/b2c-bytecode/src/main/java/org/javamaster/b2c/bytecode/attribute/InnerClassesAttribute.java:25— b2c-parent/b2c-bytecode/src/main/java/org/javamaster/b2c/bytecode/attribute/InnerClassesAttribute.java:25-32 | b2c-parent/b2c-bytecode/src/main/java/org/javamaster/b2c/bytecode/attribute/LocalVariableTableAttribute.java:23-30 | b2c-parent/b2c-bytecode/src/main/java/org/javamaster/b2c/bytecode/attribute/LocalVariableTypeTableAttribute.java:23-30 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 12+ corresponding lines) · ×1
Edited copies of one member (4 members, 12+ corresponding lines) tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/redis/impl/HashRedisDataTypeService.java:152— tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/redis/impl/HashRedisDataTypeService.java:152-163 | tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/redis/impl/ListRedisDataTypeService.java:111-122 | tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/redis/impl/SetRedisDataTypeService.java:117-128 | tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/redis/impl/ZSetRedisDataTypeService.java:83-94 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 10+ corresponding lines) · ×1
Edited copies of one member (4 members, 10+ corresponding lines) tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/service/impl/RedisServiceImpl.kt:180— tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/service/impl/RedisServiceImpl.kt:180-190 | tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/service/impl/RedisServiceImpl.kt:193-203 | tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/service/impl/RedisServiceImpl.kt:215-225 | tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/service/impl/RedisServiceImpl.kt:251-260 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 11+ corresponding lines) · ×1
Edited copies of one member (4 members, 11+ corresponding lines) tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/redis/impl/HashRedisStrategy.kt:159— tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/redis/impl/HashRedisStrategy.kt:159-172 | tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/redis/impl/ListRedisStrategy.kt:110-120 | tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/redis/impl/SetRedisStrategy.kt:118-131 | tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/redis/impl/ZSetRedisStrategy.kt:86-99 — 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 copy of a member (3 corresponding lines) · ×1
Edited copy of a member (3 corresponding lines) tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/MySqlDbServiceImpl.java:34— tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/MySqlDbServiceImpl.java:34-36 | tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/PostgreSqlDbServiceImpl.java:60-62 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (16–17 lines × 3) tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/redis/impl/HashRedisStrategy.kt:51— tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/redis/impl/HashRedisStrategy.kt:51-66 | tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/redis/impl/ListRedisStrategy.kt:33-48 | tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/redis/impl/SetRedisStrategy.kt:32-48 — before extracting anything, compare `tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/redis/impl/ListRedisStrategy.kt` and `tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/redis/impl/SetRedisStrategy.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 39 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/redis/impl/HashRedisStrategy.kt:51` 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 (10–12 lines × 3) tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/redis/impl/SetRedisStrategy.kt:72— tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/redis/impl/SetRedisStrategy.kt:72-81 | tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/redis/impl/StringRedisStrategy.kt:61-70 | tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/redis/impl/ZSetRedisStrategy.kt:137-148 — before extracting anything, compare `tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/redis/impl/SetRedisStrategy.kt` and `tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/redis/impl/ZSetRedisStrategy.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/redis/impl/SetRedisStrategy.kt:72` 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, `tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/redis/impl/ZSetRedisStrategy.kt:149` calls `delField` and `tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/redis/impl/StringRedisStrategy.kt:71` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (10–12 lines × 2) tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/service/impl/AbstractDbService.kt:411— tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/service/impl/AbstractDbService.kt:411-420 | tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/service/impl/AbstractDbService.kt:533-544 — both copies are in the same file, so extract the 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 `tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/service/impl/AbstractDbService.kt:533` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 4) tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/redis/impl/ListRedisStrategy.kt:75— tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/redis/impl/ListRedisStrategy.kt:75-83 | tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/redis/impl/SetRedisStrategy.kt:72-80 | tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/redis/impl/StringRedisStrategy.kt:61-69 | tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/redis/impl/ZSetRedisStrategy.kt:137-147 — before extracting anything, compare `tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/redis/impl/ListRedisStrategy.kt` and `tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/redis/impl/SetRedisStrategy.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 39 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/redis/impl/ListRedisStrategy.kt:75` 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, `tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/redis/impl/ListRedisStrategy.kt:84` calls `rPush` and `tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/redis/impl/StringRedisStrategy.kt:70` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (22–23 lines × 2) tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/redis/impl/ListRedisDataTypeService.java:39— tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/redis/impl/ListRedisDataTypeService.java:39-60 | tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/redis/impl/SetRedisDataTypeService.java:38-60 — before extracting anything, compare `tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/redis/impl/ListRedisDataTypeService.java` and `tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/redis/impl/SetRedisDataTypeService.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 41 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/redis/impl/ListRedisDataTypeService.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 (22 lines × 2) tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/AbstractDbService.java:720— tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/AbstractDbService.java:720-741 | tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/MongoDbServiceImpl.java:641-662 — 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 `tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/AbstractDbService.java:720` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 2) spring-transactional/src/main/java/org/javamaster/spring/transactional/service/impl/AddressServiceImpl.java:46— spring-transactional/src/main/java/org/javamaster/spring/transactional/service/impl/AddressServiceImpl.java:46-61 | spring-transactional/src/main/java/org/javamaster/spring/transactional/service/impl/AddressServiceImpl.java:70-85 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `spring-transactional/src/main/java/org/javamaster/spring/transactional/service/impl/AddressServiceImpl.java:46` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/AbstractDbService.java:431— tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/AbstractDbService.java:431-445 | tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/MongoDbServiceImpl.java:193-207 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (12 lines × 2) tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/config/RedisConfig.java:37— tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/config/RedisConfig.java:37-48 | tools-manage/tools-manage-admin/src/main/java/org/javamaster/spring/tools/manage/config/RedisConfig.java:50-61 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. 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 × 4) tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/AbstractDbService.java:433— tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/AbstractDbService.java:433-440 | tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/AbstractDbService.java:541-548 | tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/MongoDbServiceImpl.java:195-202 | tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/MongoDbServiceImpl.java:569-576 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/MongoDbServiceImpl.java:579` calls `put` and `tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/AbstractDbService.java:443` 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) tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/redis/impl/HashRedisDataTypeService.java:106— tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/redis/impl/HashRedisDataTypeService.java:106-112 | tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/redis/impl/HashRedisDataTypeService.java:114-120 | tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/redis/impl/ListRedisDataTypeService.java:81-87 | tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/redis/impl/SetRedisDataTypeService.java:79-85 — before extracting anything, compare `tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/redis/impl/ListRedisDataTypeService.java` and `tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/redis/impl/SetRedisDataTypeService.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 41 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (50–51 lines × 3) b2c-parent/b2c-bytecode/src/main/java/org/javamaster/b2c/bytecode/tablestructure/ConstantFieldRefInfo.java:1— b2c-parent/b2c-bytecode/src/main/java/org/javamaster/b2c/bytecode/tablestructure/ConstantFieldRefInfo.java:1-51 | b2c-parent/b2c-bytecode/src/main/java/org/javamaster/b2c/bytecode/tablestructure/ConstantInterfaceMethodRefInfo.java:1-50 | b2c-parent/b2c-bytecode/src/main/java/org/javamaster/b2c/bytecode/tablestructure/ConstantMethodRefInfo.java:1-51 — before extracting anything, compare `b2c-parent/b2c-bytecode/src/main/java/org/javamaster/b2c/bytecode/tablestructure/ConstantFieldRefInfo.java` and `b2c-parent/b2c-bytecode/src/main/java/org/javamaster/b2c/bytecode/tablestructure/ConstantInterfaceMethodRefInfo.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. 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 `b2c-parent/b2c-bytecode/src/main/java/org/javamaster/b2c/bytecode/tablestructure/ConstantFieldRefInfo.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. 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 (326 lines × 10) b2c-parent/b2c-core/src/main/java/org/javamaster/b2c/core/entity/MicrowebsiteExamExample.java:17— b2c-parent/b2c-core/src/main/java/org/javamaster/b2c/core/entity/MicrowebsiteExamExample.java:17-522 | b2c-parent/b2c-core/src/main/java/org/javamaster/b2c/core/entity/MicrowebsiteExamUserExample.java:17-342 | b2c-parent/b2c-core/src/main/java/org/javamaster/b2c/core/entity/SysAuthorityExample.java:17-342 | b2c-parent/b2c-core/src/main/java/org/javamaster/b2c/core/entity/SysGroupAuthorityExample.java:17-342 | b2c-parent/b2c-core/src/main/java/org/javamaster/b2c/core/entity/SysGroupExample.java:17-342 | b2c-parent/b2c-core/src/main/java/org/javamaster/b2c/core/entity/SysGroupUserExample.java:17-342 | b2c-parent/b2c-core/src/main/java/org/javamaster/b2c/core/entity/SysRememberMeExample.java:18-473 | b2c-parent/b2c-core/src/main/java/org/javamaster/b2c/core/entity/SysUserExample.java:17-402 | b2c-parent/b2c-mybatis/src/main/java/org/javamaster/b2c/mybatis/entity/ExamsExample.java:19-664 | b2c-parent/b2c-mybatis/src/main/java/org/javamaster/b2c/mybatis/entity/MenusExample.java:19-774 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 10 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 10 times. Read the line range as the matched WINDOW rather than a finished unit: at `b2c-parent/b2c-core/src/main/java/org/javamaster/b2c/core/entity/MicrowebsiteExamExample.java:17` 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 (79 lines × 3) spring-lifecycle/src/main/java/org/javamaster/spring/lifecycle/ContextLoaderListenerBeans/ContextBean.java:1— spring-lifecycle/src/main/java/org/javamaster/spring/lifecycle/ContextLoaderListenerBeans/ContextBean.java:1-91 | spring-lifecycle/src/main/java/org/javamaster/spring/lifecycle/DispatcherServletBeans/MvcContextBean.java:1-80 | springboot-lifecycle/src/main/java/org/javamaster/springboot/lifecycle/beans/MvcContextBean.java:1-79 — before extracting anything, compare `spring-lifecycle/src/main/java/org/javamaster/spring/lifecycle/ContextLoaderListenerBeans/ContextBean.java` and `spring-lifecycle/src/main/java/org/javamaster/spring/lifecycle/DispatcherServletBeans/MvcContextBean.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. 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 `spring-lifecycle/src/main/java/org/javamaster/spring/lifecycle/ContextLoaderListenerBeans/ContextBean.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 (9 lines × 3) b2c-parent/b2c-bytecode/src/main/java/org/javamaster/b2c/bytecode/modifier/ClassModifier.java:70— b2c-parent/b2c-bytecode/src/main/java/org/javamaster/b2c/bytecode/modifier/ClassModifier.java:70-78 | b2c-parent/b2c-bytecode/src/main/java/org/javamaster/b2c/bytecode/modifier/FieldModifier.java:64-72 | b2c-parent/b2c-bytecode/src/main/java/org/javamaster/b2c/bytecode/modifier/MethodModifier.java:72-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 all 3 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.
End-of-life framework: Spring Boot 2 b2c-parent/pom.xml:1— b2c-parent/pom.xml depends on `org.springframework.boot` at a version that pins Spring Boot 2, and Spring Boot 2.x, open-source support ended 2023-11-24. 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.
Hollow method — returns a constant without doing the work tools-manage/invocationlab-erd-online-view/src/app.tsx:8— `getInitialState` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
Forked directory tree (50 identical files, ~1.2 MB × 2 trees) tools-manage/invocationlab-admin/src/main/resources/public/invocationlab-erd-online-view/project.json:1— tools-manage/invocationlab-admin/src/main/resources/public/invocationlab-erd-online-view/ and tools-manage/invocationlab-erd-online-view/public/ are near-verbatim copies of each other: 50 files are byte-identical under the same relative paths (~1.2 MB; the trees hold 127 and 50 files). That is one structural fact, not 50 local ones: every edit made to one tree and not the other drifts silently, which is the failure whole-tree forks guarantee. Pick one tree as the single source and produce the other from it (generated, copied at build or release time, or re-exported) — or, if the copy is a stale snapshot nothing produces any more, delete it. Check first whether the copy is a deliberately published deliverable (a template consumers copy verbatim, a released sample frozen at a version); where it is, keep it produced from the source tree rather than edited in place.
Duplication concentrated across 5 sibling directories (27 clone groups) tools-manage/invocationlab-erd-online-view/src/components/dialog/export/ExportDDL.tsx:1— 27 duplicated blocks under tools-manage/invocationlab-erd-online-view/src/ have copies in at least two of the sibling directories components, pages, services, store, utils — 24 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 27 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 27 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 27 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 6 sibling directories (10 clone groups) tools-manage/invocationlab-erd-online-view/src/components/dialog/entity/AddEntity.tsx:12— 10 duplicated blocks under tools-manage/invocationlab-erd-online-view/src/components/dialog/ have copies in at least two of the sibling directories dataType, database, entity, module, query, version — 9 of them are reported below, and 1 is counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 10 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 10 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 10 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 3 sibling directories (6 clone groups) tools-manage/invocationlab-erd-online-view/src/layouts/DesignLayout/index.tsx:85— 6 duplicated blocks under tools-manage/invocationlab-erd-online-view/src/layouts/ have copies in at least two of the sibling directories DesignLayout, GroupLayout, HomeLayout — 5 of them are reported below, and 1 is counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 6 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 6 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 6 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 5 sibling directories (5 clone groups) REDACTED:320— 5 duplicated blocks under tools-manage/ have copies in at least two of the sibling directories invocationlab-admin, invocationlab-admin-21, invocationlab-erd-online-view, invocationlab-rpcpostman-view, tools-manage-view — 4 of them are reported below, and 1 is counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 5 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 5 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 5 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication· Duplicated block with local edits (261 matched lines × 2 locations) · ×1
Duplicated block with local edits (261 matched lines × 2 locations) REDACTED:320— REDACTED:320 · tools-manage/tools-manage-view/src/views/RedisManageView.vue:243 — the two spans are one implementation copied and then locally edited — 1491 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Wholesale file copy (155 identical lines × 2 files) tools-manage/invocationlab-erd-online-view/src/components/dialog/export/ExportDDL.tsx:1— tools-manage/invocationlab-erd-online-view/src/components/dialog/export/ExportDDL.tsx:1 · tools-manage/invocationlab-erd-online-view/src/pages/design/export/component/ExportDDL.tsx:1 — these 2 files are line-for-line copies of one another — 155 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication· Duplicated block with local edits (144 matched lines × 2 locations) · ×1
Duplicated block with local edits (144 matched lines × 2 locations) REDACTED:22— REDACTED:22 · tools-manage/invocationlab-erd-online-view/src/pages/design/setting/component/DatabaseSetUp.tsx:20 — the two spans are one implementation copied and then locally edited — 894 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Wholesale file copy (112 identical lines × 2 files) tools-manage/invocationlab-admin-21/src/main/resources/script/propertyOperation.js:1— tools-manage/invocationlab-admin-21/src/main/resources/script/propertyOperation.js:1 · tools-manage/invocationlab-admin/src/main/resources/script/propertyOperation.js:1 — these 2 files are line-for-line copies of one another — 112 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Duplicated block (101 lines × 2 locations) tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/ConstructSqlForm.tsx:199— tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/ConstructSqlForm.tsx:199 · tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/ConstructSqlFormMongoDB.tsx:185 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Wholesale file copy (94 identical lines × 2 files) tools-manage/invocationlab-erd-online-view/src/pages/project/group/index.tsx:1— tools-manage/invocationlab-erd-online-view/src/pages/project/group/index.tsx:1 · tools-manage/invocationlab-erd-online-view/src/pages/project/person/index.tsx:1 — these 2 files are line-for-line copies of one another — 94 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication· Duplicated block with local edits (86 matched lines × 2 locations) · ×1
Duplicated block with local edits (86 matched lines × 2 locations) tools-manage/invocationlab-erd-online-view/src/components/dialog/import/ReverseDatabase.tsx:12— tools-manage/invocationlab-erd-online-view/src/components/dialog/import/ReverseDatabase.tsx:12 · tools-manage/invocationlab-erd-online-view/src/pages/design/import/component/ReverseDatabase.tsx:9 — the two spans are one implementation copied and then locally edited — 573 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Wholesale file copy (85 identical lines × 2 files) tools-manage/invocationlab-erd-online-view/src/pages/project/group/index.tsx:1— tools-manage/invocationlab-erd-online-view/src/pages/project/group/index.tsx:1 · tools-manage/invocationlab-erd-online-view/src/pages/project/recent/index.tsx:1 — these 2 files are line-for-line copies of one another — 85 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication· Duplicated block with local edits (83 matched lines × 2 locations) · ×1
Duplicated block with local edits (83 matched lines × 2 locations) tools-manage/invocationlab-erd-online-view/src/layouts/DesignLayout/index.tsx:85— tools-manage/invocationlab-erd-online-view/src/layouts/DesignLayout/index.tsx:85 · tools-manage/invocationlab-erd-online-view/src/layouts/GroupLayout/index.tsx:20 — the two spans are one implementation copied and then locally edited — 461 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (83 lines × 2 locations) tools-manage/invocationlab-erd-online-view/src/pages/design/relation/g6.js:489— tools-manage/invocationlab-erd-online-view/src/pages/design/relation/g6.js:489 · tools-manage/invocationlab-erd-online-view/src/utils/relation2file.js:161 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication· Duplicated block with local edits (82 matched lines × 2 locations) · ×1
Duplicated block with local edits (82 matched lines × 2 locations) tools-manage/invocationlab-erd-online-view/src/components/dialog/database/AddDatabase.tsx:13— tools-manage/invocationlab-erd-online-view/src/components/dialog/database/AddDatabase.tsx:13 · tools-manage/invocationlab-erd-online-view/src/components/dialog/database/RenameDatabase.tsx:12 — the two spans are one implementation copied and then locally edited — 415 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (78 matched lines × 2 locations) · ×1
Duplicated block with local edits (78 matched lines × 2 locations) REDACTED:234— REDACTED:234 · tools-manage/invocationlab-erd-online-view/src/pages/design/setting/component/DatabaseSetUp.tsx:147 — the two spans are one implementation copied and then locally edited — 334 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (77 lines × 2 locations) tools-manage/invocationlab-erd-online-view/src/components/dialog/entity/AddEntity.tsx:12— tools-manage/invocationlab-erd-online-view/src/components/dialog/entity/AddEntity.tsx:12 · tools-manage/invocationlab-erd-online-view/src/components/dialog/module/AddModule.tsx:13 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
R10 · Code Duplication· Duplicated block with local edits (75 matched lines × 2 locations) · ×1
Duplicated block with local edits (75 matched lines × 2 locations) tools-manage/invocationlab-erd-online-view/src/pages/design/relation/g6.js:110— tools-manage/invocationlab-erd-online-view/src/pages/design/relation/g6.js:110 · tools-manage/invocationlab-erd-online-view/src/utils/relation2file.js:6 — the two spans are one implementation copied and then locally edited — 563 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (74 lines × 2 locations) tools-manage/invocationlab-erd-online-view/src/components/dialog/import/ReverseERD.tsx:43— tools-manage/invocationlab-erd-online-view/src/components/dialog/import/ReverseERD.tsx:43 · tools-manage/invocationlab-erd-online-view/src/components/dialog/import/ReversePdMan.tsx:35 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
Duplicated block (68 lines × 2 locations) tools-manage/invocationlab-erd-online-view/src/components/JExcel/index.tsx:62— tools-manage/invocationlab-erd-online-view/src/components/JExcel/index.tsx:62 · tools-manage/invocationlab-erd-online-view/src/pages/JExcel/index.tsx:87 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication· Duplicated block with local edits (68 matched lines × 2 locations) · ×1
Duplicated block with local edits (68 matched lines × 2 locations) tools-manage/invocationlab-erd-online-view/src/store/version/useVersionStore.tsx:149— tools-manage/invocationlab-erd-online-view/src/store/version/useVersionStore.tsx:149 · tools-manage/invocationlab-erd-online-view/src/utils/dbversionutils.js:42 — the two spans are one implementation copied and then locally edited — 454 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (64 matched lines × 2 locations) · ×1
Duplicated block with local edits (64 matched lines × 2 locations) spring-embed-arthas/src/main/webapp/index.js:17126— spring-embed-arthas/src/main/webapp/index.js:17126 · spring-embed-arthas/src/main/webapp/index.js:17206 — the two spans are one implementation copied and then locally edited — 663 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (61 matched lines × 2 locations) · ×1
Duplicated block with local edits (61 matched lines × 2 locations) tools-manage/invocationlab-erd-online-view/src/utils/generatehtml.js:4— tools-manage/invocationlab-erd-online-view/src/utils/generatehtml.js:4 · tools-manage/invocationlab-erd-online-view/src/utils/markdown.js:4 — the two spans are one implementation copied and then locally edited — 595 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (59 lines × 2 locations) tools-manage/invocationlab-erd-online-view/src/pages/design/import/component/ReverseERD.tsx:79— tools-manage/invocationlab-erd-online-view/src/pages/design/import/component/ReverseERD.tsx:79 · tools-manage/invocationlab-erd-online-view/src/pages/design/import/component/ReversePdMan.tsx:33 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
Duplicated block (57 lines × 3 locations) tools-manage/invocationlab-erd-online-view/copyDistToPublic.js:4— tools-manage/invocationlab-erd-online-view/copyDistToPublic.js:4 · tools-manage/invocationlab-rpcpostman-view/copyDistToPublic.js:4 · tools-manage/tools-manage-view/copyDistToPublic.js:4 — 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 (46 lines × 2 locations) tools-manage/invocationlab-erd-online-view/src/components/dialog/version/InitVersion.tsx:72— tools-manage/invocationlab-erd-online-view/src/components/dialog/version/InitVersion.tsx:72 · tools-manage/invocationlab-erd-online-view/src/components/dialog/version/RebuildVersion.tsx:33 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication· Duplicated block with local edits (46 matched lines × 2 locations) · ×1
Duplicated block with local edits (46 matched lines × 2 locations) tools-manage/invocationlab-rpcpostman-view/src/views/pages/CreateService.vue:88— tools-manage/invocationlab-rpcpostman-view/src/views/pages/CreateService.vue:88 · tools-manage/invocationlab-rpcpostman-view/src/views/pages/CreateServiceJdk.vue:76 — the two spans are one implementation copied and then locally edited — 233 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (45 lines × 2 locations) tools-manage/invocationlab-erd-online-view/src/components/dialog/import/ReversePdMan.tsx:13— tools-manage/invocationlab-erd-online-view/src/components/dialog/import/ReversePdMan.tsx:13 · tools-manage/invocationlab-erd-online-view/src/pages/design/import/component/ReversePdMan.tsx:9 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (42 lines × 2 locations) tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/ConstructSqlForm.tsx:409— tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/ConstructSqlForm.tsx:409 · tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/ConstructSqlFormMongoDB.tsx:396 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (40 lines × 2 locations) tools-manage/invocationlab-erd-online-view/src/store/version/useVersionStore.tsx:289— tools-manage/invocationlab-erd-online-view/src/store/version/useVersionStore.tsx:289 · tools-manage/invocationlab-erd-online-view/src/store/version/useVersionStore.tsx:995 — 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 (38 lines × 2 locations) tools-manage/invocationlab-erd-online-view/src/components/dialog/version/AddVersion.tsx:61— tools-manage/invocationlab-erd-online-view/src/components/dialog/version/AddVersion.tsx:61 · tools-manage/invocationlab-erd-online-view/src/components/dialog/version/RenameVersion.tsx:62 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Duplicated block (35 lines × 2 locations) tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/ConstructSqlForm.tsx:58— tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/ConstructSqlForm.tsx:58 · tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/ConstructSqlFormMongoDB.tsx:56 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication· Duplicated block with local edits (33 matched lines × 2 locations) · ×1
Duplicated block with local edits (33 matched lines × 2 locations) spring-embed-arthas/src/main/webapp/index.js:5993— spring-embed-arthas/src/main/webapp/index.js:5993 · spring-embed-arthas/src/main/webapp/index.js:6271 — the two spans are one implementation copied and then locally edited — 275 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Complex function access (cyclomatic 71, cognitive 70) tools-manage/invocationlab-erd-online-view/src/access.ts:11— access has cyclomatic complexity 71 and cognitive complexity 70; 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 sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. 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.
R2 · Cyclomatic Complexity· Complex function n (cyclomatic 36, cognitive 35) · ×1
Complex function n (cyclomatic 36, cognitive 35) spring-embed-arthas/src/main/webapp/index.js:8078— n has cyclomatic complexity 36 and cognitive complexity 35; 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 sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function getColumnValueOfType (cyclomatic 35, cognitive 54) tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/ConstructSqlForm.tsx:151— getColumnValueOfType has cyclomatic complexity 35 and cognitive complexity 54; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 34, cognitive 40) spring-embed-arthas/src/main/webapp/index.js:13219— (anonymous) has cyclomatic complexity 34 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.
Complex function Parser (cyclomatic 33, cognitive 74) tools-manage/invocationlab-erd-online-view/src/components/CodeEditor/parser/lexter.js:27— Parser has cyclomatic complexity 33 and cognitive complexity 74; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function exports (cyclomatic 28, cognitive 31) spring-embed-arthas/src/main/webapp/index.js:1480— exports has cyclomatic complexity 28 and cognitive complexity 31; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function parse (cyclomatic 27, cognitive 25) spring-embed-arthas/src/main/webapp/index.js:9035— parse has cyclomatic complexity 27 and cognitive complexity 25; 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 sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. 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.
R2 · Cyclomatic Complexity· Complex function a (cyclomatic 26, cognitive 27) · ×1
Complex function a (cyclomatic 26, cognitive 27) spring-embed-arthas/src/main/webapp/index.js:1153— a has cyclomatic complexity 26 and cognitive complexity 27; 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.
R2 · Cyclomatic Complexity· Complex function n (cyclomatic 25, cognitive 21) · ×1
Complex function n (cyclomatic 25, cognitive 21) spring-embed-arthas/src/main/webapp/index.js:2818— n has cyclomatic complexity 25 and cognitive complexity 21; 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 sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. 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.
R2 · Cyclomatic Complexity· Complex function n (cyclomatic 24, cognitive 21) · ×1
Complex function n (cyclomatic 24, cognitive 21) spring-embed-arthas/src/main/webapp/index.js:3955— n has cyclomatic complexity 24 and cognitive complexity 21; 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 sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. 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.
R2 · Cyclomatic Complexity· Complex function e (cyclomatic 23, cognitive 20) · ×1
Complex function e (cyclomatic 23, cognitive 20) spring-embed-arthas/src/main/webapp/index.js:13471— e has cyclomatic complexity 23 and cognitive complexity 20; 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 sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. 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.
R2 · Cyclomatic Complexity· Complex function s (cyclomatic 22, cognitive 35) · ×1
Complex function s (cyclomatic 22, cognitive 35) spring-embed-arthas/src/main/webapp/index.js:11903— s has cyclomatic complexity 22 and cognitive complexity 35; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function showChanges (cyclomatic 22, cognitive 30) tools-manage/invocationlab-erd-online-view/src/store/version/useVersionStore.tsx:499— showChanges has cyclomatic complexity 22 and cognitive complexity 30; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function divideTokens (cyclomatic 21, cognitive 38) tools-manage/invocationlab-erd-online-view/src/components/CodeEditor/parser/select.js:45— divideTokens has cyclomatic complexity 21 and cognitive complexity 38; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function fromString (cyclomatic 21, cognitive 29) spring-embed-arthas/src/main/webapp/index.js:1640— fromString has cyclomatic complexity 21 and cognitive complexity 29; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function getCellClasses (cyclomatic 21, cognitive 19) spring-embed-arthas/src/main/webapp/index.js:10009— getCellClasses has cyclomatic complexity 21 and cognitive complexity 19; 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 sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function parseOneSource (cyclomatic 20, cognitive 44) REDACTED:144— parseOneSource has cyclomatic complexity 20 and cognitive complexity 44; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function updateElsHeight (cyclomatic 20, cognitive 29) spring-embed-arthas/src/main/webapp/index.js:7280— updateElsHeight has cyclomatic complexity 20 and cognitive complexity 29; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 20, cognitive 25) tools-manage/invocationlab-erd-online-view/src/pages/design/relation/g6.js:1007— (anonymous) has cyclomatic complexity 20 and cognitive complexity 25; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 20, cognitive 21) tools-manage/invocationlab-erd-online-view/src/utils/json2code.ts:255— (anonymous) has cyclomatic complexity 20 and cognitive complexity 21; 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.
R2 · Cyclomatic Complexity· Complex function n (cyclomatic 19, cognitive 17) · ×1
Complex function n (cyclomatic 19, cognitive 17) spring-embed-arthas/src/main/webapp/index.js:12335— n has cyclomatic complexity 19 and cognitive complexity 17; 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 sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 19, cognitive 11) spring-embed-arthas/src/main/webapp/index.js:470— (anonymous) has cyclomatic complexity 19 and cognitive complexity 11; 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 sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 19, cognitive 9) tools-manage/invocationlab-erd-online-view/src/pages/design/table/component/table/TableCodeShow.tsx:59— (anonymous) has cyclomatic complexity 19 and cognitive complexity 9; 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 sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. 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.
R2 · Cyclomatic Complexity· Complex function i (cyclomatic 18, cognitive 38) · ×1
Complex function i (cyclomatic 18, cognitive 38) spring-embed-arthas/src/main/webapp/index.js:6851— i has cyclomatic complexity 18 and cognitive complexity 38; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function createPopper (cyclomatic 18, cognitive 16) spring-embed-arthas/src/main/webapp/index.js:425— createPopper has cyclomatic complexity 18 and cognitive complexity 16; 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 sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. 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.
R2 · Cyclomatic Complexity· Complex function n (cyclomatic 18, cognitive 16) · ×1
Complex function n (cyclomatic 18, cognitive 16) spring-embed-arthas/src/main/webapp/index.js:9059— n has cyclomatic complexity 18 and cognitive complexity 16; 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 sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function doOpen (cyclomatic 17, cognitive 19) spring-embed-arthas/src/main/webapp/index.js:686— doOpen has cyclomatic complexity 17 and cognitive complexity 19; 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.
R2 · Cyclomatic Complexity· Complex function n (cyclomatic 17, cognitive 15) · ×1
Complex function n (cyclomatic 17, cognitive 15) spring-embed-arthas/src/main/webapp/index.js:11417— n has cyclomatic complexity 17 and cognitive complexity 15; 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 sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 17, cognitive 14) spring-embed-arthas/src/main/webapp/index.js:12082— (anonymous) has cyclomatic complexity 17 and cognitive complexity 14; 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 sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function handleQueryChange (cyclomatic 16, cognitive 21) spring-embed-arthas/src/main/webapp/index.js:2311— handleQueryChange has cyclomatic complexity 16 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function handleClick (cyclomatic 15, cognitive 27) spring-embed-arthas/src/main/webapp/index.js:10044— handleClick has cyclomatic complexity 15 and cognitive complexity 27; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function keydown (cyclomatic 15, cognitive 26) spring-embed-arthas/src/main/webapp/index.js:16734— keydown has cyclomatic complexity 15 and cognitive complexity 26; 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.
R2 · Cyclomatic Complexity· Complex function b (cyclomatic 15, cognitive 16) · ×1
Complex function b (cyclomatic 15, cognitive 16) spring-embed-arthas/src/main/webapp/index.js:14605— b has cyclomatic complexity 15 and cognitive complexity 16; 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.
R2 · Cyclomatic Complexity· Complex function created (cyclomatic 15, cognitive 14) · ×1
Complex function created (cyclomatic 15, cognitive 14) spring-embed-arthas/src/main/webapp/index.js:8418— created has cyclomatic complexity 15 and cognitive complexity 14; 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 sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 15, cognitive 14) spring-embed-arthas/src/main/webapp/index.js:9970— (anonymous) has cyclomatic complexity 15 and cognitive complexity 14; 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 sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. 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.
R2 · Cyclomatic Complexity· Complex function s (cyclomatic 15, cognitive 13) · ×1
Complex function s (cyclomatic 15, cognitive 13) spring-embed-arthas/src/main/webapp/index.js:2792— s has cyclomatic complexity 15 and cognitive complexity 13; 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 sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. 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.
R3 · Large Files· spring-embed-arthas/src/main/webapp/index.js · ×1
spring-embed-arthas/src/main/webapp/index.js: 17677 lines of code spring-embed-arthas/src/main/webapp/index.js:1— spring-embed-arthas/src/main/webapp/index.js has 17677 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· tools-manage/invocationlab-erd-online-view/src/pages/design/relation/g6.js · ×1
tools-manage/invocationlab-erd-online-view/src/pages/design/relation/g6.js: 1546 lines of code tools-manage/invocationlab-erd-online-view/src/pages/design/relation/g6.js:1— tools-manage/invocationlab-erd-online-view/src/pages/design/relation/g6.js has 1546 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· tools-manage/invocationlab-erd-online-view/src/store/version/useVersionStore.tsx · ×1
tools-manage/invocationlab-erd-online-view/src/store/version/useVersionStore.tsx: 1041 lines of code tools-manage/invocationlab-erd-online-view/src/store/version/useVersionStore.tsx:1— tools-manage/invocationlab-erd-online-view/src/store/version/useVersionStore.tsx has 1041 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· tools-manage/invocationlab-rpcpostman-view/src/views/pages/AccessService.vue · ×1
tools-manage/invocationlab-rpcpostman-view/src/views/pages/AccessService.vue: 907 lines of code tools-manage/invocationlab-rpcpostman-view/src/views/pages/AccessService.vue:1— tools-manage/invocationlab-rpcpostman-view/src/views/pages/AccessService.vue has 907 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· tools-manage/invocationlab-erd-online-view/src/utils/json2code.ts · ×1
tools-manage/invocationlab-erd-online-view/src/utils/json2code.ts: 841 lines of code tools-manage/invocationlab-erd-online-view/src/utils/json2code.ts:1— tools-manage/invocationlab-erd-online-view/src/utils/json2code.ts has 841 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· tools-manage/invocationlab-rpcpostman-view/src/views/pages/CaseManage.vue · ×1
tools-manage/invocationlab-rpcpostman-view/src/views/pages/CaseManage.vue: 804 lines of code tools-manage/invocationlab-rpcpostman-view/src/views/pages/CaseManage.vue:1— tools-manage/invocationlab-rpcpostman-view/src/views/pages/CaseManage.vue has 804 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
REDACTED: 735 lines of code REDACTED:1— REDACTED has 735 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· tools-manage/invocationlab-rpcpostman-view/src/views/pages/KafkaManage.vue · ×1
tools-manage/invocationlab-rpcpostman-view/src/views/pages/KafkaManage.vue: 640 lines of code tools-manage/invocationlab-rpcpostman-view/src/views/pages/KafkaManage.vue:1— tools-manage/invocationlab-rpcpostman-view/src/views/pages/KafkaManage.vue has 640 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· tools-manage/tools-manage-view/src/views/RedisManageView.vue · ×1
tools-manage/tools-manage-view/src/views/RedisManageView.vue: 589 lines of code tools-manage/tools-manage-view/src/views/RedisManageView.vue:1— tools-manage/tools-manage-view/src/views/RedisManageView.vue has 589 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· tools-manage/invocationlab-erd-online-view/src/utils/relation2file.js · ×1
tools-manage/invocationlab-erd-online-view/src/utils/relation2file.js: 567 lines of code tools-manage/invocationlab-erd-online-view/src/utils/relation2file.js:1— tools-manage/invocationlab-erd-online-view/src/utils/relation2file.js has 567 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· tools-manage/invocationlab-erd-online-view/src/pages/design/query/index.tsx · ×1
tools-manage/invocationlab-erd-online-view/src/pages/design/query/index.tsx: 459 lines of code tools-manage/invocationlab-erd-online-view/src/pages/design/query/index.tsx:1— tools-manage/invocationlab-erd-online-view/src/pages/design/query/index.tsx has 459 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/ConstructSqlForm.tsx · ×1
tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/ConstructSqlForm.tsx: 445 lines of code tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/ConstructSqlForm.tsx:1— tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/ConstructSqlForm.tsx has 445 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/ConstructSqlFormMongoDB.tsx · ×1
tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/ConstructSqlFormMongoDB.tsx: 435 lines of code tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/ConstructSqlFormMongoDB.tsx:1— tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/ConstructSqlFormMongoDB.tsx has 435 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
Dead file (~1582 LoC) tools-manage/invocationlab-erd-online-view/src/pages/design/relation/g6.js— no import path from any entry point (31 application, 13 tooling, 11 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (tools-manage/invocationlab-erd-online-view/src/pages/design/relation/index.tsx) — 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 (~1057 LoC) tools-manage/invocationlab-erd-online-view/src/store/version/useVersionStore.tsx— no import path from any entry point (31 application, 13 tooling, 11 test roots considered), but 8 in-repo import(s) from 8 other file(s) do name it (tools-manage/invocationlab-erd-online-view/src/components/dialog/version/AddVersion.tsx, tools-manage/invocationlab-erd-online-view/src/components/dialog/version/CompareVersion.tsx, tools-manage/invocationlab-erd-online-view/src/components/dialog/version/InitVersion.tsx and 5 more) — 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 (~935 LoC) tools-manage/invocationlab-rpcpostman-view/src/views/pages/AccessService.vue— no import path from any entry point (31 application, 13 tooling, 11 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 (~865 LoC) tools-manage/invocationlab-rpcpostman-view/src/views/pages/CaseManage.vue— no import path from any entry point (31 application, 13 tooling, 11 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 (~701 LoC) tools-manage/invocationlab-erd-online-view/src/pages/design/relation/erd.ts— no import path from any entry point (31 application, 13 tooling, 11 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 (~686 LoC) REDACTED— no import path from any entry point (31 application, 13 tooling, 11 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 (~586 LoC) tools-manage/invocationlab-rpcpostman-view/src/views/pages/KafkaManage.vue— no import path from any entry point (31 application, 13 tooling, 11 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 (~487 LoC) tools-manage/invocationlab-erd-online-view/src/pages/design/query/index.tsx— no import path from any entry point (31 application, 13 tooling, 11 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (tools-manage/invocationlab-erd-online-view/src/pages/design/table/index.tsx) — 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 (~468 LoC) tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/ConstructSqlForm.tsx— no import path from any entry point (31 application, 13 tooling, 11 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (tools-manage/invocationlab-erd-online-view/src/pages/design/query/index.tsx) — 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 (~465 LoC) tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/ConstructSqlFormMongoDB.tsx— no import path from any entry point (31 application, 13 tooling, 11 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (tools-manage/invocationlab-erd-online-view/src/pages/design/query/index.tsx) — 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 (~435 LoC) tools-manage/invocationlab-erd-online-view/src/components/CodeEditor/parser/select.js— no import path from any entry point (31 application, 13 tooling, 11 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (tools-manage/invocationlab-erd-online-view/src/components/CodeEditor/parser/sqlParser.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 (~392 LoC) tools-manage/invocationlab-erd-online-view/src/pages/design/setting/component/DatabaseSetUp.tsx— no import path from any entry point (31 application, 13 tooling, 11 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 (~373 LoC) tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/QueryResult.tsx— no import path from any entry point (31 application, 13 tooling, 11 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (tools-manage/invocationlab-erd-online-view/src/pages/design/query/index.tsx) — 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 (~371 LoC) REDACTED— no import path from any entry point (31 application, 13 tooling, 11 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (tools-manage/invocationlab-erd-online-view/src/components/Menu/index.tsx) — 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 (~353 LoC) tools-manage/invocationlab-erd-online-view/src/pages/project/group/component/GroupPermission.tsx— no import path from any entry point (31 application, 13 tooling, 11 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (tools-manage/invocationlab-erd-online-view/src/pages/project/group/component/GroupSetting.tsx) — 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 (~314 LoC) tools-manage/invocationlab-erd-online-view/src/components/CodeEditor/parser/lexter.js— no import path from any entry point (31 application, 13 tooling, 11 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (tools-manage/invocationlab-erd-online-view/src/components/CodeEditor/parser/select.js, REDACTED, tools-manage/invocationlab-erd-online-view/src/components/CodeEditor/parser/sqlParser.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 (~304 LoC) tools-manage/invocationlab-erd-online-view/src/pages/design/table/component/table/FieldMultiSelect.tsx— no import path from any entry point (31 application, 13 tooling, 11 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 (~302 LoC) REDACTED— no import path from any entry point (31 application, 13 tooling, 11 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (tools-manage/invocationlab-erd-online-view/src/components/CodeEditor/parser/select.js, tools-manage/invocationlab-erd-online-view/src/components/CodeEditor/parser/sqlParser.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 (~297 LoC) tools-manage/invocationlab-erd-online-view/src/components/LeftContent/DesignLeftContent/component/MetaDataSearch.tsx— no import path from any entry point (31 application, 13 tooling, 11 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (tools-manage/invocationlab-erd-online-view/src/components/LeftContent/DesignLeftContent/index.tsx) — 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 (~295 LoC) tools-manage/invocationlab-erd-online-view/src/components/LeftContent/DesignLeftContent/component/DataTable.tsx— no import path from any entry point (31 application, 13 tooling, 11 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (tools-manage/invocationlab-erd-online-view/src/components/LeftContent/DesignLeftContent/index.tsx, tools-manage/invocationlab-erd-online-view/src/pages/design/table/component/table/TableObjectList.tsx) — 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 (~292 LoC) tools-manage/invocationlab-erd-online-view/src/pages/JExcel/index.tsx— no import path from any entry point (31 application, 13 tooling, 11 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (tools-manage/invocationlab-erd-online-view/src/pages/design/setting/component/DefaultField.tsx, tools-manage/invocationlab-erd-online-view/src/pages/design/table/component/table/TableIndexEdit.tsx, tools-manage/invocationlab-erd-online-view/src/pages/design/table/component/table/TableInfoEdit.tsx) — 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 (~285 LoC) tools-manage/invocationlab-erd-online-view/src/layouts/DesignLayout/index.tsx— no import path from any entry point (31 application, 13 tooling, 11 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (tools-manage/invocationlab-erd-online-view/src/components/LeftContent/QueryLeftContent/component/QueryTree.tsx, tools-manage/invocationlab-erd-online-view/src/layouts/GroupLayout/index.tsx, tools-manage/invocationlab-erd-online-view/src/layouts/HomeLayout/index.tsx) — 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 (~262 LoC) tools-manage/invocationlab-erd-online-view/src/pages/design/version/index.tsx— no import path from any entry point (31 application, 13 tooling, 11 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (tools-manage/invocationlab-erd-online-view/src/pages/design/index.tsx) — 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 (~249 LoC) tools-manage/invocationlab-erd-online-view/src/pages/project/home/index.tsx— no import path from any entry point (31 application, 13 tooling, 11 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 (~241 LoC) tools-manage/invocationlab-erd-online-view/src/components/dialog/setup/DefaultField.tsx— no import path from any entry point (31 application, 13 tooling, 11 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (tools-manage/invocationlab-erd-online-view/src/components/dialog/setup/DefaultSetUp.tsx) — 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 (~229 LoC) tools-manage/invocationlab-erd-online-view/src/components/CodeEditor/index.tsx— no import path from any entry point (31 application, 13 tooling, 11 test roots considered), but 8 in-repo import(s) from 8 other file(s) do name it (tools-manage/invocationlab-erd-online-view/src/components/dialog/database/AddDatabase.tsx, tools-manage/invocationlab-erd-online-view/src/components/dialog/database/PreviewDatabase.tsx, tools-manage/invocationlab-erd-online-view/src/components/dialog/database/RenameDatabase.tsx and 5 more) — 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 (~225 LoC) tools-manage/invocationlab-erd-online-view/src/components/dialog/version/CompareVersion.tsx— no import path from any entry point (31 application, 13 tooling, 11 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (tools-manage/invocationlab-erd-online-view/src/components/Menu/index.tsx, tools-manage/invocationlab-erd-online-view/src/pages/design/version/index.tsx) — 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 (~223 LoC) tools-manage/invocationlab-erd-online-view/src/components/dialog/database/RenameDatabase.tsx— no import path from any entry point (31 application, 13 tooling, 11 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (tools-manage/invocationlab-erd-online-view/src/components/LeftContent/DesignLeftContent/component/DataDomain.tsx) — 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 (~196 LoC) tools-manage/invocationlab-erd-online-view/src/utils/dbversionutils.js— no import path from any entry point (31 application, 13 tooling, 11 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (tools-manage/invocationlab-erd-online-view/src/pages/design/table/component/table/TableCodeShow.tsx) — 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 (~191 LoC) tools-manage/invocationlab-rpcpostman-view/src/views/pages/CreateService.vue— no import path from any entry point (31 application, 13 tooling, 11 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 (~190 LoC) tools-manage/invocationlab-erd-online-view/src/components/JExcel/index.tsx— no import path from any entry point (31 application, 13 tooling, 11 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 (~188 LoC) tools-manage/invocationlab-erd-online-view/src/components/Menu/index.tsx— no import path from any entry point (31 application, 13 tooling, 11 test roots considered), but 11 in-repo import(s) from 11 other file(s) do name it (tools-manage/invocationlab-erd-online-view/src/components/Header/DesignHeader/index.tsx, tools-manage/invocationlab-erd-online-view/src/components/dialog/export/ExportDDL.tsx, tools-manage/invocationlab-erd-online-view/src/components/dialog/export/ExportHTML.tsx and 8 more) — 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 (~180 LoC) tools-manage/invocationlab-erd-online-view/src/pages/project/group/component/BasicSetting.tsx— no import path from any entry point (31 application, 13 tooling, 11 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 (~175 LoC) tools-manage/invocationlab-erd-online-view/src/pages/design/table/index.tsx— no import path from any entry point (31 application, 13 tooling, 11 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 (~173 LoC) tools-manage/invocationlab-erd-online-view/src/layouts/DesignLayout/_defaultProps.tsx— no import path from any entry point (31 application, 13 tooling, 11 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (tools-manage/invocationlab-erd-online-view/src/layouts/DesignLayout/index.tsx) — 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 (~171 LoC) tools-manage/invocationlab-rpcpostman-view/src/views/pages/CreateServiceJdk.vue— no import path from any entry point (31 application, 13 tooling, 11 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 (~169 LoC) tools-manage/invocationlab-erd-online-view/src/components/dialog/database/PreviewDatabase.tsx— no import path from any entry point (31 application, 13 tooling, 11 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (tools-manage/invocationlab-erd-online-view/src/components/dialog/database/RenameDatabase.tsx) — 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
Unused dependency '@blueprintjs/docs-theme' REDACTED:56— Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency '@emotion/css' REDACTED:63— Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency '@emotion/react' REDACTED:64— Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency '@emotion/styled' REDACTED:65— Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency '@mui/lab' REDACTED:69— Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency '@umijs/route-utils' REDACTED:74— Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'copy-to-clipboard' REDACTED:78— Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'dnd-kit' REDACTED:81— Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'dotenv' REDACTED:83— Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'dotenv-expand' REDACTED:84— Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'enzyme' REDACTED:135— Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'history' REDACTED:86— Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'jsdom-global' REDACTED:140— Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'mockjs' REDACTED:142— Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'omit.js' REDACTED:95— Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'react-helmet-async' REDACTED:101— Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'react-inlinesvg' REDACTED:102— Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'react-router' REDACTED:104— Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'react-router-dom' REDACTED:105— Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'sqlparser' REDACTED:110— Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'umi-presets-pro' REDACTED:149— Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'umi-serve' REDACTED:112— Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'use-immer' REDACTED:113— Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'diff-match-patch' REDACTED:25— Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'echarts' REDACTED:18— Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'file' REDACTED:29— Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'jsonlint' REDACTED:30— Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'regenerator-runtime' REDACTED:37— Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'svg-baker-runtime' REDACTED:35— Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'system' REDACTED:28— Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Third-party script without Subresource Integrity REDACTED:6— `http://libs.baidu.com/jquery/2.0.0/jquery.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. 2 such include(s) across the repository's markup.
X2 · Cancellation propagation· Async function without AbortSignal · ×1
Async function without AbortSignal: client tools-manage/invocationlab-erd-online-view/src/store/api/client.js:4— `client` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Orphaned file tools-manage/invocationlab-erd-online-view/src/pages/design/relation/erd.ts: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 tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/MongoDbServiceImpl.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 tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/ErdOnlineProjectServiceImpl.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 tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/service/impl/ErdOnlineProjectServiceImpl.kt: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 tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/KafkaServiceImpl.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 tools-manage/invocationlab-erd-online-view/src/utils/json2code.ts: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 tools-manage/tools-manage-admin/src/main/java/org/javamaster/spring/tools/manage/service/impl/RedisServiceImpl.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 b2c-parent/b2c-mybatis/src/main/java/org/javamaster/b2c/mybatis/entity/MenusExample.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 b2c-parent/b2c-mybatis/src/main/java/org/javamaster/b2c/mybatis/entity/ExamsExample.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 tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/ConstructSqlForm.tsx: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 tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/ConstructSqlFormMongoDB.tsx: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 handypoi-excel/src/main/java/cn/com/bluemoon/handypoi/excel/resolve/ExcelWriter.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 b2c-parent/b2c-core/src/main/java/org/javamaster/b2c/core/entity/MicrowebsiteExamExample.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 tools-manage/invocationlab-erd-online-view/src/pages/design/query/index.tsx: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 tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/RedisServiceImpl.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 b2c-parent/b2c-core/src/main/java/org/javamaster/b2c/core/entity/SysRememberMeExample.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 tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/service/impl/RedisServiceImpl.kt: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 tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/ErdOnlineRoleServiceImpl.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 tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/controller/RpcPostmanServiceQueryController.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 tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/QueryResult.tsx: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 tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/service/impl/ErdOnlineRoleServiceImpl.kt: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 tools-manage/invocationlab-erd-online-view/src/store/project/profileSlice.tsx: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 tools-manage/invocationlab-erd-online-view/src/pages/design/setting/component/DatabaseSetUp.tsx: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 tools-manage/invocationlab-erd-online-view/src/components/LeftContent/DesignLeftContent/component/MetaDataSearch.tsx: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 tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/GlobalHandler.kt:26— `error` at line 26 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, 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 with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/GlobalHandler.kt:36— `error` at line 36 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, 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 with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/service/registry/impl/ZkRegister.kt:74— `info` at line 74 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, 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 with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/service/load/impl/JarLocalFileLoader.kt:84— `warn` at line 84 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, 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 with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/service/invocation/impl/DubboConverter.kt:40— `error` at line 40 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, 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 with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/service/invocation/impl/DubboInvoker.kt:42— `info` at line 42 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, 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 with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/service/invocation/impl/DubboInvoker.kt:106— `info` at line 106 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, 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 with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/controller/RpcPostmanProxyController.kt:62— `debug` at line 62 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, 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 with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/config/Initializer.kt:36— `info` at line 36 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, 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 with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/config/Initializer.kt:44— `info` at line 44 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, 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 with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/config/Initializer.kt:74— `info` at line 74 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, 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 with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/config/Initializer.kt:78— `info` at line 78 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, 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 with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/config/Initializer.kt:85— `info` at line 85 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, 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 with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/config/Initializer.kt:102— `info` at line 102 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, 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 with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/config/Initializer.kt:109— `info` at line 109 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, 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 with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/registry/impl/ZkRegister.java:83— `info` at line 83 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 tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/load/impl/JarLocalFileLoader.java:94— `warn` at line 94 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 tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/invocation/impl/DubboConverter.java:49— `error` at line 49 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 tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/invocation/impl/DubboInvoker.java:44— `info` at line 44 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 tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/invocation/impl/DubboInvoker.java:109— `info` 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.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 tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/controller/RpcPostmanProxyController.java:64— `debug` at line 64 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 REDACTED:44— `info` at line 44 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 REDACTED:51— `info` at line 51 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 REDACTED:82— `info` at line 82 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 REDACTED:86— `info` at line 86 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.
Duplicated predicate b2c-parent/b2c-core/src/main/java/org/javamaster/b2c/core/config/DatabaseConfig.java:81— `clz.isEnum() && EnumBase.class.isAssignableFrom(clz)` appears character-identically in 2 files — b2c-parent/b2c-core/src/main/java/org/javamaster/b2c/core/config/DatabaseConfig.java, b2c-parent/b2c-core/src/main/java/org/javamaster/b2c/core/jackson/EnumBaseModule.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 tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/ConstructSqlForm.tsx:103— `!conditionsChoose || conditionsChoose.length === 0` appears character-identically in 2 files — tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/ConstructSqlForm.tsx, tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/ConstructSqlFormMongoDB.tsx. 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 tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/ConstructSqlForm.tsx:93— `!tableNameChoose || !tableColumnNamesChoose` appears character-identically in 2 files — tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/ConstructSqlForm.tsx, tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/ConstructSqlFormMongoDB.tsx. 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 tools-manage/invocationlab-erd-online-view/src/pages/design/relation/g6.js:420— `(!header.relationNoShow) && (header.fieldName !== 'relationNoShow')` appears character-identically in 2 files — tools-manage/invocationlab-erd-online-view/src/pages/design/relation/g6.js, tools-manage/invocationlab-erd-online-view/src/utils/relation2file.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 tools-manage/invocationlab-erd-online-view/src/pages/design/relation/g6.js:699— `(cfg.size && cfg.size[0]) || model.width` appears character-identically in 2 files — tools-manage/invocationlab-erd-online-view/src/pages/design/relation/g6.js, tools-manage/invocationlab-erd-online-view/src/utils/relation2file.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 tools-manage/invocationlab-erd-online-view/src/pages/design/relation/g6.js:700— `(cfg.size && cfg.size[1]) || model.height` appears character-identically in 2 files — tools-manage/invocationlab-erd-online-view/src/pages/design/relation/g6.js, tools-manage/invocationlab-erd-online-view/src/utils/relation2file.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 tools-manage/invocationlab-erd-online-view/src/pages/design/relation/g6.js:759— `(currType && currType.name + field.remark) || field[fieldName]` appears character-identically in 2 files — tools-manage/invocationlab-erd-online-view/src/pages/design/relation/g6.js, tools-manage/invocationlab-erd-online-view/src/utils/relation2file.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 tools-manage/invocationlab-erd-online-view/src/pages/design/relation/g6.js:778— `(realHeight && ((realHeight - titleBox.height) / l)) || 20` appears character-identically in 2 files — tools-manage/invocationlab-erd-online-view/src/pages/design/relation/g6.js, tools-manage/invocationlab-erd-online-view/src/utils/relation2file.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 tools-manage/invocationlab-erd-online-view/src/pages/design/relation/g6.js:704— `ass.to && ass.from.entity === model.title.split(':')[0]` appears character-identically in 2 files — tools-manage/invocationlab-erd-online-view/src/pages/design/relation/g6.js, tools-manage/invocationlab-erd-online-view/src/utils/relation2file.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 tools-manage/invocationlab-erd-online-view/src/components/LeftContent/QueryLeftContent/component/QueryTree.tsx:33— `cache.getItem(CONSTANT.PROJECT_ID) || ''` appears character-identically in 8 files — tools-manage/invocationlab-erd-online-view/src/components/LeftContent/QueryLeftContent/component/QueryTree.tsx, tools-manage/invocationlab-erd-online-view/src/components/dialog/query/AddQuery.tsx, tools-manage/invocationlab-erd-online-view/src/components/dialog/query/AddQueryFolder.tsx, tools-manage/invocationlab-erd-online-view/src/layouts/DesignLayout/index.tsx. 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 tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/ConstructSqlForm.tsx:135— `conditionChoose && conditionChoose.columnSort` appears character-identically in 2 files — tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/ConstructSqlForm.tsx, tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/ConstructSqlFormMongoDB.tsx. 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 tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/ConstructSqlForm.tsx:456— `el && el.style.setProperty('margin-left', '200px', 'important')` appears character-identically in 2 files — tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/ConstructSqlForm.tsx, tools-manage/invocationlab-erd-online-view/src/pages/design/query/component/ConstructSqlFormMongoDB.tsx. 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 tools-manage/invocationlab-erd-online-view/src/pages/design/relation/g6.js:757— `fieldName === 'type' && field[fieldName]` appears character-identically in 2 files — tools-manage/invocationlab-erd-online-view/src/pages/design/relation/g6.js, tools-manage/invocationlab-erd-online-view/src/utils/relation2file.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 tools-manage/invocationlab-erd-online-view/src/pages/design/relation/g6.js:829— `firstGroup && firstGroup.get('children')[0] && firstGroup.get('children')[0].getBBox().height || 13` appears character-identically in 2 files — tools-manage/invocationlab-erd-online-view/src/pages/design/relation/g6.js, tools-manage/invocationlab-erd-online-view/src/utils/relation2file.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 REDACTED:114— `formRef && formRef.current?.resetFields()` appears character-identically in 2 files — REDACTED, tools-manage/invocationlab-erd-online-view/src/pages/design/setting/component/DatabaseSetUp.tsx. 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:78— `formRef && formRef.current?.validateFields()` appears character-identically in 2 files — REDACTED, tools-manage/invocationlab-erd-online-view/src/pages/design/setting/component/DatabaseSetUp.tsx. 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 tools-manage/invocationlab-erd-online-view/src/layouts/DesignLayout/index.tsx:247— `item.path?.startsWith('http') || item.exact` appears character-identically in 3 files — tools-manage/invocationlab-erd-online-view/src/layouts/DesignLayout/index.tsx, tools-manage/invocationlab-erd-online-view/src/layouts/GroupLayout/index.tsx, tools-manage/invocationlab-erd-online-view/src/layouts/HomeLayout/index.tsx. 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 tools-manage/invocationlab-erd-online-view/src/store/version/useVersionStore.tsx:237— `name !== 'typeName' && name !== 'dataType' && checkField[name] !== currentField[name]` appears character-identically in 2 files — tools-manage/invocationlab-erd-online-view/src/store/version/useVersionStore.tsx, tools-manage/invocationlab-erd-online-view/src/utils/dbversionutils.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 tools-manage/invocationlab-erd-online-view/src/components/dialog/dataType/AddDataType.tsx:17— `state.project.projectJSON.dataTypeDomains?.database || []` appears character-identically in 4 files — tools-manage/invocationlab-erd-online-view/src/components/dialog/dataType/AddDataType.tsx, tools-manage/invocationlab-erd-online-view/src/components/dialog/dataType/RenameDataType.tsx, tools-manage/invocationlab-erd-online-view/src/components/dialog/database/AddDatabase.tsx, tools-manage/invocationlab-erd-online-view/src/components/dialog/database/RenameDatabase.tsx. 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:30— `state.project.projectJSON?.dataTypeDomains?.database || []` appears character-identically in 2 files — REDACTED, tools-manage/invocationlab-erd-online-view/src/pages/design/setting/component/DatabaseSetUp.tsx. 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 tools-manage/invocationlab-erd-online-view/src/components/dialog/export/ExportDDL.tsx:29— `state.project.projectJSON?.profile?.dbs || []` appears character-identically in 6 files — tools-manage/invocationlab-erd-online-view/src/components/dialog/export/ExportDDL.tsx, tools-manage/invocationlab-erd-online-view/src/components/dialog/import/ReverseDatabase.tsx, REDACTED, tools-manage/invocationlab-erd-online-view/src/pages/design/export/component/ExportDDL.tsx. 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 tools-manage/invocationlab-erd-online-view/src/pages/design/relation/g6.js:429— `tempNodesId.includes(edge.source) && tempNodesId.includes(edge.target)` appears character-identically in 2 files — tools-manage/invocationlab-erd-online-view/src/pages/design/relation/g6.js, tools-manage/invocationlab-erd-online-view/src/utils/relation2file.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 tools-manage/invocationlab-erd-online-view/src/components/dialog/version/SyncVersion.tsx:38— `versions[currentVersionIndex + 1] || currentVersion` appears character-identically in 2 files — tools-manage/invocationlab-erd-online-view/src/components/dialog/version/SyncVersion.tsx, tools-manage/invocationlab-erd-online-view/src/store/version/useVersionStore.tsx. 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 tools-manage/invocationlab-erd-online-view/src/components/LeftContent/DesignLeftContent/component/DataTable.tsx:183— `window.innerHeight || document.documentElement.clientHeight || document.body.clientHeight` appears character-identically in 2 files — tools-manage/invocationlab-erd-online-view/src/components/LeftContent/DesignLeftContent/component/DataTable.tsx, tools-manage/invocationlab-erd-online-view/src/pages/design/relation/index.tsx. 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 tools-manage/invocationlab-erd-online-view/src/pages/design/relation/index.tsx:32— `window.innerWidth || document.documentElement.clientWidth || document.body.clientWidth` appears character-identically in 2 files — tools-manage/invocationlab-erd-online-view/src/pages/design/relation/index.tsx, tools-manage/invocationlab-erd-online-view/src/pages/design/table/component/table/TableIndexEdit.tsx. 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.
Blanket warning suppression tools-manage/invocationlab-erd-online-view/src/access.ts:1— A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead.
Blanket warning suppression tools-manage/invocationlab-erd-online-view/src/components/JExcel/index.tsx:1— A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead.
Blanket warning suppression tools-manage/invocationlab-erd-online-view/src/pages/JExcel/index.tsx:1— A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead.
Blanket warning suppression tools-manage/invocationlab-erd-online-view/src/pages/design/relation/Contex.js:1— A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead.
Blanket warning suppression tools-manage/invocationlab-erd-online-view/src/pages/design/relation/g6.js:15— A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead.
Blanket warning suppression tools-manage/invocationlab-erd-online-view/src/pages/design/relation/g6.js:109— A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead.
Blanket warning suppression tools-manage/invocationlab-erd-online-view/src/pages/design/relation/g6.js:483— A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead.
Blanket warning suppression tools-manage/invocationlab-erd-online-view/src/pages/design/relation/g6.js:847— A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead.
Blanket warning suppression tools-manage/invocationlab-erd-online-view/src/services/ant-design-pro/api.ts:2— A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead.
Blanket warning suppression tools-manage/invocationlab-erd-online-view/src/services/ant-design-pro/index.ts:2— A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead.
Blanket warning suppression tools-manage/invocationlab-erd-online-view/src/services/ant-design-pro/login.ts:2— A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead.
Blanket warning suppression tools-manage/invocationlab-erd-online-view/src/services/swagger/index.ts:2— A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead.
Blanket warning suppression tools-manage/invocationlab-erd-online-view/src/services/swagger/pet.ts:2— A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead.
Blanket warning suppression tools-manage/invocationlab-erd-online-view/src/services/swagger/store.ts:2— A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead.
Blanket warning suppression tools-manage/invocationlab-erd-online-view/src/services/swagger/user.ts:2— A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead.
Blanket warning suppression tools-manage/invocationlab-erd-online-view/src/utils/dbversionutils.js:1— A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead.
Blanket warning suppression tools-manage/invocationlab-erd-online-view/src/utils/generatehtml.js:1— A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead.
Blanket warning suppression tools-manage/invocationlab-erd-online-view/src/utils/json2code.ts:1— A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead.
Blanket warning suppression tools-manage/invocationlab-erd-online-view/src/utils/markdown.js:1— A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead.
Blanket warning suppression tools-manage/invocationlab-erd-online-view/src/utils/relation2file.js:1— A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead.
Blanket warning suppression tools-manage/invocationlab-erd-online-view/src/utils/string.js:1— A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead.
Blanket warning suppression tools-manage/invocationlab-erd-online-view/src/utils/uuid.js:1— A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead.
Blanket warning suppression tools-manage/invocationlab-rpcpostman-view/build/dev-client.js:1— A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead.
Fat interface: IModulesDispatchSlice (17 required operations) tools-manage/invocationlab-erd-online-view/src/store/project/modulesSlice.tsx:35— `IModulesDispatchSlice` declares 17 required operations: `addModule`, `renameModule`, `removeModule`, `updateModule`, `copyModule`, `cutModule`, `pastModule`, `refreshModule`, `updateRelation`, `setCurrentModule`, `updateAllModules`, `getOriginalModules`, `getModuleEntityTree`, `getModuleEntityFieldTree`, `setExpandedKey`, `setExpandedKeys`, `getExpandedKeys`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Fat interface: IProfileDispatchSlice (24 required operations) tools-manage/invocationlab-erd-online-view/src/store/project/profileSlice.tsx:15— `IProfileDispatchSlice` declares 24 required operations: `addDefaultFields`, `removeDefaultFields`, `updateDefaultFields`, `updateDefaultFieldsType`, `updateSqlConfig`, `addDbs`, `removeDbs`, `updateDbs`, `updateAllDbs`, `setCurrentDbKey`, `setDefaultDb`, `updateWordTemplateConfig`, `updateProfile`, `getCurrentDBName`, `getCurrentDBData`, `setProfileSliceState`, `dbReverseParse`, `checkField`, `getAllTable`, `saveSelectedRowKeys`, `getSelectedEntity`, `importReverseTable`, `getDefaultFields`, `downloadWordTemplate`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Fat interface: ErdOnlineProjectService (17 abstract methods) tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/ErdOnlineProjectService.java:24— `ErdOnlineProjectService` declares 17 abstract methods: `createProject`, `delRecordsVoFromGroupUsers`, `deleteProject`, `eraseSensitiveInfo`, `exportErd`, `findRecordsVoByProjectId`, `getDefaultDb`, `getProjectBasicInfo`, `getProjectDetail`, `getProjectList`, `refreshProjectModule`, `resumeSensitiveInfo`, `saveProject`, `saveRecordsVoToGroupUsers`, `sortModule`, `statistic`, `updateProjectBasicInfo`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Fat interface: ErdOnlineProjectService (17 abstract methods) tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/service/ErdOnlineProjectService.kt:12— `ErdOnlineProjectService` declares 17 abstract methods: `statistic`, `getProjectList`, `saveRecordsVoToGroupUsers`, `delRecordsVoFromGroupUsers`, `findRecordsVoByProjectId`, `getProjectDetail`, `eraseSensitiveInfo`, `resumeSensitiveInfo`, `getDefaultDb`, `createProject`, `deleteProject`, `updateProjectBasicInfo`, `saveProject`, `refreshProjectModule`, `getProjectBasicInfo`, `exportErd`, `sortModule`. Counted over its public functions with no body, once per name; default-bodied functions and properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
redundant comment REDACTED:138— "{{{ parseOneSource()" repeats the code it sits on: 3 of its 3 words (parse, one, source) are already in `function parseOneSource(part)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment REDACTED:216— "{{{ parseOneWhere()" repeats the code it sits on: 3 of its 3 words (parse, one, where) are already in `function parseOneWhere(part)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment tools-manage/invocationlab-erd-online-view/src/pages/design/table/component/table/FieldMultiSelect.tsx:76— "Delete the item if the user manually created it." repeats the code it sits on: 4 of its 5 words (delete, item, user, created) are already in `return {`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×3
Projects may be oversized for their cohesion REDACTED:1— `tools-manage/invocationlab-erd-online-view` (27046 LoC, 205 module-visible types across 76 directories) overshoots its size bounds. 3 of 28 build unit(s) (Gradle, Maven, npm) overshoot their size bounds, lowering Project Cohesion to 7.9/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— `tools-manage/invocationlab-admin` (16200 LoC, 241 module-visible types across 49 directories) overshoots its size bounds. 3 of 28 build unit(s) (Gradle, Maven, npm) overshoot their size bounds, lowering Project Cohesion to 7.9/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 tools-manage/invocationlab-admin-21/build.gradle.kts:1— `tools-manage/invocationlab-admin-21` (11069 LoC, 302 module-visible types across 45 directories) overshoots its size bounds. 3 of 28 build unit(s) (Gradle, Maven, npm) overshoot their size bounds, lowering Project Cohesion to 7.9/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 tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/impl/AbstractDbService.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 tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/service/impl/AbstractDbService.kt: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 tools-manage/invocationlab-erd-online-view/src/store/version/useVersionStore.tsx: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.
Silent fallback default in catch b2c-parent/b2c-bytecode/src/main/java/org/javamaster/b2c/bytecode/model/PersonCopy.java:36— `increaseAge` swallows every exception into `return -1` — a data error becomes a silent behavior change with no trail. Log the failure or let it propagate. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment in the catch or in the Javadoc, and the row stops firing.
Silent fallback default in catch spring-embed-arthas/src/main/webapp/vue.js:320— `looseEqual` swallows every exception into `return false` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Documentation: no build, run or usage example tools-manage/invocationlab-erd-online-view/README.md:1— `invocationlab-erd-online-view` is runnable (a `start` script in `REDACTED`) and neither `tools-manage/invocationlab-erd-online-view/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
No ADRs found REDACTED:62— 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 `REDACTED` makes this repository a deployable product (line 62).
D21 · Naming Consistency· `postgreSQL` spells `SQL` where 36 names in the project spell it `Sql` · ×1
`postgreSQL` spells `SQL` where 36 names in the project spell it `Sql` tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/model/erd/ApplyBean.kt:28— 36 of 38 names in project invocationlab-admin-21 spell the token `Sql` (36 of 38; unit: names in project invocationlab-admin-21 containing `Sql`). Peers: ErdOnlineQueryController.execSql (tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/controller/ErdOnlineQueryController.kt:106); ErdOnlineQueryController.exportSql (tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/controller/ErdOnlineQueryController.kt:148); EntitiesBean.originalCreateTableSql (tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/model/erd/EntitiesBean.kt:18); DbService.getCheckSql (tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/service/DbService.kt:14); DbService.execSql (tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/service/DbService.kt:26). Rename to `postgreSql`. [rule N6]
D21 · Naming Consistency· `PostgreSQLBean` spells `SQL` where 36 names in the project spell it `Sql` · ×1
`PostgreSQLBean` spells `SQL` where 36 names in the project spell it `Sql` tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/model/erd/ApplyBean.kt:56— 36 of 38 names in project invocationlab-admin-21 spell the token `Sql` (36 of 38; unit: names in project invocationlab-admin-21 containing `Sql`). Peers: ErdOnlineQueryController.execSql (tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/controller/ErdOnlineQueryController.kt:106); ErdOnlineQueryController.exportSql (tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/controller/ErdOnlineQueryController.kt:148); EntitiesBean.originalCreateTableSql (tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/model/erd/EntitiesBean.kt:18); DbService.getCheckSql (tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/service/DbService.kt:14); DbService.execSql (tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/service/DbService.kt:26). Rename to `PostgreSqlBean`. [rule N6]
D21 · Naming Consistency· `groupID` spells `ID` where 126 names in the project spell it `Id` · ×1
`groupID` spells `ID` where 126 names in the project spell it `Id` tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/service/GAV.kt:8— 126 of 128 names in project invocationlab-admin-21 spell the token `Id` (126 of 128; unit: names in project invocationlab-admin-21 containing `Id`). Peers: ErdOnlineProjectController.getProjectBasicInfo(projectId) (tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/controller/ErdOnlineProjectController.kt:121); ErdOnlineQueryController.getQueryTreeList(projectId) (tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/controller/ErdOnlineQueryController.kt:45); ErdOnlineQueryController.deleteQueryTree(projectId) (tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/controller/ErdOnlineQueryController.kt:58); ErdOnlineQueryController.deleteQueryTree(treeNodeId) (tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/controller/ErdOnlineQueryController.kt:58); ErdOnlineQueryController.queryTree(treeNodeId) (tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/controller/ErdOnlineQueryController.kt:63). Rename to `groupId`. [rule N6]
D21 · Naming Consistency· `artifactID` spells `ID` where 126 names in the project spell it `Id` · ×1
`artifactID` spells `ID` where 126 names in the project spell it `Id` tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/service/GAV.kt:9— 126 of 128 names in project invocationlab-admin-21 spell the token `Id` (126 of 128; unit: names in project invocationlab-admin-21 containing `Id`). Peers: ErdOnlineProjectController.getProjectBasicInfo(projectId) (tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/controller/ErdOnlineProjectController.kt:121); ErdOnlineQueryController.getQueryTreeList(projectId) (tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/controller/ErdOnlineQueryController.kt:45); ErdOnlineQueryController.deleteQueryTree(projectId) (tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/controller/ErdOnlineQueryController.kt:58); ErdOnlineQueryController.deleteQueryTree(treeNodeId) (tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/controller/ErdOnlineQueryController.kt:58); ErdOnlineQueryController.queryTree(treeNodeId) (tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/controller/ErdOnlineQueryController.kt:63). Rename to `artifactId`. [rule N6]
D21 · Naming Consistency· `PostgreSQLBean` spells `SQL` where 45 names in the project spell it `Sql` · ×1
`PostgreSQLBean` spells `SQL` where 45 names in the project spell it `Sql` tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/model/erd/ApplyBean.java:53— 45 of 46 names in project invocationlab-admin spell the token `Sql` (45 of 46; unit: names in project invocationlab-admin containing `Sql`). Peers: ErdOnlineQueryController.execSql (tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/controller/ErdOnlineQueryController.java:116); ErdOnlineQueryController.execSqlMongo (tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/controller/ErdOnlineQueryController.java:126); ErdOnlineQueryController.exportSql (tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/controller/ErdOnlineQueryController.java:172); DbService.execSql (tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/DbService.java:30); DbService.exportSql (tools-manage/invocationlab-admin/src/main/java/org/javamaster/invocationlab/admin/service/DbService.java:32). Rename to `PostgreSqlBean`. [rule N6]
D28 · Secrets (history)· Rotate the exposed credentials · ×1
Dormant codebase — 286 of 286 significant files have no living knowledge — the codebase as a whole is dormant, not 286 separate risks. Counted over 286 of the 1001 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over. Re-engage owners or document before change.
Thin README README.md:1— The root README is 102 words, against a bar of 120. Of the three newcomer-critical sections this check looks for by heading, in the README and in the repository documents it links, it found no a build/run or getting-started section, no an architecture or project-map section. Sections are matched on HEADING text only, so material written under a heading this check does not recognise — or with no heading at all — is not seen and this row may understate what the document covers.
No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
README/code drift tools-manage/tools-manage-view/README.md:4— tools-manage/tools-manage-view/README.md names Vue 3, but the manifest declares `vue` 2.5.17. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
Logging is not universal — Only 16/22 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `b2c-parent/b2c-classloader`, `b2c-parent/b2c-mybatis`, `spring-transactional`, `springboot-autoconfiguration`, `tools-manage/invocationlab-erd-online-view` and 1 more.
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) — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 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:52— `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 security response headers detected tools-manage/invocationlab-erd-online-view/ci/conf/nginx.conf:66— 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 `nginx.conf` 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.)
S1 · Web-Security Posture· Information-disclosure response header set · ×1
Information-disclosure response header set tools-manage/invocationlab-admin/src/main/resources/public/invocationlab-rpcpostman-view/static/js/chunk-libs.783b4dbe.js:1— `product` is set explicitly here. The OWASP Secure Headers Project lists it among the response headers to REMOVE: it names the server, framework or tooling behind the application, which is exactly what an attacker looks up known exploits for. (No deduction on this card.)
X2 · Cancellation propagation· Not all async functions that make a request accept an AbortSignal · ×1
Not all async functions that make a request accept an AbortSignal — Only 0/1 async functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
X5 · Nullable reference types· Strict null checking is not enabled everywhere the repository type-checks · ×1
Strict null checking is not enabled everywhere the repository type-checks — 1/3 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.
doc comments repeat the names tools-manage/invocationlab-erd-online-view/src/global.tsx:87— 0 of 4 documented parameters and 0 of 36 summaries in `Invocationlab-ERD-Online` only repeat the member or parameter name (e.g. "" for `template`). 4 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
doc comments repeat the names tools-manage/invocationlab-rpcpostman-view/config/index.js:63— 0 of 0 documented parameters and 1 of 3 summaries in `invocationlab-rpc-postman` only repeat the member or parameter name (e.g. "Source Maps" for `productionSourceMap`). Delete the restating tags, or add what the name does not say.
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 17 file(s) — `spring-embed-arthas/src/main/webapp/index.js`, `spring-embed-arthas/src/main/webapp/vue.js`, `tools-manage/invocationlab-admin-21/build.gradle.kts`, `tools-manage/invocationlab-admin-21/src/main/kotlin/org/javamaster/invocationlab/admin/redis/TripleFunction.kt`, `tools-manage/invocationlab-admin/src/main/resources/public/invocationlab-erd-online-view/1177.23fe5a99.async.js`, … (+12 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
Run 01a1e8b3-c9b3-78ab-a00b-cba1be5a3907 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 524 · Warnings: 1045 · Recommendations: 447 · Info: 209 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 17-11-2026 @ 08:50 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.