Public report of shuzheng/zheng, published 24 October 2026. It has the same score, grades and number of findings as the full report. The details of security findings (where they are in the code, which known vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive report Measured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.10.5). Watchdog 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, 24 October 2026, 07:28 UTC · Survey ID cd_8231e67e87cb43b799f36620206a80b2

shuzheng/zheng

Measured 24 October 2026, 07:25 UTC, at code version 7005c0a

Regression: 1 dimension fell since the last survey Supply-chain provenance & signing: not measured

A regression is a drop of 0.5 points or more in the score, or of 2.5 or more out of 10 in a dimension, since the last survey.

Supply-chain provenance & signing is not measured: Supply-chain provenance is not scored (this pipeline releases no artifact), but its build steps or GitHub Actions workflows have integrity defects, or nothing watches its dependency set for published advisories.

CAI score 24out of 100 At risk Down 1 since the last survey

The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.

Architecture 98 Exemplary Performance 61 Adequate Security and Compliance 54 Adequate Maturity 43 Weak Accessibility 31 Weak Code Health 24 Critical Production Readiness 12 Critical

A medium codebase: 33,615 lines of product code in 41 projects, tests not counted · Estimated rebuild effort: about 0.2 person-years · Weakest lens: Production Readiness, 12

Findings by how serious they are

172 critical 408 serious 170 minor

15 dimensions are left out of the score. For each one, Watchdog either couldn't measure it in this code, or found no evidence of the safeguard it looks for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.

This survey was produced by

Watchdog
Producer
Canine Development
Analyzer
Watchdog engine 1.0.0
Measured
24 October 2026, 07:25 UTC

A measurement, not a certificate. The Code Assurance Index records a number together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee the code. The standard was written by Canine Development, which also builds Watchdog. It is open to any tool that implements it, and today Watchdog is the only one that does.

A critical security finding is open, such as a library with a known critical vulnerability or a password or key found in the code. The score itself is unchanged, but its band shows At risk until the finding is fixed. See the Security and Compliance lens.

The score is deterministic, which means the same code always gets the same score. Watchdog works it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸

74of 77 dimensions measured by tools. The other 3 are advisory notes from an AI model, which explain the code but don't count towards the score.
735of 750 findings point to an exact file and line, so you can open each one in the code. The other 15 concern the repository as a whole, such as missing documentation.
77dimensions across 7 lenses, read from 33,615 lines of product code in 41 projects.
Chapters

Executive summary

shuzheng/zheng scores 24 out of 100, but it is rated At risk while a critical security finding is open; the score itself is unchanged.

The weakest lens counts most in the score, and here that is Production Readiness, which scores 12 and is rated Critical. Its REDACTED Scanning dimension scores 0 out of 10, and until that reaches 4, Production Readiness can't be rated higher than Adequate. The first actions are to resolve the 3 No assertions finding(s) in Test Quality and to resolve the 53 Leaked secret finding(s) in REDACTED Scanning, and if Production Readiness rose to 70, the score would rise from 24 to about 34.

172 findings are critical: 53 in REDACTED Scanning, 42 in Secrets (history), 40 in Forms & labels, 20 in Dependency Vulnerabilities, 12 in Page structure, two in Keyboard semantics, two in Text alternatives and one in Static Analysis (SAST).

Watchdog couldn't measure 13 dimensions in this code, among them Code Coverage, Test Reliability and Dependency Hygiene, so they are left out of the score. The product code is 33,615 lines, which would take an estimated 0.2 person-years, around €29,000, to rebuild.

Code Health 24 ⚠ Critical, capped by God Classes, Type Safety, Large Files, Dead Code and Nullable reference types Architecture 98 ★ Exemplary Maturity 43 Weak, capped by Knowledge Freshness and Architecture documentation Production Readiness 12 ⚠ Critical, capped by REDACTED Scanning, Test Coverage, CI/CD gates and Security & performance tooling Security and Compliance 54 Adequate, capped by Secrets (history) and Dependency Vulnerabilities Accessibility 31 Weak, capped by Text alternatives, Page structure, Keyboard semantics and Visual & motion safety Performance 61 Adequate

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 for The 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.
Production Readiness 12 · counts for 46%Code Health 24 · counts for 25%Accessibility 31 · counts for 14%Maturity 43 · counts for 8%Security and Compliance 54 · counts for 4%Performance 61 · counts for 2%Architecture 98 · counts for 1%

If Production Readiness rose from 12 to 70, the lowest score rated Strong, the score would rise from 24 to about 34.

Code composition: what the lines of code are
Product code 99%Tests 1%
New since the last survey: 100 findings

These 100 critical or serious findings weren't in the previous survey, on 10 October 2026.

Watchdog compares every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.

Fixed since the last survey: 288 findings

These 288 critical or serious findings were in the previous survey, on 10 October 2026, and are gone from this one. The first 100 are listed here.

  • Forms & labels · <input> without a programmatic label zheng-cms/zheng-cms-admin/src/main/webapp/WEB-INF/jsp/manage/comment/update.jsp
  • Forms & labels · <input> without a programmatic label zheng-cms/zheng-cms-admin/src/main/webapp/WEB-INF/jsp/manage/comment/update.jsp
  • Forms & labels · <select> without a programmatic label zheng-cms/zheng-cms-admin/src/main/webapp/WEB-INF/jsp/manage/menu/create.jsp
  • Forms & labels · <select> without a programmatic label zheng-cms/zheng-cms-admin/src/main/webapp/WEB-INF/jsp/manage/menu/update.jsp
  • Forms & labels · <input> without a programmatic label zheng-message/zheng-message-client/ack-index.html
  • Forms & labels · <input> without a programmatic label REDACTED
  • Forms & labels · <input> without a programmatic label REDACTED
  • Forms & labels · <input> without a programmatic label REDACTED
  • Forms & labels · <input> without a programmatic label REDACTED
  • Forms & labels · <input> without a programmatic label REDACTED
  • Forms & labels · <input> without a programmatic label REDACTED
  • Forms & labels · <textarea> without a programmatic label zheng-ui/zheng-cms-web/blog/details/index.html
  • Forms & labels · <textarea> without a programmatic label zheng-ui/zheng-cms-web/news/article/index.html
  • Forms & labels · <textarea> without a programmatic label zheng-ui/zheng-cms-web/qa/question/index.html
  • Forms & labels · <input> without a programmatic label zheng-ui/zheng-oss-web/aliyun/upload.html
  • Forms & labels · <input> without a programmatic label zheng-ui/zheng-oss-web/aliyun/upload.html
  • Forms & labels · <input> without a programmatic label zheng-ui/zheng-oss-web/aliyun/upload.html
  • Forms & labels · <input> without a programmatic label zheng-ui/zheng-oss-web/aliyun/upload.html
  • Forms & labels · <input> without a programmatic label zheng-ui/zheng-oss-web/aliyun/upload.html
  • Forms & labels · <input> without a programmatic label zheng-ui/zheng-oss-web/aliyun/upload.html
  • Forms & labels · <input> without a programmatic label zheng-ui/zheng-oss-web/aliyun/upload.html
  • Forms & labels · Link with no accessible name zheng-ui/zheng-ucenter-web/login.html
  • Forms & labels · Link with no accessible name zheng-ui/zheng-ucenter-web/login.html
  • Forms & labels · Link with no accessible name zheng-ui/zheng-ucenter-web/login.html
  • Forms & labels · Link with no accessible name zheng-ui/zheng-ucenter-web/login.html
  • Forms & labels · <input> without a programmatic label zheng-ui/zheng-ucenter-web/password.html
  • Forms & labels · <input> without a programmatic label zheng-ui/zheng-ucenter-web/password.html
  • Forms & labels · Link with no accessible name zheng-ui/zheng-ucenter-web/password.html
  • Forms & labels · Link with no accessible name zheng-ui/zheng-ucenter-web/password.html
  • Forms & labels · Link with no accessible name zheng-ui/zheng-ucenter-web/password.html
  • Forms & labels · Link with no accessible name zheng-ui/zheng-ucenter-web/password.html
  • Forms & labels · Link with no accessible name zheng-ui/zheng-ucenter-web/reg.html
  • Forms & labels · Link with no accessible name zheng-ui/zheng-ucenter-web/reg.html
  • Forms & labels · Link with no accessible name zheng-ui/zheng-ucenter-web/reg.html
  • Forms & labels · Link with no accessible name zheng-ui/zheng-ucenter-web/reg.html
  • Forms & labels · Link with no accessible name zheng-upms/zheng-upms-server/src/main/webapp/WEB-INF/jsp/manage/index.jsp
  • Forms & labels · Link with no accessible name zheng-upms/zheng-upms-server/src/main/webapp/WEB-INF/jsp/manage/index.jsp
  • Forms & labels · Link with no accessible name zheng-upms/zheng-upms-server/src/main/webapp/WEB-INF/jsp/manage/index.jsp
  • Forms & labels · <select> without a programmatic label zheng-upms/zheng-upms-server/src/main/webapp/WEB-INF/jsp/manage/permission/create.jsp
  • Forms & labels · <select> without a programmatic label zheng-upms/zheng-upms-server/src/main/webapp/WEB-INF/jsp/manage/permission/update.jsp
  • Forms & labels · <input> without a programmatic label zheng-upms/zheng-upms-server/src/main/webapp/WEB-INF/jsp/manage/system/create.jsp
  • Forms & labels · <input> without a programmatic label zheng-upms/zheng-upms-server/src/main/webapp/WEB-INF/jsp/manage/system/update.jsp
  • Forms & labels · <select> without a programmatic label zheng-upms/zheng-upms-server/src/main/webapp/WEB-INF/jsp/manage/user/organization.jsp
  • Forms & labels · <label> that labels no control zheng-upms/zheng-upms-server/src/main/webapp/WEB-INF/jsp/manage/user/permission.jsp
  • Forms & labels · <label> that labels no control zheng-upms/zheng-upms-server/src/main/webapp/WEB-INF/jsp/manage/user/permission.jsp
  • Forms & labels · <select> without a programmatic label zheng-upms/zheng-upms-server/src/main/webapp/WEB-INF/jsp/manage/user/role.jsp
  • Forms & labels · <input> without a programmatic label zheng-upms/zheng-upms-server/src/main/webapp/WEB-INF/jsp/sso/login.jsp
  • Forms & labels · <input> without a programmatic label zheng-upms/zheng-upms-server/src/main/webapp/WEB-INF/jsp/sso/login.jsp
  • Forms & labels · <input> without a programmatic label zheng-upms/zheng-upms-server/src/main/webapp/WEB-INF/jsp/sso/login.jsp
  • Forms & labels · Link with no accessible name zheng-upms/zheng-upms-server/src/main/webapp/WEB-INF/jsp/sso/login.jsp
  • Page structure · Page without a main landmark zheng-cms/zheng-cms-admin/src/main/webapp/WEB-INF/jsp/manage/tag/index.jsp
  • Page structure · Page without a main landmark zheng-cms/zheng-cms-admin/src/main/webapp/WEB-INF/jsp/manage/topic/index.jsp
  • Page structure · <html> without a lang zheng-cms/zheng-cms-job/src/main/webapp/WEB-INF/jsp/403.jsp
  • Page structure · Page without a main landmark zheng-cms/zheng-cms-job/src/main/webapp/WEB-INF/jsp/403.jsp
  • Page structure · Heading level jumps from h2 to h5 zheng-cms/zheng-cms-job/src/main/webapp/WEB-INF/jsp/403.jsp
  • Page structure · <html> without a lang zheng-cms/zheng-cms-job/src/main/webapp/WEB-INF/jsp/404.jsp
  • Page structure · Page without a main landmark zheng-cms/zheng-cms-job/src/main/webapp/WEB-INF/jsp/404.jsp
  • Page structure · <html> without a lang zheng-cms/zheng-cms-job/src/main/webapp/WEB-INF/jsp/500.jsp
  • Page structure · Page without a main landmark zheng-cms/zheng-cms-job/src/main/webapp/WEB-INF/jsp/500.jsp
  • Page structure · <html> without a lang zheng-cms/zheng-cms-job/src/main/webapp/WEB-INF/jsp/error.jsp
  • Page structure · Page without a main landmark zheng-cms/zheng-cms-job/src/main/webapp/WEB-INF/jsp/error.jsp
  • Page structure · Heading level jumps from h2 to h5 zheng-cms/zheng-cms-job/src/main/webapp/WEB-INF/jsp/error.jsp
  • Page structure · <html> without a lang zheng-cms/zheng-cms-job/src/main/webapp/WEB-INF/jsp/index.jsp
  • Page structure · Page without a main landmark zheng-cms/zheng-cms-job/src/main/webapp/WEB-INF/jsp/index.jsp
  • Page structure · <html> without a lang zheng-cms/zheng-cms-search/src/main/webapp/WEB-INF/jsp/403.jsp
  • Page structure · Page without a main landmark zheng-cms/zheng-cms-search/src/main/webapp/WEB-INF/jsp/403.jsp
  • Page structure · Heading level jumps from h2 to h5 zheng-cms/zheng-cms-search/src/main/webapp/WEB-INF/jsp/403.jsp
  • Page structure · <html> without a lang zheng-cms/zheng-cms-search/src/main/webapp/WEB-INF/jsp/404.jsp
  • Page structure · Page without a main landmark zheng-cms/zheng-cms-search/src/main/webapp/WEB-INF/jsp/404.jsp
  • Page structure · <html> without a lang zheng-cms/zheng-cms-search/src/main/webapp/WEB-INF/jsp/500.jsp
  • Page structure · Page without a main landmark zheng-cms/zheng-cms-search/src/main/webapp/WEB-INF/jsp/500.jsp
  • Page structure · <html> without a lang zheng-cms/zheng-cms-search/src/main/webapp/WEB-INF/jsp/error.jsp
  • Page structure · Page without a main landmark zheng-cms/zheng-cms-search/src/main/webapp/WEB-INF/jsp/error.jsp
  • Page structure · Heading level jumps from h2 to h5 zheng-cms/zheng-cms-search/src/main/webapp/WEB-INF/jsp/error.jsp
  • Page structure · <html> without a lang zheng-cms/zheng-cms-search/src/main/webapp/WEB-INF/jsp/index.jsp
  • Page structure · Page without a main landmark zheng-cms/zheng-cms-search/src/main/webapp/WEB-INF/jsp/index.jsp
  • Page structure · <html> without a lang zheng-cms/zheng-cms-web/src/main/webapp/WEB-INF/jsp/403.jsp
  • Page structure · Page without a main landmark zheng-cms/zheng-cms-web/src/main/webapp/WEB-INF/jsp/403.jsp
  • Page structure · Heading level jumps from h2 to h5 zheng-cms/zheng-cms-web/src/main/webapp/WEB-INF/jsp/403.jsp
  • Page structure · <html> without a lang zheng-cms/zheng-cms-web/src/main/webapp/WEB-INF/jsp/404.jsp
  • Page structure · Page without a main landmark zheng-cms/zheng-cms-web/src/main/webapp/WEB-INF/jsp/404.jsp
  • Page structure · <html> without a lang zheng-cms/zheng-cms-web/src/main/webapp/WEB-INF/jsp/500.jsp
  • Page structure · Page without a main landmark zheng-cms/zheng-cms-web/src/main/webapp/WEB-INF/jsp/500.jsp
  • Page structure · <html> without a lang zheng-cms/zheng-cms-web/src/main/webapp/WEB-INF/jsp/error.jsp
  • Page structure · Page without a main landmark zheng-cms/zheng-cms-web/src/main/webapp/WEB-INF/jsp/error.jsp
  • Page structure · Heading level jumps from h2 to h5 zheng-cms/zheng-cms-web/src/main/webapp/WEB-INF/jsp/error.jsp
  • Page structure · Page without a main landmark REDACTED
  • Page structure · Page without a main landmark zheng-demo/zheng-demo-web/src/main/webapp/WEB-INF/jsp/index.jsp
  • Page structure · <html> without a lang zheng-message/zheng-message-client/ack-index.html
  • Page structure · Page without a main landmark zheng-message/zheng-message-client/ack-index.html
  • Page structure · <html> without a lang REDACTED
  • Page structure · Page without a main landmark REDACTED
  • Page structure · <html> without a lang REDACTED
  • Page structure · Page without a main landmark REDACTED
  • Page structure · <html> without a lang REDACTED
  • Page structure · Page without a main landmark REDACTED
  • Page structure · <html> without a lang REDACTED
  • Page structure · Page without a main landmark REDACTED
  • Page structure · Heading level jumps from h1 to h4 REDACTED
  • Page structure · <html> without a lang REDACTED
Rebuild cost: about €29,000 · Estimate
Cost to rebuild€9,600 to €48,000, for 159 to 505 hours of work, about 0.2 person-years for one engineer
Difficulty of the problemStandard, 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 24. 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.
SizeMedium: 33,615 lines of product code

How the estimate is made: Watchdog prices the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.

Top priorities

The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.

1
Resolve the 3 No assertions finding(s) in Test Quality — start with UpmsServiceTest.java (3).
Raises the score by about 7 points · Low effort · Test Quality
2
Resolve the 53 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (16), REDACTED (16), REDACTED (16).
Raises the score by about 11 points · Medium effort · REDACTED Scanning
3
Resolve the 2 Test project verifies nothing finding(s) in Test Quality — start with UpmsServiceTest.java (2).
Raises the score by about 5 points · Low effort · Test Quality

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 €29,000 to build again, about 0.2 person-years of work. Its weakest lens is Production Readiness, at 12 (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 3 No assertions finding(s) in Test Quality. Of all the actions in this report, it raises the score most for the work it takes: about 7 points for low effort, because it clears the 3 Test Quality findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort

Architecture — module dependency graph

Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways — a layering smell or cycle. A clean layered graph has none.

arch zheng-admin zheng-admin zheng-api-common zheng-api-common zheng-common zheng-common zheng-api-common->zheng-common zheng-api-rpc-api zheng-api-rpc-api zheng-api-rpc-api->zheng-api-common zheng-cms-rpc-api zheng-cms-rpc-api zheng-api-rpc-api->zheng-cms-rpc-api zheng-upms-rpc-api zheng-upms-rpc-api zheng-api-rpc-api->zheng-upms-rpc-api zheng-api-server zheng-api-server zheng-api-server->zheng-admin zheng-api-server->zheng-api-rpc-api zheng-upms-client zheng-upms-client zheng-api-server->zheng-upms-client zheng-cms-admin zheng-cms-admin zheng-cms-admin->zheng-admin zheng-cms-admin->zheng-cms-rpc-api zheng-cms-admin->zheng-upms-client zheng-cms-common zheng-cms-common zheng-cms-common->zheng-common zheng-cms-dao zheng-cms-dao zheng-cms-dao->zheng-cms-common zheng-cms-rpc-api->zheng-cms-dao zheng-oss-admin zheng-oss-admin zheng-oss-admin->zheng-admin zheng-oss-sdk zheng-oss-sdk zheng-oss-admin->zheng-oss-sdk zheng-oss-admin->zheng-upms-client zheng-oss-sdk->zheng-common zheng-pay-admin zheng-pay-admin zheng-pay-admin->zheng-admin zheng-pay-rpc-api zheng-pay-rpc-api zheng-pay-admin->zheng-pay-rpc-api zheng-pay-common zheng-pay-common zheng-pay-common->zheng-common zheng-pay-dao zheng-pay-dao zheng-pay-dao->zheng-pay-common zheng-pay-rpc-api->zheng-pay-dao zheng-ucenter-common zheng-ucenter-common zheng-ucenter-common->zheng-common zheng-ucenter-dao zheng-ucenter-dao zheng-ucenter-dao->zheng-ucenter-common zheng-ucenter-rpc-api zheng-ucenter-rpc-api zheng-ucenter-rpc-api->zheng-ucenter-dao zheng-upms-client->zheng-common zheng-upms-client->zheng-upms-rpc-api __more__ +20 more projects

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.

100 modules, with 65 dependencies between them. Every module uses only modules listed above it, so there are no loops.

The table shows the 40 modules with the most connections; 60 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.
uses →1 api.rpc.api2 cms.dao.model3 common.base4 demo.rpc.api5 oss.web.service6 pay.dao.model7 ucenter.dao.mapper8 upms.client.shiro.session9 upms.dao.model10 api.common.constant11 api.rpc.service.impl12 api.server.controller13 cms.admin.controller14 cms.common.constant15 cms.dao.mapper16 cms.rpc.api17 cms.rpc.mapper18 demo.rpc.service.impl19 demo.web.controller20 message.server.controller21 oss.common.constant22 oss.web.controller23 pay.common.constant24 pay.dao.mapper25 pay.rpc.api26 pay.web.controller27 ucenter.common.constant28 ucenter.rpc.api29 upms.dao.mapper30 upms.rpc.api31 upms.rpc.mapper32 cms.admin.controller.manage33 cms.rpc.service.impl34 cms.web.controller35 cms.web.interceptor36 pay.rpc.service.impl37 ucenter.rpc.service.impl38 upms.rpc.service.impl39 upms.server.controller40 upms.server.controller.manage
1 api.rpc.api
2 cms.dao.model
3 common.base
4 demo.rpc.api
5 oss.web.service
6 pay.dao.model
7 ucenter.dao.mapper
8 upms.client.shiro.session
9 upms.dao.model
10 api.common.constant2
11 api.rpc.service.impl1
12 api.server.controller11
13 cms.admin.controller1
14 cms.common.constant2
15 cms.dao.mapper24
16 cms.rpc.api224
17 cms.rpc.mapper1
18 demo.rpc.service.impl1
19 demo.web.controller11
20 message.server.controller1
21 oss.common.constant2
22 oss.web.controller12
23 pay.common.constant2
24 pay.dao.mapper18
25 pay.rpc.api18
26 pay.web.controller1
27 ucenter.common.constant2
28 ucenter.rpc.api10
29 upms.dao.mapper20
30 upms.rpc.api2024
31 upms.rpc.mapper2
32 cms.admin.controller.manage889
33 cms.rpc.service.impl11212121
34 cms.web.controller3722
35 cms.web.interceptor1
36 pay.rpc.service.impl999
37 ucenter.rpc.service.impl556
38 upms.rpc.service.impl101218121
39 upms.server.controller214
40 upms.server.controller.manage71514
Uses a module listed above itPart of a loopThe module itself
1 api.rpc.api2 cms.dao.model3 common.base4 demo.rpc.api5 oss.web.service6 pay.dao.model7 ucenter.dao.mapper8 upms.client.shiro.session9 upms.dao.model10 api.common.constant11 api.rpc.service.impl12 api.server.controller13 cms.admin.controller14 cms.common.constant15 cms.dao.mapper16 cms.rpc.api17 cms.rpc.mapper18 demo.rpc.service.impl19 demo.web.controller20 message.server.controller21 oss.common.constant22 oss.web.controller23 pay.common.constant24 pay.dao.mapper25 pay.rpc.api26 pay.web.controller27 ucenter.common.constant28 ucenter.rpc.api29 upms.dao.mapper30 upms.rpc.api31 upms.rpc.mapper32 cms.admin.controller.manage33 cms.rpc.service.impl34 cms.web.controller35 cms.web.interceptor36 pay.rpc.service.impl37 ucenter.rpc.service.impl38 upms.rpc.service.impl39 upms.server.controller40 upms.server.controller.manageapi.rpc.api1cms.dao.model2common.base3demo.rpc.api4oss.web.service5pay.dao.model6ucenter.dao.mapper7upms.client.shiro.session8upms.dao.model9api.common.constant10api.rpc.service.impl11api.server.controller12cms.admin.controller13cms.common.constant14cms.dao.mapper15cms.rpc.api16cms.rpc.mapper17demo.rpc.service.impl18demo.web.controller19message.server.controller20oss.common.constant21oss.web.controller22pay.common.constant23pay.dao.mapper24pay.rpc.api25pay.web.controller26ucenter.common.constant27ucenter.rpc.api28upms.dao.mapper29upms.rpc.api30upms.rpc.mapper31cms.admin.controller.manage32cms.rpc.service.impl33cms.web.controller34cms.web.interceptor35pay.rpc.service.impl36ucenter.rpc.service.impl37upms.rpc.service.impl38upms.server.controller39upms.server.controller.manage4021111224224111112122181812102020242889112121213722199955610121812121471514+60 more modules (most-connected shown)

At a glance — Code Health · 24% · Critical · gated by D3, R1, R3, R7, X5 ·

The Good
D4 · .NET / C# Code Duplication 9.0 D17 · .NET / C# Explicit Debt 10.0 IC1 · Repo Incompleteness & stubs 8.5 R10 · React / TS Code Duplication 9.6 R2 · React / TS Cyclomatic Complexity 7.1 X1 · Repo Async correctness 10.0 X12 · Repo Unreachable branch 10.0 X13 · Repo Undrained process stream 10.0 X16 · Repo Unfloored truncation loop 10.0 X18 · Repo Disposal-pattern correctness 10.0 X19 · Repo Unrestored process-global state 10.0 X20 · Repo Mistyped argument guard 10.0 X21 · Repo Side-effecting pattern guard 10.0 X22 · Repo Contradicted release guard 10.0 X23 · Repo Unguarded diagnostic materialisation 10.0 X25 · Repo Inert configuration knob 10.0 X26 · Repo Unsynchronised callback handoff 10.0 X27 · Repo Collection changed while being enumerated 10.0 X28 · Repo Index access outside its own emptiness guard 10.0 X29 · Repo Per-element action decided by a fixed element 10.0 X30 · Repo Support guard that admits what it rejects 10.0
The Bad
D1 · .NET / C# Cyclomatic Complexity 6.4 D2 · .NET / C# Cognitive Complexity 5.9 X3 · Repo Exception handling 6.3 X4 · Repo Structured logging 5.1
The Ugly
D3 · .NET / C# God Classes 3.8 R1 · React / TS Type Safety 0.0 R3 · React / TS Large Files 1.4 R7 · React / TS Dead Code 0.0 X5 · Repo Nullable reference types 2.0

At a glance — Architecture · 98% · Exemplary ·

The Good
D5 · .NET / C# Coupling 10.0 D6 · .NET / C# Cohesion (LCOM4) 9.9 D26 · .NET / C# Project Cohesion 10.0 D27 · .NET / C# Navigability 9.1 D35 · .NET / C# Change Coupling 10.0 AX1 · Repo Captive dependencies 10.0 AX10 · Repo Code composition 9.4 AX2 · Repo Stateful singletons 10.0 AX3 · Repo Project dependency cycles 10.0 AX4 · Repo Dependency direction 10.0 AX6 · Repo Interface segregation 9.9 R9 · React / TS Circular Imports 10.0

At a glance — Maturity · 43% · Weak · gated by D34, M2 ·

The Good
D15 · .NET / C# Churn × Complexity Hotspots 10.0 D19 · .NET / C# Documentation Quality 7.0 D21 · .NET / C# Naming Consistency 10.0 M3 · Repo Folder & project structure 10.0 M4 · Repo Documentation accuracy 10.0
The Bad
M1 · Repo Documentation (README) 6.5
The Ugly
D20 · .NET / C# ADR Quality 0.0 D34 · .NET / C# Knowledge Freshness 0.0 M2 · Repo Architecture documentation 0.0

At a glance — Readiness · 12% · Critical · gated by D13, R4, P1, P3 ·

The Good
D9 · .NET / C# Test Distribution 10.0
The Bad
P2 · Repo Observability 6.1 P6 · Repo Release Hygiene 5.0
The Ugly
D10 · .NET / C# Test Quality 4.4 D13 · .NET / C# REDACTED Scanning 0.0 P1 · Repo CI/CD gates 0.0 P3 · Repo Security & performance tooling 0.0 R4 · React / TS Test Coverage 0.0

At a glance — Security · 54% · Adequate · gated by D28, D30 ·

The Good
D43 · .NET / C# Malicious Dependencies 10.0 D44 · .NET / C# Platform End-of-Life 10.0 X14 · Repo Bypassable address classification 10.0 X15 · Repo Unvalidated length from an untrusted reader 10.0 X17 · Repo Uncapped recursion over a caller-supplied document 10.0 X24 · Repo Document value interpolated into markup unescaped 10.0
The Bad
S1 · Repo Web-Security Posture 6.0
The Ugly
D28 · .NET / C# Secrets (history) 0.0 D29 · .NET / C# Static Analysis (SAST) 4.4 D30 · .NET / C# Dependency Vulnerabilities 0.0

At a glance — Accessibility · 31% · Weak · gated by AC1, AC3, AC4, AC6 ·

The Good
AC5 · Repo ARIA correctness 10.0
The Bad
AC2 · Repo Forms & labels 5.3
The Ugly
AC1 · Repo Text alternatives 2.7 AC3 · Repo Page structure 3.7 AC4 · Repo Keyboard semantics 1.0 AC6 · Repo Visual & motion safety 3.6 AC7 · Repo A11y enforcement 4.0

At a glance — Performance · 61% · Adequate ·

The Bad
PF2 · Repo Allocation hygiene 6.1

Security & Compliance — OWASP Top-10 mapping

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 categoryFindingsSeverity
A07:2025 — Authentication Failures96High / Critical
A03:2025 — Software Supply Chain Failures26High / Critical
A05:2025 — Injection18High / Critical

Roadmap

Immediately resolve the 53 leaked secrets in test, prod, and dev property files to eliminate critical security exposure. Strengthen test reliability by fixing assertions and ensuring the test project actually verifies behavior in UpmsServiceTest. Restore CI/CD integrity by migrating the pipeline to an active service and removing dead configuration. Finally, integrate automated security scanning into the build process to prevent regressions from reaching production.

Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.

Do thisHelpsEffortDimension
Resolve the 3 No assertions finding(s) in Test Quality — start with UpmsServiceTest.java (3).+6.7 ptsLowTest Quality
Resolve the 53 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (16), REDACTED (16), REDACTED (16).+10.8 ptsMediumREDACTED Scanning
Resolve the 2 Test project verifies nothing finding(s) in Test Quality — start with UpmsServiceTest.java (2).+5.1 ptsLowTest Quality
Port the existing pipeline to a CI service that is still operating — the build and test steps are already specified — and remove the dead configuration and its badge so the repository stops advertising a gate that no longer exists.+4.2 ptsMediumCI/CD gates
Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.+4.2 ptsMediumSecurity & performance tooling
Add tests that import the unreached modules (directly or through their public entry).+4.2 ptsMediumTest Coverage
Resolve the 1 No ADRs found finding(s) in ADR Quality.+1.5 ptsLowADR Quality
Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.+2.1 ptsMediumType Safety

File quality

Per-file score 0–10 — a quality signature. Of 147 files carrying findings, judged against the Production bar: 6% slop · 57% mixed · 37% near-clean.

FileScoreBandWorst signal
REDACTED0.5SlopDependency Vulnerabilities: Critical CVE: REDACTED
REDACTED2.3SlopREDACTED Scanning: Leaked secret: REDACTED
REDACTED2.3SlopREDACTED Scanning: Leaked secret: REDACTED
REDACTED2.3SlopREDACTED Scanning: Leaked secret: REDACTED
REDACTED2.3SlopREDACTED Scanning: Leaked secret: REDACTED
REDACTED2.3SlopREDACTED Scanning: Leaked secret: REDACTED
REDACTED2.3SlopREDACTED Scanning: Leaked secret: REDACTED
REDACTED2.3SlopREDACTED Scanning: Leaked secret: REDACTED
REDACTED2.3SlopREDACTED Scanning: Leaked secret: REDACTED
REDACTED4.4MixedREDACTED Scanning: Leaked secret: REDACTED
REDACTED4.4MixedREDACTED Scanning: Leaked secret: REDACTED
REDACTED4.4MixedREDACTED Scanning: Leaked secret: REDACTED
REDACTED4.4MixedREDACTED Scanning: Leaked secret: REDACTED
REDACTED4.4MixedREDACTED Scanning: Leaked secret: REDACTED
REDACTED4.4MixedREDACTED Scanning: Leaked secret: REDACTED
REDACTED4.4MixedREDACTED Scanning: Leaked secret: REDACTED
REDACTED4.4MixedREDACTED Scanning: Leaked secret: REDACTED
REDACTED4.4MixedREDACTED Scanning: Leaked secret: REDACTED
REDACTED5.1MixedREDACTED Scanning: Leaked secret: REDACTED
REDACTED5.1MixedREDACTED Scanning: Leaked secret: REDACTED

How the grades work

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 — 172

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 — 408

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 — 170

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

Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 74 of 77 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 3 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.8 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.

Every figure here is one of three kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact; ◐ Advisory — an LLM prose judgement. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.

What we checked — 77 dimensions across the health lenses
D1D2D3D4D5D6D9D10D13D15D17D19D20D21D26D27D28D29D30D34D35D43D44AC1AC2AC3AC4AC5AC6AC7AX1AX10AX2AX3AX4AX6IC1M1M2M3M4P1P2P3P6PF2R1R10R2R3R4R7R9S1X1X12X13X14X15X16X17X18X19X20X21X22X23X24X25X26X27X28X29X3X30X4X5

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
  1. 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, 735 of 750 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.)
  2. Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
  3. 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.

MethodBacksVersionEvaluator
Roslyn static analysisComplexity, cohesion, coupling, dead code, API surface, layering5.3.0✓ deterministic
Native secret scannerHardcoded secrets / credentials1.0.0✓ deterministic
Watchdog duplication detector (in-process)Code duplication1.0.0✓ deterministic
Coverage (coverlet / dotnet-coverage)Line & branch coverage10.0.400✓ deterministic
NuGet / dotnetOutdated, vulnerable & deprecated dependencies10.0.400✓ deterministic
git / LibGit2SharpChurn hotspots, knowledge concentration, history2.43.0 · 0.31.0✓ deterministic
gitleaks · semgrep · trivySecrets in history, SAST, CVEs, IaC & container, PII / GDPR1.86.0 · 0.69.3✓ deterministic
LLM (sampled · advisory)Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurementLocal LLM◐ LLM · sampled · advisory

Every finding is locatable in findings.md. Run 01a16ccd-216d-7c3e-aea4-cd8e40741a33.

The exact command behind every deep-scan dimension — tool, version, invocation and retained raw output — is in Appendix B — Reproduction & audit trail.

Run transparency — what happened this run

What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.

  • D8 Code Coverage — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.java) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo. To have real coverage read, produce a coverage report in a standard format (JaCoCo XML — `mvn jacoco:report`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (JaCoCo XML — `mvn jacoco:report`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
  • D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.java) and this repository declares a JVM test suite (repository root, Maven), but it was not re-run: the analyzer environment could not run it. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
  • D12 Dependency Hygiene — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — 56 Maven/Gradle manifest(s) were read, stating a version for 152 dependency(ies) and leaving 13 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
  • D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (13 contributor(s) across 1241 commit(s) sampled, automation and bot accounts excluded). One of them holds 98% of the history; the other 12 hold 0.2% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
  • D22 Internal API Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: it declares a published package (REDACTED), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict. For npm the surface is what a published package.json's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
  • AC2 Forms & labels — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 50 further occurrence(s) are not listed individually; the score already reflects all 90.
  • AC3 Page structure — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 169 further occurrence(s) are not listed individually; the score already reflects all 209.
  • AC4 Keyboard semantics — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 69 further occurrence(s) are not listed individually; the score already reflects all 109.
  • AC6 Visual & motion safety — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 13 further occurrence(s) are not listed individually; the score already reflects all 53.
  • AXB1 Runtime evidence locked — no reproducible boot — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Subject: 150 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates. The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. Watchdog then boots it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
  • C1 Data Protection — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
  • C2 Access Controls — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
  • C3 Audit Trail — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
  • C4 Data Retention — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
  • C5 Data-Subject Rights — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
  • GD1 Unfinished & placeholder code — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and this repository's Java is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • P8 Schema migrations — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. The schema may be created by a runner, a deploy script or a config file outside what this check reads, so an absence here is our blind spot rather than a missing migration strategy. The card abstains instead of scoring. You can widen what we reach: if the schema is created and evolved by a tool this check does not name, naming it lets us teach the detector to read it.

Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.

Limitations & what we did not check

Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.

Per-dimension blind spots

For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.

  • D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
  • D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
  • D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
  • D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
  • D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
  • D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
  • D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
  • D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
  • D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
  • 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 is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement. Its critique rows are drawn from a closed category vocabulary and each row means the same thing in every run, so two scans can be compared row by row; the SET that fires is still a sample, and does not repeat exactly. Measured on one frozen input, six scans at one engine SHA: 2-5 critique rows per scan, 8 distinct rows across the six, 3 of those 8 seen in only one scan. So a D19 row is evidence about the documentation, but a COUNT of D19 rows is not a quantity — never read a change in it as an improvement or a regression.
  • D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
  • D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
  • D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
  • D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
  • D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
  • D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
  • D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
  • 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 Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
  • AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
  • AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
  • AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
  • AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
  • AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
  • AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
  • AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
  • 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: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
  • P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.

The LLM boundary

LLM-set scores this run (3): D19, D21, M4 (model: Local LLM). For these, a model reads a bounded sample and sets the numeric score; each names its own sample and method on its card. They are sampled and advisory by design: they vary at the margins between runs and are never a deterministic measurement. Every other score in this report is tool-computed at confidence 1.0.

Dimensions

D1 · Cyclomatic Complexity6.4 / 10Adequate✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 6.4 / 10 · rule-coverage 100% · ceiling Prevented

38 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was jquery.mCustomScrollbar._scrollTo at 66. A further 2 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 jquery.mCustomScrollbar._autoUpdate at 18 — they are counted neither in the figure above nor in this dimension's score.

(anonymous)::(anonymous)::apply (cyclomatic 40) · ×9zheng-admin/src/plugins/select2/js/select2.js:4582
jquery.fullPage.$.fn.fullpage::onkeydown (cyclomatic 18) · ×4zheng-admin/src/plugins/fullPage/jquery.fullPage.js:1539
jquery.mCustomScrollbar._scrollTo (cyclomatic 66)zheng-admin/src/plugins/malihu-custom-scrollbar-plugin/jquery.mCustomScrollbar.js:2036
jquery.mCustomScrollbar._keyboard::_onKeyboard (cyclomatic 43)zheng-admin/src/plugins/malihu-custom-scrollbar-plugin/jquery.mCustomScrollbar.js:1727
jquery.mCustomScrollbar._tweenTo (cyclomatic 32)zheng-admin/src/plugins/malihu-custom-scrollbar-plugin/jquery.mCustomScrollbar.js:2206

+ 22 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Bring the 8 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with jquery.mCustomScrollbar._scrollTo (cyclomatic 66), jquery.mCustomScrollbar._keyboard::_onKeyboard (cyclomatic 43), (anonymous)::(anonymous)::apply (cyclomatic 40). — 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 8 together lifts Cyclomatic Complexity from 6.4 to about 7.3/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
  2. Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.

D2 · Cognitive Complexity5.9 / 10Adequate✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 5.9 / 10 · rule-coverage 100% · ceiling Prevented

42 method(s) exceeded the cognitive complexity threshold of 15; the worst was UpmsPermissionServiceImpl.getTreeByRoleId at 107.

(anonymous)::(anonymous)::apply (cognitive 74) · ×9zheng-admin/src/plugins/select2/js/select2.js:4582
jquery.fullPage.$.fn.fullpage::touchMoveHandler (cognitive 44) · ×6zheng-admin/src/plugins/fullPage/jquery.fullPage.js:961
jquery.mCustomScrollbar._contentDraggable::_onTouchmove (cognitive 27) · ×2zheng-admin/src/plugins/malihu-custom-scrollbar-plugin/jquery.mCustomScrollbar.js:1301
UpmsPermissionServiceImpl.getTreeByRoleId (cognitive 107)zheng-upms/zheng-upms-rpc-service/src/main/java/com/zheng/upms/rpc/service/impl/UpmsPermissionServiceImpl.java:45
UpmsPermissionServiceImpl.getTreeByUserId (cognitive 107)zheng-upms/zheng-upms-rpc-service/src/main/java/com/zheng/upms/rpc/service/impl/UpmsPermissionServiceImpl.java:148

+ 22 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Bring the 13 bodies over 30 down to 30 or less in Cognitive Complexity — start with UpmsPermissionServiceImpl.getTreeByRoleId (cognitive 107), UpmsPermissionServiceImpl.getTreeByUserId (cognitive 107), Paginator.getHtml (cognitive 85). — 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 13 together lifts Cognitive Complexity from 5.9 to about 7.3/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
  2. Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.

D3 · God Classes3.8 / 10Weak✓ 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.

Maturity: Documented → Verified → Prevented · effective 3.8 / 10 · rule-coverage 100% · ceiling Prevented

64 god class(es) detected.

TooManyMethods: GeneratedCriteria · ×38zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleExample.java:69
FileTooLong: js/select2.full.js · ×12zheng-admin/src/plugins/select2/js/select2.full.js
ClassTooLong: CmsArticleExample · ×10zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleExample.java:7
FunctionTooLong: jquery.fullPage.$.fn.fullpage · ×3zheng-admin/src/plugins/fullPage/jquery.fullPage.js:91
MethodTooLong: MybatisGeneratorUtil.generatorzheng-common/src/main/java/com/zheng/common/util/MybatisGeneratorUtil.java:42

What to do

  1. Resolve the 38 TooManyMethods finding(s) in God Classes — start with CmsArticleExample.java, UpmsLogExample.java, UpmsSystemExample.java. — One of this dimension's main actionable groups (38 warning-level).
  2. Resolve the 12 FileTooLong finding(s) in God Classes — start with select2.full.js, select2.js, jquery.mCustomScrollbar.js. — One of this dimension's main actionable groups (12 warning-level).
  3. Resolve the 10 ClassTooLong finding(s) in God Classes — start with CmsArticleExample.java, UpmsLogExample.java, UpmsSystemExample.java. — One of this dimension's main actionable groups (10 warning-level).
  4. Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.

D4 · Code Duplication9.0 / 10Strong✓ Tool-verified

What it measures: Copy-pasted code that should be shared instead.

Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.

Maturity: Documented → Verified → Prevented · effective 9.0 / 10 · rule-coverage 100% · ceiling Verified

74 duplicated block group(s) detected. A further 6 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted.

Duplicated block (8 lines × 2) · ×5zheng-cms/zheng-cms-web/src/main/java/com/zheng/cms/web/interceptor/CmsWebInterceptor.java:31
Duplicated block (5 lines × 2) · ×5zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsSystem.java:100
Duplicated block (7 lines × 2) · ×4zheng-cms/zheng-cms-admin/src/main/java/com/zheng/cms/admin/controller/manage/CmsSettingController.java:83
Duplicated block (6 lines × 6) · ×3zheng-cms/zheng-cms-admin/src/main/java/com/zheng/cms/admin/controller/manage/CmsArticleController.java:94
Duplicated block (14 lines × 2) · ×2zheng-api/zheng-api-server/src/main/java/com/zheng/api/server/jms/DefaultMessageQueueListener.java:26

+ 59 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Resolve the 5 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with CmsWebInterceptor.java, MybatisGeneratorUtil.java, NamespaceChatLauncher.java. — One of this dimension's main actionable groups (5 warning-level).
  2. Resolve the 5 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with CmsSystem.java, CaptchaUtil.java, CmsArticle.java. — One of this dimension's main actionable groups (5 warning-level).
  3. Resolve the 4 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with CmsSettingController.java, UpmsOrganizationController.java, UpmsRoleController.java. — One of this dimension's main actionable groups (4 warning-level).
  4. Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.

D5 · Coupling10.0 / 10Exemplary✓ 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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

40 production modules (Maven), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 1 module(s) off the main sequence, with abstractness counted on 38 of the 40 (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: zheng-common

✓ On the Gold path — maintain.

Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.

D6 · Cohesion (LCOM4)9.9 / 10Stronggated by 1 serious finding✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 9.9 / 10 · rule-coverage 100% · ceiling Verified

1 of 118 classes have LCOM4 above 3.

Low cohesion: UpmsUserController (LCOM4 4)zheng-upms/zheng-upms-server/src/main/java/com/zheng/upms/server/controller/manage/UpmsUserController.java:39

What to do

  1. Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with UpmsUserController.java. — One of this dimension's main actionable groups (1 warning-level).
  2. Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.

D9 · Test Distribution10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether the test suite has a healthy mix of unit / integration / end-to-end tests.

Method: Test projects classified (Unit/Integration/BDD/E2E) from compiled metadata; test methods counted exhaustively across projects with placement-agnostic disk fallback. Deterministic.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

3 test methods: 3 unit, 0 integration, 0 BDD, 0 e2e.

✓ On the Gold path — maintain.

Detailed fixes: d9_recommendation.md.

D10 · Test Quality4.4 / 10Weak✓ Tool-verified

What it measures: Whether the tests truly assert behaviour rather than just running the code.

Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.

Maturity: Documented → Verified → Prevented · effective 4.4 / 10 · rule-coverage 100% · ceiling Prevented

0 skipped, 3 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 3 tests.

No assertions: index · ×3zheng-upms/zheng-upms-rpc-service/src/test/java/com/zheng/upms/rpc/service/UpmsServiceTest.java:43
Test project verifies nothing: zheng-upms-rpc-service · ×2zheng-upms/zheng-upms-rpc-service/src/test/java/com/zheng/upms/rpc/service/UpmsServiceTest.java:43

What to do

  1. Resolve the 3 No assertions finding(s) in Test Quality — start with UpmsServiceTest.java (3). — One of this dimension's main actionable groups (3 warning-level).
  2. Resolve the 2 Test project verifies nothing finding(s) in Test Quality — start with UpmsServiceTest.java (2). — One of this dimension's main actionable groups (2 warning-level).
  3. Enforce Test Quality in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

Detailed fixes: d10_recommendation.md · top locations in Appendix A, every location in findings.md.

D13 · REDACTED Scanning0.0 / 10Critical✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Prevented

29 secret(s) detected.

REDACTED

What to do

  1. Resolve the 53 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (16), REDACTED (16), REDACTED (16). — One of this dimension's main actionable groups (53 issue-level).
  2. Enforce REDACTED Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

Detailed fixes: d13_recommendation.md · top locations in Appendix A, every location in findings.md.

D15 · Churn × Complexity Hotspots10.0 / 10Exemplary✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

No churn × complexity hotspots in the window.

✓ On the Gold path — maintain.

Detailed fixes: d15_recommendation.md.

D17 · Explicit Debt10.0 / 10Stronggated by 1 serious finding✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

1 deducted task-comment markers across 33615 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.

TodoCommentzheng-upms/zheng-upms-client/src/main/java/com/zheng/upms/client/shiro/session/UpmsSessionDao.java:67

What to do

  1. Resolve the 1 TodoComment finding(s) in Explicit Debt — start with UpmsSessionDao.java. — One of this dimension's main actionable groups (1 warning-level).
  2. Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.

D19 · Documentation QualityStrong◐ Sampled · advisory

What it measures: Whether the project's documentation is clear, complete, and useful.

Method: Judged by language model at low temperature (0.0-0.1) on a deterministic doc sample (READMEs plus first 25 architecture docs), with two-pass stability filtering. Advisory, sampled.

Maturity: Documented → Verified → Prevented · effective Strong / 10 · rule-coverage 100% · ceiling Documented

The root README is excellent at conveying what the project is (a comprehensive J2EE enterprise solution from frontend templates to SSO monitoring), its scope (the repository's root), and its audience (everyone). It also links to a detailed architecture/dependency outline that every section in the visible document list exists, so no sections are flagged as missing. The READMEs for each module (zheng-admin, zheng-api, zheng-cms, etc.) all describe their own directories rather than the repository and do not appear in the root's overview, so they fall outside the scope of this review. There is a single internal-focused finding against the zheng-upms README: it names ticket ids/sso-login/sso-logout without explaining what SSO means or how to configure it.

What to do

  1. Improve Documentation Quality — currently 7.0/10. — The root README is excellent at conveying what the project is (a comprehensive J2EE enterprise solution from frontend templates to SSO monitoring), its scope (the repository's root), and its audience (everyone). It also links to a detailed architecture/dependency outline that every section in the visible document list exists, so no sections are flagged as missing. The READMEs for each module (zheng-admin, zheng-api, zheng-cms, etc.) all describe their own directories rather than the repository and do not appear in the root's overview, so they fall outside the scope of this review. There is a single internal-focused finding against the zheng-upms README: it names ticket ids/sso-login/sso-logout without explaining what SSO means or how to configure it.

Detailed fixes: d19_recommendation.md.

D20 · ADR Quality0.0 / 10Critical✓ Tool-verified

What it measures: Whether architecture decisions are recorded well (context, decision, consequences).

Method: Per-ADR judgment by language model at low temperature with two-pass stability; confidence is share of ADRs evaluated; enforcement-field presence detected deterministically. Advisory.

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Documented

No architecture decision records were found.

No ADRs found

What to do

  1. Resolve the 1 No ADRs found finding(s) in ADR Quality. — 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.

D21 · Naming ConsistencyExemplary◐ Sampled · advisory

What it measures: Whether names — types, methods, variables — are clear and consistent.

Method: Judged by language model at low temperature (0.0-0.1) on a deterministic random symbol sample (fixed size, not exhaustive), with disclosed confidence band. Advisory, sampled.

Maturity: Documented → Verified → Prevented · effective Exemplary / 10 · rule-coverage 100% · ceiling Verified

0 naming inconsistencies across 0 sampled symbols.

✓ On the Gold path — maintain.

Detailed fixes: d21_recommendation.md.

D26 · Project Cohesion10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether each project is a focused, coherent unit rather than an oversized grab-bag.

Method: Project size overshoot penalties (LoC / public-type count / namespace count, 2-of-3 flag) weighted by log magnitude. Exhaustive across projects, deterministic, LLM-independent.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

0 of 41 build units (Maven) flagged as possibly oversized/incoherent.

✓ On the Gold path — maintain.

Detailed fixes: d26_recommendation.md.

D27 · Navigability9.1 / 10Exemplary✓ Tool-verified

What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.

Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.

Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.

Maturity: Documented → Verified → Prevented · effective 9.1 / 10 · rule-coverage 100% · ceiling Documented

55 % of calls cross a namespace and 17 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.

✓ On the Gold path — maintain.

Detailed fixes: d27_recommendation.md.

D28 · Secrets (history)0.0 / 10Critical✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Documented

42 finding(s): 0 critical, 42 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.

REDACTED
REDACTED

What to do

  1. Resolve the 42 REDACTED finding(s) in Secrets (history) — start with REDACTED (17), REDACTED (10), REDACTED (8). — One of this dimension's main actionable groups (42 issue-level).
  2. 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.

D29 · Static Analysis (SAST)4.4 / 10Weak✓ Tool-verified

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).

Maturity: Documented → Verified → Prevented · effective 4.4 / 10 · rule-coverage 100% · ceiling Documented

18 finding(s): 0 critical, 1 high, 11 medium, 6 low.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

+ 4 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
  2. Resolve the 5 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (5 warning-level).
  3. Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3). — One of this dimension's main actionable groups (3 warning-level).

Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.

D30 · Dependency Vulnerabilities0.0 / 10Critical✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Documented

26 finding(s): 11 critical, 9 high, 6 medium, 0 low.

REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 11 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (11). — One of this dimension's main actionable groups (11 issue-level).
  2. Resolve the 9 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (9). — One of this dimension's main actionable groups (9 issue-level).
  3. Resolve the 6 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (6). — One of this dimension's main actionable groups (6 warning-level).

Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.

D34 · Knowledge Freshness0.0 / 10Critical✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Documented

112 of 112 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleExample.java. Counted over 112 of the 374 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned file · ×109zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsUserExample.java:1
Most significant orphaned file · ×3zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleExample.java:1
Dormant codebase

What to do

  1. Resolve the 109 Orphaned file finding(s) in Knowledge Freshness — start with UpmsUserExample.java, UpmsPermissionExample.java, CmsCategoryExample.java. — One of this dimension's main actionable groups (109 recommendation-level).
  2. Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with CmsArticleExample.java, UpmsLogExample.java, UpmsSystemExample.java. — One of this dimension's main actionable groups (3 recommendation-level).
  3. 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.

D35 · Change Coupling10.0 / 10Exemplary✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

No strong hidden change-coupling between production files.

✓ On the Gold path — maintain.

Detailed fixes: d35_recommendation.md.

D43 · Malicious Dependencies10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Scored apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.

Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. SCORED, not informational.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

No dependency in any ecosystem this repository declares is published as malicious.

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

D44 · Platform End-of-Life10.0 / 10Exemplary✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 15 platform declaration(s) and 195 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.

✓ On the Gold path — maintain.

Detailed fixes: d44_recommendation.md.

Frontend & cross-cutting dimensions

R = React/JS · M = Maturity · P = Readiness.

AC1 · Text alternatives2.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. (×2) — REDACTED:139, zheng-upms/zheng-upms-server/src/main/webapp/WEB-INF/jsp/manage/index.jsp:114

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.
AC2 · Forms & labels5.3 / 10Adequate✓ Tool-verified

Other · Accessibility — Whether form controls have a programmatic label (an associated label, aria-label or aria-labelledby), buttons have text, links have an accessible name, a click handler on a plain element names the control it declares, fieldsets have a non-empty legend, known UI-library field components carry a label prop, and a placeholder isn't used as the only label. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: inputs/selects/textareas checked for an associated label[for]/wrapping label/aria-label/aria-labelledby (per document), buttons for accessible text, fieldsets for a legend; placeholder-only labelling flagged. Deterministic, hard fact per control.

Coverage: Population: form controls, buttons, links, fieldsets and known UI-library field components in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and spread/dynamic-attribute elements are skipped, so a control whose label arrives through a spread or a runtime expression is deliberately not judged. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

  • 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. (×4) — REDACTED:62, REDACTED:77, REDACTED:107, …
  • This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label. (×2) — zheng-admin/src/login.html:20, zheng-admin/src/login.html:26
  • This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×23) — zheng-admin/src/login.html:32, zheng-admin/src/plugins/awesome-bootstrap-checkbox/index.html:70, zheng-admin/src/plugins/select2/js/select2.full.js:1853, …
  • 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. (×11) — zheng-admin/src/plugins/awesome-bootstrap-checkbox/index.html:62, zheng-admin/src/plugins/awesome-bootstrap-checkbox/index.html:66, zheng-admin/src/plugins/awesome-bootstrap-checkbox/index.html:71, …

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.
AC3 · Page structure3.7 / 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.

  • No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. (×22) — zheng-admin/src/crud.html:2, zheng-admin/src/demo.html:2, REDACTED:2, …
  • The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). (×12) — zheng-admin/src/plugins/awesome-bootstrap-checkbox/index.html:2, zheng-api/zheng-api-server/src/main/webapp/WEB-INF/jsp/403.jsp:0, zheng-api/zheng-api-server/src/main/webapp/WEB-INF/jsp/404.jsp:0, …
  • Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one. (×4) — zheng-api/zheng-api-server/src/main/webapp/WEB-INF/jsp/403.jsp:18, zheng-api/zheng-api-server/src/main/webapp/WEB-INF/jsp/error.jsp:18, zheng-cms/zheng-cms-admin/src/main/webapp/WEB-INF/jsp/403.jsp:18, …
  • A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope). (×2) — zheng-cms/zheng-cms-admin/src/main/webapp/WEB-INF/jsp/manage/comment/create.jsp:20, zheng-cms/zheng-cms-admin/src/main/webapp/WEB-INF/jsp/manage/comment/update.jsp:20

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.
AC4 · Keyboard semantics1.0 / 10Critical✓ Tool-verified

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 href="#"> (or javascript:) with a click handler is a button dressed as a link — it announces the wrong role and stops working without JS. Use a <button> for an action. (×38) — zheng-admin/src/crud.html:20, zheng-admin/src/crud.html:21, zheng-admin/src/crud.html:22, …
  • The repo's own CSS styles .waves-effect with `cursor: pointer`, so this <span> 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. — REDACTED:229
  • The repo's own CSS styles .mCSB_dragger with `cursor: pointer`, so this <div> 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. — zheng-admin/src/plugins/malihu-custom-scrollbar-plugin/jquery.mCustomScrollbar.js:865

What to do

  • Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
AC5 · ARIA correctness10.0 / 10Exemplary○ Nothing flagged

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.

AC6 · Visual & motion safety3.6 / 10Weak✓ Tool-verified

Other · Accessibility — Whether focus outlines aren't removed without a replacement, motion respects prefers-reduced-motion, and literal CSS colour pairs meet contrast — PARTIAL: inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS literals are read (hex/rgb/hsl/named), never computed/runtime/external-CDN colour. Static markup readiness, not a WCAG conformance claim.

Method: Static markup/CSS scan: inline outline:none/0, literal inline colour/background contrast against the 4.5:1 AA floor, and <style>-block animation without a prefers-reduced-motion guard. Deterministic but PARTIAL — only inline styles and in-repo CSS literals are visible.

Coverage: Population: styled elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx), plus in-repo <style> blocks, in-repo .css files and CSS-in-JS literals. Colour contrast is computed from LITERAL colour pairs only (hex/rgb/hsl/named, including var() tokens and Tailwind neutral utilities) — computed, runtime-themed and external-CDN colour is never resolved, so this is a partial read of contrast by construction. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

  • `.nav-tabs .open .dropdown-toggle, .nav-pills .open .dropdown-toggle, .nav > li.dropdown.open.active > a:hover` sets color: #ffffff on background-color: #999999 — 2.8:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — zheng-message/zheng-message-client/bootstrap.css:3435
  • `.ztree li a.tmpTargetNode_inner` sets color: white on background-color: #aaa — 2.3:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — zheng-admin/src/plugins/zTree_v3/css/metroStyle/metroStyle.css:21
  • `.ztree li a.tmpTargetNode_inner` sets color: #ffff00 on background-color: #aaa — 2.2:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — zheng-admin/src/plugins/zTree_v3/css/awesomeStyle/awesome.css:80
  • `.select2-container--default .select2-results__option--highlighted[aria-selected]` sets color: white on background-color: #5897fb — 2.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — zheng-admin/src/plugins/select2/css/select2.css:290
  • `.btn-warning .badge` sets color: #f0ad4e on background-color: #fff — 1.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — zheng-admin/src/plugins/bootstrap-3.3.0/css/bootstrap.css:3057
  • `.open .dropdown-toggle` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — zheng-message/zheng-message-client/bootstrap.css:2366
  • `.btn.active` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — zheng-message/zheng-message-client/bootstrap.css:2659
  • `.btn-group.open .dropdown-toggle` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. (×2) — zheng-message/zheng-message-client/bootstrap.css:3041, zheng-admin/src/plugins/bootstrap-3.3.0/css/bootstrap.css:3424
  • `.navbar-search .search-query.focused` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — zheng-message/zheng-message-client/bootstrap.css:3738
  • `object` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — zheng-admin/src/plugins/zTree_v3/css/demo.css:2
  • `.ztree li span.button` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. (×4) — zheng-admin/src/plugins/zTree_v3/css/zTreeStyle/zTreeStyle.css:30, zheng-admin/src/plugins/zTree_v3/css/metroStyle/metroStyle.css:29, zheng-admin/src/plugins/zTree_v3/css/awesomeStyle/awesome.css:104, …
  • `.waves-button` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — zheng-admin/src/plugins/waves-0.7.5/waves.css:84
  • `.select2-container--bootstrap .select2-selection` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — zheng-admin/src/plugins/select2/theme/select2-bootstrap.css:66
  • `.select2-container--bootstrap .select2-search__field` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — zheng-admin/src/plugins/select2/theme/select2-bootstrap.css:84
  • `.select2-container--default.select2-container--focus .select2-selection--multiple` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — zheng-admin/src/plugins/select2/css/select2.css:230
  • `.select2-container--default .select2-search--inline .select2-search__field` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — zheng-admin/src/plugins/select2/css/select2.css:253
  • `.select2-container--classic .select2-search--dropdown .select2-search__field` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — zheng-admin/src/plugins/select2/css/select2.css:448
  • `.select2-container--classic .select2-search--inline .select2-search__field` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — zheng-admin/src/plugins/select2/css/select2.css:451
  • `.mCustomScrollBox` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — zheng-admin/src/plugins/malihu-custom-scrollbar-plugin/jquery.mCustomScrollbar.css:35
  • `.dropdown-toggle:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — zheng-admin/src/plugins/bootstrap-3.3.0/css/bootstrap.css:3223
  • `.dropdown-menu > .active > a` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — zheng-admin/src/plugins/bootstrap-3.3.0/css/bootstrap.css:3278
  • `.open > a` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — zheng-admin/src/plugins/bootstrap-3.3.0/css/bootstrap.css:3297
  • `.btn-group > .btn:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — zheng-admin/src/plugins/bootstrap-3.3.0/css/bootstrap.css:3372
  • `.navbar-toggle:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — zheng-admin/src/plugins/bootstrap-3.3.0/css/bootstrap.css:4011
  • `.modal` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — zheng-admin/src/plugins/bootstrap-3.3.0/css/bootstrap.css:5513
  • `.modal-content` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — zheng-admin/src/plugins/bootstrap-3.3.0/css/bootstrap.css:5547
  • `.carousel-control:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — zheng-admin/src/plugins/bootstrap-3.3.0/css/bootstrap.css:5958
  • `a` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — zheng-admin/src/css/common.css:3
  • `.collapse` moves (`transition: height 0.35s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — zheng-message/zheng-message-client/bootstrap.css:2542
  • `.btn:hover` moves (`transition: background-position 0.1s linear`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — zheng-message/zheng-message-client/bootstrap.css:2645
  • `.modal.fade` moves (`transition: opacity 0.3s linear, top 0.3s ease-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — zheng-message/zheng-message-client/bootstrap.css:4198
  • `.progress .bar` moves (`transition: width 0.6s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — zheng-message/zheng-message-client/bootstrap.css:4685
  • `.progress.active .bar` moves (`animation: progress-bar-stripes 2s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — zheng-message/zheng-message-client/bootstrap.css:4707
  • `.carousel .item` moves (`transition: 0.6s ease-in-out left`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — zheng-message/zheng-message-client/bootstrap.css:4847
  • `.zmdi-hc-spin` moves (`animation: zmdi-spin 1.5s infinite linear`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — zheng-admin/src/plugins/material-design-iconic-font-2.2.0/css/material-design-iconic-font.css:78
  • `.zmdi-hc-spin-reverse` moves (`animation: zmdi-spin-reverse 1.5s infinite linear`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — zheng-admin/src/plugins/material-design-iconic-font-2.2.0/css/material-design-iconic-font.css:82

What to do

  • Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
AC7 · A11y enforcement4.0 / 10Weak✓ Tool-verified

Other · Accessibility — Whether accessibility is ENFORCED in the toolchain — an accessibility checker configured over the markup (an a11y lint rule set, e.g. eslint-plugin-jsx-a11y or vuejs-accessibility where the project lints JavaScript) and an automated accessibility assertion wired into tests or CI (axe/pa11y/Lighthouse or an equivalent) — on the Documented→Verified→Prevented ladder.

Method: Repo config/CI scan: an accessibility checker configured over the markup (an a11y lint rule set such as eslint-plugin-jsx-a11y / vuejs-accessibility where JavaScript is linted) and an automated accessibility assertion in tests or CI (axe/pa11y/Lighthouse or equivalent), graded on the Documented→Verified→Prevented rungs. Deterministic, presence/rung detection.

Coverage: Population: the repository's own tooling configuration — lint config, test and CI files — NOT the markup. It is read for a configured accessibility checker and an automated accessibility assertion (axe/pa11y/Lighthouse, or a native-toolkit equivalent), and it credits an INVOCATION, never a mention: a licence filename, an import comment or a doc reference earns no rung. Enforcement configured entirely outside the repository leaves no evidence here and cannot be credited.

  • No accessibility enforcement found — no accessibility linting at author time and no automated accessibility check in tests or CI. Add your UI toolkit's own accessibility assertion to the test suite (Flutter `meetsGuideline`, Espresso `AccessibilityChecks`, XCTest `performAccessibilityAudit`), then gate that test in the pipeline. What was searched, so you can tell an absence from a miss: the 152 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.

What to do

  • Enforce accessibility in the toolchain your project already uses: assert accessibility in your UI test suite with your toolkit's own matcher (Flutter `meetsGuideline`, Espresso `AccessibilityChecks`, XCTest `performAccessibilityAudit`), then gate that test in CI so a regression blocks the merge.
AX1 · Captive dependencies10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether any singleton service captures a scoped/transient dependency — a silent lifetime/threading bug.

Method: Roslyn scan: DI registrations parsed from AddSingleton/Scoped/Transient; each singleton checked for captured shorter-lifetime dependencies. Exhaustive, deterministic.

AX10 · Code composition9.4 / 10Exemplary✓ Tool-verified

Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.

Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.

Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.

What to do

  • The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX2 · Stateful singletons10.0 / 10Exemplary✓ Tool-verified

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.

AX3 · Project dependency cycles10.0 / 10Exemplary✓ Tool-verified

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.

AX4 · Dependency direction10.0 / 10Exemplary✓ Tool-verified

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.

AX6 · Interface segregation9.9 / 10Exemplary✓ Tool-verified

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.

  • `BaseService<Record, Example>` declares 22 abstract methods: `countByExample`, `deleteByExample`, `deleteByPrimaryKey`, `deleteByPrimaryKeys`, `initMapper`, `insert`, `insertSelective`, `selectByExample`, `selectByExampleForOffsetPage`, `selectByExampleForStartPage`, `selectByExampleWithBLOBs`, `selectByExampleWithBLOBsForOffsetPage`, `selectByExampleWithBLOBsForStartPage`, `selectByPrimaryKey`, `selectFirstByExample`, `selectFirstByExampleWithBLOBs`, `updateByExample`, `updateByExampleSelective`, `updateByExampleWithBLOBs`, `updateByPrimaryKey`, `updateByPrimaryKeySelective`, `updateByPrimaryKeyWithBLOBs`. 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. — zheng-common/src/main/java/com/zheng/common/base/BaseService.java:11

What to do

  • Split fat interfaces into focused role-interfaces so clients depend only on what they use.
IC1 · Incompleteness & stubs8.5 / 10Strong✓ Tool-verified

Other · Code Health — Unfinished work detected by code SHAPE, not keywords, in this repository's Java: methods that only throw a "not implemented" exception, methods that take inputs and return a constant or do nothing, dead `if (false)` branches, and skeleton classes most of whose methods are holes.

Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, guards that return what the code already falls through to, tests an earlier guard already decided, comparisons against NaN, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.

  • `main` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. (×2) — zheng-pay/zheng-pay-sdk/src/main/java/com/zheng/pay/sdk/App.java:7, zheng-wechat/zheng-wechat-mp/zheng-wechat-mp-service/src/main/java/com/zheng/wechat/mp/service/App.java:7

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.
M1 · Documentation (README)6.5 / 10Adequate✓ Tool-verified

Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.

Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.

What to do

  • Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
  • Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
  • Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
  • Add a README to the 42 of 55 project(s) that lack one — worth up to 1.5 pts.
M2 · Architecture documentation0.0 / 10Critical✓ Tool-verified

Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.

Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.

  • No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
  • No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.

What to do

  • Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
  • Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure10.0 / 10Exemplary✓ Tool-verified

Maturity · Maturity — Whether the repo is organised deliberately — src/test separation and consistent project naming.

Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.

M4 · Documentation accuracy10.0 / 10Exemplary◐ Sampled · advisory

Maturity · Maturity — Whether the README actually describes the code that exists (LLM-judged, advisory).

Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.

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.

  • The pipeline is well-formed, but the only CI definition is `.travis.yml`, and its `README.md` build badge still points at `travis-ci.org` — a service shut down in June 2021. No other CI is configured in this repository, so nothing has been building or testing changes here since that shutdown — the steps below describe a gate that is not running. Porting it is mostly mechanical: the build and test commands already written here are what a replacement pipeline would run.

What to do

  • Port the existing pipeline to a CI service that is still operating — the build and test steps are already specified — and remove the dead configuration and its badge so the repository stops advertising a gate that no longer exists.
P2 · Observability6.1 / 10Adequate✓ Tool-verified

Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.

Method: Filesystem/Roslyn scan: structured-logging frameworks (Serilog, NLog), OpenTelemetry, and health-check endpoint patterns. Exhaustive, deterministic.

  • Only 20/28 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `zheng-cms/zheng-cms-dao`, `zheng-message/zheng-message-sdk`, `zheng-pay/zheng-pay-dao`, `zheng-pay/zheng-pay-sdk`, `zheng-ucenter/zheng-ucenter-dao` and 3 more.

What to do

  • Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
P3 · Security & performance tooling0.0 / 10Critical✓ Tool-verified

Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).

Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.

  • No static application security testing detected. For this repository's stack, add spotbugs with find-sec-bugs (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 81 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.

What to do

  • Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
  • Enable Dependabot/Renovate or a dependency-review gate.
  • Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release Hygiene5.0 / 10Adequate✓ Tool-verified

Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.

Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.

  • No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)

What to do

  • Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
PF2 · Allocation hygiene6.1 / 10Adequate✓ Tool-verified

Readiness · Performance — Whether the code is written to minimise allocations so it doesn't pressure its host's memory manager — buffer/slice views over copies, object pooling, stack or value-type allocation, and buffer writers. Reward-only: credited where present, never penalised where a simpler style is fine.

Method: Production-source scan: density (per 1k LoC) of allocation-aware APIs — in .NET Span/Memory, ArrayPool/ObjectPool, stackalloc, ValueTask, value-type structs, IBufferWriter, string.Create, SkipLocalsInit; off .NET, with comments and strings blanked, Go's sync.Pool, preallocated slices/maps, Grow, strconv.Append* and buf[:0] reuse; the JVM's NIO buffer views, MemorySegment, primitive collections, pools and literal presizes (plus Kotlin primitive arrays and value classes, Scala AnyVal and @specialized); Swift's reserveCapacity, ContiguousArray, withUnsafe* access and ~Copyable. Activated off .NET on the same floor (400 lines, and benchmarks or 8 uses); Rust and garbage-collected scripting languages are not applicable. Reward-only. Deterministic, syntax/text detection.

What to do

  • Raise allocation-aware density on the hot paths — currently 10 use(s) across 41,207 production line(s) (~0.2/1k). More of the idioms below on the allocation-heavy paths climbs this toward 10.
  • Java: on hot paths, work through buffer views (ByteBuffer/LongBuffer slices, MemorySegment) instead of copies, avoid boxing with primitive collections (fastutil, Eclipse Collections, HPPC, Trove), presize collections and StringBuilders, and pool expensive buffers (Netty's pooled allocator, commons-pool).
R1 · Type Safety0.0 / 10Critical✓ Tool-verified

React / JS · Code Health — How much of the frontend is typed TypeScript vs untyped JavaScript.

Method: Frontend file inventory: the share of typed TypeScript vs untyped JavaScript across the source tree. Deterministic, exhaustive over frontend files.

  • 0 typed · 14 plain JS — the untyped files are zheng-admin/src/js/admin.js, zheng-admin/src/js/common.js, zheng-admin/src/js/login.js, zheng-admin/src/plugins/My97DatePicker/lang/en.js, zheng-admin/src/plugins/My97DatePicker/lang/zh-cn.js, zheng-admin/src/plugins/My97DatePicker/lang/zh-tw.js (+8 more).

What to do

  • Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.
R10 · Code Duplication9.6 / 10Exemplary✓ Tool-verified

React / JS · Code Health — Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm over JS/TS tokens, D-386): 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. Deterministic.

  • zheng-cms/zheng-cms-web/src/main/webapp/resources/ and zheng-ui/zheng-cms-web/ are near-verbatim copies of each other: 5 files are byte-identical under the same relative paths (~237 KB; the trees hold 9 and 23 files). That is one structural fact, not 5 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. — zheng-cms/zheng-cms-web/src/main/webapp/resources/fonts/glyphicons-halflings-regular.svg:1
  • zheng-admin/src/plugins/select2/js/select2.full.js:8 · zheng-admin/src/plugins/select2/js/select2.js:8 — 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. — zheng-admin/src/plugins/select2/js/select2.full.js:8
  • zheng-admin/src/plugins/select2/js/select2.full.js:2977 · zheng-admin/src/plugins/select2/js/select2.js:2977 — 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. — zheng-admin/src/plugins/select2/js/select2.full.js:2977
  • zheng-admin/src/plugins/select2/js/select2.full.js:4744 · zheng-admin/src/plugins/select2/js/select2.js:4744 — 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. — zheng-admin/src/plugins/select2/js/select2.full.js:4744
  • zheng-admin/src/plugins/select2/js/select2.full.js:6375 · zheng-admin/src/plugins/select2/js/select2.js:5664 — 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. — zheng-admin/src/plugins/select2/js/select2.full.js:6375
  • zheng-admin/src/plugins/select2/js/select2.full.js:5700 · zheng-admin/src/plugins/select2/js/select2.full.js:5757 — 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. — zheng-admin/src/plugins/select2/js/select2.full.js:5700
  • zheng-admin/src/plugins/select2/js/select2.full.js:6071 · zheng-admin/src/plugins/select2/js/select2.full.js:6110 — 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. — zheng-admin/src/plugins/select2/js/select2.full.js:6071
  • zheng-cms/zheng-cms-web/src/main/webapp/resources/js/main.js:2 · zheng-ui/zheng-cms-web/js/main.js:2 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — zheng-cms/zheng-cms-web/src/main/webapp/resources/js/main.js:2
  • zheng-admin/src/js/admin.js:153 · zheng-admin/src/js/admin.js:167 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — zheng-admin/src/js/admin.js:153
  • zheng-admin/src/js/admin.js:124 · zheng-admin/src/js/admin.js:159 — 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. — zheng-admin/src/js/admin.js:124
  • zheng-admin/src/plugins/waves-0.7.5/waves.js:200 · zheng-admin/src/plugins/waves-0.7.5/waves.js:229 — 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. — zheng-admin/src/plugins/waves-0.7.5/waves.js:200
  • zheng-admin/src/js/admin.js:35 · zheng-admin/src/js/admin.js:48 — 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. — zheng-admin/src/js/admin.js:35

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.
R2 · Cyclomatic Complexity7.1 / 10Strong✓ Tool-verified

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.

  • apply has cyclomatic complexity 40 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. (×2) — zheng-admin/src/plugins/select2/js/select2.full.js:4582, zheng-admin/src/plugins/select2/js/select2.js:4582
  • normalize has cyclomatic complexity 32 and cognitive complexity 63; 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. (×2) — zheng-admin/src/plugins/select2/js/select2.full.js:79, zheng-admin/src/plugins/select2/js/select2.js:79
  • handler has cyclomatic complexity 27 and cognitive complexity 28; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — zheng-admin/src/plugins/select2/js/select2.full.js:6247
  • fromElement has cyclomatic complexity 23 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. (×2) — zheng-admin/src/plugins/select2/js/select2.full.js:4948, zheng-admin/src/plugins/select2/js/select2.js:4948
  • main has cyclomatic complexity 22 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. (×2) — zheng-admin/src/plugins/select2/js/select2.full.js:318, zheng-admin/src/plugins/select2/js/select2.js:318
  • (anonymous) has cyclomatic complexity 15 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 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. (×2) — zheng-admin/src/plugins/select2/js/select2.full.js:5364, zheng-admin/src/plugins/select2/js/select2.js:5364
  • _positionDropdown has cyclomatic complexity 14 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. (×2) — zheng-admin/src/plugins/select2/js/select2.full.js:4253, zheng-admin/src/plugins/select2/js/select2.js:4253
  • _syncSubtree has cyclomatic complexity 13 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 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. (×2) — zheng-admin/src/plugins/select2/js/select2.full.js:5415, zheng-admin/src/plugins/select2/js/select2.js:5415

What to do

  • Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.
R3 · Large Files1.4 / 10Critical✓ 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.

  • zheng-admin/src/plugins/select2/js/select2.full.js has 5184 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — zheng-admin/src/plugins/select2/js/select2.full.js:1
  • zheng-admin/src/plugins/select2/js/select2.js has 4622 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — zheng-admin/src/plugins/select2/js/select2.js:1
  • zheng-admin/src/plugins/waves-0.7.5/waves.js has 450 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — zheng-admin/src/plugins/waves-0.7.5/waves.js:1

What to do

  • Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
R4 · Test Coverage0.0 / 10Critical✓ Tool-verified

React / JS · Readiness — Static test reachability (D-386): the share of production files reachable from any test via the import graph — measured without running anything.

Method: Static test reachability: the share of production files reachable from any test via the import graph — measured without running anything. Deterministic.

  • 0% of 14 production file(s) reachable from 0 test file(s) via the import graph — 'production' here is the RESIDUE: every source file left once tests, tooling, generated output, config, declarations and declaration-only modules, fixture corpora, type fixtures, behaviour-free data modules, re-export barrels, registration/constant data modules and service workers are set aside, so the percentage is taken over a smaller denominator than the workspace's file count

What to do

  • Add tests that import the unreached modules (directly or through their public entry).
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 4 application, 0 tooling and 0 test entry point(s) detected in this repo. This repository declares no build, type-check or test script, so nothing here would fail on a wrong deletion — confirm by hand that nothing loads each file (including by a path built at runtime) before removing it. An undetected custom entry would make these reachable.
  • no import path from any entry point (4 application, 0 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make (×10) — zheng-admin/src/plugins/select2/js/select2.full.js, zheng-admin/src/plugins/select2/js/select2.js, zheng-admin/src/plugins/waves-0.7.5/waves.js, …

What to do

  • Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
R9 · Circular Imports10.0 / 10Exemplary✓ 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.

S1 · Web-Security Posture6.0 / 10Adequate✓ Tool-verified

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://code.jquery.com/jquery-1.10.1.min.js` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. The URL also names no version, so it resolves to whatever that origin serves at fetch time — the executed bytes can change with nobody touching this repository. 6 such include(s) across the repository's markup. — REDACTED:28
  • 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 `zheng-ui.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.) — project-tools/nginx/servers/zheng-ui.conf: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.
X1 · Async correctness10.0 / 10Exemplary○ Nothing flagged

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.

X12 · Unreachable branch10.0 / 10Exemplary○ Nothing flagged

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.

X13 · Undrained process stream10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.

Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. 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 `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.

X14 · Bypassable address classification10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.

Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.

X15 · Unvalidated length from an untrusted reader10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether a length read out of the stream being parsed is bounded before it is allocated or read — an unchecked count taken from the input lets the input choose the allocation.

Method: Roslyn syntax + semantics: integer lengths read from a BinaryReader and spent on a bulk read or an array allocation, checked for any comparison or bounding call on the value anywhere in the method. Deterministic, provable per finding. Advisory.

X16 · Unfloored truncation loop10.0 / 10Exemplary○ Nothing flagged

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.

X17 · Uncapped recursion over a caller-supplied document10.0 / 10Exemplary○ Nothing flagged

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.

X18 · Disposal-pattern correctness10.0 / 10Exemplary○ Nothing flagged

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.

X19 · Unrestored process-global state10.0 / 10Exemplary○ Nothing flagged

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.

X20 · Mistyped argument guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether an argument guard throws the exception its own condition describes — a guard that rejects a value for being EMPTY and reports it as `NullPointerException` (Java, Kotlin, Scala), `ArgumentError.notNull` (Dart) or `ArgumentNullException` (F#'s `nullArg`) tells the caller a parameter was null when it provably was not.

Method: Roslyn syntax: `throw new ArgumentNullException(nameof(p))` statements controlled by an `if`, whose condition is read for a test that is true of a NON-null `p` — an emptiness test that dereferences it (`p.Count == 0`, `!p.Any()`) or a BCL predicate documented true of the empty value (`string.IsNullOrEmpty(p)`). Deterministic, provable per finding. Advisory.

X21 · Side-effecting pattern guard10.0 / 10Exemplary○ Nothing flagged

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.

X22 · Contradicted release guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a method that TAKES a lock or semaphore and gives it back from a flag-guarded `finally` returns the value that flag implies — reporting success while the guard hands the primitive back admits a second caller the exclusion was there to keep out, and reporting failure while the guard keeps it leaves nothing to ever give it back.

Method: Roslyn syntax: `try` statements whose `finally` releases a synchronisation primitive under a bare local-bool guard, where the method also TOOK that same primitive before the `try`, checked for a `return` of a bool literal whose value disagrees with the flag state the method's own straight-line assignments put it in. Deterministic, provable per finding. Advisory.

X23 · Unguarded diagnostic materialisation10.0 / 10Exemplary○ Nothing flagged

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.

X24 · Document value interpolated into markup unescaped10.0 / 10Exemplary○ Nothing flagged

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.

X25 · Inert configuration knob10.0 / 10Exemplary○ Nothing flagged

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.

X26 · Unsynchronised callback handoff10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a value handed from a callback to the body that waits on it crosses on something built to be crossed — a `Queue<T>`/`List<T>`/`Dictionary<K,V>` written inside an event handler and read back outside it is mutated by two flows at once, and the semaphore or completion source beside it orders how MANY items exist while leaving the collection's own head, tail and backing array unprotected.

Method: Roslyn syntax: method, accessor, local-function and lambda bodies that declare BOTH a non-thread-safe generic collection (`Queue`/`Stack`/`List`/`Dictionary`/`HashSet`/`Sorted*`/`LinkedList`) and a synchronisation primitive (`SemaphoreSlim`/`TaskCompletionSource`/`ManualResetEvent(Slim)`/`AutoResetEvent`/`CountdownEvent`) as locals, then read for a `+=`-registered lambda that raises that primitive while the body outside every lambda waits on it — and, in that scope, a mutating call on the collection inside the lambda paired with a mention of it outside. Any `lock` in the scope abstains it. On a repository with no .NET source the same handoff is read in Java off the engine’s own token stream (test source sets, vendored and demonstration paths not): an `ArrayList`/`LinkedList`/`ArrayDeque`/`PriorityQueue`/`Hash*`/`LinkedHash*`/`Tree*` local and a `CountDownLatch`/`Semaphore`/`CompletableFuture` local, a lambda or anonymous class that raises the primitive and mutates the collection, and a wait outside it; any `synchronized` or `lock()` abstains the body. Because each of those primitives orders what the callback wrote before raising it, only a touch that provably overlaps the callback is convicted: one after the registration and before the next wait, or one in a loop registered-before, waiting on every pass and not declaring the collection. Deterministic, provable per finding. Advisory.

X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether an enhanced `for` leaves the collection it is walking alone — a body that adds to or removes from the very collection the loop is iterating invalidates the fail-fast iterator it is holding, so the next `next()` throws `ConcurrentModificationException` and the remaining elements are never seen.

Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.

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.

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.

X3 · Exception handling6.3 / 10Adequate✓ Tool-verified

Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.

Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.

  • An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×4) — zheng-admin/src/plugins/jquery.cookie.js:47, zheng-admin/src/plugins/malihu-custom-scrollbar-plugin/jquery.mCustomScrollbar.js:1528, zheng-admin/src/plugins/malihu-custom-scrollbar-plugin/jquery.mCustomScrollbar.js:1534, …
  • `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. (×4) — zheng-common/src/main/java/com/zheng/common/util/StringUtil.java:112, zheng-common/src/main/java/com/zheng/common/util/StringUtil.java:132, zheng-common/src/main/java/com/zheng/common/util/StringUtil.java:152, …

What to do

  • Swallowed exception (empty catch)
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.

X4 · Structured logging5.1 / 10Adequate✓ Tool-verified

Other · Code Health — Whether log calls use message templates (queryable) rather than interpolated strings.

Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `trace`/`debug`/`info`/`warn`/`error`/`fatal`/`verbose`/`silly`/`http`/`log` call on a receiver named for a logger, in a package whose own or an enclosing `package.json` declares a logger that carries values as fields (pino, pino-http, nestjs-pino, Fastify, winston, bunyan, tslog, LogTape, roarr), whose first deciding argument is a template literal with substitutions; an object-literal fields argument is stepped over, a plain string message clears the call. Python is read the same way: a `debug`/`info`/`warning`/`error`/`exception`/`critical`/`log` call on a logger in a file that imports the standard library’s `logging` or structlog (loguru, which formats at the call, is not judged), whose message is a whole f-string with a non-constant field; a `%`-formatted, `.format()`-ed or concatenated message is not convicted, as in C#. PHP is read the same way: a PSR-3 level call (`emergency`…`debug`, `log`) on a logger (`$logger`, `$this->logger`, Laravel’s `Log::`, `logger()`, `\Drupal::logger()`) in a package whose `composer.json` requires a PSR-3 logger or a framework that hands one out (psr/log, Monolog, Laravel, Symfony, Drupal, CakePHP), or a file that imports one, whose message is a double-quoted string interpolating a variable; a single-quoted message clears the call, and `sprintf` or `.` concatenation is not convicted, as in C#. Dart is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on Sentry’s structured logger (`Sentry.logger`) whose message is a whole string literal interpolating a value (`$name`, `${…}`); the `Sentry.logger.fmt` template API clears the call. Dart that logs only through loggers with one message and no fields (package:logging, package:logger, talker, dart:developer) is not applicable rather than a reach gap. Ruby is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on the console gem’s `Console` (declared by a Gemfile, gemspec or Gemfile.lock, or required) or, where SemanticLogger, Ougai or dry-logger is declared or required, on a receiver named for a logger (`logger`, `@logger`, `Rails.logger`, `log`), whose first deciding argument is, as the whole argument, a double-quoted string interpolating a non-constant value (`#{…}`, `#@ivar`); a plain literal clears the call, keyword arguments are the fields, and a block, `%`-format or `+` concatenation is not convicted. Ruby that logs only through the standard Logger (Rails.logger) is not applicable rather than a reach gap. Deterministic.

  • `error` at line 71 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. — zheng-common/src/main/java/com/zheng/common/util/RedisUtil.java:71
  • `error` at line 102 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. — zheng-common/src/main/java/com/zheng/common/util/RedisUtil.java:102
  • `error` at line 119 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. — zheng-common/src/main/java/com/zheng/common/util/RedisUtil.java:119
  • `error` at line 134 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. — zheng-common/src/main/java/com/zheng/common/util/RedisUtil.java:134
  • `error` at line 151 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. — zheng-common/src/main/java/com/zheng/common/util/RedisUtil.java:151
  • `error` at line 168 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. — zheng-common/src/main/java/com/zheng/common/util/RedisUtil.java:168
  • `error` at line 212 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. — zheng-common/src/main/java/com/zheng/common/util/RedisUtil.java:212
  • `error` at line 226 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.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. — zheng-common/src/main/java/com/zheng/common/util/RedisUtil.java:226
  • `error` at line 241 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. — zheng-common/src/main/java/com/zheng/common/util/RedisUtil.java:241
  • `error` at line 257 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. — zheng-common/src/main/java/com/zheng/common/util/RedisUtil.java:257
  • `error` at line 274 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. — zheng-common/src/main/java/com/zheng/common/util/RedisUtil.java:274
  • `debug` at line 17 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. — zheng-upms/zheng-upms-client/src/main/java/com/zheng/upms/client/shiro/listener/UpmsSessionListener.java:17
  • `debug` at line 22 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. — zheng-upms/zheng-upms-client/src/main/java/com/zheng/upms/client/shiro/listener/UpmsSessionListener.java:22
  • `debug` at line 27 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. — zheng-upms/zheng-upms-client/src/main/java/com/zheng/upms/client/shiro/listener/UpmsSessionListener.java:27

What to do

  • Interpolated log message defeats structured logging
X5 · Nullable reference types2.0 / 10Critical✓ Tool-verified

Other · Code Health — Whether Java packages are null-marked and not undermined by heavy nullness suppression — a package under `@NullMarked` (or `@NonNullApi`, `@ParametersAreNonnullByDefault`, `@NonNullByDefault`, or a NullAway/Checker Framework configuration naming it) makes an unannotated reference exclude null, and `@SuppressWarnings("NullAway")`, `("nullness")`, `("null")` and `castToNonNull(…)` are what silence it.

Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.

  • 0/82 of this repository's Java package directories are under a non-null default: a `package-info.java` declaring `@NullMarked` (JSpecify) or `@NonNullApi`, `@ParametersAreNonnullByDefault`, `@NonNullByDefault`, `@DefaultQualifier(NonNull.class)`; a `module-info.java` declaring `@NullMarked`; every type in it `@NullMarked`; or a build that runs NullAway with the package in `AnnotatedPackages`, or the Checker Framework's `NullnessChecker`. Elsewhere every reference admits null and no checker warns on the dereference that throws a `NullPointerException`.

What to do

  • Declare the default where Java declares it: `@NullMarked` (org.jspecify.annotations) in each package's `package-info.java`, or once in `module-info.java`, and run NullAway (Error Prone) or the Checker Framework so the declaration is enforced. Then annotate the real exceptions `@Nullable` and resolve the suppressions rather than adding to them: a `@SuppressWarnings("NullAway")` or `castToNonNull(x)` on a value the checker could show to be null is a `NullPointerException` waiting for the path that makes it true — where the value genuinely cannot be null, say something the checker can see instead (a null check, `Objects.requireNonNull`, a non-null field initialised in the constructor).

WCAG coverage — what static analysis assessed

Statically assessed 15 of 55 WCAG 2.2 Level A/AA success criteria (27%; ≈30% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 40 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).

DimensionWCAG 2.2 A/AA criteriaCoverage
AC1 · Text alternatives1.1.1, 1.2.2, 1.2.5Partial signal
AC2 · Forms & labels1.3.1, 3.3.2, 4.1.2Partial signal
AC3 · Page structure1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2Partial signal
AC4 · Keyboard semantics2.1.1, 2.4.3Partial signal
AC5 · ARIA correctness4.1.2Partial signal
AC6 · Visual & motion safety1.4.3, 2.4.7Partial — literal CSS only
AC7 · A11y enforcementenforcement — no page criterionEnforcement posture (process)

Not statically assessed — these 40 Level A/AA criteria need runtime or manual evaluation (WCAG-EM): 1.2.1, 1.2.3, 1.2.4, 1.3.2, 1.3.3, 1.3.4, 1.3.5, 1.4.1, 1.4.2, 1.4.5, 1.4.10, 1.4.11, 1.4.12, 1.4.13, 2.1.2, 2.1.4, 2.2.2, 2.3.1, 2.4.4, 2.4.5, 2.4.6, 2.4.11, 2.5.1, 2.5.2, 2.5.3, 2.5.4, 2.5.7, 2.5.8, 3.1.2, 3.2.1, 3.2.2, 3.2.3, 3.2.4, 3.2.6, 3.3.1, 3.3.3, 3.3.4, 3.3.7, 3.3.8, 4.1.3.

Reference — by lens

The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.

LensScoreRatingImpact
Code Health24%Critical — gated by D3, R1, R3, R7, X5Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture98%ExemplaryStrongest area.
Maturity43%Weak — gated by D34, M2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness12%Critical — gated by D13, R4, P1, P3Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security54%Adequate — gated by D28, D30Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Accessibility31%Weak — gated by AC1, AC3, AC4, AC6Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance61%AdequateAcceptable, with room to improve.
Unscored — 1 check(s) recorded observations but carry no score

These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.

  • X10 Duplicated predicate — 25 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.
  • P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
  • P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
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.

  • 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
  • AXB1 Runtime evidence locked — no reproducible boot — 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.
  • D11 Test Reliability — Test reliability not included — the .java suite was found but not re-run
  • D12 Dependency Hygiene — Not scored — 56 Maven/Gradle manifest(s) were read, stating a version for 152 dependency(ies) and leaving 13 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
  • D14 License Compliance — Not scored — this repository's 152 declared JVM dependency coordinate(s) were read from its 56 Maven/Gradle manifest(s), but Maven Central could not be asked for the licence of 81 of them (HTTP 429 Too Many Requests from https://repo1.maven.org/maven2/junit/junit/4.12/junit-4.12.pom), and a licence verdict over part of a dependency graph is not a licence verdict. Nothing is asserted about this repository's licensing in either direction.
  • D16 Bus Factor — single-maintainer repository — bus factor is not applicable
  • D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
  • 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+ projects each declaring an entity of their own. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
  • D24 Comment Value — No inline comments to assess — comment value is not applicable here.
  • D25 ADR Conformance — no ADRs to check
  • D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
  • D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
  • D36 Supply-chain Provenance & Signing — The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a published package, a container image, a deployed service or a tagged release). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
  • D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
  • D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
  • D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
  • D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
  • D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
  • D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
  • D8 Code Coverage — Coverage not included — suite not readable by the collector
  • DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this lens looks for
  • ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
  • ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
  • ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
  • GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
  • P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
  • P7 Outbound HTTP resilience — no outbound HTTP usage detected — no HTTP client call or construction in the JVM, JavaScript/TypeScript source (service entry point: zheng-api/zheng-api-server/src/main/java/com/zheng/api/server/controller/TestController.java:20 (@Controller))
  • 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 — no coverage report found on disk — produce a coverage report in a standard format (JaCoCo XML — `mvn jacoco:report`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
  • PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a package.json, 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.
  • PF3 Async & latency hygiene — Not applicable: this repository declares no async functions, so there is no asynchronous code for a blocking call to stall.
  • R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
  • R5 Dependency Freshness — no package-lock.json — dependency freshness not measured (would require an npm lockfile); JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
  • R6 Tooling — no package.json in the repository — test/lint/typecheck wiring is read from package.json scripts (corroborated against CI), so this project's own toolchain isn't measured here
  • R8 Dependency Hygiene — Not measured — no package.json declares any dependency, so there is nothing to check imports against (imports may resolve through a host runtime rather than node).
  • X2 Cancellation propagation — no C# was loaded; this repository's Java was read, and no request in it can be cancelled by a caller — a Java request off Android takes no token: it is cancelled through the handle it returns (Future.cancel, Call.cancel, a Disposable), ambiently (io.grpc.Context) or by interrupting its thread, not through a parameter
  • X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
  • X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

Appendix A — Findings (grouped)

The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.

Critical — 172 finding(s)
D13 · REDACTED Scanning · Leaked secret · ×53
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • + 28 more in this group — see findings.md.
D28 · Secrets (history) · REDACTED · ×42
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • + 17 more in this group — see findings.md.
AC2 · Forms & labels · <input> without a programmatic label · ×20
  • <input> without a programmatic label zheng-admin/src/login.html:20 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label zheng-admin/src/login.html:26 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label zheng-admin/src/login.html:32 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label zheng-admin/src/plugins/awesome-bootstrap-checkbox/index.html:70 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label zheng-admin/src/plugins/select2/js/select2.full.js:1853 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label zheng-admin/src/plugins/select2/js/select2.full.js:3907 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label zheng-admin/src/plugins/select2/js/select2.js:1853 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label zheng-admin/src/plugins/select2/js/select2.js:3907 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label zheng-cms/zheng-cms-admin/src/main/webapp/WEB-INF/jsp/manage/comment/create.jsp:21 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label zheng-cms/zheng-cms-admin/src/main/webapp/WEB-INF/jsp/manage/comment/create.jsp:22 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label zheng-cms/zheng-cms-admin/src/main/webapp/WEB-INF/jsp/manage/comment/create.jsp:23 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label zheng-cms/zheng-cms-admin/src/main/webapp/WEB-INF/jsp/manage/comment/create.jsp:24 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label zheng-cms/zheng-cms-admin/src/main/webapp/WEB-INF/jsp/manage/comment/create.jsp:25 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label zheng-cms/zheng-cms-admin/src/main/webapp/WEB-INF/jsp/manage/comment/create.jsp:36 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label zheng-cms/zheng-cms-admin/src/main/webapp/WEB-INF/jsp/manage/comment/create.jsp:37 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label zheng-cms/zheng-cms-admin/src/main/webapp/WEB-INF/jsp/manage/comment/update.jsp:22 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label zheng-cms/zheng-cms-admin/src/main/webapp/WEB-INF/jsp/manage/comment/update.jsp:23 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label zheng-cms/zheng-cms-admin/src/main/webapp/WEB-INF/jsp/manage/comment/update.jsp:24 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label zheng-cms/zheng-cms-admin/src/main/webapp/WEB-INF/jsp/manage/comment/update.jsp:25 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label zheng-cms/zheng-cms-admin/src/main/webapp/WEB-INF/jsp/manage/comment/update.jsp:26 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
AC3 · Page structure · <html> without a lang · ×12
  • <html> without a lang zheng-admin/src/plugins/awesome-bootstrap-checkbox/index.html:2 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
  • <html> without a lang zheng-api/zheng-api-server/src/main/webapp/WEB-INF/jsp/403.jsp — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
  • <html> without a lang zheng-api/zheng-api-server/src/main/webapp/WEB-INF/jsp/404.jsp — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
  • <html> without a lang zheng-api/zheng-api-server/src/main/webapp/WEB-INF/jsp/500.jsp — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
  • <html> without a lang zheng-api/zheng-api-server/src/main/webapp/WEB-INF/jsp/error.jsp — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
  • <html> without a lang zheng-api/zheng-api-server/src/main/webapp/WEB-INF/jsp/index.jsp — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
  • <html> without a lang zheng-cms/zheng-cms-admin/src/main/webapp/WEB-INF/jsp/403.jsp — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
  • <html> without a lang zheng-cms/zheng-cms-admin/src/main/webapp/WEB-INF/jsp/404.jsp — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
  • <html> without a lang zheng-cms/zheng-cms-admin/src/main/webapp/WEB-INF/jsp/500.jsp — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
  • <html> without a lang zheng-cms/zheng-cms-admin/src/main/webapp/WEB-INF/jsp/error.jsp — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
  • <html> without a lang zheng-cms/zheng-cms-admin/src/main/webapp/WEB-INF/jsp/manage/comment/create.jsp — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
  • <html> without a lang zheng-cms/zheng-cms-admin/src/main/webapp/WEB-INF/jsp/manage/comment/update.jsp — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
AC2 · Forms & labels · <label> that labels no control · ×11
  • <label> that labels no control zheng-admin/src/plugins/awesome-bootstrap-checkbox/index.html:62 — 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 zheng-admin/src/plugins/awesome-bootstrap-checkbox/index.html:66 — 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 zheng-admin/src/plugins/awesome-bootstrap-checkbox/index.html:71 — 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 zheng-admin/src/plugins/awesome-bootstrap-checkbox/index.html:184 — 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 zheng-admin/src/plugins/awesome-bootstrap-checkbox/index.html:188 — 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 zheng-cms/zheng-cms-admin/src/main/webapp/WEB-INF/jsp/manage/article/create.jsp:90 — 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 zheng-cms/zheng-cms-admin/src/main/webapp/WEB-INF/jsp/manage/article/create.jsp:103 — 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 zheng-cms/zheng-cms-admin/src/main/webapp/WEB-INF/jsp/manage/article/create.jsp:116 — 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 zheng-cms/zheng-cms-admin/src/main/webapp/WEB-INF/jsp/manage/article/update.jsp:90 — 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 zheng-cms/zheng-cms-admin/src/main/webapp/WEB-INF/jsp/manage/article/update.jsp:103 — 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 zheng-cms/zheng-cms-admin/src/main/webapp/WEB-INF/jsp/manage/article/update.jsp:116 — 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.
D30 · Dependency Vulnerabilities · Critical CVE · ×11
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D30 · Dependency Vulnerabilities · High CVE · ×9
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
AC2 · Forms & labels · <select> without a programmatic label · ×5
  • <select> without a programmatic label zheng-admin/src/plugins/select2/js/select2.full.js:5872 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <select> without a programmatic label zheng-cms/zheng-cms-admin/src/main/webapp/WEB-INF/jsp/manage/article/create.jsp:56 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <select> without a programmatic label zheng-cms/zheng-cms-admin/src/main/webapp/WEB-INF/jsp/manage/article/update.jsp:56 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <select> without a programmatic label zheng-cms/zheng-cms-admin/src/main/webapp/WEB-INF/jsp/manage/comment/create.jsp:29 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <select> without a programmatic label zheng-cms/zheng-cms-admin/src/main/webapp/WEB-INF/jsp/manage/comment/update.jsp:30 — 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 · ×4
  • Link with no accessible name REDACTED:62 — 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.
  • Link with no accessible name REDACTED:77 — 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.
  • Link with no accessible name REDACTED:107 — 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.
  • Link with no accessible name zheng-admin/src/login.html:34 — 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.
AC1 · Text alternatives · <img> without a text alternative · ×2
  • <img> without a text alternative REDACTED:139 — 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 zheng-upms/zheng-upms-server/src/main/webapp/WEB-INF/jsp/manage/index.jsp:114 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
AC4 · Keyboard semantics · Clickable element isn't keyboard-operable · ×2
  • Clickable element isn't keyboard-operable REDACTED:229 — The repo's own CSS styles .waves-effect with `cursor: pointer`, so this <span> 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 zheng-admin/src/plugins/malihu-custom-scrollbar-plugin/jquery.mCustomScrollbar.js:865 — The repo's own CSS styles .mCSB_dragger with `cursor: pointer`, so this <div> 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.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
Serious — 408 finding(s)
AC4 · Keyboard semantics · Link used as a button (placeholder href) · ×38
  • Link used as a button (placeholder href) zheng-admin/src/crud.html:20 — An <a href="#"> (or javascript:) with a click handler is a button dressed as a link — it announces the wrong role and stops working without JS. Use a <button> for an action.
  • Link used as a button (placeholder href) zheng-admin/src/crud.html:21 — An <a href="#"> (or javascript:) with a click handler is a button dressed as a link — it announces the wrong role and stops working without JS. Use a <button> for an action.
  • Link used as a button (placeholder href) zheng-admin/src/crud.html:22 — An <a href="#"> (or javascript:) with a click handler is a button dressed as a link — it announces the wrong role and stops working without JS. Use a <button> for an action.
  • Link used as a button (placeholder href) zheng-cms/zheng-cms-admin/src/main/webapp/WEB-INF/jsp/manage/article/create.jsp:135 — An <a href="#"> (or javascript:) with a click handler is a button dressed as a link — it announces the wrong role and stops working without JS. Use a <button> for an action.
  • Link used as a button (placeholder href) zheng-cms/zheng-cms-admin/src/main/webapp/WEB-INF/jsp/manage/article/create.jsp:136 — An <a href="#"> (or javascript:) with a click handler is a button dressed as a link — it announces the wrong role and stops working without JS. Use a <button> for an action.
  • Link used as a button (placeholder href) zheng-cms/zheng-cms-admin/src/main/webapp/WEB-INF/jsp/manage/article/index.jsp:21 — An <a href="#"> (or javascript:) with a click handler is a button dressed as a link — it announces the wrong role and stops working without JS. Use a <button> for an action.
  • Link used as a button (placeholder href) zheng-cms/zheng-cms-admin/src/main/webapp/WEB-INF/jsp/manage/article/index.jsp:22 — An <a href="#"> (or javascript:) with a click handler is a button dressed as a link — it announces the wrong role and stops working without JS. Use a <button> for an action.
  • Link used as a button (placeholder href) zheng-cms/zheng-cms-admin/src/main/webapp/WEB-INF/jsp/manage/article/index.jsp:23 — An <a href="#"> (or javascript:) with a click handler is a button dressed as a link — it announces the wrong role and stops working without JS. Use a <button> for an action.
  • Link used as a button (placeholder href) zheng-cms/zheng-cms-admin/src/main/webapp/WEB-INF/jsp/manage/article/update.jsp:135 — An <a href="#"> (or javascript:) with a click handler is a button dressed as a link — it announces the wrong role and stops working without JS. Use a <button> for an action.
  • Link used as a button (placeholder href) zheng-cms/zheng-cms-admin/src/main/webapp/WEB-INF/jsp/manage/article/update.jsp:136 — An <a href="#"> (or javascript:) with a click handler is a button dressed as a link — it announces the wrong role and stops working without JS. Use a <button> for an action.
  • Link used as a button (placeholder href) zheng-cms/zheng-cms-admin/src/main/webapp/WEB-INF/jsp/manage/category/create.jsp:50 — An <a href="#"> (or javascript:) with a click handler is a button dressed as a link — it announces the wrong role and stops working without JS. Use a <button> for an action.
  • Link used as a button (placeholder href) zheng-cms/zheng-cms-admin/src/main/webapp/WEB-INF/jsp/manage/category/create.jsp:51 — An <a href="#"> (or javascript:) with a click handler is a button dressed as a link — it announces the wrong role and stops working without JS. Use a <button> for an action.
  • Link used as a button (placeholder href) zheng-cms/zheng-cms-admin/src/main/webapp/WEB-INF/jsp/manage/category/index.jsp:21 — An <a href="#"> (or javascript:) with a click handler is a button dressed as a link — it announces the wrong role and stops working without JS. Use a <button> for an action.
  • Link used as a button (placeholder href) zheng-cms/zheng-cms-admin/src/main/webapp/WEB-INF/jsp/manage/category/index.jsp:22 — An <a href="#"> (or javascript:) with a click handler is a button dressed as a link — it announces the wrong role and stops working without JS. Use a <button> for an action.
  • Link used as a button (placeholder href) zheng-cms/zheng-cms-admin/src/main/webapp/WEB-INF/jsp/manage/category/index.jsp:23 — An <a href="#"> (or javascript:) with a click handler is a button dressed as a link — it announces the wrong role and stops working without JS. Use a <button> for an action.
  • Link used as a button (placeholder href) zheng-cms/zheng-cms-admin/src/main/webapp/WEB-INF/jsp/manage/category/update.jsp:50 — An <a href="#"> (or javascript:) with a click handler is a button dressed as a link — it announces the wrong role and stops working without JS. Use a <button> for an action.
  • Link used as a button (placeholder href) zheng-cms/zheng-cms-admin/src/main/webapp/WEB-INF/jsp/manage/category/update.jsp:51 — An <a href="#"> (or javascript:) with a click handler is a button dressed as a link — it announces the wrong role and stops working without JS. Use a <button> for an action.
  • Link used as a button (placeholder href) zheng-cms/zheng-cms-admin/src/main/webapp/WEB-INF/jsp/manage/comment/index.jsp:21 — An <a href="#"> (or javascript:) with a click handler is a button dressed as a link — it announces the wrong role and stops working without JS. Use a <button> for an action.
  • Link used as a button (placeholder href) zheng-cms/zheng-cms-admin/src/main/webapp/WEB-INF/jsp/manage/menu/create.jsp:30 — An <a href="#"> (or javascript:) with a click handler is a button dressed as a link — it announces the wrong role and stops working without JS. Use a <button> for an action.
  • Link used as a button (placeholder href) zheng-cms/zheng-cms-admin/src/main/webapp/WEB-INF/jsp/manage/menu/create.jsp:31 — An <a href="#"> (or javascript:) with a click handler is a button dressed as a link — it announces the wrong role and stops working without JS. Use a <button> for an action.
  • Link used as a button (placeholder href) zheng-cms/zheng-cms-admin/src/main/webapp/WEB-INF/jsp/manage/menu/index.jsp:21 — An <a href="#"> (or javascript:) with a click handler is a button dressed as a link — it announces the wrong role and stops working without JS. Use a <button> for an action.
  • Link used as a button (placeholder href) zheng-cms/zheng-cms-admin/src/main/webapp/WEB-INF/jsp/manage/menu/index.jsp:22 — An <a href="#"> (or javascript:) with a click handler is a button dressed as a link — it announces the wrong role and stops working without JS. Use a <button> for an action.
  • Link used as a button (placeholder href) zheng-cms/zheng-cms-admin/src/main/webapp/WEB-INF/jsp/manage/menu/index.jsp:23 — An <a href="#"> (or javascript:) with a click handler is a button dressed as a link — it announces the wrong role and stops working without JS. Use a <button> for an action.
  • Link used as a button (placeholder href) zheng-cms/zheng-cms-admin/src/main/webapp/WEB-INF/jsp/manage/menu/index.jsp:24 — An <a href="#"> (or javascript:) with a click handler is a button dressed as a link — it announces the wrong role and stops working without JS. Use a <button> for an action.
  • Link used as a button (placeholder href) zheng-cms/zheng-cms-admin/src/main/webapp/WEB-INF/jsp/manage/menu/index.jsp:25 — An <a href="#"> (or javascript:) with a click handler is a button dressed as a link — it announces the wrong role and stops working without JS. Use a <button> for an action.
  • + 13 more in this group — see findings.md.
D3 · God Classes · TooManyMethods · ×38
  • TooManyMethods: GeneratedCriteria zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleExample.java:69 — TooManyMethods — 223 methods. The bar is 30 methods; this is 193 over it, 7.43× 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 zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsLogExample.java:69 — TooManyMethods — 169 methods. The bar is 30 methods; this is 139 over it, 5.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 zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsSystemExample.java:69 — TooManyMethods — 153 methods. The bar is 30 methods; this is 123 over it, 5.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: GeneratedCriteria zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsUserExample.java:69 — TooManyMethods — 153 methods. The bar is 30 methods; this is 123 over it, 5.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: GeneratedCriteria zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsCategoryExample.java:69 — TooManyMethods — 147 methods. The bar is 30 methods; this is 117 over it, 4.90× 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 zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsPermissionExample.java:69 — TooManyMethods — 147 methods. The bar is 30 methods; this is 117 over it, 4.90× 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 zheng-ucenter/zheng-ucenter-dao/src/main/java/com/zheng/ucenter/dao/model/UcenterUserExample.java:70 — TooManyMethods — 139 methods. The bar is 30 methods; this is 109 over it, 4.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 zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsTagExample.java:69 — TooManyMethods — 123 methods. The bar is 30 methods; this is 93 over it, 4.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: GeneratedCriteria zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsCommentExample.java:69 — TooManyMethods — 119 methods. The bar is 30 methods; this is 89 over it, 3.97× 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 zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsPageExample.java:69 — TooManyMethods — 111 methods. The bar is 30 methods; this is 81 over it, 3.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: GeneratedCriteria zheng-pay/zheng-pay-dao/src/main/java/com/zheng/pay/dao/model/PayInOrderDetailExample.java:69 — TooManyMethods — 97 methods. The bar is 30 methods; this is 67 over it, 3.23× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: GeneratedCriteria zheng-ucenter/zheng-ucenter-dao/src/main/java/com/zheng/ucenter/dao/model/UcenterUserDetailsExample.java:70 — TooManyMethods — 87 methods. The bar is 30 methods; this is 57 over it, 2.90× 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 zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsMenuExample.java:69 — TooManyMethods — 85 methods. The bar is 30 methods; this is 55 over it, 2.83× 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 zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsSystemExample.java:69 — TooManyMethods — 85 methods. The bar is 30 methods; this is 55 over it, 2.83× 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 zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsRoleExample.java:69 — TooManyMethods — 85 methods. The bar is 30 methods; this is 55 over it, 2.83× 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 zheng-pay/zheng-pay-dao/src/main/java/com/zheng/pay/dao/model/PayInOrderExample.java:69 — TooManyMethods — 79 methods. The bar is 30 methods; this is 49 over it, 2.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 zheng-pay/zheng-pay-dao/src/main/java/com/zheng/pay/dao/model/PayOutOrderExample.java:69 — TooManyMethods — 79 methods. The bar is 30 methods; this is 49 over it, 2.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 zheng-pay/zheng-pay-dao/src/main/java/com/zheng/pay/dao/model/PayMchExample.java:69 — TooManyMethods — 75 methods. The bar is 30 methods; this is 45 over it, 2.50× 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 zheng-pay/zheng-pay-dao/src/main/java/com/zheng/pay/dao/model/PayVendorExample.java:69 — TooManyMethods — 75 methods. The bar is 30 methods; this is 45 over it, 2.50× 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 zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsTopicExample.java:69 — TooManyMethods — 73 methods. The bar is 30 methods; this is 43 over it, 2.43× 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 zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsOrganizationExample.java:69 — 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 zheng-ucenter/zheng-ucenter-dao/src/main/java/com/zheng/ucenter/dao/model/UcenterUserOauthExample.java:70 — TooManyMethods — 67 methods. The bar is 30 methods; this is 37 over it, 2.23× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: GeneratedCriteria zheng-pay/zheng-pay-dao/src/main/java/com/zheng/pay/dao/model/PayVestExample.java:69 — TooManyMethods — 59 methods. The bar is 30 methods; this is 29 over it, 1.97× 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 zheng-ucenter/zheng-ucenter-dao/src/main/java/com/zheng/ucenter/dao/model/UcenterUserLogExample.java:70 — TooManyMethods — 57 methods. The bar is 30 methods; this is 27 over it, 1.90× 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 zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsUserPermissionExample.java:69 — TooManyMethods — 55 methods. The bar is 30 methods; this is 25 over it, 1.83× 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.
  • + 13 more in this group — see findings.md.
AC6 · Visual & motion safety · Focus outline removed in CSS without a · ×27
  • Focus outline removed in CSS without a :focus replacement zheng-message/zheng-message-client/bootstrap.css:2366 — `.open .dropdown-toggle` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
  • Focus outline removed in CSS without a :focus replacement zheng-message/zheng-message-client/bootstrap.css:2659 — `.btn.active` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
  • Focus outline removed in CSS without a :focus replacement zheng-message/zheng-message-client/bootstrap.css:3041 — `.btn-group.open .dropdown-toggle` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
  • Focus outline removed in CSS without a :focus replacement zheng-message/zheng-message-client/bootstrap.css:3738 — `.navbar-search .search-query.focused` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
  • Focus outline removed in CSS without a :focus replacement zheng-admin/src/plugins/zTree_v3/css/demo.css:2 — `object` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
  • Focus outline removed in CSS without a :focus replacement zheng-admin/src/plugins/zTree_v3/css/zTreeStyle/zTreeStyle.css:30 — `.ztree li span.button` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
  • Focus outline removed in CSS without a :focus replacement zheng-admin/src/plugins/zTree_v3/css/metroStyle/metroStyle.css:29 — `.ztree li span.button` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
  • Focus outline removed in CSS without a :focus replacement zheng-admin/src/plugins/zTree_v3/css/awesomeStyle/awesome.css:104 — `.ztree li span.button` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
  • Focus outline removed in CSS without a :focus replacement zheng-admin/src/plugins/zTree_v3/css/awesomeStyle/awesome.less:61 — `.ztree li span.button` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
  • Focus outline removed in CSS without a :focus replacement zheng-admin/src/plugins/waves-0.7.5/waves.css:84 — `.waves-button` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
  • Focus outline removed in CSS without a :focus replacement zheng-admin/src/plugins/select2/theme/select2-bootstrap.css:66 — `.select2-container--bootstrap .select2-selection` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
  • Focus outline removed in CSS without a :focus replacement zheng-admin/src/plugins/select2/theme/select2-bootstrap.css:84 — `.select2-container--bootstrap .select2-search__field` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
  • Focus outline removed in CSS without a :focus replacement zheng-admin/src/plugins/select2/css/select2.css:230 — `.select2-container--default.select2-container--focus .select2-selection--multiple` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
  • Focus outline removed in CSS without a :focus replacement zheng-admin/src/plugins/select2/css/select2.css:253 — `.select2-container--default .select2-search--inline .select2-search__field` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
  • Focus outline removed in CSS without a :focus replacement zheng-admin/src/plugins/select2/css/select2.css:448 — `.select2-container--classic .select2-search--dropdown .select2-search__field` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
  • Focus outline removed in CSS without a :focus replacement zheng-admin/src/plugins/select2/css/select2.css:451 — `.select2-container--classic .select2-search--inline .select2-search__field` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
  • Focus outline removed in CSS without a :focus replacement zheng-admin/src/plugins/malihu-custom-scrollbar-plugin/jquery.mCustomScrollbar.css:35 — `.mCustomScrollBox` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
  • Focus outline removed in CSS without a :focus replacement zheng-admin/src/plugins/bootstrap-3.3.0/css/bootstrap.css:3223 — `.dropdown-toggle:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
  • Focus outline removed in CSS without a :focus replacement zheng-admin/src/plugins/bootstrap-3.3.0/css/bootstrap.css:3278 — `.dropdown-menu > .active > a` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
  • Focus outline removed in CSS without a :focus replacement zheng-admin/src/plugins/bootstrap-3.3.0/css/bootstrap.css:3297 — `.open > a` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
  • Focus outline removed in CSS without a :focus replacement zheng-admin/src/plugins/bootstrap-3.3.0/css/bootstrap.css:3372 — `.btn-group > .btn:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
  • Focus outline removed in CSS without a :focus replacement zheng-admin/src/plugins/bootstrap-3.3.0/css/bootstrap.css:3424 — `.btn-group.open .dropdown-toggle` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
  • Focus outline removed in CSS without a :focus replacement zheng-admin/src/plugins/bootstrap-3.3.0/css/bootstrap.css:4011 — `.navbar-toggle:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
  • Focus outline removed in CSS without a :focus replacement zheng-admin/src/plugins/bootstrap-3.3.0/css/bootstrap.css:5513 — `.modal` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
  • Focus outline removed in CSS without a :focus replacement zheng-admin/src/plugins/bootstrap-3.3.0/css/bootstrap.css:5547 — `.modal-content` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
  • + 2 more in this group — see findings.md.
AC3 · Page structure · Page without a main landmark · ×22
  • Page without a main landmark zheng-admin/src/crud.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 zheng-admin/src/demo.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 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 zheng-admin/src/login.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 zheng-admin/src/plugins/awesome-bootstrap-checkbox/index.html:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark zheng-api/zheng-api-server/src/main/webapp/WEB-INF/jsp/403.jsp — 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 zheng-api/zheng-api-server/src/main/webapp/WEB-INF/jsp/404.jsp — 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 zheng-api/zheng-api-server/src/main/webapp/WEB-INF/jsp/500.jsp — 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 zheng-api/zheng-api-server/src/main/webapp/WEB-INF/jsp/error.jsp — 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 zheng-api/zheng-api-server/src/main/webapp/WEB-INF/jsp/index.jsp — 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 zheng-cms/zheng-cms-admin/src/main/webapp/WEB-INF/jsp/403.jsp — 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 zheng-cms/zheng-cms-admin/src/main/webapp/WEB-INF/jsp/404.jsp — 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 zheng-cms/zheng-cms-admin/src/main/webapp/WEB-INF/jsp/500.jsp — 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 zheng-cms/zheng-cms-admin/src/main/webapp/WEB-INF/jsp/error.jsp — 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 zheng-cms/zheng-cms-admin/src/main/webapp/WEB-INF/jsp/manage/article/index.jsp — 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 zheng-cms/zheng-cms-admin/src/main/webapp/WEB-INF/jsp/manage/category/index.jsp — 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 zheng-cms/zheng-cms-admin/src/main/webapp/WEB-INF/jsp/manage/comment/create.jsp — 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 zheng-cms/zheng-cms-admin/src/main/webapp/WEB-INF/jsp/manage/comment/index.jsp — 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 zheng-cms/zheng-cms-admin/src/main/webapp/WEB-INF/jsp/manage/comment/update.jsp — 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 zheng-cms/zheng-cms-admin/src/main/webapp/WEB-INF/jsp/manage/menu/index.jsp — 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 zheng-cms/zheng-cms-admin/src/main/webapp/WEB-INF/jsp/manage/page/index.jsp — 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 zheng-cms/zheng-cms-admin/src/main/webapp/WEB-INF/jsp/manage/setting/index.jsp — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
D3 · God Classes · FileTooLong · ×12
  • FileTooLong: js/select2.full.js zheng-admin/src/plugins/select2/js/select2.full.js — FileTooLong — 3899 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 2399 over it, 2.60× 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: js/select2.js zheng-admin/src/plugins/select2/js/select2.js — FileTooLong — 3503 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 2003 over it, 2.34× 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: malihu-custom-scrollbar-plugin/jquery.mCustomScrollbar.js zheng-admin/src/plugins/malihu-custom-scrollbar-plugin/jquery.mCustomScrollbar.js — FileTooLong — 1351 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 851 over it, 2.70× 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: js/bootstrap.js zheng-admin/src/plugins/bootstrap-3.3.0/js/bootstrap.js — FileTooLong — 1281 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 781 over it, 2.56× 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: fullPage/jquery.fullPage.js zheng-admin/src/plugins/fullPage/jquery.fullPage.js — FileTooLong — 1237 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 737 over it, 2.47× 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: model/CmsArticleExample.java zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleExample.java — FileTooLong — 763 significant lines (blank, comment-only and punctuation-only lines excluded), about 99% of them inside a single declaration: CmsArticleExample (7-1283). The bar is 500 significant lines; this is 263 over it, 1.53× 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: model/UpmsLogExample.java zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsLogExample.java — FileTooLong — 601 significant lines (blank, comment-only and punctuation-only lines excluded), about 99% of them inside a single declaration: UpmsLogExample (7-1013). The bar is 500 significant lines; this is 101 over it, 1.20× 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: model/UpmsSystemExample.java zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsSystemExample.java — FileTooLong — 553 significant lines (blank, comment-only and punctuation-only lines excluded), about 99% of them inside a single declaration: UpmsSystemExample (7-933). The bar is 500 significant lines; this is 53 over it, 1.11× 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: model/UpmsUserExample.java zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsUserExample.java — FileTooLong — 553 significant lines (blank, comment-only and punctuation-only lines excluded), about 99% of them inside a single declaration: UpmsUserExample (7-933). The bar is 500 significant lines; this is 53 over it, 1.11× 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: model/CmsCategoryExample.java zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsCategoryExample.java — FileTooLong — 535 significant lines (blank, comment-only and punctuation-only lines excluded), about 99% of them inside a single declaration: CmsCategoryExample (7-903). The bar is 500 significant lines; this is 35 over it, 1.07× 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: model/UpmsPermissionExample.java zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsPermissionExample.java — FileTooLong — 535 significant lines (blank, comment-only and punctuation-only lines excluded), about 99% of them inside a single declaration: UpmsPermissionExample (7-903). The bar is 500 significant lines; this is 35 over it, 1.07× 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: model/UcenterUserExample.java zheng-ucenter/zheng-ucenter-dao/src/main/java/com/zheng/ucenter/dao/model/UcenterUserExample.java — FileTooLong — 512 significant lines (blank, comment-only and punctuation-only lines excluded), about 99% of them inside a single declaration: UcenterUserExample (8-864). The bar is 500 significant lines; this is 12 over it, 1.02× 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.
D3 · God Classes · ClassTooLong · ×10
  • ClassTooLong: CmsArticleExample zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleExample.java:7 — ClassTooLong — 759 significant lines (blank, comment-only and punctuation-only lines excluded), 11 methods. The bar is 400 significant lines; this is 359 over it, 1.90× 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: UpmsLogExample zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsLogExample.java:7 — ClassTooLong — 597 significant lines (blank, comment-only and punctuation-only lines excluded), 11 methods. The bar is 400 significant lines; this is 197 over it, 1.49× 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: UpmsSystemExample zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsSystemExample.java:7 — ClassTooLong — 549 significant lines (blank, comment-only and punctuation-only lines excluded), 11 methods. The bar is 400 significant lines; this is 149 over it, 1.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.
  • ClassTooLong: UpmsUserExample zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsUserExample.java:7 — ClassTooLong — 549 significant lines (blank, comment-only and punctuation-only lines excluded), 11 methods. The bar is 400 significant lines; this is 149 over it, 1.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.
  • ClassTooLong: CmsCategoryExample zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsCategoryExample.java:7 — ClassTooLong — 531 significant lines (blank, comment-only and punctuation-only lines excluded), 11 methods. The bar is 400 significant lines; this is 131 over it, 1.33× 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: UpmsPermissionExample zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsPermissionExample.java:7 — ClassTooLong — 531 significant lines (blank, comment-only and punctuation-only lines excluded), 11 methods. The bar is 400 significant lines; this is 131 over it, 1.33× 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: UcenterUserExample zheng-ucenter/zheng-ucenter-dao/src/main/java/com/zheng/ucenter/dao/model/UcenterUserExample.java:8 — ClassTooLong — 507 significant lines (blank, comment-only and punctuation-only lines excluded), 11 methods. The bar is 400 significant lines; this is 107 over it, 1.27× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: CmsTagExample zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsTagExample.java:7 — ClassTooLong — 459 significant lines (blank, comment-only and punctuation-only lines excluded), 11 methods. The bar is 400 significant lines; this is 59 over it, 1.15× 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: CmsCommentExample zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsCommentExample.java:7 — ClassTooLong — 447 significant lines (blank, comment-only and punctuation-only lines excluded), 11 methods. The bar is 400 significant lines; this is 47 over it, 1.12× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: CmsPageExample zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsPageExample.java:7 — ClassTooLong — 423 significant lines (blank, comment-only and punctuation-only lines excluded), 11 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.
D1 · Cyclomatic Complexity · (anonymous) · ×9
  • (anonymous)::(anonymous)::apply (cyclomatic 40) zheng-admin/src/plugins/select2/js/select2.js:4582 — (anonymous)::(anonymous)::apply has cyclomatic complexity 40 (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)::(anonymous)::apply (cyclomatic 40) zheng-admin/src/plugins/select2/js/select2.full.js:4582 — (anonymous)::(anonymous)::apply has cyclomatic complexity 40 (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)::(anonymous)::(anonymous)::normalize (cyclomatic 32) zheng-admin/src/plugins/select2/js/select2.js:79 — (anonymous)::(anonymous)::(anonymous)::normalize 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.
  • (anonymous)::(anonymous)::(anonymous)::normalize (cyclomatic 32) zheng-admin/src/plugins/select2/js/select2.full.js:79 — (anonymous)::(anonymous)::(anonymous)::normalize 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.
  • (anonymous)::(anonymous)::handler (cyclomatic 27) zheng-admin/src/plugins/select2/js/select2.full.js:6247 — (anonymous)::(anonymous)::handler 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.
  • (anonymous)::(anonymous)::fromElement (cyclomatic 23) zheng-admin/src/plugins/select2/js/select2.js:4948 — (anonymous)::(anonymous)::fromElement has cyclomatic complexity 23 (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)::(anonymous)::fromElement (cyclomatic 23) zheng-admin/src/plugins/select2/js/select2.full.js:4948 — (anonymous)::(anonymous)::fromElement has cyclomatic complexity 23 (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)::(anonymous)::(anonymous)::main (cyclomatic 22) zheng-admin/src/plugins/select2/js/select2.js:318 — (anonymous)::(anonymous)::(anonymous)::main 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.
  • (anonymous)::(anonymous)::(anonymous)::main (cyclomatic 22) zheng-admin/src/plugins/select2/js/select2.full.js:318 — (anonymous)::(anonymous)::(anonymous)::main 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.
D2 · Cognitive Complexity · (anonymous) · ×9
  • (anonymous)::(anonymous)::apply (cognitive 74) zheng-admin/src/plugins/select2/js/select2.js:4582 — (anonymous)::(anonymous)::apply has cognitive complexity 74 (threshold 15). Drivers by points: if/else 34 (59 pts), error handling 2 (7 pts), boolean chains 6, loops 1 (2 pts) (nesting depth added 31). 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)::apply (cognitive 74) zheng-admin/src/plugins/select2/js/select2.full.js:4582 — (anonymous)::(anonymous)::apply has cognitive complexity 74 (threshold 15). Drivers by points: if/else 34 (59 pts), error handling 2 (7 pts), boolean chains 6, loops 1 (2 pts) (nesting depth added 31). 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)::(anonymous)::normalize (cognitive 63) zheng-admin/src/plugins/select2/js/select2.js:79 — (anonymous)::(anonymous)::(anonymous)::normalize has cognitive complexity 63 (threshold 15). Drivers by points: if/else 16 (43 pts), boolean chains 11, loops 3 (9 pts) (nesting depth added 33). 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)::(anonymous)::(anonymous)::normalize (cognitive 63) zheng-admin/src/plugins/select2/js/select2.full.js:79 — (anonymous)::(anonymous)::(anonymous)::normalize has cognitive complexity 63 (threshold 15). Drivers by points: if/else 16 (43 pts), boolean chains 11, loops 3 (9 pts) (nesting depth added 33). 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)::(anonymous)::(anonymous)::main (cognitive 29) zheng-admin/src/plugins/select2/js/select2.js:318 — (anonymous)::(anonymous)::(anonymous)::main has cognitive complexity 29 (threshold 15). Drivers by points: if/else 11 (16 pts), boolean chains 7, ternaries 2 (4 pts), 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)::(anonymous)::fromElement (cognitive 29) zheng-admin/src/plugins/select2/js/select2.js:4948 — (anonymous)::(anonymous)::fromElement has cognitive complexity 29 (threshold 15). Drivers by points: if/else 18 (24 pts), boolean chains 4, 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.
  • (anonymous)::(anonymous)::(anonymous)::main (cognitive 29) zheng-admin/src/plugins/select2/js/select2.full.js:318 — (anonymous)::(anonymous)::(anonymous)::main has cognitive complexity 29 (threshold 15). Drivers by points: if/else 11 (16 pts), boolean chains 7, ternaries 2 (4 pts), 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)::(anonymous)::fromElement (cognitive 29) zheng-admin/src/plugins/select2/js/select2.full.js:4948 — (anonymous)::(anonymous)::fromElement has cognitive complexity 29 (threshold 15). Drivers by points: if/else 18 (24 pts), boolean chains 4, 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.
  • (anonymous)::(anonymous)::handler (cognitive 28) zheng-admin/src/plugins/select2/js/select2.full.js:6247 — (anonymous)::(anonymous)::handler has cognitive complexity 28 (threshold 15). Drivers by points: if/else 16 (18 pts), boolean chains 6, ternaries 4 (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.
AC6 · Visual & motion safety · Animation without a prefers-reduced-motion guard · ×8
  • Animation without a prefers-reduced-motion guard zheng-message/zheng-message-client/bootstrap.css:2542 — `.collapse` moves (`transition: height 0.35s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard zheng-message/zheng-message-client/bootstrap.css:2645 — `.btn:hover` moves (`transition: background-position 0.1s linear`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard zheng-message/zheng-message-client/bootstrap.css:4198 — `.modal.fade` moves (`transition: opacity 0.3s linear, top 0.3s ease-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard zheng-message/zheng-message-client/bootstrap.css:4685 — `.progress .bar` moves (`transition: width 0.6s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard zheng-message/zheng-message-client/bootstrap.css:4707 — `.progress.active .bar` moves (`animation: progress-bar-stripes 2s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard zheng-message/zheng-message-client/bootstrap.css:4847 — `.carousel .item` moves (`transition: 0.6s ease-in-out left`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard zheng-admin/src/plugins/material-design-iconic-font-2.2.0/css/material-design-iconic-font.css:78 — `.zmdi-hc-spin` moves (`animation: zmdi-spin 1.5s infinite linear`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard zheng-admin/src/plugins/material-design-iconic-font-2.2.0/css/material-design-iconic-font.css:82 — `.zmdi-hc-spin-reverse` moves (`animation: zmdi-spin-reverse 1.5s infinite linear`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
D2 · Cognitive Complexity · jquery.fullPage.$.fn.fullpage · ×6
  • jquery.fullPage.$.fn.fullpage::touchMoveHandler (cognitive 44) zheng-admin/src/plugins/fullPage/jquery.fullPage.js:961 — jquery.fullPage.$.fn.fullpage::touchMoveHandler has cognitive complexity 44 (threshold 15). Drivers by points: if/else 13 (41 pts), boolean chains 3 (nesting depth added 28). 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: 5 other methods here (jquery.fullPage.$.fn.fullpage::init, jquery.fullPage.$.fn.fullpage::scrollHandler, jquery.fullPage.$.fn.fullpage::MouseWheelHandler, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 6 times rather than 6 independent problems. Splitting this body alone leaves the other 5 exactly as they are. Where these are variations on one operation, the change that clears all 6 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.
  • jquery.fullPage.$.fn.fullpage::scrollHandler (cognitive 27) zheng-admin/src/plugins/fullPage/jquery.fullPage.js:813 — jquery.fullPage.$.fn.fullpage::scrollHandler has cognitive complexity 27 (threshold 15). Drivers by points: if/else 8 (19 pts), boolean chains 6, loops 1 (2 pts) (nesting depth added 12). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function. This shape REPEATS in the file: 5 other methods here (jquery.fullPage.$.fn.fullpage::init, jquery.fullPage.$.fn.fullpage::touchMoveHandler, jquery.fullPage.$.fn.fullpage::MouseWheelHandler, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 6 times rather than 6 independent problems. Splitting this body alone leaves the other 5 exactly as they are. Where these are variations on one operation, the change that clears all 6 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.
  • jquery.fullPage.$.fn.fullpage::init (cognitive 25) zheng-admin/src/plugins/fullPage/jquery.fullPage.js:492 — jquery.fullPage.$.fn.fullpage::init has cognitive complexity 25 (threshold 15). Drivers by points: if/else 13 (20 pts), boolean chains 5 (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. This shape REPEATS in the file: 5 other methods here (jquery.fullPage.$.fn.fullpage::scrollHandler, jquery.fullPage.$.fn.fullpage::touchMoveHandler, jquery.fullPage.$.fn.fullpage::MouseWheelHandler, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 6 times rather than 6 independent problems. Splitting this body alone leaves the other 5 exactly as they are. Where these are variations on one operation, the change that clears all 6 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.
  • jquery.fullPage.$.fn.fullpage::MouseWheelHandler (cognitive 24) zheng-admin/src/plugins/fullPage/jquery.fullPage.js:1087 — jquery.fullPage.$.fn.fullpage::MouseWheelHandler has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (18 pts), boolean chains 3, ternaries 1 (3 pts) (nesting depth added 11). 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: 5 other methods here (jquery.fullPage.$.fn.fullpage::init, jquery.fullPage.$.fn.fullpage::scrollHandler, jquery.fullPage.$.fn.fullpage::touchMoveHandler, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 6 times rather than 6 independent problems. Splitting this body alone leaves the other 5 exactly as they are. Where these are variations on one operation, the change that clears all 6 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.
  • jquery.fullPage.$.fn.fullpage::landscapeScroll (cognitive 17) zheng-admin/src/plugins/fullPage/jquery.fullPage.js:1685 — jquery.fullPage.$.fn.fullpage::landscapeScroll has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 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. This shape REPEATS in the file: 5 other methods here (jquery.fullPage.$.fn.fullpage::init, jquery.fullPage.$.fn.fullpage::scrollHandler, jquery.fullPage.$.fn.fullpage::touchMoveHandler, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 6 times rather than 6 independent problems. Splitting this body alone leaves the other 5 exactly as they are. Where these are variations on one operation, the change that clears all 6 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.
  • jquery.fullPage.$.fn.fullpage::onkeydown (cognitive 16) zheng-admin/src/plugins/fullPage/jquery.fullPage.js:1539 — jquery.fullPage.$.fn.fullpage::onkeydown has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 1, match/switch 1 (nesting depth added 7). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident. This shape REPEATS in the file: 5 other methods here (jquery.fullPage.$.fn.fullpage::init, jquery.fullPage.$.fn.fullpage::scrollHandler, jquery.fullPage.$.fn.fullpage::touchMoveHandler, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 6 times rather than 6 independent problems. Splitting this body alone leaves the other 5 exactly as they are. Where these are variations on one operation, the change that clears all 6 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.
D30 · Dependency Vulnerabilities · Medium CVE · ×6
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Duplicated block (8 lines × 2) · ×5
  • Duplicated block (8 lines × 2) zheng-cms/zheng-cms-web/src/main/java/com/zheng/cms/web/interceptor/CmsWebInterceptor.java:31 — zheng-cms/zheng-cms-web/src/main/java/com/zheng/cms/web/interceptor/CmsWebInterceptor.java:31-38 | zheng-ucenter/zheng-ucenter-web/src/main/java/com/zheng/ucenter/web/interceptor/UcenterWebInterceptor.java:26-33 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (8 lines × 2) zheng-common/src/main/java/com/zheng/common/util/MybatisGeneratorUtil.java:140 — zheng-common/src/main/java/com/zheng/common/util/MybatisGeneratorUtil.java:140-147 | zheng-common/src/main/java/com/zheng/common/util/MybatisGeneratorUtil.java:150-157 — 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 `zheng-common/src/main/java/com/zheng/common/util/MybatisGeneratorUtil.java:140` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `zheng-common/src/main/java/com/zheng/common/util/MybatisGeneratorUtil.java:158` calls `put`, `toLowerCaseFirstOne` and `zheng-common/src/main/java/com/zheng/common/util/MybatisGeneratorUtil.java:148` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (8 lines × 2) zheng-message/zheng-message-server/src/main/java/com/zheng/message/server/NamespaceChatLauncher.java:15 — zheng-message/zheng-message-server/src/main/java/com/zheng/message/server/NamespaceChatLauncher.java:15-22 | zheng-message/zheng-message-server/src/main/java/com/zheng/message/server/NamespaceChatLauncher.java:24-31 — 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) zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsRole.java:105 — zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsRole.java:105-112 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsSystem.java:185-192 — before extracting anything, compare `zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsRole.java` and `zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsSystem.java` as WHOLE FILES: 84% 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 `zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsRole.java:105` 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 (8 lines × 2) zheng-upms/zheng-upms-server/src/main/java/com/zheng/upms/server/controller/manage/UpmsRoleController.java:116 — zheng-upms/zheng-upms-server/src/main/java/com/zheng/upms/server/controller/manage/UpmsRoleController.java:116-123 | zheng-upms/zheng-upms-server/src/main/java/com/zheng/upms/server/controller/manage/UpmsRoleController.java:154-161 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (5 lines × 2) · ×5
  • Duplicated block (5 lines × 2) zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsSystem.java:100 — zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsSystem.java:100-104 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsSystem.java:175-179 — 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) zheng-common/src/main/java/com/zheng/common/util/CaptchaUtil.java:163 — zheng-common/src/main/java/com/zheng/common/util/CaptchaUtil.java:163-167 | zheng-common/src/main/java/com/zheng/common/util/CaptchaUtil.java:184-188 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `zheng-common/src/main/java/com/zheng/common/util/CaptchaUtil.java:163` 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, `zheng-common/src/main/java/com/zheng/common/util/CaptchaUtil.java:161` calls `nextInt` and `zheng-common/src/main/java/com/zheng/common/util/CaptchaUtil.java:183` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (5 lines × 2) zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticle.java:357 — zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticle.java:357-361 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsPage.java:195-199 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticle.java:357` 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 (5 lines × 2) zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsCategory.java:227 — zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsCategory.java:227-231 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsTag.java:191-195 — before extracting anything, compare `zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsCategory.java` and `zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsTag.java` as WHOLE FILES: 90% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (5 lines × 2) zheng-pay/zheng-pay-dao/src/main/java/com/zheng/pay/dao/model/PayInOrder.java:111 — zheng-pay/zheng-pay-dao/src/main/java/com/zheng/pay/dao/model/PayInOrder.java:111-115 | zheng-pay/zheng-pay-dao/src/main/java/com/zheng/pay/dao/model/PayOutOrder.java:111-115 — 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 `zheng-pay/zheng-pay-dao/src/main/java/com/zheng/pay/dao/model/PayInOrder.java:111` 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.
AC3 · Page structure · Heading level jumps from h2 to h5 · ×4
  • Heading level jumps from h2 to h5 zheng-api/zheng-api-server/src/main/webapp/WEB-INF/jsp/403.jsp:18 — Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
  • Heading level jumps from h2 to h5 zheng-api/zheng-api-server/src/main/webapp/WEB-INF/jsp/error.jsp:18 — Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
  • Heading level jumps from h2 to h5 zheng-cms/zheng-cms-admin/src/main/webapp/WEB-INF/jsp/403.jsp:18 — Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
  • Heading level jumps from h2 to h5 zheng-cms/zheng-cms-admin/src/main/webapp/WEB-INF/jsp/error.jsp:18 — Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
D1 · Cyclomatic Complexity · jquery.fullPage.$.fn.fullpage · ×4
  • jquery.fullPage.$.fn.fullpage::onkeydown (cyclomatic 18) zheng-admin/src/plugins/fullPage/jquery.fullPage.js:1539 — jquery.fullPage.$.fn.fullpage::onkeydown 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: 3 other methods here (jquery.fullPage.$.fn.fullpage::init, jquery.fullPage.$.fn.fullpage::scrollHandler, jquery.fullPage.$.fn.fullpage::touchMoveHandler) 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.
  • jquery.fullPage.$.fn.fullpage::init (cyclomatic 17) zheng-admin/src/plugins/fullPage/jquery.fullPage.js:492 — jquery.fullPage.$.fn.fullpage::init 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 shape REPEATS in the file: 3 other methods here (jquery.fullPage.$.fn.fullpage::scrollHandler, jquery.fullPage.$.fn.fullpage::touchMoveHandler, jquery.fullPage.$.fn.fullpage::onkeydown) 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.
  • jquery.fullPage.$.fn.fullpage::scrollHandler (cyclomatic 16) zheng-admin/src/plugins/fullPage/jquery.fullPage.js:813 — jquery.fullPage.$.fn.fullpage::scrollHandler 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: 3 other methods here (jquery.fullPage.$.fn.fullpage::init, jquery.fullPage.$.fn.fullpage::touchMoveHandler, jquery.fullPage.$.fn.fullpage::onkeydown) 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.
  • jquery.fullPage.$.fn.fullpage::touchMoveHandler (cyclomatic 16) zheng-admin/src/plugins/fullPage/jquery.fullPage.js:961 — jquery.fullPage.$.fn.fullpage::touchMoveHandler 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: 3 other methods here (jquery.fullPage.$.fn.fullpage::init, jquery.fullPage.$.fn.fullpage::scrollHandler, jquery.fullPage.$.fn.fullpage::onkeydown) 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.
D4 · Code Duplication · Duplicated block (7 lines × 2) · ×4
  • Duplicated block (7 lines × 2) zheng-cms/zheng-cms-admin/src/main/java/com/zheng/cms/admin/controller/manage/CmsSettingController.java:83 — zheng-cms/zheng-cms-admin/src/main/java/com/zheng/cms/admin/controller/manage/CmsSettingController.java:83-89 | zheng-cms/zheng-cms-admin/src/main/java/com/zheng/cms/admin/controller/manage/CmsSettingController.java:117-123 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. 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) zheng-upms/zheng-upms-server/src/main/java/com/zheng/upms/server/controller/manage/UpmsOrganizationController.java:60 — zheng-upms/zheng-upms-server/src/main/java/com/zheng/upms/server/controller/manage/UpmsOrganizationController.java:60-66 | zheng-upms/zheng-upms-server/src/main/java/com/zheng/upms/server/controller/manage/UpmsPermissionController.java:81-87 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (7 lines × 2) zheng-upms/zheng-upms-server/src/main/java/com/zheng/upms/server/controller/manage/UpmsRoleController.java:89 — zheng-upms/zheng-upms-server/src/main/java/com/zheng/upms/server/controller/manage/UpmsRoleController.java:89-95 | zheng-upms/zheng-upms-server/src/main/java/com/zheng/upms/server/controller/manage/UpmsSystemController.java:60-66 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (7 lines × 2) zheng-upms/zheng-upms-server/src/main/java/com/zheng/upms/server/controller/manage/UpmsSystemController.java:87 — zheng-upms/zheng-upms-server/src/main/java/com/zheng/upms/server/controller/manage/UpmsSystemController.java:87-93 | zheng-upms/zheng-upms-server/src/main/java/com/zheng/upms/server/controller/manage/UpmsSystemController.java:125-131 — 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 `zheng-upms/zheng-upms-server/src/main/java/com/zheng/upms/server/controller/manage/UpmsSystemController.java:87` 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.
X3 · Exception handling · Swallowed exception (empty catch) · ×4
  • Swallowed exception (empty catch) zheng-admin/src/plugins/jquery.cookie.js:47 — 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) zheng-admin/src/plugins/malihu-custom-scrollbar-plugin/jquery.mCustomScrollbar.js:1528 — 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) zheng-admin/src/plugins/malihu-custom-scrollbar-plugin/jquery.mCustomScrollbar.js:1534 — 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) zheng-common/src/main/java/com/zheng/common/util/RedisUtil.java:97 — 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.
X3 · Exception handling · Swallowed exception (caught, then discarded) · ×4
  • Swallowed exception (caught, then discarded) zheng-common/src/main/java/com/zheng/common/util/StringUtil.java:112 — `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) zheng-common/src/main/java/com/zheng/common/util/StringUtil.java:132 — `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) zheng-common/src/main/java/com/zheng/common/util/StringUtil.java:152 — `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) REDACTED:41 — `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.
D10 · Test Quality · No assertions · ×3
  • No assertions: index zheng-upms/zheng-upms-rpc-service/src/test/java/com/zheng/upms/rpc/service/UpmsServiceTest.java:43 — This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: selectForPage zheng-upms/zheng-upms-rpc-service/src/test/java/com/zheng/upms/rpc/service/UpmsServiceTest.java:60 — This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: index zheng-upms/zheng-upms-server/src/test/java/com/zheng/upms/server/UpmsServiceTest.java:28 — This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D3 · God Classes · FunctionTooLong · ×3
  • FunctionTooLong: jquery.fullPage.$.fn.fullpage zheng-admin/src/plugins/fullPage/jquery.fullPage.js:91 — FunctionTooLong — $.fn.fullpage runs 1173 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 1073 over it, 11.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: jquery.mCustomScrollbar._contentDraggable zheng-admin/src/plugins/malihu-custom-scrollbar-plugin/jquery.mCustomScrollbar.js:1250 — FunctionTooLong — _contentDraggable runs 117 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 17 over it, 1.17× 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: jquery.mCustomScrollbar._scrollTo zheng-admin/src/plugins/malihu-custom-scrollbar-plugin/jquery.mCustomScrollbar.js:2036 — FunctionTooLong — _scrollTo runs 115 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 15 over it, 1.15× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
D4 · Code Duplication · Duplicated block (6 lines × 6) · ×3
  • Duplicated block (6 lines × 6) zheng-cms/zheng-cms-admin/src/main/java/com/zheng/cms/admin/controller/manage/CmsArticleController.java:94 — zheng-cms/zheng-cms-admin/src/main/java/com/zheng/cms/admin/controller/manage/CmsArticleController.java:94-99 | zheng-cms/zheng-cms-admin/src/main/java/com/zheng/cms/admin/controller/manage/CmsCategoryController.java:84-89 | zheng-cms/zheng-cms-admin/src/main/java/com/zheng/cms/admin/controller/manage/CmsMenuController.java:84-89 | zheng-cms/zheng-cms-admin/src/main/java/com/zheng/cms/admin/controller/manage/CmsPageController.java:84-89 | zheng-cms/zheng-cms-admin/src/main/java/com/zheng/cms/admin/controller/manage/CmsTagController.java:84-89 | zheng-cms/zheng-cms-admin/src/main/java/com/zheng/cms/admin/controller/manage/CmsTopicController.java:84-89 — 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 6 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `zheng-cms/zheng-cms-admin/src/main/java/com/zheng/cms/admin/controller/manage/CmsArticleController.java:94` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `zheng-cms/zheng-cms-admin/src/main/java/com/zheng/cms/admin/controller/manage/CmsArticleController.java:102` calls `setReadnumber` and `zheng-cms/zheng-cms-admin/src/main/java/com/zheng/cms/admin/controller/manage/CmsCategoryController.java:92` 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 × 6) zheng-upms/zheng-upms-rpc-service/src/main/java/com/zheng/upms/rpc/service/impl/UpmsPermissionServiceImpl.java:80 — zheng-upms/zheng-upms-rpc-service/src/main/java/com/zheng/upms/rpc/service/impl/UpmsPermissionServiceImpl.java:80-85 | zheng-upms/zheng-upms-rpc-service/src/main/java/com/zheng/upms/rpc/service/impl/UpmsPermissionServiceImpl.java:97-102 | zheng-upms/zheng-upms-rpc-service/src/main/java/com/zheng/upms/rpc/service/impl/UpmsPermissionServiceImpl.java:114-119 | zheng-upms/zheng-upms-rpc-service/src/main/java/com/zheng/upms/rpc/service/impl/UpmsPermissionServiceImpl.java:187-192 | zheng-upms/zheng-upms-rpc-service/src/main/java/com/zheng/upms/rpc/service/impl/UpmsPermissionServiceImpl.java:204-209 | zheng-upms/zheng-upms-rpc-service/src/main/java/com/zheng/upms/rpc/service/impl/UpmsPermissionServiceImpl.java:221-226 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `zheng-upms/zheng-upms-rpc-service/src/main/java/com/zheng/upms/rpc/service/impl/UpmsPermissionServiceImpl.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 (6 lines × 6) zheng-upms/zheng-upms-server/src/main/java/com/zheng/upms/server/controller/manage/UpmsOrganizationController.java:88 — zheng-upms/zheng-upms-server/src/main/java/com/zheng/upms/server/controller/manage/UpmsOrganizationController.java:88-93 | zheng-upms/zheng-upms-server/src/main/java/com/zheng/upms/server/controller/manage/UpmsOrganizationController.java:124-129 | zheng-upms/zheng-upms-server/src/main/java/com/zheng/upms/server/controller/manage/UpmsPermissionController.java:130-135 | zheng-upms/zheng-upms-server/src/main/java/com/zheng/upms/server/controller/manage/UpmsPermissionController.java:172-177 | zheng-upms/zheng-upms-server/src/main/java/com/zheng/upms/server/controller/manage/UpmsSystemController.java:89-94 | zheng-upms/zheng-upms-server/src/main/java/com/zheng/upms/server/controller/manage/UpmsSystemController.java:127-132 — there are 6 copies across 3 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 6 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `zheng-upms/zheng-upms-server/src/main/java/com/zheng/upms/server/controller/manage/UpmsOrganizationController.java:88` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `zheng-upms/zheng-upms-server/src/main/java/com/zheng/upms/server/controller/manage/UpmsPermissionController.java:138` calls `setOrders` and `zheng-upms/zheng-upms-server/src/main/java/com/zheng/upms/server/controller/manage/UpmsOrganizationController.java:96` 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.
R7 · Dead Code · Dead file (~14 LoC) · ×3
  • Dead file (~14 LoC) zheng-admin/src/plugins/My97DatePicker/lang/en.js — no import path from any entry point (4 application, 0 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
  • Dead file (~14 LoC) zheng-admin/src/plugins/My97DatePicker/lang/zh-cn.js — no import path from any entry point (4 application, 0 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
  • Dead file (~14 LoC) zheng-admin/src/plugins/My97DatePicker/lang/zh-tw.js — no import path from any entry point (4 application, 0 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
AC3 · Page structure · Data table has no header cells · ×2
  • Data table has no header cells zheng-cms/zheng-cms-admin/src/main/webapp/WEB-INF/jsp/manage/comment/create.jsp:20 — 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 zheng-cms/zheng-cms-admin/src/main/webapp/WEB-INF/jsp/manage/comment/update.jsp:20 — 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).
D10 · Test Quality · Test project verifies nothing · ×2
  • Test project verifies nothing: zheng-upms-rpc-service zheng-upms/zheng-upms-rpc-service/src/test/java/com/zheng/upms/rpc/service/UpmsServiceTest.java:43 — No conventional assertion call was detected in 2 of 2 tests in `zheng-upms-rpc-service` — the project as a whole, not one method. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a suite that genuinely checks nothing. If it is the latter, this project passes unconditionally and cannot fail.
  • Test project verifies nothing: zheng-upms-server zheng-upms/zheng-upms-server/src/test/java/com/zheng/upms/server/UpmsServiceTest.java:28 — No conventional assertion call was detected in 1 of 1 tests in `zheng-upms-server` — the project as a whole, not one method. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a suite that genuinely checks nothing. If it is the latter, this project passes unconditionally and cannot fail.
D2 · Cognitive Complexity · jquery.mCustomScrollbar._contentDraggable · ×2
  • jquery.mCustomScrollbar._contentDraggable::_onTouchmove (cognitive 27) zheng-admin/src/plugins/malihu-custom-scrollbar-plugin/jquery.mCustomScrollbar.js:1301 — jquery.mCustomScrollbar._contentDraggable::_onTouchmove has cognitive complexity 27 (threshold 15). Drivers by points: if/else 12 (20 pts), boolean chains 7 (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: one other method here (jquery.mCustomScrollbar._contentDraggable::_m) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
  • jquery.mCustomScrollbar._contentDraggable::_m (cognitive 19) zheng-admin/src/plugins/malihu-custom-scrollbar-plugin/jquery.mCustomScrollbar.js:1372 — jquery.mCustomScrollbar._contentDraggable::_m has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 6 (15 pts), if/else 4 (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: one other method here (jquery.mCustomScrollbar._contentDraggable::_onTouchmove) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Duplicated block (14 lines × 2) · ×2
  • Duplicated block (14 lines × 2) zheng-api/zheng-api-server/src/main/java/com/zheng/api/server/jms/DefaultMessageQueueListener.java:26 — zheng-api/zheng-api-server/src/main/java/com/zheng/api/server/jms/DefaultMessageQueueListener.java:26-39 | zheng-cms/zheng-cms-admin/src/main/java/com/zheng/cms/admin/jms/DefaultMessageQueueListener.java:26-39 — before extracting anything, compare `zheng-api/zheng-api-server/src/main/java/com/zheng/api/server/jms/DefaultMessageQueueListener.java` and `zheng-cms/zheng-cms-admin/src/main/java/com/zheng/cms/admin/jms/DefaultMessageQueueListener.java` as WHOLE FILES: 82% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (14 lines × 2) zheng-common/src/main/java/com/zheng/common/base/BaseServiceImpl.java:230 — zheng-common/src/main/java/com/zheng/common/base/BaseServiceImpl.java:230-243 | zheng-common/src/main/java/com/zheng/common/base/BaseServiceImpl.java:250-263 — 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 `zheng-common/src/main/java/com/zheng/common/base/BaseServiceImpl.java:230` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (11 lines × 2) · ×2
  • Duplicated block (11 lines × 2) zheng-cms/zheng-cms-admin/src/main/java/com/zheng/cms/admin/controller/manage/CmsMenuController.java:135 — zheng-cms/zheng-cms-admin/src/main/java/com/zheng/cms/admin/controller/manage/CmsMenuController.java:135-145 | zheng-cms/zheng-cms-admin/src/main/java/com/zheng/cms/admin/controller/manage/CmsMenuController.java:165-175 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (11 lines × 2) zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsCategory.java:182 — zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsCategory.java:182-192 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsTag.java:150-160 — before extracting anything, compare `zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsCategory.java` and `zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsTag.java` as WHOLE FILES: 90% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. 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 `zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsCategory.java:182` 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.
D4 · Code Duplication · Duplicated block (7 lines × 6) · ×2
  • Duplicated block (7 lines × 6) zheng-cms/zheng-cms-admin/src/main/java/com/zheng/cms/admin/controller/manage/CmsArticleController.java:92 — zheng-cms/zheng-cms-admin/src/main/java/com/zheng/cms/admin/controller/manage/CmsArticleController.java:92-98 | zheng-cms/zheng-cms-admin/src/main/java/com/zheng/cms/admin/controller/manage/CmsArticleController.java:134-140 | zheng-cms/zheng-cms-admin/src/main/java/com/zheng/cms/admin/controller/manage/CmsPageController.java:82-88 | zheng-cms/zheng-cms-admin/src/main/java/com/zheng/cms/admin/controller/manage/CmsPageController.java:119-125 | zheng-cms/zheng-cms-admin/src/main/java/com/zheng/cms/admin/controller/manage/CmsTopicController.java:82-88 | zheng-cms/zheng-cms-admin/src/main/java/com/zheng/cms/admin/controller/manage/CmsTopicController.java:118-124 — there are 6 copies across 3 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 6 sites; resolving a subset leaves the remainder to drift apart. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `zheng-cms/zheng-cms-admin/src/main/java/com/zheng/cms/admin/controller/manage/CmsPageController.java:91` calls `setOrders` and `zheng-cms/zheng-cms-admin/src/main/java/com/zheng/cms/admin/controller/manage/CmsTopicController.java:91` 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 × 6) zheng-cms/zheng-cms-admin/src/main/java/com/zheng/cms/admin/controller/manage/CmsCategoryController.java:82 — zheng-cms/zheng-cms-admin/src/main/java/com/zheng/cms/admin/controller/manage/CmsCategoryController.java:82-88 | zheng-cms/zheng-cms-admin/src/main/java/com/zheng/cms/admin/controller/manage/CmsCategoryController.java:119-125 | zheng-cms/zheng-cms-admin/src/main/java/com/zheng/cms/admin/controller/manage/CmsMenuController.java:82-88 | zheng-cms/zheng-cms-admin/src/main/java/com/zheng/cms/admin/controller/manage/CmsMenuController.java:118-124 | zheng-cms/zheng-cms-admin/src/main/java/com/zheng/cms/admin/controller/manage/CmsTagController.java:82-88 | zheng-cms/zheng-cms-admin/src/main/java/com/zheng/cms/admin/controller/manage/CmsTagController.java:119-125 — there are 6 copies across 3 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 6 sites; resolving a subset leaves the remainder to drift apart. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `zheng-cms/zheng-cms-admin/src/main/java/com/zheng/cms/admin/controller/manage/CmsCategoryController.java:90` calls `setCtime` and `zheng-cms/zheng-cms-admin/src/main/java/com/zheng/cms/admin/controller/manage/CmsMenuController.java:90` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
IC1 · Incompleteness & stubs · Empty method body · ×2
  • Empty method body — does nothing with its inputs zheng-pay/zheng-pay-sdk/src/main/java/com/zheng/pay/sdk/App.java:7 — `main` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
  • Empty method body — does nothing with its inputs zheng-wechat/zheng-wechat-mp/zheng-wechat-mp-service/src/main/java/com/zheng/wechat/mp/service/App.java:7 — `main` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
R2 · Cyclomatic Complexity · Complex function apply (cyclomatic 40, cognitive 74) · ×2
  • Complex function apply (cyclomatic 40, cognitive 74) zheng-admin/src/plugins/select2/js/select2.full.js:4582 — apply has cyclomatic complexity 40 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 apply (cyclomatic 40, cognitive 74) zheng-admin/src/plugins/select2/js/select2.js:4582 — apply has cyclomatic complexity 40 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.
R2 · Cyclomatic Complexity · Complex function normalize (cyclomatic 32, cognitive 63) · ×2
  • Complex function normalize (cyclomatic 32, cognitive 63) zheng-admin/src/plugins/select2/js/select2.full.js:79 — normalize has cyclomatic complexity 32 and cognitive complexity 63; 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 normalize (cyclomatic 32, cognitive 63) zheng-admin/src/plugins/select2/js/select2.js:79 — normalize has cyclomatic complexity 32 and cognitive complexity 63; 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 fromElement (cyclomatic 23, cognitive 29) · ×2
  • Complex function fromElement (cyclomatic 23, cognitive 29) zheng-admin/src/plugins/select2/js/select2.full.js:4948 — fromElement has cyclomatic complexity 23 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 fromElement (cyclomatic 23, cognitive 29) zheng-admin/src/plugins/select2/js/select2.js:4948 — fromElement has cyclomatic complexity 23 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.
R2 · Cyclomatic Complexity · Complex function main (cyclomatic 22, cognitive 29) · ×2
  • Complex function main (cyclomatic 22, cognitive 29) zheng-admin/src/plugins/select2/js/select2.full.js:318 — main has cyclomatic complexity 22 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 main (cyclomatic 22, cognitive 29) zheng-admin/src/plugins/select2/js/select2.js:318 — main has cyclomatic complexity 22 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.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 15, cognitive 15) · ×2
  • Complex function (anonymous) (cyclomatic 15, cognitive 15) zheng-admin/src/plugins/select2/js/select2.full.js:5364 — (anonymous) has cyclomatic complexity 15 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 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 15, cognitive 15) zheng-admin/src/plugins/select2/js/select2.js:5364 — (anonymous) has cyclomatic complexity 15 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 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 _positionDropdown (cyclomatic 14, cognitive 11) · ×2
  • Complex function _positionDropdown (cyclomatic 14, cognitive 11) zheng-admin/src/plugins/select2/js/select2.full.js:4253 — _positionDropdown has cyclomatic complexity 14 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 _positionDropdown (cyclomatic 14, cognitive 11) zheng-admin/src/plugins/select2/js/select2.js:4253 — _positionDropdown has cyclomatic complexity 14 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.
R2 · Cyclomatic Complexity · Complex function _syncSubtree (cyclomatic 13, cognitive 13) · ×2
  • Complex function _syncSubtree (cyclomatic 13, cognitive 13) zheng-admin/src/plugins/select2/js/select2.full.js:5415 — _syncSubtree has cyclomatic complexity 13 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 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 _syncSubtree (cyclomatic 13, cognitive 13) zheng-admin/src/plugins/select2/js/select2.js:5415 — _syncSubtree has cyclomatic complexity 13 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 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.
AC6 · Visual & motion safety · Low contrast colour pair in CSS (2.8 · ×1
  • Low contrast colour pair in CSS (2.8:1) zheng-message/zheng-message-client/bootstrap.css:3435 — `.nav-tabs .open .dropdown-toggle, .nav-pills .open .dropdown-toggle, .nav > li.dropdown.open.active > a:hover` sets color: #ffffff on background-color: #999999 — 2.8:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
AC6 · Visual & motion safety · Low contrast colour pair in CSS (2.3 · ×1
  • Low contrast colour pair in CSS (2.3:1) zheng-admin/src/plugins/zTree_v3/css/metroStyle/metroStyle.css:21 — `.ztree li a.tmpTargetNode_inner` sets color: white on background-color: #aaa — 2.3:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
AC6 · Visual & motion safety · Low contrast colour pair in CSS (2.2 · ×1
  • Low contrast colour pair in CSS (2.2:1) zheng-admin/src/plugins/zTree_v3/css/awesomeStyle/awesome.css:80 — `.ztree li a.tmpTargetNode_inner` sets color: #ffff00 on background-color: #aaa — 2.2:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
AC6 · Visual & motion safety · Low contrast colour pair in CSS (2.9 · ×1
  • Low contrast colour pair in CSS (2.9:1) zheng-admin/src/plugins/select2/css/select2.css:290 — `.select2-container--default .select2-results__option--highlighted[aria-selected]` sets color: white on background-color: #5897fb — 2.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
AC6 · Visual & motion safety · Low contrast colour pair in CSS (1.9 · ×1
  • Low contrast colour pair in CSS (1.9:1) zheng-admin/src/plugins/bootstrap-3.3.0/css/bootstrap.css:3057 — `.btn-warning .badge` sets color: #f0ad4e on background-color: #fff — 1.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
AC7 · A11y enforcement · Accessibility enforcement below the top rung · ×1
  • Accessibility enforcement below the top rung — No accessibility enforcement found — no accessibility linting at author time and no automated accessibility check in tests or CI. Add your UI toolkit's own accessibility assertion to the test suite (Flutter `meetsGuideline`, Espresso `AccessibilityChecks`, XCTest `performAccessibilityAudit`), then gate that test in the pipeline. What was searched, so you can tell an absence from a miss: the 152 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.
D1 · Cyclomatic Complexity · jquery.mCustomScrollbar._scrollTo (cyclomatic 66) · ×1
  • jquery.mCustomScrollbar._scrollTo (cyclomatic 66) zheng-admin/src/plugins/malihu-custom-scrollbar-plugin/jquery.mCustomScrollbar.js:2036 — jquery.mCustomScrollbar._scrollTo has cyclomatic complexity 66 (threshold 15). Of this number, 44 points are the body's own statements and 22 belong to 6 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This file is where this pass's cyclomatic complexity CONCENTRATES: zheng-admin/src/plugins/malihu-custom-scrollbar-plugin/jquery.mCustomScrollbar.js holds 13 of the 38 methods over the threshold — including the worst — and 174 of the 370 points over it (47%), 2.5× the next-largest file (zheng-admin/src/plugins/select2/js/select2.full.js at 69). 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.
D1 · Cyclomatic Complexity · jquery.mCustomScrollbar._keyboard · ×1
  • jquery.mCustomScrollbar._keyboard::_onKeyboard (cyclomatic 43) zheng-admin/src/plugins/malihu-custom-scrollbar-plugin/jquery.mCustomScrollbar.js:1727 — jquery.mCustomScrollbar._keyboard::_onKeyboard has cyclomatic complexity 43 (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: zheng-admin/src/plugins/malihu-custom-scrollbar-plugin/jquery.mCustomScrollbar.js holds 13 of the 38 methods over the threshold — including the worst — and 174 of the 370 points over it (47%), 2.5× the next-largest file (zheng-admin/src/plugins/select2/js/select2.full.js at 69). 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.
D1 · Cyclomatic Complexity · jquery.mCustomScrollbar._tweenTo (cyclomatic 32) · ×1
  • jquery.mCustomScrollbar._tweenTo (cyclomatic 32) zheng-admin/src/plugins/malihu-custom-scrollbar-plugin/jquery.mCustomScrollbar.js:2206 — jquery.mCustomScrollbar._tweenTo has cyclomatic complexity 32 (threshold 15). Most of this is not in the body itself: 8 of the 32 points are its own statements and the rest belongs to 5 function items inside it that branch (_ease, _step, _cancelTween, …). 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: zheng-admin/src/plugins/malihu-custom-scrollbar-plugin/jquery.mCustomScrollbar.js holds 13 of the 38 methods over the threshold — including the worst — and 174 of the 370 points over it (47%), 2.5× the next-largest file (zheng-admin/src/plugins/select2/js/select2.full.js at 69). 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.
D1 · Cyclomatic Complexity · jquery.mCustomScrollbar._to (cyclomatic 31) · ×1
  • jquery.mCustomScrollbar._to (cyclomatic 31) zheng-admin/src/plugins/malihu-custom-scrollbar-plugin/jquery.mCustomScrollbar.js:1870 — jquery.mCustomScrollbar._to 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 file is where this pass's cyclomatic complexity CONCENTRATES: zheng-admin/src/plugins/malihu-custom-scrollbar-plugin/jquery.mCustomScrollbar.js holds 13 of the 38 methods over the threshold — including the worst — and 174 of the 370 points over it (47%), 2.5× the next-largest file (zheng-admin/src/plugins/select2/js/select2.full.js at 69). 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.
D1 · Cyclomatic Complexity · jquery.mCustomScrollbar._mousewheel · ×1
  • jquery.mCustomScrollbar._mousewheel::_onMousewheel (cyclomatic 30) zheng-admin/src/plugins/malihu-custom-scrollbar-plugin/jquery.mCustomScrollbar.js:1473 — jquery.mCustomScrollbar._mousewheel::_onMousewheel 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. This file is where this pass's cyclomatic complexity CONCENTRATES: zheng-admin/src/plugins/malihu-custom-scrollbar-plugin/jquery.mCustomScrollbar.js holds 13 of the 38 methods over the threshold — including the worst — and 174 of the 370 points over it (47%), 2.5× the next-largest file (zheng-admin/src/plugins/select2/js/select2.full.js at 69). 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.
D1 · Cyclomatic Complexity · Paginator.getHtml (cyclomatic 29) · ×1
  • Paginator.getHtml (cyclomatic 29) zheng-common/src/main/java/com/zheng/common/util/Paginator.java:129 — Paginator.getHtml has cyclomatic complexity 29 (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.
D1 · Cyclomatic Complexity · jquery.mCustomScrollbar._selectable (cyclomatic 27) · ×1
  • jquery.mCustomScrollbar._selectable (cyclomatic 27) zheng-admin/src/plugins/malihu-custom-scrollbar-plugin/jquery.mCustomScrollbar.js:1396 — jquery.mCustomScrollbar._selectable 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 5 function items inside it that branch (a function literal at line 1405, _sel, _seq, …). 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: zheng-admin/src/plugins/malihu-custom-scrollbar-plugin/jquery.mCustomScrollbar.js holds 13 of the 38 methods over the threshold — including the worst — and 174 of the 370 points over it (47%), 2.5× the next-largest file (zheng-admin/src/plugins/select2/js/select2.full.js at 69). 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.
D1 · Cyclomatic Complexity · UpmsPermissionServiceImpl.getTreeByRoleId (cyclomatic 25) · ×1
  • UpmsPermissionServiceImpl.getTreeByRoleId (cyclomatic 25) zheng-upms/zheng-upms-rpc-service/src/main/java/com/zheng/upms/rpc/service/impl/UpmsPermissionServiceImpl.java:45 — UpmsPermissionServiceImpl.getTreeByRoleId has cyclomatic complexity 25 (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: one other method here (UpmsPermissionServiceImpl.getTreeByUserId) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · UpmsPermissionServiceImpl.getTreeByUserId (cyclomatic 25) · ×1
  • UpmsPermissionServiceImpl.getTreeByUserId (cyclomatic 25) zheng-upms/zheng-upms-rpc-service/src/main/java/com/zheng/upms/rpc/service/impl/UpmsPermissionServiceImpl.java:148 — UpmsPermissionServiceImpl.getTreeByUserId has cyclomatic complexity 25 (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: one other method here (UpmsPermissionServiceImpl.getTreeByRoleId) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · jquery.mCustomScrollbar._contentDraggable · ×1
  • jquery.mCustomScrollbar._contentDraggable::_onTouchmove (cyclomatic 24) zheng-admin/src/plugins/malihu-custom-scrollbar-plugin/jquery.mCustomScrollbar.js:1301 — jquery.mCustomScrollbar._contentDraggable::_onTouchmove 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. This file is where this pass's cyclomatic complexity CONCENTRATES: zheng-admin/src/plugins/malihu-custom-scrollbar-plugin/jquery.mCustomScrollbar.js holds 13 of the 38 methods over the threshold — including the worst — and 174 of the 370 points over it (47%), 2.5× the next-largest file (zheng-admin/src/plugins/select2/js/select2.full.js at 69). 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.
D1 · Cyclomatic Complexity · CmsArticle.equals (cyclomatic 23) · ×1
  • CmsArticle.equals (cyclomatic 23) zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticle.java:307 — CmsArticle.equals has cyclomatic complexity 23 (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.
D1 · Cyclomatic Complexity · bootstrap.Tooltip.show (cyclomatic 23) · ×1
  • bootstrap.Tooltip.show (cyclomatic 23) zheng-admin/src/plugins/bootstrap-3.3.0/js/bootstrap.js:1334 — bootstrap.Tooltip.show has cyclomatic complexity 23 (threshold 15). Of this number, 22 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.
D1 · Cyclomatic Complexity · jquery.mCustomScrollbar._sequentialScroll · ×1
  • jquery.mCustomScrollbar._sequentialScroll::_on (cyclomatic 22) zheng-admin/src/plugins/malihu-custom-scrollbar-plugin/jquery.mCustomScrollbar.js:1815 — jquery.mCustomScrollbar._sequentialScroll::_on 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 shape REPEATS in the file: one other method here (jquery.mCustomScrollbar._sequentialScroll) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared. This file is where this pass's cyclomatic complexity CONCENTRATES: zheng-admin/src/plugins/malihu-custom-scrollbar-plugin/jquery.mCustomScrollbar.js holds 13 of the 38 methods over the threshold — including the worst — and 174 of the 370 points over it (47%), 2.5× the next-largest file (zheng-admin/src/plugins/select2/js/select2.full.js at 69). 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.
D1 · Cyclomatic Complexity · jquery.mCustomScrollbar._coordinates (cyclomatic 20) · ×1
  • jquery.mCustomScrollbar._coordinates (cyclomatic 20) zheng-admin/src/plugins/malihu-custom-scrollbar-plugin/jquery.mCustomScrollbar.js:1161 — jquery.mCustomScrollbar._coordinates has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions. This file is where this pass's cyclomatic complexity CONCENTRATES: zheng-admin/src/plugins/malihu-custom-scrollbar-plugin/jquery.mCustomScrollbar.js holds 13 of the 38 methods over the threshold — including the worst — and 174 of the 370 points over it (47%), 2.5× the next-largest file (zheng-admin/src/plugins/select2/js/select2.full.js at 69). 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.
D1 · Cyclomatic Complexity · UpmsLog.equals (cyclomatic 19) · ×1
  • UpmsLog.equals (cyclomatic 19) zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsLog.java:233 — UpmsLog.equals has cyclomatic complexity 19 (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.
D1 · Cyclomatic Complexity · CmsArticle.hashCode (cyclomatic 19) · ×1
  • CmsArticle.hashCode (cyclomatic 19) zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticle.java:339 — CmsArticle.hashCode has cyclomatic complexity 19 (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.
D1 · Cyclomatic Complexity · jquery.mCustomScrollbar._buttons (cyclomatic 19) · ×1
  • jquery.mCustomScrollbar._buttons (cyclomatic 19) zheng-admin/src/plugins/malihu-custom-scrollbar-plugin/jquery.mCustomScrollbar.js:1659 — jquery.mCustomScrollbar._buttons 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 one function literal inside it that branches (line 1666). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest. This file is where this pass's cyclomatic complexity CONCENTRATES: zheng-admin/src/plugins/malihu-custom-scrollbar-plugin/jquery.mCustomScrollbar.js holds 13 of the 38 methods over the threshold — including the worst — and 174 of the 370 points over it (47%), 2.5× the next-largest file (zheng-admin/src/plugins/select2/js/select2.full.js at 69). 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.
D1 · Cyclomatic Complexity · jquery.mCustomScrollbar._sequentialScroll (cyclomatic 19) · ×1
  • jquery.mCustomScrollbar._sequentialScroll (cyclomatic 19) zheng-admin/src/plugins/malihu-custom-scrollbar-plugin/jquery.mCustomScrollbar.js:1790 — jquery.mCustomScrollbar._sequentialScroll 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: one other method here (jquery.mCustomScrollbar._sequentialScroll::_on) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared. This file is where this pass's cyclomatic complexity CONCENTRATES: zheng-admin/src/plugins/malihu-custom-scrollbar-plugin/jquery.mCustomScrollbar.js holds 13 of the 38 methods over the threshold — including the worst — and 174 of the 370 points over it (47%), 2.5× the next-largest file (zheng-admin/src/plugins/select2/js/select2.full.js at 69). 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.
D1 · Cyclomatic Complexity · jquery.mCustomScrollbar._pluginMarkup (cyclomatic 18) · ×1
  • jquery.mCustomScrollbar._pluginMarkup (cyclomatic 18) zheng-admin/src/plugins/malihu-custom-scrollbar-plugin/jquery.mCustomScrollbar.js:862 — jquery.mCustomScrollbar._pluginMarkup 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. This file is where this pass's cyclomatic complexity CONCENTRATES: zheng-admin/src/plugins/malihu-custom-scrollbar-plugin/jquery.mCustomScrollbar.js holds 13 of the 38 methods over the threshold — including the worst — and 174 of the 370 points over it (47%), 2.5× the next-largest file (zheng-admin/src/plugins/select2/js/select2.full.js at 69). 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.
D1 · Cyclomatic Complexity · jquery.mCustomScrollbar._draggable (cyclomatic 18) · ×1
  • jquery.mCustomScrollbar._draggable (cyclomatic 18) zheng-admin/src/plugins/malihu-custom-scrollbar-plugin/jquery.mCustomScrollbar.js:1184 — jquery.mCustomScrollbar._draggable has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 5 of the 18 points are its own statements and the rest belongs to 4 function items inside it that branch (a function literal at line 1195, a function literal at line 1217, a function literal at line 1223, …). 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: zheng-admin/src/plugins/malihu-custom-scrollbar-plugin/jquery.mCustomScrollbar.js holds 13 of the 38 methods over the threshold — including the worst — and 174 of the 370 points over it (47%), 2.5× the next-largest file (zheng-admin/src/plugins/select2/js/select2.full.js at 69). 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.
D1 · Cyclomatic Complexity · UpmsPermission.equals (cyclomatic 16) · ×1
  • UpmsPermission.equals (cyclomatic 16) zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsPermission.java:195 — UpmsPermission.equals has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · UpmsSystem.equals (cyclomatic 16) · ×1
  • UpmsSystem.equals (cyclomatic 16) zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsSystem.java:195 — UpmsSystem.equals has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · UpmsUser.equals (cyclomatic 16) · ×1
  • UpmsUser.equals (cyclomatic 16) zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsUser.java:195 — UpmsUser.equals has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · CmsCategory.equals (cyclomatic 16) · ×1
  • CmsCategory.equals (cyclomatic 16) zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsCategory.java:195 — CmsCategory.equals has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · bootstrap.Modal.backdrop (cyclomatic 16) · ×1
  • bootstrap.Modal.backdrop (cyclomatic 16) zheng-admin/src/plugins/bootstrap-3.3.0/js/bootstrap.js:1064 — bootstrap.Modal.backdrop has cyclomatic complexity 16 (threshold 15). Of this number, 13 points are the body's own statements and 3 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D17 · Explicit Debt · TodoComment · ×1
  • TodoComment zheng-upms/zheng-upms-client/src/main/java/com/zheng/upms/client/shiro/session/UpmsSessionDao.java:67 — // 更新ZHENG_UPMS_SERVER_SESSION_ID、ZHENG_UPMS_SERVER_CODE过期时间 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.
D2 · Cognitive Complexity · UpmsPermissionServiceImpl.getTreeByRoleId (cognitive 107) · ×1
  • UpmsPermissionServiceImpl.getTreeByRoleId (cognitive 107) zheng-upms/zheng-upms-rpc-service/src/main/java/com/zheng/upms/rpc/service/impl/UpmsPermissionServiceImpl.java:45 — UpmsPermissionServiceImpl.getTreeByRoleId has cognitive complexity 107 (threshold 15). Drivers by points: if/else 11 (58 pts), loops 10 (46 pts), boolean chains 3 (nesting depth added 83). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (UpmsPermissionServiceImpl.getTreeByUserId) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · UpmsPermissionServiceImpl.getTreeByUserId (cognitive 107) · ×1
  • UpmsPermissionServiceImpl.getTreeByUserId (cognitive 107) zheng-upms/zheng-upms-rpc-service/src/main/java/com/zheng/upms/rpc/service/impl/UpmsPermissionServiceImpl.java:148 — UpmsPermissionServiceImpl.getTreeByUserId has cognitive complexity 107 (threshold 15). Drivers by points: if/else 11 (58 pts), loops 10 (46 pts), boolean chains 3 (nesting depth added 83). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (UpmsPermissionServiceImpl.getTreeByRoleId) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · Paginator.getHtml (cognitive 85) · ×1
  • Paginator.getHtml (cognitive 85) zheng-common/src/main/java/com/zheng/common/util/Paginator.java:129 — Paginator.getHtml has cognitive complexity 85 (threshold 15). Drivers by points: if/else 39 (75 pts), loops 4 (10 pts) (nesting depth added 42). 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.
D2 · Cognitive Complexity · jquery.mCustomScrollbar._keyboard · ×1
  • jquery.mCustomScrollbar._keyboard::_onKeyboard (cognitive 81) zheng-admin/src/plugins/malihu-custom-scrollbar-plugin/jquery.mCustomScrollbar.js:1727 — jquery.mCustomScrollbar._keyboard::_onKeyboard has cognitive complexity 81 (threshold 15). Drivers by points: if/else 16 (43 pts), boolean chains 19, ternaries 4 (18 pts), match/switch 1 (nesting depth added 41). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · jquery.mCustomScrollbar._scrollTo (cognitive 75) · ×1
  • jquery.mCustomScrollbar._scrollTo (cognitive 75) zheng-admin/src/plugins/malihu-custom-scrollbar-plugin/jquery.mCustomScrollbar.js:2036 — jquery.mCustomScrollbar._scrollTo has cognitive complexity 75 (threshold 15). Drivers by points: if/else 23 (31 pts), boolean chains 23, ternaries 11 (20 pts), match/switch 1 (nesting depth added 17). Of this number, 57 points are the body's own statements and 18 belong to 6 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.
D2 · Cognitive Complexity · jquery.mCustomScrollbar._to (cognitive 47) · ×1
  • jquery.mCustomScrollbar._to (cognitive 47) zheng-admin/src/plugins/malihu-custom-scrollbar-plugin/jquery.mCustomScrollbar.js:1870 — jquery.mCustomScrollbar._to has cognitive complexity 47 (threshold 15). Drivers by points: if/else 16 (23 pts), ternaries 8 (19 pts), boolean chains 4, match/switch 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.
D2 · Cognitive Complexity · jquery.mCustomScrollbar._selectable (cognitive 37) · ×1
  • jquery.mCustomScrollbar._selectable (cognitive 37) zheng-admin/src/plugins/malihu-custom-scrollbar-plugin/jquery.mCustomScrollbar.js:1396 — jquery.mCustomScrollbar._selectable has cognitive complexity 37 (threshold 15). Drivers by points: if/else 14 (27 pts), boolean chains 6, ternaries 3 (4 pts) (nesting depth added 14). None of this is in the body itself: all 37 points belong to 5 function items inside it that branch (a function literal at line 1405, _sel, a function literal at line 1402, …). 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.
D2 · Cognitive Complexity · jquery.mCustomScrollbar._mousewheel · ×1
  • jquery.mCustomScrollbar._mousewheel::_onMousewheel (cognitive 36) zheng-admin/src/plugins/malihu-custom-scrollbar-plugin/jquery.mCustomScrollbar.js:1473 — jquery.mCustomScrollbar._mousewheel::_onMousewheel has cognitive complexity 36 (threshold 15). Drivers by points: ternaries 7 (15 pts), boolean chains 13, if/else 8 (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.
D2 · Cognitive Complexity · jquery.mCustomScrollbar._scrollbarVisibility (cognitive 30) · ×1
  • jquery.mCustomScrollbar._scrollbarVisibility (cognitive 30) zheng-admin/src/plugins/malihu-custom-scrollbar-plugin/jquery.mCustomScrollbar.js:1115 — jquery.mCustomScrollbar._scrollbarVisibility has cognitive complexity 30 (threshold 15). Drivers by points: if/else 14 (26 pts), boolean chains 3, ternaries 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · bootstrap.Tooltip.show (cognitive 28) · ×1
  • bootstrap.Tooltip.show (cognitive 28) zheng-admin/src/plugins/bootstrap-3.3.0/js/bootstrap.js:1334 — bootstrap.Tooltip.show has cognitive complexity 28 (threshold 15). Drivers by points: if/else 6 (11 pts), ternaries 4 (9 pts), boolean chains 8 (nesting depth added 10). Of this number, 26 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · jquery.mCustomScrollbar._tweenTo (cognitive 26) · ×1
  • jquery.mCustomScrollbar._tweenTo (cognitive 26) zheng-admin/src/plugins/malihu-custom-scrollbar-plugin/jquery.mCustomScrollbar.js:2206 — jquery.mCustomScrollbar._tweenTo has cognitive complexity 26 (threshold 15). Drivers by points: if/else 17 (21 pts), boolean chains 4, match/switch 1 (nesting depth added 4). Most of this is not in the body itself: 7 of the 26 points are its own statements and the rest belongs to 5 function items inside it that branch (_step, _ease, _cancelTween, …). 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.
D2 · Cognitive Complexity · jquery.mCustomScrollbar._sequentialScroll · ×1
  • jquery.mCustomScrollbar._sequentialScroll::_on (cognitive 25) zheng-admin/src/plugins/malihu-custom-scrollbar-plugin/jquery.mCustomScrollbar.js:1815 — jquery.mCustomScrollbar._sequentialScroll::_on has cognitive complexity 25 (threshold 15). Drivers by points: ternaries 14 (21 pts), if/else 3, boolean chains 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.
D2 · Cognitive Complexity · CmsArticle.equals (cognitive 22) · ×1
  • CmsArticle.equals (cognitive 22) zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticle.java:307 — CmsArticle.equals has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 18, if/else 3, boolean chains 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.
D2 · Cognitive Complexity · UpmsAuthenticationFilter.validateClient (cognitive 21) · ×1
  • UpmsAuthenticationFilter.validateClient (cognitive 21) REDACTED:97 — UpmsAuthenticationFilter.validateClient has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (11 pts), error handling 3 (9 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.
D2 · Cognitive Complexity · jquery.mCustomScrollbar._pluginMarkup (cognitive 20) · ×1
  • jquery.mCustomScrollbar._pluginMarkup (cognitive 20) zheng-admin/src/plugins/malihu-custom-scrollbar-plugin/jquery.mCustomScrollbar.js:862 — jquery.mCustomScrollbar._pluginMarkup has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 8 (10 pts), if/else 6 (7 pts), boolean chains 3 (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.
D2 · Cognitive Complexity · waves.showEffect (cognitive 20) · ×1
  • waves.showEffect (cognitive 20) zheng-admin/src/plugins/waves-0.7.5/waves.js:380 — waves.showEffect has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (18 pts), boolean chains 2 (nesting depth added 10). Of this number, 11 points are the body's own statements and 9 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.
D2 · Cognitive Complexity · JarUtil.decompress (cognitive 19) · ×1
  • JarUtil.decompress (cognitive 19) zheng-common/src/main/java/com/zheng/common/util/JarUtil.java:18 — JarUtil.decompress has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (12 pts), loops 2 (4 pts), error handling 2 (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.
D2 · Cognitive Complexity · jquery.mCustomScrollbar._draggerRail (cognitive 19) · ×1
  • jquery.mCustomScrollbar._draggerRail (cognitive 19) zheng-admin/src/plugins/malihu-custom-scrollbar-plugin/jquery.mCustomScrollbar.js:1568 — jquery.mCustomScrollbar._draggerRail has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (12 pts), ternaries 2 (6 pts), boolean chains 1 (nesting depth added 9). None of this is in the body itself: all 19 points belong to 2 function literals inside it that branch (lines 1580, 1575). 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.
D2 · Cognitive Complexity · UpmsLog.equals (cognitive 18) · ×1
  • UpmsLog.equals (cognitive 18) zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsLog.java:233 — UpmsLog.equals has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 14, if/else 3, boolean chains 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.
D2 · Cognitive Complexity · CmsArticle.hashCode (cognitive 18) · ×1
  • CmsArticle.hashCode (cognitive 18) zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticle.java:339 — CmsArticle.hashCode has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 18. 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.
D2 · Cognitive Complexity · bootstrap.Affix.getState (cognitive 18) · ×1
  • bootstrap.Affix.getState (cognitive 18) zheng-admin/src/plugins/bootstrap-3.3.0/js/bootstrap.js:2154 — bootstrap.Affix.getState has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 5 (9 pts), if/else 5 (6 pts), boolean chains 3 (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.
D2 · Cognitive Complexity · bootstrap.Modal.backdrop (cognitive 17) · ×1
  • bootstrap.Modal.backdrop (cognitive 17) zheng-admin/src/plugins/bootstrap-3.3.0/js/bootstrap.js:1064 — bootstrap.Modal.backdrop has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (7 pts), boolean chains 5, ternaries 3 (5 pts) (nesting depth added 4). Of this number, 16 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.
D2 · Cognitive Complexity · SSOController.login (cognitive 16) · ×1
  • SSOController.login (cognitive 16) zheng-upms/zheng-upms-server/src/main/java/com/zheng/upms/server/controller/SSOController.java:115 — SSOController.login has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (8 pts), error handling 3 (6 pts), ternaries 1 (2 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.
D2 · Cognitive Complexity · jquery.mCustomScrollbar._draggable (cognitive 16) · ×1
  • jquery.mCustomScrollbar._draggable (cognitive 16) zheng-admin/src/plugins/malihu-custom-scrollbar-plugin/jquery.mCustomScrollbar.js:1184 — jquery.mCustomScrollbar._draggable has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (10 pts), boolean chains 4, ternaries 2 (nesting depth added 1). Most of this is not in the body itself: 4 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 1195, a function literal at line 1217, a function literal at line 1223, …). 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.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D3 · God Classes · MethodTooLong · ×1
  • MethodTooLong: MybatisGeneratorUtil.generator zheng-common/src/main/java/com/zheng/common/util/MybatisGeneratorUtil.java:42 — MethodTooLong — generator runs 103 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 3 over it, 1.03× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
D4 · Code Duplication · Near-duplicate member pair (94 shared lines) · ×1
  • Near-duplicate member pair (94 shared lines) zheng-upms/zheng-upms-rpc-service/src/main/java/com/zheng/upms/rpc/service/impl/UpmsPermissionServiceImpl.java:45 — zheng-upms/zheng-upms-rpc-service/src/main/java/com/zheng/upms/rpc/service/impl/UpmsPermissionServiceImpl.java:45-145 | zheng-upms/zheng-upms-rpc-service/src/main/java/com/zheng/upms/rpc/service/impl/UpmsPermissionServiceImpl.java:148-252 — These two members are variants of one another: 94 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication · Members sharing a duplicated core (12 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (12 members, 50+ identical tokens) zheng-cms/zheng-cms-admin/src/main/java/com/zheng/cms/admin/controller/manage/CmsArticleController.java:91 — zheng-cms/zheng-cms-admin/src/main/java/com/zheng/cms/admin/controller/manage/CmsArticleController.java:91-105 | zheng-cms/zheng-cms-admin/src/main/java/com/zheng/cms/admin/controller/manage/CmsArticleController.java:133-144 | zheng-cms/zheng-cms-admin/src/main/java/com/zheng/cms/admin/controller/manage/CmsCategoryController.java:81-94 | zheng-cms/zheng-cms-admin/src/main/java/com/zheng/cms/admin/controller/manage/CmsCategoryController.java:118-129 | zheng-cms/zheng-cms-admin/src/main/java/com/zheng/cms/admin/controller/manage/CmsMenuController.java:81-93 | zheng-cms/zheng-cms-admin/src/main/java/com/zheng/cms/admin/controller/manage/CmsMenuController.java:117-128 | zheng-cms/zheng-cms-admin/src/main/java/com/zheng/cms/admin/controller/manage/CmsPageController.java:81-94 | zheng-cms/zheng-cms-admin/src/main/java/com/zheng/cms/admin/controller/manage/CmsPageController.java:118-129 | zheng-cms/zheng-cms-admin/src/main/java/com/zheng/cms/admin/controller/manage/CmsTagController.java:81-94 | zheng-cms/zheng-cms-admin/src/main/java/com/zheng/cms/admin/controller/manage/CmsTagController.java:118-129 | zheng-cms/zheng-cms-admin/src/main/java/com/zheng/cms/admin/controller/manage/CmsTopicController.java:81-93 | zheng-cms/zheng-cms-admin/src/main/java/com/zheng/cms/admin/controller/manage/CmsTopicController.java:117-128 — These 12 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 12 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 12 times.
D4 · Code Duplication · Members sharing a duplicated core (11 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (11 members, 50+ identical tokens) zheng-common/src/main/java/com/zheng/common/base/BaseServiceImpl.java:24 — zheng-common/src/main/java/com/zheng/common/base/BaseServiceImpl.java:24-39 | zheng-common/src/main/java/com/zheng/common/base/BaseServiceImpl.java:42-57 | zheng-common/src/main/java/com/zheng/common/base/BaseServiceImpl.java:60-75 | zheng-common/src/main/java/com/zheng/common/base/BaseServiceImpl.java:78-93 | zheng-common/src/main/java/com/zheng/common/base/BaseServiceImpl.java:96-111 | zheng-common/src/main/java/com/zheng/common/base/BaseServiceImpl.java:284-299 | zheng-common/src/main/java/com/zheng/common/base/BaseServiceImpl.java:302-317 | zheng-common/src/main/java/com/zheng/common/base/BaseServiceImpl.java:320-335 | zheng-common/src/main/java/com/zheng/common/base/BaseServiceImpl.java:338-353 | zheng-common/src/main/java/com/zheng/common/base/BaseServiceImpl.java:356-371 | zheng-common/src/main/java/com/zheng/common/base/BaseServiceImpl.java:374-389 — These 11 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 11 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 11 times.
D4 · Code Duplication · Members sharing a duplicated core (8 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (8 members, 50+ identical tokens) zheng-upms/zheng-upms-server/src/main/java/com/zheng/upms/server/controller/manage/UpmsOrganizationController.java:86 — zheng-upms/zheng-upms-server/src/main/java/com/zheng/upms/server/controller/manage/UpmsOrganizationController.java:86-98 | zheng-upms/zheng-upms-server/src/main/java/com/zheng/upms/server/controller/manage/UpmsOrganizationController.java:122-133 | zheng-upms/zheng-upms-server/src/main/java/com/zheng/upms/server/controller/manage/UpmsPermissionController.java:128-141 | zheng-upms/zheng-upms-server/src/main/java/com/zheng/upms/server/controller/manage/UpmsPermissionController.java:170-181 | zheng-upms/zheng-upms-server/src/main/java/com/zheng/upms/server/controller/manage/UpmsRoleController.java:115-129 | zheng-upms/zheng-upms-server/src/main/java/com/zheng/upms/server/controller/manage/UpmsRoleController.java:153-165 | zheng-upms/zheng-upms-server/src/main/java/com/zheng/upms/server/controller/manage/UpmsSystemController.java:86-100 | zheng-upms/zheng-upms-server/src/main/java/com/zheng/upms/server/controller/manage/UpmsSystemController.java:124-136 — These 8 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 8 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 8 times.
D4 · Code Duplication · Members sharing a duplicated core (6 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (6 members, 50+ identical tokens) zheng-common/src/main/java/com/zheng/common/base/BaseServiceImpl.java:114 — zheng-common/src/main/java/com/zheng/common/base/BaseServiceImpl.java:114-129 | zheng-common/src/main/java/com/zheng/common/base/BaseServiceImpl.java:132-147 | zheng-common/src/main/java/com/zheng/common/base/BaseServiceImpl.java:150-166 | zheng-common/src/main/java/com/zheng/common/base/BaseServiceImpl.java:169-185 | zheng-common/src/main/java/com/zheng/common/base/BaseServiceImpl.java:188-204 | zheng-common/src/main/java/com/zheng/common/base/BaseServiceImpl.java:207-223 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
D4 · Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (4 members, 50+ identical tokens) zheng-message/zheng-message-server/src/main/java/com/zheng/message/server/ChatLauncher.java:8 — zheng-message/zheng-message-server/src/main/java/com/zheng/message/server/ChatLauncher.java:8-28 | zheng-message/zheng-message-server/src/main/java/com/zheng/message/server/EventChatLauncher.java:11-30 | zheng-message/zheng-message-server/src/main/java/com/zheng/message/server/NamespaceChatLauncher.java:8-38 | zheng-message/zheng-message-server/src/main/java/com/zheng/message/server/SslChatLauncher.java:13-36 — 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 · Duplicated block (37 lines × 2) · ×1
  • Duplicated block (37 lines × 2) zheng-upms/zheng-upms-rpc-service/src/main/java/com/zheng/upms/rpc/service/impl/UpmsPermissionServiceImpl.java:49 — zheng-upms/zheng-upms-rpc-service/src/main/java/com/zheng/upms/rpc/service/impl/UpmsPermissionServiceImpl.java:49-85 | zheng-upms/zheng-upms-rpc-service/src/main/java/com/zheng/upms/rpc/service/impl/UpmsPermissionServiceImpl.java:156-192 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `zheng-upms/zheng-upms-rpc-service/src/main/java/com/zheng/upms/rpc/service/impl/UpmsPermissionServiceImpl.java:49` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (27 lines × 3) · ×1
  • Duplicated block (27 lines × 3) zheng-cms/zheng-cms-web/src/main/java/com/zheng/cms/web/controller/BlogController.java:66 — zheng-cms/zheng-cms-web/src/main/java/com/zheng/cms/web/controller/BlogController.java:66-92 | zheng-cms/zheng-cms-web/src/main/java/com/zheng/cms/web/controller/NewsController.java:66-92 | zheng-cms/zheng-cms-web/src/main/java/com/zheng/cms/web/controller/QaController.java:66-92 — before extracting anything, compare `zheng-cms/zheng-cms-web/src/main/java/com/zheng/cms/web/controller/BlogController.java` and `zheng-cms/zheng-cms-web/src/main/java/com/zheng/cms/web/controller/NewsController.java` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 126 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.
D4 · Code Duplication · Duplicated block (25 lines × 2) · ×1
  • Duplicated block (25 lines × 2) zheng-upms/zheng-upms-rpc-service/src/main/java/com/zheng/upms/rpc/service/impl/UpmsPermissionServiceImpl.java:121 — zheng-upms/zheng-upms-rpc-service/src/main/java/com/zheng/upms/rpc/service/impl/UpmsPermissionServiceImpl.java:121-145 | zheng-upms/zheng-upms-rpc-service/src/main/java/com/zheng/upms/rpc/service/impl/UpmsPermissionServiceImpl.java:228-252 — 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 `zheng-upms/zheng-upms-rpc-service/src/main/java/com/zheng/upms/rpc/service/impl/UpmsPermissionServiceImpl.java:121` 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.
D4 · Code Duplication · Duplicated block (23 lines × 3) · ×1
  • Duplicated block (23 lines × 3) zheng-cms/zheng-cms-web/src/main/java/com/zheng/cms/web/controller/BlogController.java:155 — zheng-cms/zheng-cms-web/src/main/java/com/zheng/cms/web/controller/BlogController.java:155-177 | zheng-cms/zheng-cms-web/src/main/java/com/zheng/cms/web/controller/NewsController.java:155-177 | zheng-cms/zheng-cms-web/src/main/java/com/zheng/cms/web/controller/QaController.java:155-177 — before extracting anything, compare `zheng-cms/zheng-cms-web/src/main/java/com/zheng/cms/web/controller/BlogController.java` and `zheng-cms/zheng-cms-web/src/main/java/com/zheng/cms/web/controller/NewsController.java` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 126 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. 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.
D4 · Code Duplication · Duplicated block (22 lines × 3) · ×1
  • Duplicated block (22 lines × 3) zheng-cms/zheng-cms-web/src/main/java/com/zheng/cms/web/controller/BlogController.java:118 — zheng-cms/zheng-cms-web/src/main/java/com/zheng/cms/web/controller/BlogController.java:118-139 | zheng-cms/zheng-cms-web/src/main/java/com/zheng/cms/web/controller/NewsController.java:118-139 | zheng-cms/zheng-cms-web/src/main/java/com/zheng/cms/web/controller/QaController.java:118-139 — before extracting anything, compare `zheng-cms/zheng-cms-web/src/main/java/com/zheng/cms/web/controller/BlogController.java` and `zheng-cms/zheng-cms-web/src/main/java/com/zheng/cms/web/controller/NewsController.java` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 126 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 `zheng-cms/zheng-cms-web/src/main/java/com/zheng/cms/web/controller/BlogController.java:118` 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.
D4 · Code Duplication · Duplicated block (19 lines × 3) · ×1
  • Duplicated block (19 lines × 3) zheng-cms/zheng-cms-web/src/main/java/com/zheng/cms/web/controller/BlogController.java:187 — zheng-cms/zheng-cms-web/src/main/java/com/zheng/cms/web/controller/BlogController.java:187-205 | zheng-cms/zheng-cms-web/src/main/java/com/zheng/cms/web/controller/NewsController.java:187-205 | zheng-cms/zheng-cms-web/src/main/java/com/zheng/cms/web/controller/QaController.java:187-205 — before extracting anything, compare `zheng-cms/zheng-cms-web/src/main/java/com/zheng/cms/web/controller/BlogController.java` and `zheng-cms/zheng-cms-web/src/main/java/com/zheng/cms/web/controller/NewsController.java` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 126 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. 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.
D4 · Code Duplication · Duplicated block (19 lines × 2) · ×1
  • Duplicated block (19 lines × 2) zheng-common/src/main/java/com/zheng/common/plugin/PaginationPlugin.java:31 — zheng-common/src/main/java/com/zheng/common/plugin/PaginationPlugin.java:31-49 | zheng-common/src/main/java/com/zheng/common/plugin/PaginationPlugin.java:51-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.
D4 · Code Duplication · Duplicated block (16 lines × 4) · ×1
  • Duplicated block (16 lines × 4) zheng-upms/zheng-upms-rpc-service/src/main/java/com/zheng/upms/rpc/service/impl/UpmsPermissionServiceImpl.java:87 — zheng-upms/zheng-upms-rpc-service/src/main/java/com/zheng/upms/rpc/service/impl/UpmsPermissionServiceImpl.java:87-102 | zheng-upms/zheng-upms-rpc-service/src/main/java/com/zheng/upms/rpc/service/impl/UpmsPermissionServiceImpl.java:104-119 | zheng-upms/zheng-upms-rpc-service/src/main/java/com/zheng/upms/rpc/service/impl/UpmsPermissionServiceImpl.java:194-209 | zheng-upms/zheng-upms-rpc-service/src/main/java/com/zheng/upms/rpc/service/impl/UpmsPermissionServiceImpl.java:211-226 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `zheng-upms/zheng-upms-rpc-service/src/main/java/com/zheng/upms/rpc/service/impl/UpmsPermissionServiceImpl.java:87` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (16 lines × 2) · ×1
  • Duplicated block (16 lines × 2) REDACTED:32 — REDACTED:32-47 | REDACTED:86-101 — 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:32` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (15 lines × 3) · ×1
  • Duplicated block (15 lines × 3) zheng-cms/zheng-cms-web/src/main/java/com/zheng/cms/web/controller/BlogController.java:218 — zheng-cms/zheng-cms-web/src/main/java/com/zheng/cms/web/controller/BlogController.java:218-232 | zheng-cms/zheng-cms-web/src/main/java/com/zheng/cms/web/controller/NewsController.java:218-232 | zheng-cms/zheng-cms-web/src/main/java/com/zheng/cms/web/controller/QaController.java:218-232 — before extracting anything, compare `zheng-cms/zheng-cms-web/src/main/java/com/zheng/cms/web/controller/BlogController.java` and `zheng-cms/zheng-cms-web/src/main/java/com/zheng/cms/web/controller/NewsController.java` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 126 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. 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.
D4 · Code Duplication · Duplicated block (13–14 lines × 4) · ×1
  • Duplicated block (13–14 lines × 4) zheng-message/zheng-message-server/src/main/java/com/zheng/message/server/ChatLauncher.java:15 — zheng-message/zheng-message-server/src/main/java/com/zheng/message/server/ChatLauncher.java:15-28 | zheng-message/zheng-message-server/src/main/java/com/zheng/message/server/EventChatLauncher.java:18-30 | zheng-message/zheng-message-server/src/main/java/com/zheng/message/server/NamespaceChatLauncher.java:25-38 | zheng-message/zheng-message-server/src/main/java/com/zheng/message/server/SslChatLauncher.java:24-36 — before extracting anything, compare `zheng-message/zheng-message-server/src/main/java/com/zheng/message/server/ChatLauncher.java` and `zheng-message/zheng-message-server/src/main/java/com/zheng/message/server/NamespaceChatLauncher.java` as WHOLE FILES: 82% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. 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 `zheng-message/zheng-message-server/src/main/java/com/zheng/message/server/ChatLauncher.java:15` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (13 lines × 2) · ×1
  • Duplicated block (13 lines × 2) zheng-cms/zheng-cms-job/src/main/java/com/zheng/cms/job/jms/DefaultMessageQueueListener.java:26 — zheng-cms/zheng-cms-job/src/main/java/com/zheng/cms/job/jms/DefaultMessageQueueListener.java:26-38 | zheng-cms/zheng-cms-web/src/main/java/com/zheng/cms/web/jms/DefaultMessageQueueListener.java:26-38 — before extracting anything, compare `zheng-cms/zheng-cms-job/src/main/java/com/zheng/cms/job/jms/DefaultMessageQueueListener.java` and `zheng-cms/zheng-cms-web/src/main/java/com/zheng/cms/web/jms/DefaultMessageQueueListener.java` as WHOLE FILES: 96% 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.
D4 · Code Duplication · Duplicated block (12 lines × 6) · ×1
  • Duplicated block (12 lines × 6) zheng-common/src/main/java/com/zheng/common/base/BaseServiceImpl.java:118 — zheng-common/src/main/java/com/zheng/common/base/BaseServiceImpl.java:118-129 | zheng-common/src/main/java/com/zheng/common/base/BaseServiceImpl.java:136-147 | zheng-common/src/main/java/com/zheng/common/base/BaseServiceImpl.java:155-166 | zheng-common/src/main/java/com/zheng/common/base/BaseServiceImpl.java:174-185 | zheng-common/src/main/java/com/zheng/common/base/BaseServiceImpl.java:193-204 | zheng-common/src/main/java/com/zheng/common/base/BaseServiceImpl.java:212-223 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `zheng-common/src/main/java/com/zheng/common/base/BaseServiceImpl.java:118` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `zheng-common/src/main/java/com/zheng/common/base/BaseServiceImpl.java:154` calls `startPage` and `zheng-common/src/main/java/com/zheng/common/base/BaseServiceImpl.java:117` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (12 lines × 5) · ×1
  • Duplicated block (12 lines × 5) zheng-common/src/main/java/com/zheng/common/base/BaseServiceImpl.java:79 — zheng-common/src/main/java/com/zheng/common/base/BaseServiceImpl.java:79-90 | zheng-common/src/main/java/com/zheng/common/base/BaseServiceImpl.java:97-108 | zheng-common/src/main/java/com/zheng/common/base/BaseServiceImpl.java:339-350 | zheng-common/src/main/java/com/zheng/common/base/BaseServiceImpl.java:357-368 | zheng-common/src/main/java/com/zheng/common/base/BaseServiceImpl.java:375-386 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (12 lines × 2) · ×1
  • Duplicated block (12 lines × 2) zheng-cms/zheng-cms-admin/src/main/java/com/zheng/cms/admin/controller/manage/CmsMenuController.java:147 — zheng-cms/zheng-cms-admin/src/main/java/com/zheng/cms/admin/controller/manage/CmsMenuController.java:147-158 | zheng-cms/zheng-cms-admin/src/main/java/com/zheng/cms/admin/controller/manage/CmsMenuController.java:177-188 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `zheng-cms/zheng-cms-admin/src/main/java/com/zheng/cms/admin/controller/manage/CmsMenuController.java:147` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (11 lines × 11) · ×1
  • Duplicated block (11 lines × 11) zheng-common/src/main/java/com/zheng/common/base/BaseServiceImpl.java:29 — zheng-common/src/main/java/com/zheng/common/base/BaseServiceImpl.java:29-39 | zheng-common/src/main/java/com/zheng/common/base/BaseServiceImpl.java:47-57 | zheng-common/src/main/java/com/zheng/common/base/BaseServiceImpl.java:65-75 | zheng-common/src/main/java/com/zheng/common/base/BaseServiceImpl.java:83-93 | zheng-common/src/main/java/com/zheng/common/base/BaseServiceImpl.java:101-111 | zheng-common/src/main/java/com/zheng/common/base/BaseServiceImpl.java:289-299 | zheng-common/src/main/java/com/zheng/common/base/BaseServiceImpl.java:307-317 | zheng-common/src/main/java/com/zheng/common/base/BaseServiceImpl.java:325-335 | zheng-common/src/main/java/com/zheng/common/base/BaseServiceImpl.java:343-353 | zheng-common/src/main/java/com/zheng/common/base/BaseServiceImpl.java:361-371 | zheng-common/src/main/java/com/zheng/common/base/BaseServiceImpl.java:379-389 — all 11 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `zheng-common/src/main/java/com/zheng/common/base/BaseServiceImpl.java:29` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (11 lines × 4) · ×1
  • Duplicated block (11 lines × 4) zheng-cms/zheng-cms-web/src/main/java/com/zheng/cms/web/controller/BlogController.java:91 — zheng-cms/zheng-cms-web/src/main/java/com/zheng/cms/web/controller/BlogController.java:91-101 | zheng-cms/zheng-cms-web/src/main/java/com/zheng/cms/web/controller/NewsController.java:91-101 | zheng-cms/zheng-cms-web/src/main/java/com/zheng/cms/web/controller/QaController.java:91-101 | zheng-cms/zheng-cms-web/src/main/java/com/zheng/cms/web/controller/SearchController.java:52-62 — before extracting anything, compare `zheng-cms/zheng-cms-web/src/main/java/com/zheng/cms/web/controller/BlogController.java` and `zheng-cms/zheng-cms-web/src/main/java/com/zheng/cms/web/controller/NewsController.java` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 126 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 `zheng-cms/zheng-cms-web/src/main/java/com/zheng/cms/web/controller/BlogController.java:91` 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.
D4 · Code Duplication · Duplicated block (10 lines × 2) · ×1
  • Duplicated block (10 lines × 2) zheng-common/src/main/java/com/zheng/common/listener/ApplicationContextListener.java:28 — zheng-common/src/main/java/com/zheng/common/listener/ApplicationContextListener.java:28-37 | zheng-common/src/main/java/com/zheng/common/listener/ApplicationContextListener.java:41-50 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (8–9 lines × 6) · ×1
  • Duplicated block (8–9 lines × 6) zheng-cms/zheng-cms-web/src/main/java/com/zheng/cms/web/controller/BlogController.java:65 — zheng-cms/zheng-cms-web/src/main/java/com/zheng/cms/web/controller/BlogController.java:65-72 | zheng-cms/zheng-cms-web/src/main/java/com/zheng/cms/web/controller/BlogController.java:117-125 | zheng-cms/zheng-cms-web/src/main/java/com/zheng/cms/web/controller/NewsController.java:65-72 | zheng-cms/zheng-cms-web/src/main/java/com/zheng/cms/web/controller/NewsController.java:117-125 | zheng-cms/zheng-cms-web/src/main/java/com/zheng/cms/web/controller/QaController.java:65-72 | zheng-cms/zheng-cms-web/src/main/java/com/zheng/cms/web/controller/QaController.java:117-125 — before extracting anything, compare `zheng-cms/zheng-cms-web/src/main/java/com/zheng/cms/web/controller/BlogController.java` and `zheng-cms/zheng-cms-web/src/main/java/com/zheng/cms/web/controller/NewsController.java` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 126 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (8 lines × 4) · ×1
  • Duplicated block (8 lines × 4) zheng-cms/zheng-cms-admin/src/main/java/com/zheng/cms/admin/controller/manage/CmsArticleController.java:94 — zheng-cms/zheng-cms-admin/src/main/java/com/zheng/cms/admin/controller/manage/CmsArticleController.java:94-101 | zheng-cms/zheng-cms-admin/src/main/java/com/zheng/cms/admin/controller/manage/CmsCategoryController.java:84-91 | zheng-cms/zheng-cms-admin/src/main/java/com/zheng/cms/admin/controller/manage/CmsPageController.java:84-91 | zheng-cms/zheng-cms-admin/src/main/java/com/zheng/cms/admin/controller/manage/CmsTagController.java:84-91 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 4 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `zheng-cms/zheng-cms-admin/src/main/java/com/zheng/cms/admin/controller/manage/CmsArticleController.java:94` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `zheng-cms/zheng-cms-admin/src/main/java/com/zheng/cms/admin/controller/manage/CmsArticleController.java:102` calls `setReadnumber` and `zheng-cms/zheng-cms-admin/src/main/java/com/zheng/cms/admin/controller/manage/CmsCategoryController.java:92` 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.
D4 · Code Duplication · Duplicated block (3–8 lines × 4) · ×1
  • Duplicated block (3–8 lines × 4) zheng-common/src/main/java/com/zheng/common/util/Paginator.java:198 — zheng-common/src/main/java/com/zheng/common/util/Paginator.java:198-205 | zheng-common/src/main/java/com/zheng/common/util/Paginator.java:208-210 | zheng-common/src/main/java/com/zheng/common/util/Paginator.java:218-225 | zheng-common/src/main/java/com/zheng/common/util/Paginator.java:231-238 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `zheng-common/src/main/java/com/zheng/common/util/Paginator.java:198` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `zheng-common/src/main/java/com/zheng/common/util/Paginator.java:211` calls `concat` and `zheng-common/src/main/java/com/zheng/common/util/Paginator.java:225` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (8 lines × 3) · ×1
  • Duplicated block (8 lines × 3) zheng-upms/zheng-upms-server/src/main/java/com/zheng/upms/server/controller/manage/UpmsPermissionController.java:131 — zheng-upms/zheng-upms-server/src/main/java/com/zheng/upms/server/controller/manage/UpmsPermissionController.java:131-138 | zheng-upms/zheng-upms-server/src/main/java/com/zheng/upms/server/controller/manage/UpmsRoleController.java:119-126 | zheng-upms/zheng-upms-server/src/main/java/com/zheng/upms/server/controller/manage/UpmsSystemController.java:90-97 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `zheng-upms/zheng-upms-server/src/main/java/com/zheng/upms/server/controller/manage/UpmsPermissionController.java:131` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `zheng-upms/zheng-upms-server/src/main/java/com/zheng/upms/server/controller/manage/UpmsRoleController.java:118` calls `on`, `getTitle`, `LengthValidator` and `zheng-upms/zheng-upms-server/src/main/java/com/zheng/upms/server/controller/manage/UpmsPermissionController.java:130` 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.
D4 · Code Duplication · Duplicated block (7 lines × 5) · ×1
  • Duplicated block (7 lines × 5) zheng-cms/zheng-cms-admin/src/main/java/com/zheng/cms/admin/controller/manage/CmsArticleController.java:94 — zheng-cms/zheng-cms-admin/src/main/java/com/zheng/cms/admin/controller/manage/CmsArticleController.java:94-100 | zheng-cms/zheng-cms-admin/src/main/java/com/zheng/cms/admin/controller/manage/CmsCategoryController.java:84-90 | zheng-cms/zheng-cms-admin/src/main/java/com/zheng/cms/admin/controller/manage/CmsPageController.java:84-90 | zheng-cms/zheng-cms-admin/src/main/java/com/zheng/cms/admin/controller/manage/CmsTagController.java:84-90 | zheng-cms/zheng-cms-admin/src/main/java/com/zheng/cms/admin/controller/manage/CmsTopicController.java:84-90 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 5 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `zheng-cms/zheng-cms-admin/src/main/java/com/zheng/cms/admin/controller/manage/CmsArticleController.java:94` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `zheng-cms/zheng-cms-admin/src/main/java/com/zheng/cms/admin/controller/manage/CmsArticleController.java:102` calls `setReadnumber` and `zheng-cms/zheng-cms-admin/src/main/java/com/zheng/cms/admin/controller/manage/CmsCategoryController.java:92` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (7 lines × 4) · ×1
  • Duplicated block (7 lines × 4) zheng-upms/zheng-upms-server/src/main/java/com/zheng/upms/server/controller/manage/UpmsOrganizationController.java:89 — zheng-upms/zheng-upms-server/src/main/java/com/zheng/upms/server/controller/manage/UpmsOrganizationController.java:89-95 | zheng-upms/zheng-upms-server/src/main/java/com/zheng/upms/server/controller/manage/UpmsPermissionController.java:131-137 | zheng-upms/zheng-upms-server/src/main/java/com/zheng/upms/server/controller/manage/UpmsRoleController.java:119-125 | zheng-upms/zheng-upms-server/src/main/java/com/zheng/upms/server/controller/manage/UpmsSystemController.java:90-96 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 4 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `zheng-upms/zheng-upms-server/src/main/java/com/zheng/upms/server/controller/manage/UpmsOrganizationController.java:89` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `zheng-upms/zheng-upms-server/src/main/java/com/zheng/upms/server/controller/manage/UpmsPermissionController.java:138` calls `setOrders` and `zheng-upms/zheng-upms-server/src/main/java/com/zheng/upms/server/controller/manage/UpmsOrganizationController.java:96` 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.
D4 · Code Duplication · Duplicated block (6 lines × 2) · ×1
  • Duplicated block (6 lines × 2) zheng-upms/zheng-upms-server/src/main/java/com/zheng/upms/server/controller/manage/UpmsUserController.java:182 — zheng-upms/zheng-upms-server/src/main/java/com/zheng/upms/server/controller/manage/UpmsUserController.java:182-187 | zheng-upms/zheng-upms-server/src/main/java/com/zheng/upms/server/controller/manage/UpmsUserController.java:226-231 — 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 `zheng-upms/zheng-upms-server/src/main/java/com/zheng/upms/server/controller/manage/UpmsUserController.java:182` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `zheng-upms/zheng-upms-server/src/main/java/com/zheng/upms/server/controller/manage/UpmsUserController.java:181` calls `on`, `getPassword`, `LengthValidator` and `zheng-upms/zheng-upms-server/src/main/java/com/zheng/upms/server/controller/manage/UpmsUserController.java:225` 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.
D4 · Code Duplication · Duplicated block (5 lines × 3) · ×1
  • Duplicated block (5 lines × 3) zheng-ucenter/zheng-ucenter-dao/src/main/java/com/zheng/ucenter/dao/model/UcenterUser.java:161 — zheng-ucenter/zheng-ucenter-dao/src/main/java/com/zheng/ucenter/dao/model/UcenterUser.java:161-165 | zheng-ucenter/zheng-ucenter-dao/src/main/java/com/zheng/ucenter/dao/model/UcenterUserDetails.java:101-105 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsUser.java:175-179 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
D4 · Code Duplication · Duplicated block (15 lines × 2) · ×1
  • Duplicated block (15 lines × 2) zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleCategory.java:67 — zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleCategory.java:67-81 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleTag.java:67-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.
D4 · Code Duplication · Duplicated block (20 lines × 6) · ×1
  • Duplicated block (20 lines × 6) zheng-api/zheng-api-common/src/main/java/com/zheng/api/common/constant/ApiResultConstant.java:18 — zheng-api/zheng-api-common/src/main/java/com/zheng/api/common/constant/ApiResultConstant.java:18-37 | zheng-cms/zheng-cms-common/src/main/java/com/zheng/cms/common/constant/CmsResultConstant.java:38-57 | zheng-oss/zheng-oss-sdk/src/main/java/com/zheng/oss/common/constant/OssResultConstant.java:23-42 | zheng-pay/zheng-pay-common/src/main/java/com/zheng/pay/common/constant/PayResultConstant.java:23-42 | zheng-ucenter/zheng-ucenter-common/src/main/java/com/zheng/ucenter/common/constant/UcenterResultConstant.java:23-42 | zheng-upms/zheng-upms-common/src/main/java/com/zheng/upms/common/constant/UpmsResultConstant.java:53-72 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 6 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 6 times.
D4 · Code Duplication · Duplicated block (366 lines × 35) · ×1
  • Duplicated block (366 lines × 35) zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleCategoryExample.java:16 — zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleCategoryExample.java:16-381 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleExample.java:16-1281 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleTagExample.java:16-381 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsCategoryExample.java:16-901 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsCategoryTagExample.java:16-381 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsCommentExample.java:16-761 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsMenuExample.java:16-591 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsPageExample.java:16-721 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsSettingExample.java:16-401 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsSystemExample.java:16-591 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsTagExample.java:16-781 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsTopicExample.java:16-531 | zheng-pay/zheng-pay-dao/src/main/java/com/zheng/pay/dao/model/PayInOrderDetailExample.java:16-651 | zheng-pay/zheng-pay-dao/src/main/java/com/zheng/pay/dao/model/PayInOrderExample.java:16-561 | zheng-pay/zheng-pay-dao/src/main/java/com/zheng/pay/dao/model/PayMchExample.java:16-541 | zheng-pay/zheng-pay-dao/src/main/java/com/zheng/pay/dao/model/PayOutOrderDetailExample.java:16-391 | zheng-pay/zheng-pay-dao/src/main/java/com/zheng/pay/dao/model/PayOutOrderExample.java:16-561 | zheng-pay/zheng-pay-dao/src/main/java/com/zheng/pay/dao/model/PayPayExample.java:16-391 | zheng-pay/zheng-pay-dao/src/main/java/com/zheng/pay/dao/model/PayTypeExample.java:16-381 | zheng-pay/zheng-pay-dao/src/main/java/com/zheng/pay/dao/model/PayVendorExample.java:16-541 | zheng-pay/zheng-pay-dao/src/main/java/com/zheng/pay/dao/model/PayVestExample.java:16-461 | zheng-ucenter/zheng-ucenter-dao/src/main/java/com/zheng/ucenter/dao/model/UcenterUserDetailsExample.java:17-602 | zheng-ucenter/zheng-ucenter-dao/src/main/java/com/zheng/ucenter/dao/model/UcenterUserExample.java:17-862 | zheng-ucenter/zheng-ucenter-dao/src/main/java/com/zheng/ucenter/dao/model/UcenterUserLogExample.java:17-452 | zheng-ucenter/zheng-ucenter-dao/src/main/java/com/zheng/ucenter/dao/model/UcenterUserOauthExample.java:17-502 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsLogExample.java:16-1011 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsOrganizationExample.java:16-521 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsPermissionExample.java:16-901 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsRoleExample.java:16-591 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsRolePermissionExample.java:16-381 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsSystemExample.java:16-931 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsUserExample.java:16-931 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsUserOrganizationExample.java:16-381 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsUserPermissionExample.java:16-441 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsUserRoleExample.java:16-381 — before extracting anything, compare `zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleExample.java` and `zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsCategoryExample.java` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 25320 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 `zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleCategoryExample.java:16` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (886 lines × 6) · ×1
  • Duplicated block (886 lines × 6) zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleExample.java:16 — zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleExample.java:16-1281 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsCategoryExample.java:16-901 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsLogExample.java:16-1011 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsPermissionExample.java:16-901 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsSystemExample.java:16-931 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsUserExample.java:16-931 — before extracting anything, compare `zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleExample.java` and `zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsCategoryExample.java` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 25320 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 `zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleExample.java:16` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (746 lines × 9) · ×1
  • Duplicated block (746 lines × 9) zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleExample.java:16 — zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleExample.java:16-1281 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsCategoryExample.java:16-901 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsCommentExample.java:16-761 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsTagExample.java:16-781 | zheng-ucenter/zheng-ucenter-dao/src/main/java/com/zheng/ucenter/dao/model/UcenterUserExample.java:17-862 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsLogExample.java:16-1011 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsPermissionExample.java:16-901 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsSystemExample.java:16-931 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsUserExample.java:16-931 — before extracting anything, compare `zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleExample.java` and `zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsCategoryExample.java` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 25320 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 `zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleExample.java:16` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (576 lines × 15) · ×1
  • Duplicated block (576 lines × 15) zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleExample.java:16 — zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleExample.java:16-1281 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsCategoryExample.java:16-901 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsCommentExample.java:16-761 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsMenuExample.java:16-591 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsPageExample.java:16-721 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsSystemExample.java:16-591 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsTagExample.java:16-781 | zheng-pay/zheng-pay-dao/src/main/java/com/zheng/pay/dao/model/PayInOrderDetailExample.java:16-651 | zheng-ucenter/zheng-ucenter-dao/src/main/java/com/zheng/ucenter/dao/model/UcenterUserDetailsExample.java:17-602 | zheng-ucenter/zheng-ucenter-dao/src/main/java/com/zheng/ucenter/dao/model/UcenterUserExample.java:17-862 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsLogExample.java:16-1011 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsPermissionExample.java:16-901 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsRoleExample.java:16-591 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsSystemExample.java:16-931 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsUserExample.java:16-931 — before extracting anything, compare `zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleExample.java` and `zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsCategoryExample.java` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 25320 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 `zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleExample.java:16` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (706 lines × 10) · ×1
  • Duplicated block (706 lines × 10) zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleExample.java:16 — zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleExample.java:16-1281 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsCategoryExample.java:16-901 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsCommentExample.java:16-761 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsPageExample.java:16-721 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsTagExample.java:16-781 | zheng-ucenter/zheng-ucenter-dao/src/main/java/com/zheng/ucenter/dao/model/UcenterUserExample.java:17-862 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsLogExample.java:16-1011 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsPermissionExample.java:16-901 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsSystemExample.java:16-931 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsUserExample.java:16-931 — before extracting anything, compare `zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleExample.java` and `zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsCategoryExample.java` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 25320 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 `zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleExample.java:16` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (386 lines × 26) · ×1
  • Duplicated block (386 lines × 26) zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleExample.java:16 — zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleExample.java:16-1281 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsCategoryExample.java:16-901 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsCommentExample.java:16-761 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsMenuExample.java:16-591 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsPageExample.java:16-721 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsSettingExample.java:16-401 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsSystemExample.java:16-591 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsTagExample.java:16-781 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsTopicExample.java:16-531 | zheng-pay/zheng-pay-dao/src/main/java/com/zheng/pay/dao/model/PayInOrderDetailExample.java:16-651 | zheng-pay/zheng-pay-dao/src/main/java/com/zheng/pay/dao/model/PayInOrderExample.java:16-561 | zheng-pay/zheng-pay-dao/src/main/java/com/zheng/pay/dao/model/PayMchExample.java:16-541 | zheng-pay/zheng-pay-dao/src/main/java/com/zheng/pay/dao/model/PayOutOrderExample.java:16-561 | zheng-pay/zheng-pay-dao/src/main/java/com/zheng/pay/dao/model/PayVendorExample.java:16-541 | zheng-pay/zheng-pay-dao/src/main/java/com/zheng/pay/dao/model/PayVestExample.java:16-461 | zheng-ucenter/zheng-ucenter-dao/src/main/java/com/zheng/ucenter/dao/model/UcenterUserDetailsExample.java:17-602 | zheng-ucenter/zheng-ucenter-dao/src/main/java/com/zheng/ucenter/dao/model/UcenterUserExample.java:17-862 | zheng-ucenter/zheng-ucenter-dao/src/main/java/com/zheng/ucenter/dao/model/UcenterUserLogExample.java:17-452 | zheng-ucenter/zheng-ucenter-dao/src/main/java/com/zheng/ucenter/dao/model/UcenterUserOauthExample.java:17-502 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsLogExample.java:16-1011 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsOrganizationExample.java:16-521 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsPermissionExample.java:16-901 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsRoleExample.java:16-591 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsSystemExample.java:16-931 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsUserExample.java:16-931 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsUserPermissionExample.java:16-441 — before extracting anything, compare `zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleExample.java` and `zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsCategoryExample.java` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 25320 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 `zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleExample.java:16` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (766 lines × 8) · ×1
  • Duplicated block (766 lines × 8) zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleExample.java:16 — zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleExample.java:16-1281 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsCategoryExample.java:16-901 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsTagExample.java:16-781 | zheng-ucenter/zheng-ucenter-dao/src/main/java/com/zheng/ucenter/dao/model/UcenterUserExample.java:17-862 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsLogExample.java:16-1011 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsPermissionExample.java:16-901 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsSystemExample.java:16-931 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsUserExample.java:16-931 — before extracting anything, compare `zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleExample.java` and `zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsCategoryExample.java` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 25320 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 `zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleExample.java:16` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (516 lines × 20) · ×1
  • Duplicated block (516 lines × 20) zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleExample.java:16 — zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleExample.java:16-1281 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsCategoryExample.java:16-901 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsCommentExample.java:16-761 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsMenuExample.java:16-591 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsPageExample.java:16-721 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsSystemExample.java:16-591 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsTagExample.java:16-781 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsTopicExample.java:16-531 | zheng-pay/zheng-pay-dao/src/main/java/com/zheng/pay/dao/model/PayInOrderDetailExample.java:16-651 | zheng-pay/zheng-pay-dao/src/main/java/com/zheng/pay/dao/model/PayInOrderExample.java:16-561 | zheng-pay/zheng-pay-dao/src/main/java/com/zheng/pay/dao/model/PayMchExample.java:16-541 | zheng-pay/zheng-pay-dao/src/main/java/com/zheng/pay/dao/model/PayOutOrderExample.java:16-561 | zheng-pay/zheng-pay-dao/src/main/java/com/zheng/pay/dao/model/PayVendorExample.java:16-541 | zheng-ucenter/zheng-ucenter-dao/src/main/java/com/zheng/ucenter/dao/model/UcenterUserDetailsExample.java:17-602 | zheng-ucenter/zheng-ucenter-dao/src/main/java/com/zheng/ucenter/dao/model/UcenterUserExample.java:17-862 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsLogExample.java:16-1011 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsPermissionExample.java:16-901 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsRoleExample.java:16-591 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsSystemExample.java:16-931 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsUserExample.java:16-931 — before extracting anything, compare `zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleExample.java` and `zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsCategoryExample.java` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 25320 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 `zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleExample.java:16` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (29 lines × 2) · ×1
  • Duplicated block (29 lines × 2) zheng-common/src/main/java/com/zheng/common/base/BaseResult.java:24 — zheng-common/src/main/java/com/zheng/common/base/BaseResult.java:24-52 | zheng-message/zheng-message-sdk/src/main/java/com/zheng/message/sdk/BaseResult.java:24-52 — before extracting anything, compare `zheng-common/src/main/java/com/zheng/common/base/BaseResult.java` and `zheng-message/zheng-message-sdk/src/main/java/com/zheng/message/sdk/BaseResult.java` as WHOLE FILES: 97% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (636 lines × 11) · ×1
  • Duplicated block (636 lines × 11) zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleExample.java:16 — zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleExample.java:16-1281 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsCategoryExample.java:16-901 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsCommentExample.java:16-761 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsPageExample.java:16-721 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsTagExample.java:16-781 | zheng-pay/zheng-pay-dao/src/main/java/com/zheng/pay/dao/model/PayInOrderDetailExample.java:16-651 | zheng-ucenter/zheng-ucenter-dao/src/main/java/com/zheng/ucenter/dao/model/UcenterUserExample.java:17-862 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsLogExample.java:16-1011 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsPermissionExample.java:16-901 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsSystemExample.java:16-931 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsUserExample.java:16-931 — before extracting anything, compare `zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleExample.java` and `zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsCategoryExample.java` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 25320 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 `zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleExample.java:16` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (546 lines × 17) · ×1
  • Duplicated block (546 lines × 17) zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleExample.java:16 — zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleExample.java:16-1281 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsCategoryExample.java:16-901 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsCommentExample.java:16-761 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsMenuExample.java:16-591 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsPageExample.java:16-721 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsSystemExample.java:16-591 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsTagExample.java:16-781 | zheng-pay/zheng-pay-dao/src/main/java/com/zheng/pay/dao/model/PayInOrderDetailExample.java:16-651 | zheng-pay/zheng-pay-dao/src/main/java/com/zheng/pay/dao/model/PayInOrderExample.java:16-561 | zheng-pay/zheng-pay-dao/src/main/java/com/zheng/pay/dao/model/PayOutOrderExample.java:16-561 | zheng-ucenter/zheng-ucenter-dao/src/main/java/com/zheng/ucenter/dao/model/UcenterUserDetailsExample.java:17-602 | zheng-ucenter/zheng-ucenter-dao/src/main/java/com/zheng/ucenter/dao/model/UcenterUserExample.java:17-862 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsLogExample.java:16-1011 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsPermissionExample.java:16-901 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsRoleExample.java:16-591 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsSystemExample.java:16-931 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsUserExample.java:16-931 — before extracting anything, compare `zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleExample.java` and `zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsCategoryExample.java` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 25320 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 `zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleExample.java:16` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (526 lines × 19) · ×1
  • Duplicated block (526 lines × 19) zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleExample.java:16 — zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleExample.java:16-1281 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsCategoryExample.java:16-901 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsCommentExample.java:16-761 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsMenuExample.java:16-591 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsPageExample.java:16-721 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsSystemExample.java:16-591 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsTagExample.java:16-781 | zheng-pay/zheng-pay-dao/src/main/java/com/zheng/pay/dao/model/PayInOrderDetailExample.java:16-651 | zheng-pay/zheng-pay-dao/src/main/java/com/zheng/pay/dao/model/PayInOrderExample.java:16-561 | zheng-pay/zheng-pay-dao/src/main/java/com/zheng/pay/dao/model/PayMchExample.java:16-541 | zheng-pay/zheng-pay-dao/src/main/java/com/zheng/pay/dao/model/PayOutOrderExample.java:16-561 | zheng-pay/zheng-pay-dao/src/main/java/com/zheng/pay/dao/model/PayVendorExample.java:16-541 | zheng-ucenter/zheng-ucenter-dao/src/main/java/com/zheng/ucenter/dao/model/UcenterUserDetailsExample.java:17-602 | zheng-ucenter/zheng-ucenter-dao/src/main/java/com/zheng/ucenter/dao/model/UcenterUserExample.java:17-862 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsLogExample.java:16-1011 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsPermissionExample.java:16-901 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsRoleExample.java:16-591 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsSystemExample.java:16-931 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsUserExample.java:16-931 — before extracting anything, compare `zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleExample.java` and `zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsCategoryExample.java` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 25320 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 `zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleExample.java:16` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (376 lines × 28) · ×1
  • Duplicated block (376 lines × 28) zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleExample.java:16 — zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleExample.java:16-1281 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsCategoryExample.java:16-901 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsCommentExample.java:16-761 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsMenuExample.java:16-591 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsPageExample.java:16-721 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsSettingExample.java:16-401 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsSystemExample.java:16-591 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsTagExample.java:16-781 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsTopicExample.java:16-531 | zheng-pay/zheng-pay-dao/src/main/java/com/zheng/pay/dao/model/PayInOrderDetailExample.java:16-651 | zheng-pay/zheng-pay-dao/src/main/java/com/zheng/pay/dao/model/PayInOrderExample.java:16-561 | zheng-pay/zheng-pay-dao/src/main/java/com/zheng/pay/dao/model/PayMchExample.java:16-541 | zheng-pay/zheng-pay-dao/src/main/java/com/zheng/pay/dao/model/PayOutOrderDetailExample.java:16-391 | zheng-pay/zheng-pay-dao/src/main/java/com/zheng/pay/dao/model/PayOutOrderExample.java:16-561 | zheng-pay/zheng-pay-dao/src/main/java/com/zheng/pay/dao/model/PayPayExample.java:16-391 | zheng-pay/zheng-pay-dao/src/main/java/com/zheng/pay/dao/model/PayVendorExample.java:16-541 | zheng-pay/zheng-pay-dao/src/main/java/com/zheng/pay/dao/model/PayVestExample.java:16-461 | zheng-ucenter/zheng-ucenter-dao/src/main/java/com/zheng/ucenter/dao/model/UcenterUserDetailsExample.java:17-602 | zheng-ucenter/zheng-ucenter-dao/src/main/java/com/zheng/ucenter/dao/model/UcenterUserExample.java:17-862 | zheng-ucenter/zheng-ucenter-dao/src/main/java/com/zheng/ucenter/dao/model/UcenterUserLogExample.java:17-452 | zheng-ucenter/zheng-ucenter-dao/src/main/java/com/zheng/ucenter/dao/model/UcenterUserOauthExample.java:17-502 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsLogExample.java:16-1011 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsOrganizationExample.java:16-521 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsPermissionExample.java:16-901 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsRoleExample.java:16-591 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsSystemExample.java:16-931 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsUserExample.java:16-931 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsUserPermissionExample.java:16-441 — before extracting anything, compare `zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleExample.java` and `zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsCategoryExample.java` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 25320 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 `zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleExample.java:16` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (446 lines × 23) · ×1
  • Duplicated block (446 lines × 23) zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleExample.java:16 — zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleExample.java:16-1281 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsCategoryExample.java:16-901 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsCommentExample.java:16-761 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsMenuExample.java:16-591 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsPageExample.java:16-721 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsSystemExample.java:16-591 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsTagExample.java:16-781 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsTopicExample.java:16-531 | zheng-pay/zheng-pay-dao/src/main/java/com/zheng/pay/dao/model/PayInOrderDetailExample.java:16-651 | zheng-pay/zheng-pay-dao/src/main/java/com/zheng/pay/dao/model/PayInOrderExample.java:16-561 | zheng-pay/zheng-pay-dao/src/main/java/com/zheng/pay/dao/model/PayMchExample.java:16-541 | zheng-pay/zheng-pay-dao/src/main/java/com/zheng/pay/dao/model/PayOutOrderExample.java:16-561 | zheng-pay/zheng-pay-dao/src/main/java/com/zheng/pay/dao/model/PayVendorExample.java:16-541 | zheng-pay/zheng-pay-dao/src/main/java/com/zheng/pay/dao/model/PayVestExample.java:16-461 | zheng-ucenter/zheng-ucenter-dao/src/main/java/com/zheng/ucenter/dao/model/UcenterUserDetailsExample.java:17-602 | zheng-ucenter/zheng-ucenter-dao/src/main/java/com/zheng/ucenter/dao/model/UcenterUserExample.java:17-862 | zheng-ucenter/zheng-ucenter-dao/src/main/java/com/zheng/ucenter/dao/model/UcenterUserOauthExample.java:17-502 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsLogExample.java:16-1011 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsOrganizationExample.java:16-521 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsPermissionExample.java:16-901 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsRoleExample.java:16-591 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsSystemExample.java:16-931 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsUserExample.java:16-931 — before extracting anything, compare `zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleExample.java` and `zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsCategoryExample.java` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 25320 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 `zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleExample.java:16` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (316 lines × 36) · ×1
  • Duplicated block (316 lines × 36) zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleCategoryExample.java:16 — zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleCategoryExample.java:16-381 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleExample.java:16-1281 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleTagExample.java:16-381 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsCategoryExample.java:16-901 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsCategoryTagExample.java:16-381 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsCommentExample.java:16-761 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsMenuExample.java:16-591 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsPageExample.java:16-721 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsSettingExample.java:16-401 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsSystemExample.java:16-591 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsTagExample.java:16-781 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsTopicExample.java:16-531 | zheng-pay/zheng-pay-dao/src/main/java/com/zheng/pay/dao/model/PayInOrderDetailExample.java:16-651 | zheng-pay/zheng-pay-dao/src/main/java/com/zheng/pay/dao/model/PayInOrderExample.java:16-561 | zheng-pay/zheng-pay-dao/src/main/java/com/zheng/pay/dao/model/PayMchExample.java:16-541 | zheng-pay/zheng-pay-dao/src/main/java/com/zheng/pay/dao/model/PayOutOrderDetailExample.java:16-391 | zheng-pay/zheng-pay-dao/src/main/java/com/zheng/pay/dao/model/PayOutOrderExample.java:16-561 | zheng-pay/zheng-pay-dao/src/main/java/com/zheng/pay/dao/model/PayPayExample.java:16-391 | zheng-pay/zheng-pay-dao/src/main/java/com/zheng/pay/dao/model/PayTypeExample.java:16-381 | zheng-pay/zheng-pay-dao/src/main/java/com/zheng/pay/dao/model/PayVendorExample.java:16-541 | zheng-pay/zheng-pay-dao/src/main/java/com/zheng/pay/dao/model/PayVestExample.java:16-461 | zheng-ucenter/zheng-ucenter-dao/src/main/java/com/zheng/ucenter/dao/model/UcenterOauthExample.java:16-331 | zheng-ucenter/zheng-ucenter-dao/src/main/java/com/zheng/ucenter/dao/model/UcenterUserDetailsExample.java:17-602 | zheng-ucenter/zheng-ucenter-dao/src/main/java/com/zheng/ucenter/dao/model/UcenterUserExample.java:17-862 | zheng-ucenter/zheng-ucenter-dao/src/main/java/com/zheng/ucenter/dao/model/UcenterUserLogExample.java:17-452 | zheng-ucenter/zheng-ucenter-dao/src/main/java/com/zheng/ucenter/dao/model/UcenterUserOauthExample.java:17-502 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsLogExample.java:16-1011 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsOrganizationExample.java:16-521 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsPermissionExample.java:16-901 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsRoleExample.java:16-591 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsRolePermissionExample.java:16-381 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsSystemExample.java:16-931 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsUserExample.java:16-931 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsUserOrganizationExample.java:16-381 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsUserPermissionExample.java:16-441 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsUserRoleExample.java:16-381 — before extracting anything, compare `zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleExample.java` and `zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsCategoryExample.java` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 25320 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 `zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleCategoryExample.java:16` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (586 lines × 12) · ×1
  • Duplicated block (586 lines × 12) zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleExample.java:16 — zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleExample.java:16-1281 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsCategoryExample.java:16-901 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsCommentExample.java:16-761 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsPageExample.java:16-721 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsTagExample.java:16-781 | zheng-pay/zheng-pay-dao/src/main/java/com/zheng/pay/dao/model/PayInOrderDetailExample.java:16-651 | zheng-ucenter/zheng-ucenter-dao/src/main/java/com/zheng/ucenter/dao/model/UcenterUserDetailsExample.java:17-602 | zheng-ucenter/zheng-ucenter-dao/src/main/java/com/zheng/ucenter/dao/model/UcenterUserExample.java:17-862 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsLogExample.java:16-1011 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsPermissionExample.java:16-901 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsSystemExample.java:16-931 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsUserExample.java:16-931 — before extracting anything, compare `zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleExample.java` and `zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsCategoryExample.java` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 25320 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 `zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleExample.java:16` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (846 lines × 7) · ×1
  • Duplicated block (846 lines × 7) zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleExample.java:16 — zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleExample.java:16-1281 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsCategoryExample.java:16-901 | zheng-ucenter/zheng-ucenter-dao/src/main/java/com/zheng/ucenter/dao/model/UcenterUserExample.java:17-862 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsLogExample.java:16-1011 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsPermissionExample.java:16-901 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsSystemExample.java:16-931 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsUserExample.java:16-931 — before extracting anything, compare `zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleExample.java` and `zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsCategoryExample.java` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 25320 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 `zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleExample.java:16` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (436 lines × 24) · ×1
  • Duplicated block (436 lines × 24) zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleExample.java:16 — zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleExample.java:16-1281 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsCategoryExample.java:16-901 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsCommentExample.java:16-761 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsMenuExample.java:16-591 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsPageExample.java:16-721 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsSystemExample.java:16-591 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsTagExample.java:16-781 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsTopicExample.java:16-531 | zheng-pay/zheng-pay-dao/src/main/java/com/zheng/pay/dao/model/PayInOrderDetailExample.java:16-651 | zheng-pay/zheng-pay-dao/src/main/java/com/zheng/pay/dao/model/PayInOrderExample.java:16-561 | zheng-pay/zheng-pay-dao/src/main/java/com/zheng/pay/dao/model/PayMchExample.java:16-541 | zheng-pay/zheng-pay-dao/src/main/java/com/zheng/pay/dao/model/PayOutOrderExample.java:16-561 | zheng-pay/zheng-pay-dao/src/main/java/com/zheng/pay/dao/model/PayVendorExample.java:16-541 | zheng-pay/zheng-pay-dao/src/main/java/com/zheng/pay/dao/model/PayVestExample.java:16-461 | zheng-ucenter/zheng-ucenter-dao/src/main/java/com/zheng/ucenter/dao/model/UcenterUserDetailsExample.java:17-602 | zheng-ucenter/zheng-ucenter-dao/src/main/java/com/zheng/ucenter/dao/model/UcenterUserExample.java:17-862 | zheng-ucenter/zheng-ucenter-dao/src/main/java/com/zheng/ucenter/dao/model/UcenterUserLogExample.java:17-452 | zheng-ucenter/zheng-ucenter-dao/src/main/java/com/zheng/ucenter/dao/model/UcenterUserOauthExample.java:17-502 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsLogExample.java:16-1011 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsOrganizationExample.java:16-521 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsPermissionExample.java:16-901 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsRoleExample.java:16-591 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsSystemExample.java:16-931 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsUserExample.java:16-931 — before extracting anything, compare `zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleExample.java` and `zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsCategoryExample.java` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 25320 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 `zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleExample.java:16` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (486 lines × 22) · ×1
  • Duplicated block (486 lines × 22) zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleExample.java:16 — zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleExample.java:16-1281 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsCategoryExample.java:16-901 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsCommentExample.java:16-761 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsMenuExample.java:16-591 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsPageExample.java:16-721 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsSystemExample.java:16-591 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsTagExample.java:16-781 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsTopicExample.java:16-531 | zheng-pay/zheng-pay-dao/src/main/java/com/zheng/pay/dao/model/PayInOrderDetailExample.java:16-651 | zheng-pay/zheng-pay-dao/src/main/java/com/zheng/pay/dao/model/PayInOrderExample.java:16-561 | zheng-pay/zheng-pay-dao/src/main/java/com/zheng/pay/dao/model/PayMchExample.java:16-541 | zheng-pay/zheng-pay-dao/src/main/java/com/zheng/pay/dao/model/PayOutOrderExample.java:16-561 | zheng-pay/zheng-pay-dao/src/main/java/com/zheng/pay/dao/model/PayVendorExample.java:16-541 | zheng-ucenter/zheng-ucenter-dao/src/main/java/com/zheng/ucenter/dao/model/UcenterUserDetailsExample.java:17-602 | zheng-ucenter/zheng-ucenter-dao/src/main/java/com/zheng/ucenter/dao/model/UcenterUserExample.java:17-862 | zheng-ucenter/zheng-ucenter-dao/src/main/java/com/zheng/ucenter/dao/model/UcenterUserOauthExample.java:17-502 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsLogExample.java:16-1011 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsOrganizationExample.java:16-521 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsPermissionExample.java:16-901 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsRoleExample.java:16-591 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsSystemExample.java:16-931 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsUserExample.java:16-931 — before extracting anything, compare `zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleExample.java` and `zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsCategoryExample.java` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 25320 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 `zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleExample.java:16` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (996 lines × 2) · ×1
  • Duplicated block (996 lines × 2) zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleExample.java:16 — zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleExample.java:16-1281 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsLogExample.java:16-1011 — before extracting anything, compare `zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleExample.java` and `zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsLogExample.java` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 27852 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleExample.java:16` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (506 lines × 21) · ×1
  • Duplicated block (506 lines × 21) zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleExample.java:16 — zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleExample.java:16-1281 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsCategoryExample.java:16-901 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsCommentExample.java:16-761 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsMenuExample.java:16-591 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsPageExample.java:16-721 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsSystemExample.java:16-591 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsTagExample.java:16-781 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsTopicExample.java:16-531 | zheng-pay/zheng-pay-dao/src/main/java/com/zheng/pay/dao/model/PayInOrderDetailExample.java:16-651 | zheng-pay/zheng-pay-dao/src/main/java/com/zheng/pay/dao/model/PayInOrderExample.java:16-561 | zheng-pay/zheng-pay-dao/src/main/java/com/zheng/pay/dao/model/PayMchExample.java:16-541 | zheng-pay/zheng-pay-dao/src/main/java/com/zheng/pay/dao/model/PayOutOrderExample.java:16-561 | zheng-pay/zheng-pay-dao/src/main/java/com/zheng/pay/dao/model/PayVendorExample.java:16-541 | zheng-ucenter/zheng-ucenter-dao/src/main/java/com/zheng/ucenter/dao/model/UcenterUserDetailsExample.java:17-602 | zheng-ucenter/zheng-ucenter-dao/src/main/java/com/zheng/ucenter/dao/model/UcenterUserExample.java:17-862 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsLogExample.java:16-1011 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsOrganizationExample.java:16-521 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsPermissionExample.java:16-901 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsRoleExample.java:16-591 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsSystemExample.java:16-931 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsUserExample.java:16-931 — before extracting anything, compare `zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleExample.java` and `zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsCategoryExample.java` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 25320 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 `zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleExample.java:16` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (916 lines × 4) · ×1
  • Duplicated block (916 lines × 4) zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleExample.java:16 — zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleExample.java:16-1281 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsLogExample.java:16-1011 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsSystemExample.java:16-931 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsUserExample.java:16-931 — before extracting anything, compare `zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleExample.java` and `zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsLogExample.java` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 27852 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleExample.java:16` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (426 lines × 25) · ×1
  • Duplicated block (426 lines × 25) zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleExample.java:16 — zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleExample.java:16-1281 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsCategoryExample.java:16-901 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsCommentExample.java:16-761 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsMenuExample.java:16-591 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsPageExample.java:16-721 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsSystemExample.java:16-591 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsTagExample.java:16-781 | zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsTopicExample.java:16-531 | zheng-pay/zheng-pay-dao/src/main/java/com/zheng/pay/dao/model/PayInOrderDetailExample.java:16-651 | zheng-pay/zheng-pay-dao/src/main/java/com/zheng/pay/dao/model/PayInOrderExample.java:16-561 | zheng-pay/zheng-pay-dao/src/main/java/com/zheng/pay/dao/model/PayMchExample.java:16-541 | zheng-pay/zheng-pay-dao/src/main/java/com/zheng/pay/dao/model/PayOutOrderExample.java:16-561 | zheng-pay/zheng-pay-dao/src/main/java/com/zheng/pay/dao/model/PayVendorExample.java:16-541 | zheng-pay/zheng-pay-dao/src/main/java/com/zheng/pay/dao/model/PayVestExample.java:16-461 | zheng-ucenter/zheng-ucenter-dao/src/main/java/com/zheng/ucenter/dao/model/UcenterUserDetailsExample.java:17-602 | zheng-ucenter/zheng-ucenter-dao/src/main/java/com/zheng/ucenter/dao/model/UcenterUserExample.java:17-862 | zheng-ucenter/zheng-ucenter-dao/src/main/java/com/zheng/ucenter/dao/model/UcenterUserLogExample.java:17-452 | zheng-ucenter/zheng-ucenter-dao/src/main/java/com/zheng/ucenter/dao/model/UcenterUserOauthExample.java:17-502 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsLogExample.java:16-1011 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsOrganizationExample.java:16-521 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsPermissionExample.java:16-901 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsRoleExample.java:16-591 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsSystemExample.java:16-931 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsUserExample.java:16-931 | zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsUserPermissionExample.java:16-441 — before extracting anything, compare `zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleExample.java` and `zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsCategoryExample.java` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 25320 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 `zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleExample.java:16` 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.
D6 · Cohesion (LCOM4) · Low cohesion · ×1
  • Low cohesion: UpmsUserController (LCOM4 4) zheng-upms/zheng-upms-server/src/main/java/com/zheng/upms/server/controller/manage/UpmsUserController.java:39 — UpmsUserController's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
P1 · CI/CD gates · CI pipeline targets a decommissioned service · ×1
  • CI pipeline targets a decommissioned service — The pipeline is well-formed, but the only CI definition is `.travis.yml`, and its `README.md` build badge still points at `travis-ci.org` — a service shut down in June 2021. No other CI is configured in this repository, so nothing has been building or testing changes here since that shutdown — the steps below describe a gate that is not running. Porting it is mostly mechanical: the build and test commands already written here are what a replacement pipeline would run.
R1 · Type Safety · Type Safety · ×1
  • Type Safety — 0 typed · 14 plain JS — the untyped files are zheng-admin/src/js/admin.js, zheng-admin/src/js/common.js, zheng-admin/src/js/login.js, zheng-admin/src/plugins/My97DatePicker/lang/en.js, zheng-admin/src/plugins/My97DatePicker/lang/zh-cn.js, zheng-admin/src/plugins/My97DatePicker/lang/zh-tw.js (+8 more).
R10 · Code Duplication · Forked directory tree (5 identical files, ~237 KB × 2 trees) · ×1
  • Forked directory tree (5 identical files, ~237 KB × 2 trees) zheng-cms/zheng-cms-web/src/main/webapp/resources/fonts/glyphicons-halflings-regular.svg:1 — zheng-cms/zheng-cms-web/src/main/webapp/resources/ and zheng-ui/zheng-cms-web/ are near-verbatim copies of each other: 5 files are byte-identical under the same relative paths (~237 KB; the trees hold 9 and 23 files). That is one structural fact, not 5 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.
R10 · Code Duplication · Duplicated block (1497 lines × 2 locations) · ×1
  • Duplicated block (1497 lines × 2 locations) zheng-admin/src/plugins/select2/js/select2.full.js:8 — zheng-admin/src/plugins/select2/js/select2.full.js:8 · zheng-admin/src/plugins/select2/js/select2.js:8 — 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 (1256 lines × 2 locations) · ×1
  • Duplicated block (1256 lines × 2 locations) zheng-admin/src/plugins/select2/js/select2.full.js:2977 — zheng-admin/src/plugins/select2/js/select2.full.js:2977 · zheng-admin/src/plugins/select2/js/select2.js:2977 — 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 (681 lines × 2 locations) · ×1
  • Duplicated block (681 lines × 2 locations) zheng-admin/src/plugins/select2/js/select2.full.js:4744 — zheng-admin/src/plugins/select2/js/select2.full.js:4744 · zheng-admin/src/plugins/select2/js/select2.js:4744 — 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 (53 lines × 2 locations) · ×1
  • Duplicated block (53 lines × 2 locations) zheng-admin/src/plugins/select2/js/select2.full.js:6375 — zheng-admin/src/plugins/select2/js/select2.full.js:6375 · zheng-admin/src/plugins/select2/js/select2.js:5664 — 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 (38 lines × 2 locations) · ×1
  • Duplicated block (38 lines × 2 locations) zheng-admin/src/plugins/select2/js/select2.full.js:5700 — zheng-admin/src/plugins/select2/js/select2.full.js:5700 · zheng-admin/src/plugins/select2/js/select2.full.js:5757 — 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.
R10 · Code Duplication · Duplicated block (33 lines × 2 locations) · ×1
  • Duplicated block (33 lines × 2 locations) zheng-admin/src/plugins/select2/js/select2.full.js:6071 — zheng-admin/src/plugins/select2/js/select2.full.js:6071 · zheng-admin/src/plugins/select2/js/select2.full.js:6110 — 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.
R10 · Code Duplication · Duplicated block (16 lines × 2 locations) · ×1
  • Duplicated block (16 lines × 2 locations) zheng-cms/zheng-cms-web/src/main/webapp/resources/js/main.js:2 — zheng-cms/zheng-cms-web/src/main/webapp/resources/js/main.js:2 · zheng-ui/zheng-cms-web/js/main.js:2 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
R10 · Code Duplication · Duplicated block (14 lines × 2 locations) · ×1
  • Duplicated block (14 lines × 2 locations) zheng-admin/src/js/admin.js:153 — zheng-admin/src/js/admin.js:153 · zheng-admin/src/js/admin.js:167 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
R10 · Code Duplication · Duplicated block (12 lines × 2 locations) · ×1
  • Duplicated block (12 lines × 2 locations) zheng-admin/src/js/admin.js:124 — zheng-admin/src/js/admin.js:124 · zheng-admin/src/js/admin.js:159 — 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.
R10 · Code Duplication · Duplicated block (7 lines × 2 locations) · ×1
  • Duplicated block (7 lines × 2 locations) zheng-admin/src/plugins/waves-0.7.5/waves.js:200 — zheng-admin/src/plugins/waves-0.7.5/waves.js:200 · zheng-admin/src/plugins/waves-0.7.5/waves.js:229 — 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.
R10 · Code Duplication · Duplicated block (6 lines × 2 locations) · ×1
  • Duplicated block (6 lines × 2 locations) zheng-admin/src/js/admin.js:35 — zheng-admin/src/js/admin.js:35 · zheng-admin/src/js/admin.js:48 — 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.
R2 · Cyclomatic Complexity · Complex function handler (cyclomatic 27, cognitive 28) · ×1
  • Complex function handler (cyclomatic 27, cognitive 28) zheng-admin/src/plugins/select2/js/select2.full.js:6247 — handler has cyclomatic complexity 27 and cognitive complexity 28; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R3 · Large Files · zheng-admin/src/plugins/select2/js/select2.full.js · ×1
  • zheng-admin/src/plugins/select2/js/select2.full.js: 5184 lines of code zheng-admin/src/plugins/select2/js/select2.full.js:1 — zheng-admin/src/plugins/select2/js/select2.full.js has 5184 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 · zheng-admin/src/plugins/select2/js/select2.js · ×1
  • zheng-admin/src/plugins/select2/js/select2.js: 4622 lines of code zheng-admin/src/plugins/select2/js/select2.js:1 — zheng-admin/src/plugins/select2/js/select2.js has 4622 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 · zheng-admin/src/plugins/waves-0.7.5/waves.js · ×1
  • zheng-admin/src/plugins/waves-0.7.5/waves.js: 450 lines of code zheng-admin/src/plugins/waves-0.7.5/waves.js:1 — zheng-admin/src/plugins/waves-0.7.5/waves.js has 450 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R4 · Test Coverage · Test Coverage · ×1
  • Test Coverage — 0% of 14 production file(s) reachable from 0 test file(s) via the import graph — 'production' here is the RESIDUE: every source file left once tests, tooling, generated output, config, declarations and declaration-only modules, fixture corpora, type fixtures, behaviour-free data modules, re-export barrels, registration/constant data modules and service workers are set aside, so the percentage is taken over a smaller denominator than the workspace's file count
R7 · Dead Code · Dead file (~6453 LoC) · ×1
  • Dead file (~6453 LoC) zheng-admin/src/plugins/select2/js/select2.full.js — no import path from any entry point (4 application, 0 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~5742 LoC) · ×1
  • Dead file (~5742 LoC) zheng-admin/src/plugins/select2/js/select2.js — no import path from any entry point (4 application, 0 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~582 LoC) · ×1
  • Dead file (~582 LoC) zheng-admin/src/plugins/waves-0.7.5/waves.js — no import path from any entry point (4 application, 0 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~258 LoC) · ×1
  • Dead file (~258 LoC) zheng-admin/src/js/admin.js — no import path from any entry point (4 application, 0 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~125 LoC) · ×1
  • Dead file (~125 LoC) zheng-admin/src/plugins/angular/angular-1.5.8/angular-locale_zh-cn.js — no import path from any entry point (4 application, 0 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~49 LoC) · ×1
  • Dead file (~49 LoC) zheng-admin/src/plugins/bootstrap-table-1.11.0/locale/bootstrap-table-en-US.js — no import path from any entry point (4 application, 0 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~46 LoC) · ×1
  • Dead file (~46 LoC) zheng-admin/src/plugins/bootstrap-table-1.11.0/locale/bootstrap-table-zh-CN.js — no import path from any entry point (4 application, 0 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
S1 · Web-Security Posture · Third-party script without Subresource Integrity · ×1
  • Third-party script without Subresource Integrity REDACTED:28 — `http://code.jquery.com/jquery-1.10.1.min.js` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. The URL also names no version, so it resolves to whatever that origin serves at fetch time — the executed bytes can change with nobody touching this repository. 6 such include(s) across the repository's markup.
Minor — 169 finding(s)
D34 · Knowledge Freshness · Orphaned file · ×109
  • Orphaned file zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsUserExample.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 zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsPermissionExample.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 zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsCategoryExample.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 zheng-ucenter/zheng-ucenter-dao/src/main/java/com/zheng/ucenter/dao/model/UcenterUserExample.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 zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsTagExample.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 zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsCommentExample.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 zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsPageExample.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 zheng-pay/zheng-pay-dao/src/main/java/com/zheng/pay/dao/model/PayInOrderDetailExample.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 zheng-ucenter/zheng-ucenter-dao/src/main/java/com/zheng/ucenter/dao/model/UcenterUserDetailsExample.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 zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsSystemExample.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 zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsRoleExample.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 zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsMenuExample.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 zheng-pay/zheng-pay-dao/src/main/java/com/zheng/pay/dao/model/PayOutOrderExample.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 zheng-pay/zheng-pay-dao/src/main/java/com/zheng/pay/dao/model/PayInOrderExample.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 zheng-pay/zheng-pay-dao/src/main/java/com/zheng/pay/dao/model/PayVendorExample.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 zheng-pay/zheng-pay-dao/src/main/java/com/zheng/pay/dao/model/PayMchExample.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 zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsTopicExample.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 zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsOrganizationExample.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 zheng-ucenter/zheng-ucenter-dao/src/main/java/com/zheng/ucenter/dao/model/UcenterUserOauthExample.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 zheng-common/src/main/java/com/zheng/common/base/BaseServiceImpl.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 zheng-pay/zheng-pay-dao/src/main/java/com/zheng/pay/dao/model/PayVestExample.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 zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsUserPermissionExample.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 zheng-ucenter/zheng-ucenter-dao/src/main/java/com/zheng/ucenter/dao/model/UcenterUserLogExample.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 zheng-upms/zheng-upms-rpc-service/src/main/java/com/zheng/upms/rpc/service/impl/UpmsPermissionServiceImpl.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 zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsSettingExample.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.
  • + 84 more in this group — see findings.md.
X10 · Duplicated predicate · Duplicated predicate · ×25
  • Duplicated predicate zheng-cms/zheng-cms-admin/src/main/java/com/zheng/cms/admin/controller/manage/CmsArticleController.java:65 — `!StringUtils.isBlank(sort) && !StringUtils.isBlank(order)` appears character-identically in 18 files — zheng-cms/zheng-cms-admin/src/main/java/com/zheng/cms/admin/controller/manage/CmsArticleController.java, zheng-cms/zheng-cms-admin/src/main/java/com/zheng/cms/admin/controller/manage/CmsCategoryController.java, zheng-cms/zheng-cms-admin/src/main/java/com/zheng/cms/admin/controller/manage/CmsCommentController.java, zheng-cms/zheng-cms-admin/src/main/java/com/zheng/cms/admin/controller/manage/CmsMenuController.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 zheng-cms/zheng-cms-web/src/main/java/com/zheng/cms/web/interceptor/CmsWebInterceptor.java:31 — `null != request.getHeader("X-Requested-With") && "XMLHttpRequest".equalsIgnoreCase(request.getHeader("X-Requested-With"))` appears character-identically in 4 files — zheng-cms/zheng-cms-web/src/main/java/com/zheng/cms/web/interceptor/CmsWebInterceptor.java, zheng-common/src/main/java/com/zheng/common/base/BaseController.java, zheng-ucenter/zheng-ucenter-web/src/main/java/com/zheng/ucenter/web/interceptor/UcenterWebInterceptor.java, zheng-upms/zheng-upms-server/src/main/java/com/zheng/upms/server/interceptor/UpmsInterceptor.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 zheng-admin/src/plugins/select2/js/select2.full.js:3170 — `!$option.is('option') && !$option.is('optgroup')` appears character-identically in 2 files — zheng-admin/src/plugins/select2/js/select2.full.js, zheng-admin/src/plugins/select2/js/select2.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 zheng-admin/src/plugins/select2/js/select2.full.js:4309 — `!enoughRoomAbove && enoughRoomBelow && isCurrentlyAbove` appears character-identically in 2 files — zheng-admin/src/plugins/select2/js/select2.full.js, zheng-admin/src/plugins/select2/js/select2.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 zheng-admin/src/plugins/select2/js/select2.full.js:4307 — `!enoughRoomBelow && enoughRoomAbove && !isCurrentlyAbove` appears character-identically in 2 files — zheng-admin/src/plugins/select2/js/select2.full.js, zheng-admin/src/plugins/select2/js/select2.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 zheng-admin/src/plugins/select2/js/select2.full.js:171 — `!foundStarMap && starMap && starMap[nameSegment]` appears character-identically in 2 files — zheng-admin/src/plugins/select2/js/select2.full.js, zheng-admin/src/plugins/select2/js/select2.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 zheng-admin/src/plugins/select2/js/select2.full.js:228 — `!hasProp(defined, name) && !hasProp(defining, name)` appears character-identically in 2 files — zheng-admin/src/plugins/select2/js/select2.full.js, zheng-admin/src/plugins/select2/js/select2.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 zheng-admin/src/plugins/select2/js/select2.full.js:467 — `!hasProp(defined, name) && !hasProp(waiting, name)` appears character-identically in 2 files — zheng-admin/src/plugins/select2/js/select2.full.js, zheng-admin/src/plugins/select2/js/select2.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 zheng-admin/src/plugins/select2/js/select2.full.js:3474 — `!results || !results.results || !$.isArray(results.results)` appears character-identically in 2 files — zheng-admin/src/plugins/select2/js/select2.full.js, zheng-admin/src/plugins/select2/js/select2.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 zheng-admin/src/plugins/select2/js/select2.full.js:5010 — `$.fn.jquery && $.fn.jquery.substr(0, 2) == '1.' && $e[0].dataset` appears character-identically in 2 files — zheng-admin/src/plugins/select2/js/select2.full.js, zheng-admin/src/plugins/select2/js/select2.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 zheng-admin/src/plugins/select2/js/select2.full.js:729 — `$el.innerHeight() < el.scrollHeight || $el.innerWidth() < el.scrollWidth` appears character-identically in 2 files — zheng-admin/src/plugins/select2/js/select2.full.js, zheng-admin/src/plugins/select2/js/select2.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 zheng-admin/src/plugins/select2/js/select2.full.js:3486 — `$request.status && $request.status === '0'` appears character-identically in 2 files — zheng-admin/src/plugins/select2/js/select2.full.js, zheng-admin/src/plugins/select2/js/select2.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 zheng-admin/src/plugins/select2/js/select2.full.js:4431 — `(data.element != null && data.element.selected) || (data.element == null && data.selected)` appears character-identically in 2 files — zheng-admin/src/plugins/select2/js/select2.full.js, zheng-admin/src/plugins/select2/js/select2.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 zheng-admin/src/plugins/select2/js/select2.full.js:1429 — `(document.activeElement == self.$selection[0]) || ($.contains(self.$selection[0], document.activeElement))` appears character-identically in 2 files — zheng-admin/src/plugins/select2/js/select2.full.js, zheng-admin/src/plugins/select2/js/select2.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 zheng-admin/src/plugins/select2/js/select2.full.js:911 — `(item.element != null && item.element.selected) || (item.element == null && $.inArray(id, selectedIds) > -1)` appears character-identically in 2 files — zheng-admin/src/plugins/select2/js/select2.full.js, zheng-admin/src/plugins/select2/js/select2.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 zheng-admin/src/plugins/select2/js/select2.full.js:328 — `callbackType === 'undefined' || callbackType === 'function'` appears character-identically in 2 files — zheng-admin/src/plugins/select2/js/select2.full.js, zheng-admin/src/plugins/select2/js/select2.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 zheng-admin/src/plugins/select2/js/select2.full.js:365 — `cjsModule && cjsModule.exports !== undef && cjsModule.exports !== defined[name]` appears character-identically in 2 files — zheng-admin/src/plugins/select2/js/select2.full.js, zheng-admin/src/plugins/select2/js/select2.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 zheng-admin/src/plugins/select2/js/select2.full.js:292 — `config && config.config && config.config[name]` appears character-identically in 2 files — zheng-admin/src/plugins/select2/js/select2.full.js, zheng-admin/src/plugins/select2/js/select2.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 zheng-admin/src/plugins/select2/js/select2.full.js:96 — `config.nodeIdCompat && jsSuffixRegExp.test(name[lastIndex])` appears character-identically in 2 files — zheng-admin/src/plugins/select2/js/select2.full.js, zheng-admin/src/plugins/select2/js/select2.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 zheng-admin/src/plugins/select2/js/select2.full.js:3657 — `container.dropdown.$search || container.selection.$search || $container.find('.select2-search__field')` appears character-identically in 2 files — zheng-admin/src/plugins/select2/js/select2.full.js, zheng-admin/src/plugins/select2/js/select2.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 zheng-admin/src/plugins/select2/js/select2.full.js:4841 — `data.children && data.children.length > 0` appears character-identically in 2 files — zheng-admin/src/plugins/select2/js/select2.full.js, zheng-admin/src/plugins/select2/js/select2.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 zheng-admin/src/plugins/select2/js/select2.full.js:1725 — `data.length == 1 && data[0].id != this.placeholder.id` appears character-identically in 2 files — zheng-admin/src/plugins/select2/js/select2.full.js, zheng-admin/src/plugins/select2/js/select2.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 zheng-admin/src/plugins/select2/js/select2.full.js:839 — `data.results == null || data.results.length === 0` appears character-identically in 2 files — zheng-admin/src/plugins/select2/js/select2.full.js, zheng-admin/src/plugins/select2/js/select2.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 zheng-admin/src/plugins/select2/js/select2.full.js:1968 — `disableInputEvents && evt.type === 'input'` appears character-identically in 2 files — zheng-admin/src/plugins/select2/js/select2.full.js, zheng-admin/src/plugins/select2/js/select2.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 zheng-admin/src/plugins/select2/js/select2.full.js:1187 — `e.deltaY < 0 && bottom <= self.$results.height()` appears character-identically in 2 files — zheng-admin/src/plugins/select2/js/select2.full.js, zheng-admin/src/plugins/select2/js/select2.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.
X4 · Structured logging · Interpolated log message defeats structured logging · ×14
  • Interpolated log message defeats structured logging zheng-common/src/main/java/com/zheng/common/util/RedisUtil.java:71 — `error` at line 71 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 zheng-common/src/main/java/com/zheng/common/util/RedisUtil.java:102 — `error` at line 102 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 zheng-common/src/main/java/com/zheng/common/util/RedisUtil.java:119 — `error` at line 119 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 zheng-common/src/main/java/com/zheng/common/util/RedisUtil.java:134 — `error` at line 134 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 zheng-common/src/main/java/com/zheng/common/util/RedisUtil.java:151 — `error` at line 151 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 zheng-common/src/main/java/com/zheng/common/util/RedisUtil.java:168 — `error` at line 168 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 zheng-common/src/main/java/com/zheng/common/util/RedisUtil.java:212 — `error` at line 212 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 zheng-common/src/main/java/com/zheng/common/util/RedisUtil.java:226 — `error` at line 226 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.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 zheng-common/src/main/java/com/zheng/common/util/RedisUtil.java:241 — `error` at line 241 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 zheng-common/src/main/java/com/zheng/common/util/RedisUtil.java:257 — `error` at line 257 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 zheng-common/src/main/java/com/zheng/common/util/RedisUtil.java:274 — `error` at line 274 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 zheng-upms/zheng-upms-client/src/main/java/com/zheng/upms/client/shiro/listener/UpmsSessionListener.java:17 — `debug` at line 17 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 zheng-upms/zheng-upms-client/src/main/java/com/zheng/upms/client/shiro/listener/UpmsSessionListener.java:22 — `debug` at line 22 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 zheng-upms/zheng-upms-client/src/main/java/com/zheng/upms/client/shiro/listener/UpmsSessionListener.java:27 — `debug` at line 27 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.
D34 · Knowledge Freshness · Most significant orphaned file · ×3
  • Most significant orphaned file zheng-cms/zheng-cms-dao/src/main/java/com/zheng/cms/dao/model/CmsArticleExample.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 zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsLogExample.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 zheng-upms/zheng-upms-dao/src/main/java/com/zheng/upms/dao/model/UpmsSystemExample.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.
D29 · Static Analysis (SAST) · REDACTED · ×2
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×2
  • REDACTED
  • REDACTED
AX6 · Interface segregation · Fat interface · ×1
  • Fat interface: BaseService<Record, Example> (22 abstract methods) zheng-common/src/main/java/com/zheng/common/base/BaseService.java:11 — `BaseService<Record, Example>` declares 22 abstract methods: `countByExample`, `deleteByExample`, `deleteByPrimaryKey`, `deleteByPrimaryKeys`, `initMapper`, `insert`, `insertSelective`, `selectByExample`, `selectByExampleForOffsetPage`, `selectByExampleForStartPage`, `selectByExampleWithBLOBs`, `selectByExampleWithBLOBsForOffsetPage`, `selectByExampleWithBLOBsForStartPage`, `selectByPrimaryKey`, `selectFirstByExample`, `selectFirstByExampleWithBLOBs`, `updateByExample`, `updateByExampleSelective`, `updateByExampleWithBLOBs`, `updateByPrimaryKey`, `updateByPrimaryKeySelective`, `updateByPrimaryKeyWithBLOBs`. 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.
D20 · ADR Quality · No ADRs found · ×1
  • No ADRs found — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`.
D28 · Secrets (history) · Rotate the exposed credentials · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D34 · Knowledge Freshness · Dormant codebase · ×1
  • Dormant codebase — 112 of 112 significant files have no living knowledge — the codebase as a whole is dormant, not 112 separate risks. Counted over 112 of the 374 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.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
M2 · Architecture documentation · No ADRs · ×1
  • No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
M2 · Architecture documentation · No architecture diagram/doc · ×1
  • No architecture diagram/doc — No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
P2 · Observability · Logging is not universal · ×1
  • Logging is not universal — Only 20/28 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `zheng-cms/zheng-cms-dao`, `zheng-message/zheng-message-sdk`, `zheng-pay/zheng-pay-dao`, `zheng-pay/zheng-pay-sdk`, `zheng-ucenter/zheng-ucenter-dao` and 3 more.
P3 · Security & performance tooling · No SAST · ×1
  • No SAST — No static application security testing detected. For this repository's stack, add spotbugs with find-sec-bugs (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 81 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.
P6 · Release Hygiene · No changelog · ×1
  • No changelog — No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
S1 · Web-Security Posture · No security response headers detected · ×1
  • No security response headers detected project-tools/nginx/servers/zheng-ui.conf:1 — None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. This is reported because `zheng-ui.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.)
X5 · Nullable reference types · Java packages are not null-marked everywhere · ×1
  • Java packages are not null-marked everywhere — 0/82 of this repository's Java package directories are under a non-null default: a `package-info.java` declaring `@NullMarked` (JSpecify) or `@NonNullApi`, `@ParametersAreNonnullByDefault`, `@NonNullByDefault`, `@DefaultQualifier(NonNull.class)`; a `module-info.java` declaring `@NullMarked`; every type in it `@NullMarked`; or a build that runs NullAway with the package in `AnnotatedPackages`, or the Checker Framework's `NullnessChecker`. Elsewhere every reference admits null and no checker warns on the dereference that throws a `NullPointerException`.
Minor — 1 finding(s)
D5 · Coupling · Off the main sequence · ×1
  • Off the main sequence: zheng-common — zheng-common: abstractness 0.14, instability 0.00, distance 0.86 — the shape a shared-kernel / building-block library has BY DESIGN — concrete and widely depended-on is what makes it useful, and this dimension does not penalise it (the distance is reported for completeness, not as a defect). Worth a look only if it has grown past one coherent kernel into an everything-bucket.

Appendix B — Reproduction & audit trail

Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-9434cf74aef24f89b5697db5611bb401/history.json --exit-code 0 --source .47artifacts/raw/gitleaks-history.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-9434cf74aef24f89b5697db5611bb401/tree.json --exit-code 0 --source .17artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)semgrep—semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off .18artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiesosv-scanner—osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm .26artifacts/raw/osv-scanner.json
D31 · IaC & Container Securitytrivy—trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.0—
D32 · Data Compliance (PII/GDPR)semgrep—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.0—
D37 · Vulnerability-disclosure Policydisclosure—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.0—
D40 · Network Egress Confinementruntime-hardening—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.0—
D41 · Kernel & Syscall Confinementruntime-hardening—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.0—
D42 · Runtime Threat Enforcementruntime-hardening—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.0—
D43 · Malicious Dependenciesosv-scanner—osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm .0artifacts/raw/osv-scanner.json

Run 01a16ccd-216d-7c3e-aea4-cd8e40741a33 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Issues: 172 · Warnings: 408 · Recommendations: 169 · Info: 1 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 24-10-2026 @ 07:25 UTC.

Downloadable artifacts

Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.

⬇ Findings, MITRE CWE-tagged .sarif⬇ Health changelog .md