Public report of linlinjava/litemall, published 13 November 2026. It has the same score, grades and number of findings as the full report. The details of security findings (where they are in the code, which known vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive report Measured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.3). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey → Signed and filed in the standard's public register, 13 November 2026, 14:06 UTC · Survey ID cd_c0971a256ac947aa86bc16f8c13e3eca

linlinjava/litemall

Measured 13 November 2026, 14:06 UTC, at code version a1ef964

Bus factor is not measured: No living knowledge left to concentrate.

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 30out of 100 At risk No change since the last survey

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

A medium codebase: 67,046 lines of product code in 9 projects, tests not counted · Estimated rebuild effort: about 0.4 person-years · Weakest lens: Production Readiness, 21

Findings by how serious they are

167 critical 451 serious 523 minor

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

This survey was produced by

Assert small markCanine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
13 November 2026, 14:06 UTC

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

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

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

70of 70 dimensions measured by tools.
962of 1141 findings point to an exact file and line, so you can open each one in the code. The other 179 concern the repository as a whole, such as missing documentation.
70dimensions across 6 lenses, read from 67,046 lines of product code in 9 projects.
Chapters

Executive summary

linlinjava/litemall is rated At risk because critical security findings are open. Its score is held back because five passwords or keys sit in the current code and we found no automated security scanning of the code, its secrets or its dependencies. It scores 30 out of 100, which the At risk rating leaves unchanged.

Production Readiness, at 21, is the weakest lens and counts most in the score. The best first step is replacing the five exposed passwords or keys and switching the old ones off, worth about 7 points. Fixing the two passwords or keys in the code's history comes next, worth about 5 points. Raising Production Readiness to 70 would lift the score to about 38.

Thirty-six known security holes in the packages the code depends on can be used by attackers. Twenty-nine passwords or keys in the code's history and five in the code are open to anyone who can read the repository, and thirty-six controls can't be used without a mouse. Updating the vulnerable packages, replacing each exposed password or key and making the controls work with a keyboard would close these risks. Pinning each tool to an exact version would fix the seven pipeline tools referenced by a changeable name, and the unsafe setting in infrastructure or container files needs changing to safe values. The 27 images with no text description need a text description.

The product code is 67,046 lines, about €58,000 to rebuild.

A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.

How the score is built: what each lens counts 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 21 · counts for 46%Code Health 28 · counts for 25%Accessibility 34 · counts for 14%Maturity 48 · counts for 8%Architecture 62 · counts for 4%Security and Compliance 69 · counts for 2%

If Production Readiness rose from 21 to 70, the lowest score rated Strong, the score would rise from 30 to about 38.

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

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

  • Code Duplication · Edited copy of a member (69 corresponding lines) litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxCouponController.java
  • Code Duplication · Edited copy of a member (61 corresponding lines) litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxCartController.java
  • Code Duplication · Edited copy of a member (34 corresponding lines) litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxAuthController.java
  • Code Duplication · Edited copy of a member (33 corresponding lines) litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallGoodsService.java
  • Code Duplication · Edited copy of a member (22 corresponding lines) litemall-core/src/main/java/org/linlinjava/litemall/core/util/bcrypt/BCrypt.java
  • Code Duplication · Edited copy of a member (24 corresponding lines) litemall-core/src/main/java/org/linlinjava/litemall/core/qcode/QCodeService.java
  • Code Duplication · Edited copy of a member (20 corresponding lines) litemall-db/src/main/java/org/linlinjava/litemall/db/util/DbUtil.java
  • Code Duplication · Edited copy of a member (17 corresponding lines) litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxStorageController.java
  • Code Duplication · Edited copies of one member (4 members, 19+ corresponding lines) litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallCollectService.java
  • Code Duplication · Edited copies of one member (6 members, 18+ corresponding lines) litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallAdService.java
  • Code Duplication · Edited copy of a member (19 corresponding lines) litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallCartService.java
  • Code Duplication · Edited copies of one member (4 members, 18+ corresponding lines) litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminAftersaleController.java
  • Code Duplication · Edited copy of a member (12 corresponding lines) litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminCategoryController.java
  • Code Duplication · Edited copy of a member (22 corresponding lines) litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxCartController.java
  • Code Duplication · Edited copy of a member (16 corresponding lines) litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/task/AdminTaskStartupRunner.java
  • Code Duplication · Edited copy of a member (17 corresponding lines) litemall-core/src/main/java/org/linlinjava/litemall/core/notify/TencentSmsSender.java
  • Code Duplication · Edited copy of a member (11 corresponding lines) litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallCommentService.java
  • Code Duplication · Edited copies of one member (3 members, 16+ corresponding lines) litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallPermissionService.java
  • Code Duplication · Edited copy of a member (15 corresponding lines) litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminBrandController.java
  • Code Duplication · Edited copy of a member (15 corresponding lines) litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminGrouponController.java
  • Code Duplication · Edited copy of a member (14 corresponding lines) litemall-core/src/main/java/org/linlinjava/litemall/core/storage/AliyunStorage.java
  • Code Duplication · Edited copy of a member (16 corresponding lines) litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminAdminController.java
  • Code Duplication · Edited copy of a member (13 corresponding lines) litemall-core/src/main/java/org/linlinjava/litemall/core/storage/QiniuStorage.java
  • Code Duplication · Edited copy of a member (14 corresponding lines) litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallGrouponRulesService.java
  • Code Duplication · Edited copies of one member (8 members, 12+ corresponding lines) litemall-core/src/main/java/org/linlinjava/litemall/core/util/JacksonUtil.java
  • Code Duplication · Edited copy of a member (8 corresponding lines) litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminStatController.java
  • Code Duplication · Edited copies of one member (4 members, 12+ corresponding lines) litemall-core/src/main/java/org/linlinjava/litemall/core/storage/AliyunStorage.java
  • Code Duplication · Edited copy of a member (9 corresponding lines) litemall-core/src/main/java/org/linlinjava/litemall/core/storage/config/StorageAutoConfiguration.java
  • Code Duplication · Edited copy of a member (9 corresponding lines) litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallAftersaleService.java
  • Code Duplication · Edited copy of a member (11 corresponding lines) litemall-db/src/main/java/org/linlinjava/litemall/db/mybatis/JsonIntegerArrayTypeHandler.java
  • Code Duplication · Edited copies of one member (8 members, 8+ corresponding lines) litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallAftersaleService.java
  • Code Duplication · Edited copy of a member (7 corresponding lines) litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallOrderService.java
  • Code Duplication · Edited copy of a member (14 corresponding lines) litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminCouponController.java
  • Code Duplication · Edited copy of a member (7 corresponding lines) REDACTED
  • Code Duplication · Edited copies of one member (3 members, 4+ corresponding lines) litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/service/AdminGoodsService.java
  • Code Duplication · Edited copy of a member (7 corresponding lines) litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminKeywordController.java
  • Code Duplication · Edited copies of one member (6 members, 5+ corresponding lines) litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallAddressService.java
  • Code Duplication · Edited copy of a member (5 corresponding lines) litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallAdminService.java
  • Code Duplication · Edited copy of a member (5 corresponding lines) litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallCouponUserService.java
  • Code Duplication · Edited copies of one member (3 members, 5+ corresponding lines) litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallGoodsAttributeService.java
  • Code Duplication · Edited copy of a member (5 corresponding lines) litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallGoodsService.java
  • Code Duplication · Edited copies of one member (6 members, 4+ corresponding lines) litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminAdminController.java
  • Dependency Vulnerabilities · REDACTED
  • Dependency Hygiene · Unused dependency '@vue/cli-plugin-babel'
  • Dependency Hygiene · Unused dependency '@vue/cli-service'
  • Dependency Hygiene · Unused dependency 'chokidar'
  • Dependency Hygiene · Unused dependency 'core-js'
  • Dependency Hygiene · Unused dependency 'echarts'
  • Dependency Hygiene · Unused dependency 'file-saver'
  • Dependency Hygiene · Unused dependency 'vue-template-compiler'
  • Dependency Hygiene · Unused dependency 'xlsx'
  • Dependency Hygiene · Unused dependency '@vue/cli-plugin-babel'
  • Dependency Hygiene · Unused dependency '@vue/cli-service'
  • Dependency Hygiene · Unused dependency 'vue-template-compiler'
  • Dependency Hygiene · Unused dependency 'vuelidate'
  • Exception handling · Swallowed exception (empty catch) litemall-wx/pages/ucenter/index/index.js
  • Exception handling · Swallowed exception (empty catch) litemall-wx/pages/ucenter/index/index.js
  • Exception handling · Swallowed exception (empty catch) litemall-wx/pages/ucenter/couponSelect/couponSelect.js
  • Exception handling · Swallowed exception (empty catch) litemall-wx/pages/ucenter/couponSelect/couponSelect.js
  • Exception handling · Swallowed exception (empty catch) litemall-wx/lib/vant-weapp/mixins/transition.js
  • Exception handling · Swallowed exception (empty catch) litemall-wx/lib/vant-weapp/mixins/transition.js
  • Exception handling · Swallowed exception (empty catch) litemall-wx/lib/vant-weapp/area/index.js
  • Exception handling · Swallowed exception (empty catch) litemall-wx/lib/vant-weapp/area/index.js
  • Exception handling · Swallowed exception (empty catch) litemall-vue/src/views/user/order-list/index.vue
  • Exception handling · Swallowed exception (empty catch) litemall-vue/src/views/user/order-list/index.vue
  • Exception handling · Swallowed exception (empty catch) litemall-vue/src/views/user/order-list/index.vue
  • Exception handling · Swallowed exception (empty catch) litemall-vue/src/views/user/order-list/index.vue
  • Exception handling · Swallowed exception (empty catch) litemall-vue/src/views/order/order-detail/index.vue
  • Exception handling · Swallowed exception (empty catch) litemall-vue/src/views/order/order-detail/index.vue
  • Exception handling · Swallowed exception (empty catch) litemall-vue/src/views/order/order-detail/index.vue
  • Exception handling · Swallowed exception (empty catch) litemall-vue/src/views/order/order-detail/index.vue
  • Visual & motion safety · Low contrast colour pair in CSS (1.9:1) litemall-admin/src/views/layout/components/TagsView/index.vue
  • Visual & motion safety · Low contrast colour pair in CSS (3.8:1) litemall-admin/src/views/errorPage/404.vue

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

Fixed since the last survey: 160 findings

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

  • Code Duplication · Duplicated block (7 lines × 2) litemall-core/src/main/java/org/linlinjava/litemall/core/system/SystemInistService.java
  • Code Duplication · Duplicated block (6 lines × 3) litemall-core/src/main/java/org/linlinjava/litemall/core/system/SystemInistService.java
  • Code Duplication · Duplicated block (6 lines × 2) litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/service/AdminGoodsService.java
  • REDACTED Scanning · Leaked secret: REDACTED REDACTED
  • REDACTED Scanning · Leaked secret: REDACTED REDACTED
  • REDACTED Scanning · Leaked secret: signing-key REDACTED
  • Secrets (history) · High secret: REDACTED litemall-admin-api/src/main/resources/application-dev.properties
  • Secrets (history) · High secret: REDACTED litemall-all/src/main/resources/application-dev.properties
  • Secrets (history) · REDACTED: REDACTED litemall-all/src/main/resources/application-dev.properties
  • Secrets (history) · High secret: REDACTED litemall-db/src/main/resources/application-dev.properties
  • Secrets (history) · High secret: REDACTED litemall-os-api/src/main/resources/application-dev.properties
  • Secrets (history) · REDACTED: REDACTED litemall-vue/mock/db.json
  • Secrets (history) · High secret: REDACTED litemall-wx-api/src/main/resources/application-dev.properties
  • Secrets (history) · REDACTED: REDACTED litemall-wx-api/src/main/resources/application-dev.properties
  • Code Duplication · Duplicated block (48 lines × 2 locations) litemall-wx/pages/brand/brand.js
  • Code Duplication · Duplicated block with local edits (47 matched lines × 2 locations) litemall-admin/src/views/mall/category.vue
  • Code Duplication · Duplicated block with local edits (45 matched lines × 2 locations) litemall-wx/pages/ucenter/collect/collect.js
  • Code Duplication · Duplicated block (44 lines × 3 locations) litemall-admin/src/views/config/express.vue
  • Code Duplication · Duplicated block with local edits (44 matched lines × 2 locations) litemall-wx/pages/ucenter/aftersale/aftersale.js
  • Code Duplication · Duplicated block (41 lines × 2 locations) REDACTED
  • Code Duplication · Duplicated block (40 lines × 2 locations) litemall-vue/src/views/user/coupon-list/index.vue
  • Code Duplication · Duplicated block (40 lines × 2 locations) litemall-wx/pages/checkout/checkout.js
  • Code Duplication · Duplicated block (40 lines × 2 locations) litemall-wx/utils/util.js
  • Code Duplication · Duplicated block (37 lines × 2 locations) litemall-admin/src/views/promotion/coupon.vue
  • Code Duplication · Duplicated block (37 lines × 4 locations) litemall-admin/src/views/user/address.vue
  • Code Duplication · Duplicated block (37 lines × 2 locations) litemall-wx/app.js
  • Code Duplication · Duplicated block (36 lines × 2 locations) litemall-vue/src/views/items/brand-list/index.vue
  • Code Duplication · Duplicated block with local edits (35 matched lines × 2 locations) renard-wx/pages/groupon/grouponDetail/grouponDetail.js
  • Code Duplication · Duplicated block (33 lines × 2 locations) litemall-admin/src/views/promotion/topic.vue
  • Code Duplication · Duplicated block (32 lines × 2 locations) litemall-admin/src/views/goods/list.vue
  • Code Duplication · Duplicated block (31 lines × 2 locations) litemall-wx/pages/help/help.js
  • Code Duplication · Duplicated block (31 lines × 2 locations) litemall-wx/pages/payResult/payResult.js
  • Code Duplication · Duplicated block with local edits (30 matched lines × 2 locations) litemall-admin/src/views/mall/category.vue
  • Code Duplication · Duplicated block (29 lines × 3 locations) litemall-admin/src/views/mall/issue.vue
  • Code Duplication · Duplicated block (29 lines × 2 locations) renard-wx/pages/goods/goods.js
  • Code Duplication · Duplicated block (28 lines × 5 locations) litemall-admin/src/views/promotion/grouponActivity.vue
  • Code Duplication · Duplicated block (28 lines × 2 locations) litemall-wx/pages/groupon/myGroupon/myGroupon.js
  • Code Duplication · Duplicated block (27 lines × 2 locations) litemall-admin/src/views/goods/comment.vue
  • Code Duplication · Duplicated block (27 lines × 2 locations) litemall-wx/pages/catalog/catalog.js
  • Code Duplication · Duplicated block (24 lines × 6 locations) litemall-admin/src/views/mall/aftersale.vue
  • Code Duplication · Duplicated block with local edits (24 matched lines × 2 locations) litemall-admin/src/views/promotion/coupon.vue
  • Code Duplication · Duplicated block (24 lines × 2 locations) litemall-vue/src/views/items/detail/index.vue
  • Code Duplication · Duplicated block (23 lines × 3 locations) litemall-admin/src/views/goods/create.vue
  • Code Duplication · Duplicated block (23 lines × 7 locations) litemall-admin/src/views/mall/aftersale.vue
  • Code Duplication · Duplicated block (23 lines × 2 locations) litemall-wx/pages/category/category.js
  • Code Duplication · Duplicated block (22 lines × 2 locations) litemall-admin/src/store/modules/tagsView.js
  • Code Duplication · Duplicated block (21 lines × 2 locations) litemall-admin/src/views/mall/order.vue
  • Code Duplication · Duplicated block with local edits (21 matched lines × 2 locations) litemall-wx/lib/vant-weapp/notice-bar/index.js
  • Code Duplication · Duplicated block (21 lines × 2 locations) litemall-wx/pages/category/category.js
  • Code Duplication · Duplicated block (21 lines × 2 locations) litemall-wx/pages/checkout/checkout.js
  • Code Duplication · Duplicated block (21 lines × 4 locations) litemall-wx/pages/coupon/coupon.js
  • Code Duplication · Duplicated block (21 lines × 2 locations) litemall-wx/pages/ucenter/aftersale/aftersale.js
  • Code Duplication · Duplicated block (21 lines × 2 locations) litemall-wx/pages/ucenter/index/index.js
  • Code Duplication · Duplicated block (20 lines × 2 locations) litemall-wx/pages/goods/goods.js
  • Code Duplication · Duplicated block with local edits (19 matched lines × 2 locations) litemall-admin/src/components/ScrollPane/index.vue
  • Code Duplication · Duplicated block (19 lines × 2 locations) litemall-admin/src/views/mall/order.vue
  • Code Duplication · Duplicated block (19 lines × 2 locations) litemall-admin/src/views/promotion/couponDetail.vue
  • Code Duplication · Duplicated block (19 lines × 2 locations) REDACTED
  • Code Duplication · Duplicated block with local edits (19 matched lines × 2 locations) litemall-wx/lib/vant-weapp/notify/index.js
  • Code Duplication · Duplicated block (18 lines × 3 locations) litemall-admin/src/views/config/mall.vue
  • Code Duplication · Duplicated block (18 lines × 2 locations) litemall-wx/pages/category/category.js
  • Code Duplication · Duplicated block (17 lines × 2 locations) litemall-admin/src/views/stat/goods.vue
  • Code Duplication · Duplicated block (16 lines × 3 locations) litemall-admin/src/views/profile/notice.vue
  • Code Duplication · Duplicated block (16 lines × 2 locations) litemall-admin/src/views/sys/role.vue
  • Code Duplication · Duplicated block (16 lines × 2 locations) litemall-wx/lib/vant-weapp/checkbox-group/index.js
  • Code Duplication · Duplicated block (16 lines × 2 locations) litemall-wx/lib/vant-weapp/checkbox-group/index.js
  • Code Duplication · Duplicated block (16 lines × 2 locations) litemall-wx/pages/groupon/grouponDetail/grouponDetail.js
  • Code Duplication · Duplicated block with local edits (15 matched lines × 2 locations) litemall-wx/lib/vant-weapp/sidebar/index.js
  • Code Duplication · Duplicated block (15 lines × 3 locations) litemall-wx/pages/checkout/checkout.js
  • Code Duplication · Duplicated block (15 lines × 2 locations) litemall-wx/pages/topicDetail/topicDetail.js
  • Code Duplication · Duplicated block (15 lines × 2 locations) litemall-wx/pages/ucenter/aftersaleDetail/aftersaleDetail.js
  • Code Duplication · Duplicated block (14 lines × 2 locations) litemall-admin/src/views/promotion/coupon.vue
  • Code Duplication · Duplicated block (14 lines × 3 locations) litemall-admin/src/views/stat/goods.vue
  • Code Duplication · Duplicated block (14 lines × 2 locations) litemall-vue/src/views/items/category/index.vue
  • Code Duplication · Duplicated block (14 lines × 2 locations) litemall-wx/pages/auth/accountLogin/accountLogin.js
  • Code Duplication · Duplicated block (14 lines × 2 locations) litemall-wx/pages/index/index.js
  • Code Duplication · Duplicated block with local edits (14 matched lines × 2 locations) renard-wx/pages/ucenter/coupon/coupon.js
  • Code Duplication · Duplicated block (13 lines × 3 locations) litemall-admin/src/views/goods/edit.vue
  • Code Duplication · Duplicated block (13 lines × 2 locations) litemall-admin/src/views/mall/category.vue
  • Code Duplication · Duplicated block (13 lines × 3 locations) litemall-vue/src/views/items/brand/index.vue
  • Code Duplication · Duplicated block (13 lines × 2 locations) litemall-vue/src/views/login/forget-status/index.vue
  • Code Duplication · Duplicated block (13 lines × 2 locations) litemall-vue/src/views/user/user-information-set/set-mobile/index.vue
  • Code Duplication · Duplicated block (13 lines × 2 locations) litemall-wx/lib/vant-weapp/collapse/index.js
  • Code Duplication · Duplicated block with local edits (13 matched lines × 2 locations) litemall-wx/lib/vant-weapp/sticky/index.js
  • Code Duplication · Duplicated block (13 lines × 4 locations) litemall-wx/pages/checkout/checkout.js
  • Code Duplication · Duplicated block (12 lines × 11 locations) litemall-admin/src/views/goods/list.vue
  • Code Duplication · Duplicated block with local edits (12 matched lines × 2 locations) litemall-admin/src/views/goods/list.vue
  • Code Duplication · Duplicated block (12 lines × 3 locations) litemall-vue/src/views/login/forget-status/index.vue
  • Code Duplication · Duplicated block (12 lines × 3 locations) litemall-wx/lib/vant-weapp/area/index.js
  • Code Duplication · Duplicated block with local edits (12 matched lines × 2 locations) litemall-wx/lib/vant-weapp/dropdown-menu/index.js
  • Code Duplication · Duplicated block with local edits (12 matched lines × 2 locations) litemall-wx/lib/vant-weapp/slider/index.js
  • Code Duplication · Duplicated block (12 lines × 2 locations) litemall-wx/pages/topicDetail/topicDetail.js
  • Code Duplication · Duplicated block (11 lines × 2 locations) litemall-admin/src/components/ScrollPane/index.vue
  • Code Duplication · Duplicated block with local edits (11 matched lines × 2 locations) litemall-admin/src/directive/permission/permission.js
  • Code Duplication · Duplicated block (11 lines × 7 locations) litemall-vue/src/views/order/order-detail/index.vue
  • Code Duplication · Duplicated block (11 lines × 3 locations) litemall-wx/lib/vant-weapp/area/index.js
  • Code Duplication · Duplicated block with local edits (11 matched lines × 2 locations) litemall-wx/lib/vant-weapp/collapse/index.js
  • Code Duplication · Duplicated block (11 lines × 3 locations) litemall-wx/pages/help/help.js
  • Code Duplication · Duplicated block (11 lines × 2 locations) renard-wx/pages/groupon/myGroupon/myGroupon.js
  • Code Duplication · Duplicated block (10 lines × 4 locations) litemall-admin/src/views/goods/create.vue
Rebuild cost: about €58,000 · Estimate
Cost to rebuild€19,000 to €97,000, for 320 to 1,016 hours of work, about 0.4 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 30. 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: 67,046 lines of product code
What it is notNot a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.

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

Top priorities

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

1
Resolve the 5 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2), REDACTED, REDACTED.
Raises the score by about 7 points · Low effort · REDACTED Scanning
2
Resolve the 2 REDACTED finding(s) in REDACTED Scanning — start with REDACTED (2).
Raises the score by about 5 points · Low effort · REDACTED Scanning
3
Resolve the 42 No direct assertions finding(s) in Test Quality — start with BCryptTest.java (12), DbTest.java (4), SmsTest.java (4).
Raises the score by about 3 points · Medium 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 €58,000 to build again, about 0.4 person-years of work. Its weakest lens is Production Readiness, at 21 (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 5 Leaked secret finding(s) in REDACTED Scanning. Of all the actions in this report, it raises the score most for the work it takes: about 7 points for low effort, because it clears the 5 REDACTED Scanning findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort

Architecture — module dependency graph

Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.

arch litemall-admin litemall-admin litemall-admin-api litemall-admin-api litemall-core litemall-core litemall-admin-api->litemall-core litemall-db litemall-db litemall-admin-api->litemall-db litemall-all litemall-all litemall-all->litemall-admin-api litemall-all->litemall-core litemall-all->litemall-db litemall-wx-api litemall-wx-api litemall-all->litemall-wx-api litemall-all-war litemall-all-war litemall-all-war->litemall-admin-api litemall-all-war->litemall-core litemall-all-war->litemall-db litemall-all-war->litemall-wx-api litemall-core->litemall-db litemall-vue litemall-vue litemall-wx-api->litemall-core litemall-wx-api->litemall-db

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.

64 modules, with 53 dependencies between them. One loop runs through 2 of the modules, marked above the diagonal.

The table shows the 40 modules with the most connections; 24 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 litemall-admin.src2 litemall-admin.src.api3 litemall-admin.src.directive4 litemall-admin.src.store.modules5 litemall-admin.src.utils6 litemall-vue.src7 litemall-vue.src.api8 litemall-vue.src.router9 litemall-vue.src.store10 litemall-vue.src.utils11 litemall-wx.lib.vant-weapp12 litemall-wx.lib.vant-weapp.common13 org.linlinjava.litemall.admin.annotation14 org.linlinjava.litemall.admin.vo15 org.linlinjava.litemall.core.express.dao16 org.linlinjava.litemall.core.notify17 org.linlinjava.litemall.core.task18 org.linlinjava.litemall.db.domain19 org.linlinjava.litemall.wx.dto20 org.linlinjava.litemall.wx.vo21 org.linlinjava.litemall.admin.dto22 org.linlinjava.litemall.admin.util23 org.linlinjava.litemall.core.express.config24 org.linlinjava.litemall.core.notify.config25 org.linlinjava.litemall.db.dao26 org.linlinjava.litemall.db.util27 org.linlinjava.litemall.core.express28 org.linlinjava.litemall.db.service29 org.linlinjava.litemall.admin.job30 org.linlinjava.litemall.admin.shiro31 org.linlinjava.litemall.admin.task32 org.linlinjava.litemall.core.storage33 org.linlinjava.litemall.core.system34 org.linlinjava.litemall.wx.task35 org.linlinjava.litemall.core.qcode36 org.linlinjava.litemall.core.storage.config37 org.linlinjava.litemall.admin.service38 org.linlinjava.litemall.wx.service39 org.linlinjava.litemall.admin.web40 org.linlinjava.litemall.wx.web
1 litemall-admin.src
2 litemall-admin.src.api
3 litemall-admin.src.directive
4 litemall-admin.src.store.modules
5 litemall-admin.src.utils
6 litemall-vue.src
7 litemall-vue.src.api
8 litemall-vue.src.router
9 litemall-vue.src.store
10 litemall-vue.src.utils
11 litemall-wx.lib.vant-weapp
12 litemall-wx.lib.vant-weapp.common
13 org.linlinjava.litemall.admin.annotation
14 org.linlinjava.litemall.admin.vo
15 org.linlinjava.litemall.core.express.dao
16 org.linlinjava.litemall.core.notify
17 org.linlinjava.litemall.core.task
18 org.linlinjava.litemall.db.domain
19 org.linlinjava.litemall.wx.dto
20 org.linlinjava.litemall.wx.vo
21 org.linlinjava.litemall.admin.dto4
22 org.linlinjava.litemall.admin.util11
23 org.linlinjava.litemall.core.express.config1
24 org.linlinjava.litemall.core.notify.config3
25 org.linlinjava.litemall.db.dao104
26 org.linlinjava.litemall.db.util1
27 org.linlinjava.litemall.core.express11
28 org.linlinjava.litemall.db.service4539
29 org.linlinjava.litemall.admin.job7
30 org.linlinjava.litemall.admin.shiro3
31 org.linlinjava.litemall.admin.task21
32 org.linlinjava.litemall.core.storage11
33 org.linlinjava.litemall.core.system1
34 org.linlinjava.litemall.wx.task21
35 org.linlinjava.litemall.core.qcode11
36 org.linlinjava.litemall.core.storage.config5
37 org.linlinjava.litemall.admin.service111141
38 org.linlinjava.litemall.wx.service111211191
39 org.linlinjava.litemall.admin.web11116114615
40 org.linlinjava.litemall.wx.web161116615
Uses a module listed above itPart of a loopThe module itself
1 litemall-admin.src2 litemall-admin.src.api3 litemall-admin.src.directive4 litemall-admin.src.store.modules5 litemall-admin.src.utils6 litemall-vue.src7 litemall-vue.src.api8 litemall-vue.src.router9 litemall-vue.src.store10 litemall-vue.src.utils11 litemall-wx.lib.vant-weapp12 litemall-wx.lib.vant-weapp.common13 org.linlinjava.litemall.admin.annotation14 org.linlinjava.litemall.admin.vo15 org.linlinjava.litemall.core.express.dao16 org.linlinjava.litemall.core.notify17 org.linlinjava.litemall.core.task18 org.linlinjava.litemall.db.domain19 org.linlinjava.litemall.wx.dto20 org.linlinjava.litemall.wx.vo21 org.linlinjava.litemall.admin.dto22 org.linlinjava.litemall.admin.util23 org.linlinjava.litemall.core.express.config24 org.linlinjava.litemall.core.notify.config25 org.linlinjava.litemall.db.dao26 org.linlinjava.litemall.db.util27 org.linlinjava.litemall.core.express28 org.linlinjava.litemall.db.service29 org.linlinjava.litemall.admin.job30 org.linlinjava.litemall.admin.shiro31 org.linlinjava.litemall.admin.task32 org.linlinjava.litemall.core.storage33 org.linlinjava.litemall.core.system34 org.linlinjava.litemall.wx.task35 org.linlinjava.litemall.core.qcode36 org.linlinjava.litemall.core.storage.config37 org.linlinjava.litemall.admin.service38 org.linlinjava.litemall.wx.service39 org.linlinjava.litemall.admin.web40 org.linlinjava.litemall.wx.weblitemall-admin.src1litemall-admin.src.api2litemall-admin.src.directive3litemall-admin.src.store.modules4litemall-admin.src.utils5litemall-vue.src6litemall-vue.src.api7litemall-vue.src.router8litemall-vue.src.store9litemall-vue.src.utils10litemall-wx.lib.vant-weapp11litemall-wx.lib.vant-weapp.common12org.linlinjava.litemall.admin.annotation13org.linlinjava.litemall.admin.vo14org.linlinjava.litemall.core.express.dao15org.linlinjava.litemall.core.notify16org.linlinjava.litemall.core.task17org.linlinjava.litemall.db.domain18org.linlinjava.litemall.wx.dto19org.linlinjava.litemall.wx.vo20org.linlinjava.litemall.admin.dto21org.linlinjava.litemall.admin.util22org.linlinjava.litemall.core.express.config23org.linlinjava.litemall.core.notify.config24org.linlinjava.litemall.db.dao25org.linlinjava.litemall.db.util26org.linlinjava.litemall.core.express27org.linlinjava.litemall.db.service28org.linlinjava.litemall.admin.job29org.linlinjava.litemall.admin.shiro30org.linlinjava.litemall.admin.task31org.linlinjava.litemall.core.storage32org.linlinjava.litemall.core.system33org.linlinjava.litemall.wx.task34org.linlinjava.litemall.core.qcode35org.linlinjava.litemall.core.storage.config36org.linlinjava.litemall.admin.service37org.linlinjava.litemall.wx.service38org.linlinjava.litemall.admin.web39org.linlinjava.litemall.wx.web4041113104111453973211112111511114111121119111116114615161116615+24 more modules (most-connected shown)

At a glance — Code Health · 28% · Weak · gated by R1, R7, X1, X5 ·

At a glance — Architecture · 62% · Adequate · gated by R9 ·

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

At a glance — Readiness · 21% · Critical · gated by D13, R4, R8, P3, P7 ·

At a glance — Security · 69% · Adequate · gated by D28, D29 ·

At a glance — Accessibility · 34% · Weak · gated by AC1, AC4 ·

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
A03:2025 — Software Supply Chain Failures48High / Critical
A07:2025 — Authentication Failures43High / Critical
A05:2025 — Injection33High / Critical
A02:2025 — Security Misconfiguration4High / Critical

Roadmap

Top priorities: Resolve the 5 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2), REDACTED, REDACTED; Resolve the 2 REDACTED finding(s) in REDACTED Scanning — start with REDACTED (2); Resolve the 42 No direct assertions finding(s) in Test Quality — start with BCryptTest.java (12), DbTest.java (4), SmsTest.java (4).

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

Do thisHelpsEffortDimension
Resolve the 5 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2), REDACTED, REDACTED.+7.4 ptsLowREDACTED Scanning
Resolve the 2 REDACTED finding(s) in REDACTED Scanning — start with REDACTED (2).+5.0 ptsLowREDACTED Scanning
Resolve the 42 No direct assertions finding(s) in Test Quality — start with BCryptTest.java (12), DbTest.java (4), SmsTest.java (4).+3.5 ptsMediumTest Quality
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.+3.4 ptsMediumSecurity & performance tooling
Add tests that import the unreached modules (directly or through their public entry).+3.4 ptsMediumTest Coverage
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.+3.4 ptsMediumDependency Hygiene
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with REDACTED.+1.7 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.3 ptsMediumType Safety

File quality

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

FileScoreBandWorst signal
REDACTED0.0SlopDependency Vulnerabilities: Critical CVE: REDACTED
REDACTED0.4SlopStatic Analysis (SAST): High: REDACTED
REDACTED1.1SlopDependency Vulnerabilities: High CVE: REDACTED
REDACTED4.0MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED4.0MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED4.4MixedREDACTED Scanning: Leaked secret: REDACTED
REDACTED4.4MixedREDACTED Scanning: Leaked secret: REDACTED
REDACTED4.4MixedREDACTED Scanning: Leaked secret: REDACTED
REDACTED4.4MixedIaC & Container Security: High IaC: REDACTED
REDACTED4.8MixedSecrets (history): REDACTED: REDACTED
REDACTED4.8MixedDependency Vulnerabilities: Critical CVE: REDACTED
REDACTED5.1MixedREDACTED Scanning: Leaked secret: REDACTED
REDACTED5.1MixedSecrets (history): REDACTED: REDACTED
REDACTED5.7MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED5.8MixedSecrets (history): High secret: REDACTED
REDACTED5.8MixedSecrets (history): High secret: REDACTED
REDACTED5.8MixedSecrets (history): REDACTED: REDACTED
REDACTED5.8MixedSecrets (history): High secret: REDACTED
REDACTED5.8MixedSecrets (history): High secret: REDACTED
REDACTED5.9MixedStatic Analysis (SAST): Medium: 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 — 167

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

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

Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.

Could not be resolved — 13

Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.

Methodology & how to trust this report

This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 70 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.

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

What we checked — 70 dimensions across the health lenses
D1D2D3D4D5D6D10D12D13D14D15D17D19D20D24D26D27D28D29D30D31D34D35D37D43D44AC1AC2AC3AC4AC5AC6AX1AX10AX2AX3AX4AX6M1M2M3M4P1P2P3P4P5P6P7R1R10R11R2R3R4R6R7R8R9S1X1X12X16X18X21X23X24X29X3X5

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, 962 of 1141 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 or a scanner, 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
Canine Code Analyzer 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 · trivy · checkovSecrets in history, SAST, CVEs, IaC & container, PII / GDPR1.86.0 · 0.69.3 · 3.2.533✓ deterministic

Every finding is locatable in findings.md. Run 01a1d53a-cbb6-77ef-8825-bb63e0bd1cbe.

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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.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.
  • D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.java) and this repository declares a JVM test suite (repository root, Maven), but it was not re-run: no test result was produced. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
  • D12 Dependency Hygiene — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Currency was graded against Maven Central, but whether an artifact is DEPRECATED is not: Maven Central publishes no deprecation marker, exactly as rubygems.org does not. Whether one is UNMAINTAINED is not graded either — no registry publishes a maintenance status, and release age does not stand in for one. Two of this dimension's four signals are therefore unread on a Maven tree, and its score reflects currency alone.
  • D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares package.json, but the licence verdict published here was taken over its JVM dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
  • D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. All 250 significant source file(s) were last meaningfully changed so long ago that no living knowledge remains — nothing since has been substantial enough to re-establish ownership (a broad, mechanical sweep that touches many files shallowly does not count, and neither does no activity at all). There is no concentration to measure, so the bus factor is not scored. This is not a clean bill: nobody currently holds working knowledge of this code (see D34 Knowledge Freshness). Counted over 76 of the 566 production source files in this repository: 316 are under the ~2,400-byte size floor this dimension measures over, and the remaining 174 have no attributable history left to measure.
  • D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
  • D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
  • D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
  • D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is a COLLECTOR gap, not an environment fault: no published-package marker D22 reads admitted any project here, so this ecosystem's public API has no collector, and the remedy is to write one — no change to the scan image can close it.
  • D24 Comment Value — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. D24 compares a comment's words with the identifiers, literals and constructs of the code it annotates, using English function-word and rationale lexicons. Comments in another script or language were left unread rather than counted as clean.
  • D24 Comment Value — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
  • AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DockerCompose (REDACTED). compose up failed (exit 17 — an image could not be built) — failed to solve: openjdk:8-jre: failed to resolve source metadata for docker.io/library/openjdk:8-jre: docker.io/library/openjdk:8-jre: not found; runtime evidence skipped.
  • C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
  • C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
  • C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
  • C4 Data Retention — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
  • C5 Data-Subject Rights — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
  • GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and this repository's Java, Vue components is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and this repository's Vue components is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
  • P1 CI/CD gates — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. A CI pipeline exists and the word "test" appears, but no explicit test-runner invocation (your stack's test command, or a test job) was matched — so either the gate runs tests through a step this pass could not recognise, or "test" is incidental here (a path, "latest", a reporter). Which of the two it is cannot be settled from this dimension's evidence; the coverage dimensions report whether a suite exists at all. You can widen what we reach: name the test runner explicitly in the pipeline step (your stack's test command, or a job named for the suite) so the gate is unambiguous to a reader and to this pass.
  • R10 Code Duplication — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 93 further occurrence(s) are not listed individually; the score already reflects all 133.
  • R7 Dead Code — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 67 further occurrence(s) are not listed individually; the score already reflects all 107.
  • X1 Async correctness — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
  • X12 Unreachable branch — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
  • X27 Collection changed while being enumerated — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.

Repo exclusion declarations: 8 pattern(s) declared (.gitattributes linguist-generated/vendored, .editorconfig generated_code) excluded 0 source file(s) from code-quality scoring. Declarations are the repo's own visible statement that a tree is machine-written or vendored — auditable in any diff, honored by GitHub the same way.

Limitations & what we did not check

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

Per-dimension blind spots

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

  • D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
  • D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
  • D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
  • D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
  • D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
  • D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
  • D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
  • D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
  • D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
  • D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
  • D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
  • D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
  • D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
  • D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
  • D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
  • D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
  • D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
  • D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
  • D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
  • D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
  • D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
  • D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
  • D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
  • D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
  • D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
  • AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
  • AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
  • AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
  • AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
  • AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
  • AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
  • AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
  • M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
  • P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
  • P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
  • P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.

Dimensions

D1 · Cyclomatic Complexity6.8 / 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.8 / 10 · rule-coverage 100% · ceiling Prevented

28 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was WxOrderService.submit at 48.

showdown.showdown.Converter (cyclomatic 46) · ×2REDACTED:708
htmlparser.HTMLParser (cyclomatic 36) · ×2litemall-wx/lib/wxParse/htmlparser.js:35
showdown.validate (cyclomatic 26) · ×2REDACTED:307
showdown.showdown.subParser("tables") (cyclomatic 21) · ×2REDACTED:2387
(anonymous) (cyclomatic 21) · ×2REDACTED:2387

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

What to do

  1. Bring the 20 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with WxOrderService.submit (cyclomatic 48), showdown.showdown.Converter (cyclomatic 46), showdown.showdown.Converter (cyclomatic 46). — 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 20 together lifts Cyclomatic Complexity from 6.8 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.

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

D2 · Cognitive Complexity6.2 / 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 6.2 / 10 · rule-coverage 100% · ceiling Prevented

57 method(s) exceeded the cognitive complexity threshold of 15; the worst was WxOrderService.submit at 82.

(anonymous)::writeImageTag (cognitive 22) · ×4REDACTED:1910
HTMLParser (cognitive 79) · ×2litemall-wx/lib/wxParse/htmlparser.js:35
showdown.validate (cognitive 56) · ×2REDACTED:307
html2json (cognitive 33) · ×2litemall-wx/lib/wxParse/html2json.js:54
(anonymous) (cognitive 32) · ×2REDACTED:2003

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

What to do

  1. Bring the 11 bodies over 30 down to 30 or less in Cognitive Complexity — start with WxOrderService.submit (cognitive 82), HTMLParser (cognitive 79), HTMLParser (cognitive 79). — 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 11 together lifts Cognitive Complexity from 6.2 to about 7.3/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.

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

D3 · God Classes9.8 / 10Stronggated by 5 serious findings✓ Tool-verified

What it measures: Over-large classes that try to do too much ("god classes").

Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.

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

5 god class(es) detected.

FileTooLong: REDACTED · ×3REDACTED
MethodTooLong: WxOrderService.submitlitemall-wx-api/src/main/java/org/linlinjava/litemall/wx/service/WxOrderService.java:248
ClassTooLong: WxOrderServicelitemall-wx-api/src/main/java/org/linlinjava/litemall/wx/service/WxOrderService.java:69

What to do

  1. Resolve the 3 FileTooLong finding(s) in God Classes — start with REDACTED (2), WxOrderService.java. — One of this dimension's main actionable groups (3 warning-level).
  2. Resolve the 1 MethodTooLong finding(s) in God Classes — start with WxOrderService.java. — One of this dimension's main actionable groups (1 warning-level).
  3. Resolve the 1 ClassTooLong finding(s) in God Classes — start with WxOrderService.java. — One of this dimension's main actionable groups (1 warning-level).

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

D4 · Code Duplication9.5 / 10Stronggated by 119 serious findings✓ 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.5 / 10 · rule-coverage 100% · ceiling Verified

71 duplicated block group(s) detected. A further 48 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted. Measured on part of this repository only: .js, .vue (70% of production source) was not exposed to THIS dimension's token comparison and is not in this count; duplication there is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream.

Duplicated block (5 lines × 2) · ×7litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminNoticeController.java:62
Duplicated block (9 lines × 2) · ×6litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/service/AdminGoodsService.java:145
Duplicated block (8 lines × 2) · ×5litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminRegionController.java:52
Duplicated block (12 lines × 2) · ×4litemall-db/src/main/java/org/linlinjava/litemall/db/util/DbUtil.java:18
Duplicated block (7 lines × 2) · ×4litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminCategoryController.java:147

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

What to do

  1. Resolve the 7 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with AdminNoticeController.java, AdminStorageController.java, LitemallGrouponRulesService.java. — One of this dimension's main actionable groups (7 warning-level).
  2. Resolve the 6 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with AdminGoodsService.java, PermissionUtil.java, AdminCategoryController.java. — One of this dimension's main actionable groups (6 warning-level).
  3. Resolve the 5 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with BCrypt.java (2), AdminRegionController.java, WxOrderService.java. — One of this dimension's main actionable groups (5 warning-level).

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

D5 · Coupling8.0 / 10Strong✓ Tool-verified

What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.

Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.

Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.

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

8 production modules (Maven+npm), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 2 module(s) off the main sequence, with abstractness counted on 6 of the 8 (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: litemall-db · ×2

What to do

  1. Resolve the 2 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (2 warning-level).

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

D6 · Cohesion (LCOM4)10.0 / 10Exemplary✓ 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 10.0 / 10 · rule-coverage 100% · ceiling Verified

0 of 163 classes have LCOM4 above 3.

✓ On the Gold path — maintain.

Detailed fixes: d6_recommendation.md.

D10 · Test Quality9.1 / 10Stronggated by 5 serious findings✓ 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 9.1 / 10 · rule-coverage 100% · ceiling Prevented

0 skipped, 45 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 50 tests (3 harness-style project(s) excluded from the assertion penalty).

No assertions: test · ×3litemall-all/src/test/java/org/linlinjava/litemall/allinone/AllinoneConfigTest.java:19
Test project verifies nothing: litemall-all · ×2litemall-all/src/test/java/org/linlinjava/litemall/allinone/AllinoneConfigTest.java:19
No direct assertions: test · ×42litemall-admin-api/src/test/java/org/linlinjava/litemall/admin/AdminConfigTest.java:19

What to do

  1. Resolve the 42 No direct assertions finding(s) in Test Quality — start with BCryptTest.java (12), DbTest.java (4), SmsTest.java (4). — One of this dimension's main actionable groups (42 recommendation-level).
  2. Resolve the 3 No assertions finding(s) in Test Quality — start with AllinoneConfigTest.java, BigDecimalTest.java, WxConfigTest.java. — One of this dimension's main actionable groups (3 warning-level).
  3. Resolve the 2 Test project verifies nothing finding(s) in Test Quality — start with AllinoneConfigTest.java, BigDecimalTest.java. — One of this dimension's main actionable groups (2 warning-level).

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

D12 · Dependency Hygiene8.0 / 10Strong✓ Tool-verified

What it measures: Whether dependencies are current, not deprecated, and not bloated. Known vulnerabilities are D30's.

Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (capped-linear for deprecation, prerelease and outdated) per KLoC. Known-vulnerable packages are D30's and are not charged here (rubric-2026.11.2). Exhaustive.

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

152 outdated artifact(s) of 169 resolved by the build, graded against Maven Central. The poms themselves state a version for only 4 of 49 declaration(s) — the rest are parent- or BOM-managed, which is why this is read from the resolved graph rather than from the manifests. Whether any of these is DEPRECATED is not graded — Maven Central publishes no deprecation marker, exactly as rubygems.org does not. Whether any is UNMAINTAINED is not graded either: no registry publishes a maintenance status, and release age does not stand in for one. Known CVEs in this graph are D30's question, read from the manifest there.

Outdated (compile -- module commons.collections (auto)): commons-collections:commons-collections · ×2
Outdated (compile -- module commons.logging (auto)): commons-logging:commons-logging · ×2
Outdated (compile (optional) -- module spring.boot.devtools [auto]): org.springframework.boot:spring-boot-devtools
Outdated (compile -- module spring.boot [auto]): org.springframework.boot:spring-boot
Outdated (compile -- module spring.context [auto]): org.springframework:spring-context

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

Detailed fixes: d12_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

5 secret(s) detected. 1 detection(s) were excluded as holding no minted credential in material that runs: a name, reference or comparison rather than a value, a readable phrase or pattern, a value that declares itself fake, or development, test, example, mock or demo material. 2 password hash(es) are listed to check and are not counted as leaked credentials.

REDACTED
REDACTED

What to do

  1. Resolve the 5 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (5 issue-level).
  2. Resolve the 2 REDACTED finding(s) in REDACTED Scanning — start with REDACTED (2). — One of this dimension's main actionable groups (2 recommendation-level).

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

D14 · License Compliance10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether the licenses of third-party packages are compatible with your policy.

Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.

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

0 of 4 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 7 Maven/Gradle manifest(s) declare with a version resolvable from the manifest itself — the same declaration-site closure this analysis reads for dependency currency. The JVM has no lockfile a checkout is guaranteed to carry, so this is deliberately NOT the transitive closure. 45 further coordinate(s) are declared with no version at the declaration site — inherited from a parent POM, a BOM or an unresolved Gradle version reference — and are NOT graded: this verdict covers what the checkout pins, not the full transitive graph. ★ COVERAGE OF THIS VERDICT: it grades this repository's JVM dependencies and nothing else. The repository also declares package.json, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.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 Debt9.9 / 10Stronggated by 12 serious findings✓ 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 9.9 / 10 · rule-coverage 100% · ceiling Prevented

12 deducted task-comment markers across 17319 LoC (0.1/KLoC) → score 9.9. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.

TodoComment · ×12litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxCartController.java:63

What to do

  1. Resolve the 12 TodoComment finding(s) in Explicit Debt — start with WxOrderService.java (3), PermissionUtil.java (2), AdminOrderService.java (2). — One of this dimension's main actionable groups (12 warning-level).

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

D19 · Documentation Quality10.0 / 10Exemplary○ Nothing flagged

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

Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.

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

1 of 1 documentation facets pass in full. 16 document(s) read across 3 unit(s).

✓ On the Gold path — maintain.

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: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.

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

No architecture decision records were found.

No ADRs foundlitemall-wx-api/pom.xml:83

What to do

  1. Resolve the 1 No ADRs found finding(s) in ADR Quality — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).

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

D24 · Comment Value9.4 3.8 / 10Weak✓ Tool-verified

What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).

Method: Every inline C# comment compared word by word with the identifiers, literals and constructs of the code it annotates (taken from the syntax); a comment whose words that code already contains is redundant, as are closing-brace labels and generator template text. Comments giving a reason or a reference are kept; other scripts and languages are not judged. Deterministic, exhaustive, advisory.

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

2 of 313 judged comments only repeat the code they sit on (0.6 %). 613 comment(s) in another language or script were not judged.

redundant comment · ×2REDACTED:978
doc comments repeat the names · ×2REDACTED:773

What to do

  1. Resolve the 2 redundant comment finding(s) in Comment Value — start with REDACTED (2). — One of this dimension's main actionable groups (2 recommendation-level).

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

D26 · Project Cohesion7.8 / 10Strong✓ 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.

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

1 of 9 build units (Maven, npm) flagged as possibly oversized/incoherent.

Projects may be oversized for their cohesion

What to do

  1. Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).

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

D27 · Navigability10.0 / 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 10.0 / 10 · rule-coverage 100% · ceiling Documented

89 % of calls cross a namespace and 1 % 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

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

REDACTED
REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 18 REDACTED finding(s) in Secrets (history) — start with REDACTED (5), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (18 issue-level).
  2. Resolve the 11 High secret finding(s) in Secrets (history) — start with REDACTED (5), REDACTED (5), REDACTED. — One of this dimension's main actionable groups (11 issue-level).
  3. Resolve the 6 REDACTED finding(s) in Secrets (history) — start with REDACTED (4), REDACTED (2). — One of this dimension's main actionable groups (6 recommendation-level).

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

D29 · Static Analysis (SAST)2.7 / 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 2.7 / 10 · rule-coverage 100% · ceiling Documented

33 finding(s): 0 critical, 7 high, 25 medium, 1 low. 7 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 4 file(s) — `REDACTED`, `REDACTED`, `litemall-admin/public/index.html` (line 9, line 12), `REDACTED` — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

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

What to do

  1. Resolve the 9 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (9 warning-level).
  2. Resolve the 6 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (6). — One of this dimension's main actionable groups (6 warning-level).
  3. No action in Static Analysis (SAST) — all 7 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (7 issue-level, 0 of them charged here).

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. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.

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

48 finding(s): 12 critical, 24 high, 10 medium, 2 low.

REDACTED
REDACTED
REDACTED
REDACTED

What to do

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

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

D31 · IaC & Container Security9.4 / 10Adequategated by 1 critical finding✓ Tool-verified

What it measures: Whether Dockerfiles / Terraform / Kubernetes config follow security best practices.

Method: IaC/container misconfiguration scan via trivy config (REDACTED/Terraform/K8s/Helm/CloudFormation); severity rules to 0-10 moderate normalizer. NotApplicable without manifests. Exhaustive, deterministic.

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

4 finding(s): 0 critical, 1 high, 2 medium, 1 low.

REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 1 High IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
  2. Resolve the 2 Medium IaC finding(s) in IaC & Container Security — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
  3. Resolve the 1 Low IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d31_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

250 of 250 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is REDACTED. Counted over 250 of the 566 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned file · ×247litemall-core/src/main/java/org/linlinjava/litemall/core/util/bcrypt/BCrypt.java:1
Most significant orphaned file · ×3REDACTED:1
Dormant codebase

What to do

  1. Resolve the 247 Orphaned file finding(s) in Knowledge Freshness — start with REDACTED (28), REDACTED (19), api.js (3). — One of this dimension's main actionable groups (247 recommendation-level).
  2. Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with REDACTED (2), WxOrderService.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.

D37 · Vulnerability-disclosure Policy10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether the repository publishes a coordinated-vulnerability-disclosure policy (SECURITY.md or security.txt) with a reporting contact, so finders know how to report a vulnerability. Presence of a policy file with a contact, not whether the policy is adequate or honoured.

Method: Vulnerability-disclosure policy read deterministically from the repo: a SECURITY.md (root/.github/docs) or .well-known/security.txt / security.txt, regex-checked for a reporting contact (email / URL / mailto). Present + contact → 10; present without a contact → 4; NotApplicable when no policy file exists (it may live off-repo). Detects the policy file's presence + contact, not its adequacy.

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

A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.

✓ On the Gold path — maintain.

Detailed fixes: d37_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. Reported apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.

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

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-Life8.5 / 10Strong✓ 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 8.5 / 10 · rule-coverage 100% · ceiling Documented

0 end-of-life runtime(s) and 1 end-of-life framework(s), read from 1 platform declaration(s) and 11 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.

End-of-life framework: Spring Boot 2REDACTED:1

What to do

  1. Resolve the 1 End-of-life framework finding(s) in Platform End-of-Life — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).

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

Frontend & cross-cutting dimensions

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

AC1 · Text alternatives2.4 / 10Critical✓ Tool-verified

Other · Accessibility — Whether non-text content carries a text alternative — img/area/input[type=image] have alt, a meaningful svg has a title or aria-label, video has a captions track, and object/embed/canvas have a name or fallback content. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: every img/area/input[type=image] checked for alt, svg[role=img] for a title/aria-label, video for a captions <track>. Components skipped, spreads suppressed. Deterministic, hard fact per element.

Coverage: Population: image/media elements — img, area, input[type=image], svg, video, object, embed, canvas — across the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and dynamic-attribute elements are skipped. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is NOT read by any producer, so it contributes no element to this population; where such a frontend is present the card discloses it as an analyzer gap rather than scoring around it.

  • An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative. (×27) — litemall-admin/src/views/errorPage/401.vue:24, litemall-admin/src/views/goods/create.vue:46, litemall-admin/src/views/goods/create.vue:173, …

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 & labels4.4 / 10Weak✓ Tool-verified

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

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

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

  • This <svg> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label. — litemall-admin/src/components/Hamburger/index.vue:0
  • This <i> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label. (×4) — litemall-admin/src/components/Notice/index.vue:4, litemall-admin/src/components/Notice/index.vue:0, litemall-admin/src/components/Screenfull/index.vue:3, …
  • This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. — litemall-vue/src/components/field/index.vue:5
  • This <div> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label. (×8) — litemall-vue/src/views/items/tabbar-catalog.vue:5, litemall-vue/src/views/user/tabbar-user-coupon.vue:11, litemall-vue/src/views/user/tabbar-user-coupon.vue:17, …

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 structure4.8 / 10Weak✓ Tool-verified

Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.

Coverage: Population: the PARSED MARKUP documents (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx). The page-level checks — lang, title, single main landmark — fire ONCE PER FULL DOCUMENT (an <html> root) and never on a partial or component fragment, so a repo of fragments is assessed only on the per-element checks (heading order, table headers, iframe titles, meta-refresh, zoom). Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

  • The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). — litemall-admin/public/index.html:2
  • No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="app">, so there is no content here to wrap — render the <main> from the component mounted into it. — litemall-admin/public/index.html:2
  • user-scalable=no/0 or a maximum-scale below 2 stops low-vision users zooming to 200%. Remove the zoom restriction from the viewport meta. (×2) — litemall-admin/public/index.html:7, litemall-vue/public/index.html:8
  • Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one. — litemall-admin/src/views/errorPage/401.vue:9
  • No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. — litemall-vue/public/index.html:2

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

  • A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler. (×36) — litemall-admin/src/components/BackToTop/index.vue:3, litemall-admin/src/components/Hamburger/index.vue:0, litemall-admin/src/components/Notice/index.vue:4, …
  • An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action. — litemall-admin/src/components/Breadcrumb/index.vue:6
  • A positive tabindex forces a manual tab order that fights the DOM and is fragile. Use tabindex="0" (or restructure the DOM). (×2) — litemall-admin/src/views/login/index.vue:14, litemall-admin/src/views/login/index.vue:21

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 safety5.5 / 10Adequate✓ 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.

  • `&:hover` sets color: #fff on background-color: #b4bccc — 1.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — litemall-admin/src/views/layout/components/TagsView/index.vue:282
  • `&__return-home` sets color: #ffffff on background-color: #1482f0 — 3.8:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — litemall-admin/src/views/errorPage/404.vue:198
  • `.navbar .right-menu: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. — litemall-admin/src/views/layout/components/Navbar.vue:116
  • `.pan-btn` 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. — litemall-admin/src/styles/btn.scss:50
  • `.custom-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. — litemall-admin/src/styles/btn.scss:94
  • `a: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. — litemall-admin/src/styles/index.scss:45
  • `.wscn-http404 .pic-404__child.left` moves (`animation-name: cloudLeft`) 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. — litemall-admin/src/views/errorPage/404.vue:62
  • `.wscn-http404 .pic-404__child.mid` moves (`animation-name: cloudMid`) 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. — litemall-admin/src/views/errorPage/404.vue:73
  • `.wscn-http404 .pic-404__child.right` moves (`animation-name: cloudRight`) 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. — litemall-admin/src/views/errorPage/404.vue:84
  • `.wscn-http404 .bullshit__oops` moves (`animation-name: slideUp`) 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. — litemall-admin/src/views/errorPage/404.vue:171
  • `.wscn-http404 .bullshit__headline` moves (`animation-name: slideUp`) 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. — litemall-admin/src/views/errorPage/404.vue:182
  • `.wscn-http404 .bullshit__info` moves (`animation-name: slideUp`) 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. — litemall-admin/src/views/errorPage/404.vue:193
  • `.wscn-http404 .bullshit__return-home` moves (`animation-name: slideUp`) 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. — litemall-admin/src/views/errorPage/404.vue:211
  • `#app .main-container` moves (`transition: margin-left .28s`) 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. — litemall-admin/src/styles/sidebar.scss:5
  • `#app .sidebar-container` moves (`transition: width 0.28s`) 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. — litemall-admin/src/styles/sidebar.scss:11
  • `#app .mobile .sidebar-container` moves (`transition: transform .28s`) 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. — litemall-admin/src/styles/sidebar.scss:168

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.
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 composition8.3 / 10Strong✓ 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.

AX2 · Stateful singletons7.0 / 10Adequate✓ 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.

  • `LocalStorage` is a singleton (@Bean: the container shares one instance across every request thread) but mutates instance state outside any lock (storagePath, rootLocation; e.g. `storagePath` in `setStoragePath` at line 35). — litemall-core/src/main/java/org/linlinjava/litemall/core/storage/LocalStorage.java:21
  • `QiniuStorage` is a singleton (@Bean: the container shares one instance across every request thread) but mutates instance state outside any lock (auth, bucketManager, uploadManager; e.g. `auth` in `delete` at line 108). — litemall-core/src/main/java/org/linlinjava/litemall/core/storage/QiniuStorage.java:19
  • `TencentStorage` is a singleton (@Bean: the container shares one instance across every request thread) but mutates instance state outside any lock (cosClient; e.g. `cosClient` in `getCOSClient` at line 67). — litemall-core/src/main/java/org/linlinjava/litemall/core/storage/TencentStorage.java:24

What to do

  • Java/Kotlin: keep container singletons stateless — move per-request data into locals or a request-scoped bean — or back the state with java.util.concurrent types (ConcurrentHashMap, AtomicInteger/AtomicReference), guard it with synchronized / a Lock (Kotlin: withLock), or mark a flag that is only ever overwritten volatile (@Volatile).
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.1 / 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.

  • `LitemallAdMapper` declares 18 abstract methods: `countByExample`, `deleteByExample`, `deleteByPrimaryKey`, `insert`, `insertSelective`, `logicalDeleteByExample`, `logicalDeleteByPrimaryKey`, `selectByExample`, `selectByExampleSelective`, `selectByPrimaryKey`, `selectByPrimaryKeySelective`, `selectByPrimaryKeyWithLogicalDelete`, `selectOneByExample`, `selectOneByExampleSelective`, `updateByExample`, `updateByExampleSelective`, `updateByPrimaryKey`, `updateByPrimaryKeySelective`. 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. — litemall-db/src/main/java/org/linlinjava/litemall/db/dao/LitemallAdMapper.java:8
  • `LitemallAddressMapper` declares 18 abstract methods: `countByExample`, `deleteByExample`, `deleteByPrimaryKey`, `insert`, `insertSelective`, `logicalDeleteByExample`, `logicalDeleteByPrimaryKey`, `selectByExample`, `selectByExampleSelective`, `selectByPrimaryKey`, `selectByPrimaryKeySelective`, `selectByPrimaryKeyWithLogicalDelete`, `selectOneByExample`, `selectOneByExampleSelective`, `updateByExample`, `updateByExampleSelective`, `updateByPrimaryKey`, `updateByPrimaryKeySelective`. 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. — litemall-db/src/main/java/org/linlinjava/litemall/db/dao/LitemallAddressMapper.java:8
  • `LitemallAdminMapper` declares 18 abstract methods: `countByExample`, `deleteByExample`, `deleteByPrimaryKey`, `insert`, `insertSelective`, `logicalDeleteByExample`, `logicalDeleteByPrimaryKey`, `selectByExample`, `selectByExampleSelective`, `selectByPrimaryKey`, `selectByPrimaryKeySelective`, `selectByPrimaryKeyWithLogicalDelete`, `selectOneByExample`, `selectOneByExampleSelective`, `updateByExample`, `updateByExampleSelective`, `updateByPrimaryKey`, `updateByPrimaryKeySelective`. 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. — litemall-db/src/main/java/org/linlinjava/litemall/db/dao/LitemallAdminMapper.java:8
  • `LitemallAftersaleMapper` declares 18 abstract methods: `countByExample`, `deleteByExample`, `deleteByPrimaryKey`, `insert`, `insertSelective`, `logicalDeleteByExample`, `logicalDeleteByPrimaryKey`, `selectByExample`, `selectByExampleSelective`, `selectByPrimaryKey`, `selectByPrimaryKeySelective`, `selectByPrimaryKeyWithLogicalDelete`, `selectOneByExample`, `selectOneByExampleSelective`, `updateByExample`, `updateByExampleSelective`, `updateByPrimaryKey`, `updateByPrimaryKeySelective`. 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. — litemall-db/src/main/java/org/linlinjava/litemall/db/dao/LitemallAftersaleMapper.java:8
  • `LitemallBrandMapper` declares 18 abstract methods: `countByExample`, `deleteByExample`, `deleteByPrimaryKey`, `insert`, `insertSelective`, `logicalDeleteByExample`, `logicalDeleteByPrimaryKey`, `selectByExample`, `selectByExampleSelective`, `selectByPrimaryKey`, `selectByPrimaryKeySelective`, `selectByPrimaryKeyWithLogicalDelete`, `selectOneByExample`, `selectOneByExampleSelective`, `updateByExample`, `updateByExampleSelective`, `updateByPrimaryKey`, `updateByPrimaryKeySelective`. 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. — litemall-db/src/main/java/org/linlinjava/litemall/db/dao/LitemallBrandMapper.java:8
  • `LitemallCartMapper` declares 18 abstract methods: `countByExample`, `deleteByExample`, `deleteByPrimaryKey`, `insert`, `insertSelective`, `logicalDeleteByExample`, `logicalDeleteByPrimaryKey`, `selectByExample`, `selectByExampleSelective`, `selectByPrimaryKey`, `selectByPrimaryKeySelective`, `selectByPrimaryKeyWithLogicalDelete`, `selectOneByExample`, `selectOneByExampleSelective`, `updateByExample`, `updateByExampleSelective`, `updateByPrimaryKey`, `updateByPrimaryKeySelective`. 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. — litemall-db/src/main/java/org/linlinjava/litemall/db/dao/LitemallCartMapper.java:8
  • `LitemallCategoryMapper` declares 18 abstract methods: `countByExample`, `deleteByExample`, `deleteByPrimaryKey`, `insert`, `insertSelective`, `logicalDeleteByExample`, `logicalDeleteByPrimaryKey`, `selectByExample`, `selectByExampleSelective`, `selectByPrimaryKey`, `selectByPrimaryKeySelective`, `selectByPrimaryKeyWithLogicalDelete`, `selectOneByExample`, `selectOneByExampleSelective`, `updateByExample`, `updateByExampleSelective`, `updateByPrimaryKey`, `updateByPrimaryKeySelective`. 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. — litemall-db/src/main/java/org/linlinjava/litemall/db/dao/LitemallCategoryMapper.java:8
  • `LitemallCollectMapper` declares 18 abstract methods: `countByExample`, `deleteByExample`, `deleteByPrimaryKey`, `insert`, `insertSelective`, `logicalDeleteByExample`, `logicalDeleteByPrimaryKey`, `selectByExample`, `selectByExampleSelective`, `selectByPrimaryKey`, `selectByPrimaryKeySelective`, `selectByPrimaryKeyWithLogicalDelete`, `selectOneByExample`, `selectOneByExampleSelective`, `updateByExample`, `updateByExampleSelective`, `updateByPrimaryKey`, `updateByPrimaryKeySelective`. 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. — litemall-db/src/main/java/org/linlinjava/litemall/db/dao/LitemallCollectMapper.java:8
  • `LitemallCommentMapper` declares 18 abstract methods: `countByExample`, `deleteByExample`, `deleteByPrimaryKey`, `insert`, `insertSelective`, `logicalDeleteByExample`, `logicalDeleteByPrimaryKey`, `selectByExample`, `selectByExampleSelective`, `selectByPrimaryKey`, `selectByPrimaryKeySelective`, `selectByPrimaryKeyWithLogicalDelete`, `selectOneByExample`, `selectOneByExampleSelective`, `updateByExample`, `updateByExampleSelective`, `updateByPrimaryKey`, `updateByPrimaryKeySelective`. 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. — litemall-db/src/main/java/org/linlinjava/litemall/db/dao/LitemallCommentMapper.java:8
  • `LitemallCouponMapper` declares 18 abstract methods: `countByExample`, `deleteByExample`, `deleteByPrimaryKey`, `insert`, `insertSelective`, `logicalDeleteByExample`, `logicalDeleteByPrimaryKey`, `selectByExample`, `selectByExampleSelective`, `selectByPrimaryKey`, `selectByPrimaryKeySelective`, `selectByPrimaryKeyWithLogicalDelete`, `selectOneByExample`, `selectOneByExampleSelective`, `updateByExample`, `updateByExampleSelective`, `updateByPrimaryKey`, `updateByPrimaryKeySelective`. 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. — litemall-db/src/main/java/org/linlinjava/litemall/db/dao/LitemallCouponMapper.java:8
  • `LitemallCouponUserMapper` declares 18 abstract methods: `countByExample`, `deleteByExample`, `deleteByPrimaryKey`, `insert`, `insertSelective`, `logicalDeleteByExample`, `logicalDeleteByPrimaryKey`, `selectByExample`, `selectByExampleSelective`, `selectByPrimaryKey`, `selectByPrimaryKeySelective`, `selectByPrimaryKeyWithLogicalDelete`, `selectOneByExample`, `selectOneByExampleSelective`, `updateByExample`, `updateByExampleSelective`, `updateByPrimaryKey`, `updateByPrimaryKeySelective`. 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. — litemall-db/src/main/java/org/linlinjava/litemall/db/dao/LitemallCouponUserMapper.java:8
  • `LitemallFeedbackMapper` declares 18 abstract methods: `countByExample`, `deleteByExample`, `deleteByPrimaryKey`, `insert`, `insertSelective`, `logicalDeleteByExample`, `logicalDeleteByPrimaryKey`, `selectByExample`, `selectByExampleSelective`, `selectByPrimaryKey`, `selectByPrimaryKeySelective`, `selectByPrimaryKeyWithLogicalDelete`, `selectOneByExample`, `selectOneByExampleSelective`, `updateByExample`, `updateByExampleSelective`, `updateByPrimaryKey`, `updateByPrimaryKeySelective`. 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. — litemall-db/src/main/java/org/linlinjava/litemall/db/dao/LitemallFeedbackMapper.java:8
  • `LitemallFootprintMapper` declares 18 abstract methods: `countByExample`, `deleteByExample`, `deleteByPrimaryKey`, `insert`, `insertSelective`, `logicalDeleteByExample`, `logicalDeleteByPrimaryKey`, `selectByExample`, `selectByExampleSelective`, `selectByPrimaryKey`, `selectByPrimaryKeySelective`, `selectByPrimaryKeyWithLogicalDelete`, `selectOneByExample`, `selectOneByExampleSelective`, `updateByExample`, `updateByExampleSelective`, `updateByPrimaryKey`, `updateByPrimaryKeySelective`. 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. — litemall-db/src/main/java/org/linlinjava/litemall/db/dao/LitemallFootprintMapper.java:8
  • `LitemallGoodsAttributeMapper` declares 18 abstract methods: `countByExample`, `deleteByExample`, `deleteByPrimaryKey`, `insert`, `insertSelective`, `logicalDeleteByExample`, `logicalDeleteByPrimaryKey`, `selectByExample`, `selectByExampleSelective`, `selectByPrimaryKey`, `selectByPrimaryKeySelective`, `selectByPrimaryKeyWithLogicalDelete`, `selectOneByExample`, `selectOneByExampleSelective`, `updateByExample`, `updateByExampleSelective`, `updateByPrimaryKey`, `updateByPrimaryKeySelective`. 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. — litemall-db/src/main/java/org/linlinjava/litemall/db/dao/LitemallGoodsAttributeMapper.java:8
  • `LitemallGoodsMapper` declares 22 abstract methods: `countByExample`, `deleteByExample`, `deleteByPrimaryKey`, `insert`, `insertSelective`, `logicalDeleteByExample`, `logicalDeleteByPrimaryKey`, `selectByExample`, `selectByExampleSelective`, `selectByExampleWithBLOBs`, `selectByPrimaryKey`, `selectByPrimaryKeySelective`, `selectByPrimaryKeyWithLogicalDelete`, `selectOneByExample`, `selectOneByExampleSelective`, `selectOneByExampleWithBLOBs`, `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. — litemall-db/src/main/java/org/linlinjava/litemall/db/dao/LitemallGoodsMapper.java:8
  • `LitemallGoodsProductMapper` declares 18 abstract methods: `countByExample`, `deleteByExample`, `deleteByPrimaryKey`, `insert`, `insertSelective`, `logicalDeleteByExample`, `logicalDeleteByPrimaryKey`, `selectByExample`, `selectByExampleSelective`, `selectByPrimaryKey`, `selectByPrimaryKeySelective`, `selectByPrimaryKeyWithLogicalDelete`, `selectOneByExample`, `selectOneByExampleSelective`, `updateByExample`, `updateByExampleSelective`, `updateByPrimaryKey`, `updateByPrimaryKeySelective`. 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. — litemall-db/src/main/java/org/linlinjava/litemall/db/dao/LitemallGoodsProductMapper.java:8
  • `LitemallGoodsSpecificationMapper` declares 18 abstract methods: `countByExample`, `deleteByExample`, `deleteByPrimaryKey`, `insert`, `insertSelective`, `logicalDeleteByExample`, `logicalDeleteByPrimaryKey`, `selectByExample`, `selectByExampleSelective`, `selectByPrimaryKey`, `selectByPrimaryKeySelective`, `selectByPrimaryKeyWithLogicalDelete`, `selectOneByExample`, `selectOneByExampleSelective`, `updateByExample`, `updateByExampleSelective`, `updateByPrimaryKey`, `updateByPrimaryKeySelective`. 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. — litemall-db/src/main/java/org/linlinjava/litemall/db/dao/LitemallGoodsSpecificationMapper.java:8
  • `LitemallGrouponMapper` declares 18 abstract methods: `countByExample`, `deleteByExample`, `deleteByPrimaryKey`, `insert`, `insertSelective`, `logicalDeleteByExample`, `logicalDeleteByPrimaryKey`, `selectByExample`, `selectByExampleSelective`, `selectByPrimaryKey`, `selectByPrimaryKeySelective`, `selectByPrimaryKeyWithLogicalDelete`, `selectOneByExample`, `selectOneByExampleSelective`, `updateByExample`, `updateByExampleSelective`, `updateByPrimaryKey`, `updateByPrimaryKeySelective`. 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. — litemall-db/src/main/java/org/linlinjava/litemall/db/dao/LitemallGrouponMapper.java:8
  • `LitemallGrouponRulesMapper` declares 18 abstract methods: `countByExample`, `deleteByExample`, `deleteByPrimaryKey`, `insert`, `insertSelective`, `logicalDeleteByExample`, `logicalDeleteByPrimaryKey`, `selectByExample`, `selectByExampleSelective`, `selectByPrimaryKey`, `selectByPrimaryKeySelective`, `selectByPrimaryKeyWithLogicalDelete`, `selectOneByExample`, `selectOneByExampleSelective`, `updateByExample`, `updateByExampleSelective`, `updateByPrimaryKey`, `updateByPrimaryKeySelective`. 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. — litemall-db/src/main/java/org/linlinjava/litemall/db/dao/LitemallGrouponRulesMapper.java:8
  • `LitemallIssueMapper` declares 18 abstract methods: `countByExample`, `deleteByExample`, `deleteByPrimaryKey`, `insert`, `insertSelective`, `logicalDeleteByExample`, `logicalDeleteByPrimaryKey`, `selectByExample`, `selectByExampleSelective`, `selectByPrimaryKey`, `selectByPrimaryKeySelective`, `selectByPrimaryKeyWithLogicalDelete`, `selectOneByExample`, `selectOneByExampleSelective`, `updateByExample`, `updateByExampleSelective`, `updateByPrimaryKey`, `updateByPrimaryKeySelective`. 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. — litemall-db/src/main/java/org/linlinjava/litemall/db/dao/LitemallIssueMapper.java:8
  • `LitemallKeywordMapper` declares 18 abstract methods: `countByExample`, `deleteByExample`, `deleteByPrimaryKey`, `insert`, `insertSelective`, `logicalDeleteByExample`, `logicalDeleteByPrimaryKey`, `selectByExample`, `selectByExampleSelective`, `selectByPrimaryKey`, `selectByPrimaryKeySelective`, `selectByPrimaryKeyWithLogicalDelete`, `selectOneByExample`, `selectOneByExampleSelective`, `updateByExample`, `updateByExampleSelective`, `updateByPrimaryKey`, `updateByPrimaryKeySelective`. 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. — litemall-db/src/main/java/org/linlinjava/litemall/db/dao/LitemallKeywordMapper.java:8
  • `LitemallLogMapper` declares 18 abstract methods: `countByExample`, `deleteByExample`, `deleteByPrimaryKey`, `insert`, `insertSelective`, `logicalDeleteByExample`, `logicalDeleteByPrimaryKey`, `selectByExample`, `selectByExampleSelective`, `selectByPrimaryKey`, `selectByPrimaryKeySelective`, `selectByPrimaryKeyWithLogicalDelete`, `selectOneByExample`, `selectOneByExampleSelective`, `updateByExample`, `updateByExampleSelective`, `updateByPrimaryKey`, `updateByPrimaryKeySelective`. 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. — litemall-db/src/main/java/org/linlinjava/litemall/db/dao/LitemallLogMapper.java:8
  • `LitemallNoticeAdminMapper` declares 18 abstract methods: `countByExample`, `deleteByExample`, `deleteByPrimaryKey`, `insert`, `insertSelective`, `logicalDeleteByExample`, `logicalDeleteByPrimaryKey`, `selectByExample`, `selectByExampleSelective`, `selectByPrimaryKey`, `selectByPrimaryKeySelective`, `selectByPrimaryKeyWithLogicalDelete`, `selectOneByExample`, `selectOneByExampleSelective`, `updateByExample`, `updateByExampleSelective`, `updateByPrimaryKey`, `updateByPrimaryKeySelective`. 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. — litemall-db/src/main/java/org/linlinjava/litemall/db/dao/LitemallNoticeAdminMapper.java:8
  • `LitemallNoticeMapper` declares 18 abstract methods: `countByExample`, `deleteByExample`, `deleteByPrimaryKey`, `insert`, `insertSelective`, `logicalDeleteByExample`, `logicalDeleteByPrimaryKey`, `selectByExample`, `selectByExampleSelective`, `selectByPrimaryKey`, `selectByPrimaryKeySelective`, `selectByPrimaryKeyWithLogicalDelete`, `selectOneByExample`, `selectOneByExampleSelective`, `updateByExample`, `updateByExampleSelective`, `updateByPrimaryKey`, `updateByPrimaryKeySelective`. 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. — litemall-db/src/main/java/org/linlinjava/litemall/db/dao/LitemallNoticeMapper.java:8
  • `LitemallOrderGoodsMapper` declares 18 abstract methods: `countByExample`, `deleteByExample`, `deleteByPrimaryKey`, `insert`, `insertSelective`, `logicalDeleteByExample`, `logicalDeleteByPrimaryKey`, `selectByExample`, `selectByExampleSelective`, `selectByPrimaryKey`, `selectByPrimaryKeySelective`, `selectByPrimaryKeyWithLogicalDelete`, `selectOneByExample`, `selectOneByExampleSelective`, `updateByExample`, `updateByExampleSelective`, `updateByPrimaryKey`, `updateByPrimaryKeySelective`. 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. — litemall-db/src/main/java/org/linlinjava/litemall/db/dao/LitemallOrderGoodsMapper.java:8
  • `LitemallOrderMapper` declares 18 abstract methods: `countByExample`, `deleteByExample`, `deleteByPrimaryKey`, `insert`, `insertSelective`, `logicalDeleteByExample`, `logicalDeleteByPrimaryKey`, `selectByExample`, `selectByExampleSelective`, `selectByPrimaryKey`, `selectByPrimaryKeySelective`, `selectByPrimaryKeyWithLogicalDelete`, `selectOneByExample`, `selectOneByExampleSelective`, `updateByExample`, `updateByExampleSelective`, `updateByPrimaryKey`, `updateByPrimaryKeySelective`. 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. — litemall-db/src/main/java/org/linlinjava/litemall/db/dao/LitemallOrderMapper.java:8
  • `LitemallPermissionMapper` declares 18 abstract methods: `countByExample`, `deleteByExample`, `deleteByPrimaryKey`, `insert`, `insertSelective`, `logicalDeleteByExample`, `logicalDeleteByPrimaryKey`, `selectByExample`, `selectByExampleSelective`, `selectByPrimaryKey`, `selectByPrimaryKeySelective`, `selectByPrimaryKeyWithLogicalDelete`, `selectOneByExample`, `selectOneByExampleSelective`, `updateByExample`, `updateByExampleSelective`, `updateByPrimaryKey`, `updateByPrimaryKeySelective`. 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. — litemall-db/src/main/java/org/linlinjava/litemall/db/dao/LitemallPermissionMapper.java:8
  • `LitemallRoleMapper` declares 18 abstract methods: `countByExample`, `deleteByExample`, `deleteByPrimaryKey`, `insert`, `insertSelective`, `logicalDeleteByExample`, `logicalDeleteByPrimaryKey`, `selectByExample`, `selectByExampleSelective`, `selectByPrimaryKey`, `selectByPrimaryKeySelective`, `selectByPrimaryKeyWithLogicalDelete`, `selectOneByExample`, `selectOneByExampleSelective`, `updateByExample`, `updateByExampleSelective`, `updateByPrimaryKey`, `updateByPrimaryKeySelective`. 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. — litemall-db/src/main/java/org/linlinjava/litemall/db/dao/LitemallRoleMapper.java:8
  • `LitemallSearchHistoryMapper` declares 18 abstract methods: `countByExample`, `deleteByExample`, `deleteByPrimaryKey`, `insert`, `insertSelective`, `logicalDeleteByExample`, `logicalDeleteByPrimaryKey`, `selectByExample`, `selectByExampleSelective`, `selectByPrimaryKey`, `selectByPrimaryKeySelective`, `selectByPrimaryKeyWithLogicalDelete`, `selectOneByExample`, `selectOneByExampleSelective`, `updateByExample`, `updateByExampleSelective`, `updateByPrimaryKey`, `updateByPrimaryKeySelective`. 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. — litemall-db/src/main/java/org/linlinjava/litemall/db/dao/LitemallSearchHistoryMapper.java:8
  • `LitemallStorageMapper` declares 18 abstract methods: `countByExample`, `deleteByExample`, `deleteByPrimaryKey`, `insert`, `insertSelective`, `logicalDeleteByExample`, `logicalDeleteByPrimaryKey`, `selectByExample`, `selectByExampleSelective`, `selectByPrimaryKey`, `selectByPrimaryKeySelective`, `selectByPrimaryKeyWithLogicalDelete`, `selectOneByExample`, `selectOneByExampleSelective`, `updateByExample`, `updateByExampleSelective`, `updateByPrimaryKey`, `updateByPrimaryKeySelective`. 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. — litemall-db/src/main/java/org/linlinjava/litemall/db/dao/LitemallStorageMapper.java:8
  • `LitemallSystemMapper` declares 18 abstract methods: `countByExample`, `deleteByExample`, `deleteByPrimaryKey`, `insert`, `insertSelective`, `logicalDeleteByExample`, `logicalDeleteByPrimaryKey`, `selectByExample`, `selectByExampleSelective`, `selectByPrimaryKey`, `selectByPrimaryKeySelective`, `selectByPrimaryKeyWithLogicalDelete`, `selectOneByExample`, `selectOneByExampleSelective`, `updateByExample`, `updateByExampleSelective`, `updateByPrimaryKey`, `updateByPrimaryKeySelective`. 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. — litemall-db/src/main/java/org/linlinjava/litemall/db/dao/LitemallSystemMapper.java:8
  • `LitemallTopicMapper` declares 22 abstract methods: `countByExample`, `deleteByExample`, `deleteByPrimaryKey`, `insert`, `insertSelective`, `logicalDeleteByExample`, `logicalDeleteByPrimaryKey`, `selectByExample`, `selectByExampleSelective`, `selectByExampleWithBLOBs`, `selectByPrimaryKey`, `selectByPrimaryKeySelective`, `selectByPrimaryKeyWithLogicalDelete`, `selectOneByExample`, `selectOneByExampleSelective`, `selectOneByExampleWithBLOBs`, `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. — litemall-db/src/main/java/org/linlinjava/litemall/db/dao/LitemallTopicMapper.java:8
  • `LitemallUserMapper` declares 18 abstract methods: `countByExample`, `deleteByExample`, `deleteByPrimaryKey`, `insert`, `insertSelective`, `logicalDeleteByExample`, `logicalDeleteByPrimaryKey`, `selectByExample`, `selectByExampleSelective`, `selectByPrimaryKey`, `selectByPrimaryKeySelective`, `selectByPrimaryKeyWithLogicalDelete`, `selectOneByExample`, `selectOneByExampleSelective`, `updateByExample`, `updateByExampleSelective`, `updateByPrimaryKey`, `updateByPrimaryKeySelective`. 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. — litemall-db/src/main/java/org/linlinjava/litemall/db/dao/LitemallUserMapper.java:8

What to do

  • Split fat interfaces into focused role-interfaces so clients depend only on what they use.
M1 · Documentation (README)6.0 / 10Adequate✓ Tool-verified

Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.

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

What to do

  • 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.
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 repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.

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

M4 · Documentation accuracy10.0 / 10Exemplary○ Nothing flagged

Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.

Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.

P1 · CI/CD gates8.5 / 10Strong✓ Tool-verified

Readiness · Readiness — Whether an automated pipeline builds and tests every change.

Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.

What to do

  • Run the test suite in CI via an explicit runner step (`mvn test` for the toolchain this pipeline already uses) and gate merges on it.
P2 · Observability5.8 / 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 3/5 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `litemall-all`, `litemall-all-war`.

What to do

  • Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
  • Add a health-check endpoint (@godaddy/terminus or a /health route) so orchestrators and load balancers can probe liveness/readiness.
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 1 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:3
  • `litemall-admin/package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — litemall-admin/package.json:45

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.
P4 · Deployment & Rollback8.0 / 10Strong✓ Tool-verified

Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.

Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.

  • Deployment is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever reaches the release trigger goes to production unreviewed, so a mistaken merge or tag is live before anyone can stop it.

What to do

  • Add an approval/environment gate (required reviewers / protection rules) before production promotion.
P5 · DR & Backup4.0 / 10Weak✓ Tool-verified

Readiness · Readiness — Whether disaster recovery is planned and codified — backups, geo-recovery, RTO/RPO, persistence guarantees — from IaC + container manifests + docs, never the live cloud.

Method: Filesystem scan: disaster recovery, backup, geo-recovery, RTO/RPO, persistence guarantees from IaC, manifests, and docs. Exhaustive, deterministic, never a live environment.

What to do

  • Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery).
  • No persistence guard on critical data stores — use Docker named volumes (or your orchestrator's persistent-volume equivalent) so the data store can't be wiped by a container recreate (or, in cloud, set purge-protection / soft-delete / prevent_destroy).
P6 · Release Hygiene10.0 / 10Exemplary✓ 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.

P7 · Outbound HTTP resilience3.0 / 10Weak✓ Tool-verified

Readiness · Readiness — Whether outbound HTTP calls are wrapped in resilience (retry/timeout/circuit-breaker) so a failing dependency doesn't cascade.

Method: Source scan: outbound HTTP clients and what bounds them — resilience handlers (Polly, AddStandardResilienceHandler) on .NET; on Go, the JVM, Python, JavaScript/TypeScript, Ruby, PHP, Rust, Elixir, Swift, Dart and Erlang, a timeout, deadline, retry or breaker beside each call, or a process-wide client default (a framework-wide deadline such as Drupal core's, Laravel's or actix's awc counts). Exhaustive, deterministic.

  • `.openConnection(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. — litemall-core/src/main/java/org/linlinjava/litemall/core/util/HttpUtil.java:37

What to do

  • Set connect and read timeouts on every client (`RestTemplateBuilder.connectTimeout/readTimeout`, WebClient `responseTimeout`, `HttpRequest.Builder.timeout`, `HttpURLConnection.setReadTimeout`, Feign `connectTimeout`/`readTimeout` in configuration), and wrap calls to dependencies in resilience4j `@Retry`/`@CircuitBreaker`/`@TimeLimiter` (or Spring Retry).
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 · 364 plain JS — the untyped files are litemall-admin/src/App.vue, litemall-admin/src/api/ad.js, litemall-admin/src/api/admin.js, litemall-admin/src/api/aftersale.js, litemall-admin/src/api/brand.js, litemall-admin/src/api/category.js (+358 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 Duplication8.7 / 10Strong✓ 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.

  • 61 duplicated blocks under the repository root have copies in at least two of the sibling directories litemall-admin, litemall-vue, litemall-wx, renard-wx — 49 of them are reported below, and 12 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 61 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 61 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 61 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — REDACTED:12
  • 21 duplicated blocks under litemall-admin/src/views/ have copies in at least two of the sibling directories goods, mall, profile, promotion, sys, user — 18 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 21 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 21 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 21 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — litemall-admin/src/views/mall/keyword.vue:113
  • 8 duplicated blocks under litemall-vue/src/views/ have copies in at least two of the sibling directories home, items, login, order, user — 6 of them are reported below, and 2 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 8 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 8 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 8 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — litemall-vue/src/views/order/order-detail/index.vue:114
  • 7 of the duplicated blocks reported below have copies in at least two of the sibling directories checkbox-group, collapse, dialog, dropdown-menu, goods-action, grid (+5 more sibling(s) not listed) under litemall-wx/lib/vant-weapp/. That concentration is one structural fact, not 7 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 7 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — litemall-wx/lib/vant-weapp/checkbox-group/index.js:2
  • REDACTED:12 · REDACTED:12 — these 2 files are line-for-line copies of one another — 1082 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — REDACTED:12
  • litemall-wx/pages/goods/goods.js:175 · renard-wx/pages/goods/goods.js:131 — the two spans are one implementation copied and then locally edited — 1792 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — litemall-wx/pages/goods/goods.js:175
  • litemall-wx/pages/ucenter/addressAdd/addressAdd.js:1 · renard-wx/pages/ucenter/addressAdd/addressAdd.js:1 — these 2 files are line-for-line copies of one another — 241 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — litemall-wx/pages/ucenter/addressAdd/addressAdd.js:1
  • litemall-wx/pages/cart/cart.js:1 · renard-wx/pages/cart/cart.js:1 — these 2 files are line-for-line copies of one another — 216 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — litemall-wx/pages/cart/cart.js:1
  • litemall-wx/lib/wxParse/wxDiscode.js:2 · renard-wx/lib/wxParse/wxDiscode.js:2 — these 2 files are line-for-line copies of one another — 174 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — litemall-wx/lib/wxParse/wxDiscode.js:2
  • litemall-wx/pages/ucenter/orderDetail/orderDetail.js:1 · renard-wx/pages/ucenter/orderDetail/orderDetail.js:1 — these 2 files are line-for-line copies of one another — 151 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — litemall-wx/pages/ucenter/orderDetail/orderDetail.js:1
  • litemall-wx/pages/search/search.js:1 · renard-wx/pages/search/search.js:1 — these 2 files are line-for-line copies of one another — 148 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — litemall-wx/pages/search/search.js:1
  • litemall-wx/lib/wxParse/html2json.js:12 · renard-wx/lib/wxParse/html2json.js:12 — these 2 files are line-for-line copies of one another — 140 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — litemall-wx/lib/wxParse/html2json.js:12
  • litemall-admin/src/views/promotion/topicCreate.vue:118 · litemall-admin/src/views/promotion/topicEdit.vue:118 — these 2 files are line-for-line copies of one another — 114 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — litemall-admin/src/views/promotion/topicCreate.vue:118
  • litemall-admin/src/views/sys/notice.vue:137 · litemall-admin/src/views/sys/role.vue:109 — 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. — litemall-admin/src/views/sys/notice.vue:137
  • litemall-wx/pages/auth/register/register.js:13 · litemall-wx/pages/auth/reset/reset.js:12 — the two spans are one implementation copied and then locally edited — 471 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — litemall-wx/pages/auth/register/register.js:13
  • litemall-wx/pages/commentPost/commentPost.js:2 · litemall-wx/pages/topicCommentPost/topicCommentPost.js:2 · renard-wx/pages/commentPost/commentPost.js:2 — these 3 files are line-for-line copies of one another — 106 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — litemall-wx/pages/commentPost/commentPost.js:2
  • litemall-admin/src/views/mall/keyword.vue:113 · litemall-admin/src/views/sys/notice.vue:138 · litemall-admin/src/views/sys/role.vue:110 — the 3 copies are spread across 3 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. — litemall-admin/src/views/mall/keyword.vue:113
  • litemall-wx/pages/comment/comment.js:1 · litemall-wx/pages/topicComment/topicComment.js:1 — these 2 files are line-for-line copies of one another — 97 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — litemall-wx/pages/comment/comment.js:1
  • litemall-wx/lib/wxParse/htmlparser.js:12 · renard-wx/lib/wxParse/htmlparser.js:12 — these 2 files are line-for-line copies of one another — 94 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — litemall-wx/lib/wxParse/htmlparser.js:12
  • litemall-admin/src/views/goods/create.vue:404 · litemall-admin/src/views/goods/edit.vue:413 — 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. — litemall-admin/src/views/goods/create.vue:404
  • litemall-admin/src/views/mall/issue.vue:113 · litemall-admin/src/views/sys/admin.vue:208 — 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. — litemall-admin/src/views/mall/issue.vue:113
  • litemall-wx/lib/wxParse/wxParse.js:15 · renard-wx/lib/wxParse/wxParse.js:15 — these 2 files are line-for-line copies of one another — 80 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — litemall-wx/lib/wxParse/wxParse.js:15
  • litemall-admin/src/views/sys/admin.vue:208 · litemall-admin/src/views/sys/notice.vue:168 · litemall-admin/src/views/sys/role.vue:140 — the 3 copies are spread across 3 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. — litemall-admin/src/views/sys/admin.vue:208
  • litemall-wx/pages/checkout/checkout.js:98 · renard-wx/pages/shopping/checkout/checkout.js:80 — the two spans are one implementation copied and then locally edited — 375 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — litemall-wx/pages/checkout/checkout.js:98
  • litemall-wx/pages/hotGoods/hotGoods.js:1 · litemall-wx/pages/newGoods/newGoods.js:1 · REDACTED:1 · REDACTED:1 — these 4 files are line-for-line copies of one another — 72 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — litemall-wx/pages/hotGoods/hotGoods.js:1
  • litemall-wx/pages/index/index.js:6 · renard-wx/pages/index/index.js:6 — the two spans are one implementation copied and then locally edited — 370 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — litemall-wx/pages/index/index.js:6
  • litemall-wx/pages/auth/accountLogin/accountLogin.js:5 · litemall-wx/pages/auth/reset/reset.js:4 — the two spans are one implementation copied and then locally edited — 319 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — litemall-wx/pages/auth/accountLogin/accountLogin.js:5
  • litemall-wx/pages/goods/goods.js:55 · renard-wx/pages/goods/goods.js:40 — the two spans are one implementation copied and then locally edited — 423 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — litemall-wx/pages/goods/goods.js:55
  • litemall-admin/src/views/mall/brand.vue:197 · litemall-admin/src/views/sys/admin.vue:216 · litemall-admin/src/views/sys/notice.vue:176 · litemall-admin/src/views/sys/role.vue:148 — the 4 copies are spread across 4 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. — litemall-admin/src/views/mall/brand.vue:197
  • litemall-wx/pages/groupon/grouponList/grouponList.js:2 · renard-wx/pages/groupon/grouponList/grouponList.js:2 — these 2 files are line-for-line copies of one another — 60 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — litemall-wx/pages/groupon/grouponList/grouponList.js:2
  • litemall-wx/pages/topic/topic.js:1 · renard-wx/pages/topic/topic.js:1 — these 2 files are line-for-line copies of one another — 58 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — litemall-wx/pages/topic/topic.js:1
  • litemall-wx/pages/coupon/coupon.js:4 · litemall-wx/pages/groupon/grouponList/grouponList.js:4 · renard-wx/pages/groupon/grouponList/grouponList.js:4 — the 3 copies are spread across 3 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. — litemall-wx/pages/coupon/coupon.js:4
  • litemall-vue/src/views/order/order-detail/index.vue:114 · litemall-vue/src/views/user/order-list/index.vue:116 — the two spans are one implementation copied and then locally edited — 317 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — litemall-vue/src/views/order/order-detail/index.vue:114
  • litemall-wx/pages/auth/login/login.js:5 · renard-wx/pages/auth/login/login.js:5 — 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. — litemall-wx/pages/auth/login/login.js:5
  • litemall-wx/utils/area.js:3227 · renard-wx/utils/area.js:3227 — 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. — litemall-wx/utils/area.js:3227
  • litemall-admin/src/views/user/footprint.vue:37 · litemall-admin/src/views/user/history.vue:36 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — litemall-admin/src/views/user/footprint.vue:37
  • litemall-wx/pages/brandDetail/brandDetail.js:5 · renard-wx/pages/brandDetail/brandDetail.js:4 — 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. — litemall-wx/pages/brandDetail/brandDetail.js:5
  • litemall-wx/pages/ucenter/aftersaleList/aftersaleList.js:13 · litemall-wx/pages/ucenter/order/order.js:23 — 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. — litemall-wx/pages/ucenter/aftersaleList/aftersaleList.js:13
  • litemall-wx/utils/user.js:4 · renard-wx/utils/user.js:4 — these 2 files are line-for-line copies of one another — 53 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — litemall-wx/utils/user.js:4
  • litemall-wx/pages/ucenter/address/address.js:1 · renard-wx/pages/ucenter/address/address.js:1 — these 2 files are line-for-line copies of one another — 52 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — litemall-wx/pages/ucenter/address/address.js:1

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.
R11 · Import Boundaries8.4 / 10Strong✓ Tool-verified

React / JS · Architecture — Conformance to the detected frontend architecture layout (feature-sliced / layered src) plus cross-package deep-import rules (D-386).

Method: Conformance to the detected frontend layout (feature-sliced / layered src) plus cross-package deep-import rules, over the module graph. Deterministic.

  • litemall-admin/src/locales/en.js:2 imports element-ui/lib/locale/lang/en, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — litemall-admin/src/locales/en.js:2
  • litemall-admin/src/locales/zh-Hans.js:2 imports element-ui/lib/locale/lang/zh-CN, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — litemall-admin/src/locales/zh-Hans.js:2
  • litemall-admin/src/main.js:9 imports element-ui/lib/locale, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — litemall-admin/src/main.js:9
  • litemall-admin/src/views/stat/goods.vue:9 imports v-charts/lib/line, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — litemall-admin/src/views/stat/goods.vue:9
  • litemall-admin/src/views/stat/order.vue:9 imports v-charts/lib/line, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — litemall-admin/src/views/stat/order.vue:9
  • litemall-admin/src/views/stat/user.vue:9 imports v-charts/lib/histogram, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — litemall-admin/src/views/stat/user.vue:9

What to do

  • Fix the listed violations: import through public entries (package exports / slice index), never reach into another layer or package's internals.
R2 · Cyclomatic Complexity9.8 / 10Exemplary✓ 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.

  • validate has cyclomatic complexity 26 and cognitive complexity 56; 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) — REDACTED:307, REDACTED:307
  • HTMLParser has cyclomatic complexity 16 and cognitive complexity 44; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. (×2) — litemall-wx/lib/wxParse/htmlparser.js:35, renard-wx/lib/wxParse/htmlparser.js:35
  • writeImageTag has cyclomatic complexity 14 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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) — REDACTED:1910, REDACTED:1888
  • _parseExtension has cyclomatic complexity 14 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. (×2) — REDACTED:778, REDACTED:778
  • getHtml has cyclomatic complexity 13 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. — litemall-admin/src/utils/print.js:42
  • specToProduct has cyclomatic complexity 13 and cognitive complexity 24; 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. — litemall-admin/src/views/goods/create.vue:533
  • (anonymous) has cyclomatic complexity 13 and cognitive complexity 19; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. (×2) — REDACTED:2446, REDACTED:2424
  • moveToTarget has cyclomatic complexity 12 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — litemall-admin/src/components/ScrollPane/index.vue:23
  • rgxFindMatchPos has cyclomatic complexity 11 and cognitive complexity 23; 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) — REDACTED:545, REDACTED:545
R3 · Large Files8.4 / 10Strong✓ Tool-verified

React / JS · Code Health — How many source files exceed the large-file threshold.

Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.

  • litemall-wx/utils/area.js has 3285 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — litemall-wx/utils/area.js:1
  • renard-wx/utils/area.js has 3284 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — renard-wx/utils/area.js:1
  • REDACTED has 2174 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
  • REDACTED has 2154 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
  • litemall-admin/src/views/promotion/coupon.vue has 623 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — litemall-admin/src/views/promotion/coupon.vue:1
  • REDACTED has 609 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
  • litemall-wx/pages/goods/goods.js has 602 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — litemall-wx/pages/goods/goods.js:1
  • litemall-admin/src/views/goods/create.vue has 591 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — litemall-admin/src/views/goods/create.vue:1
  • litemall-admin/src/views/goods/edit.vue has 555 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — litemall-admin/src/views/goods/edit.vue:1
  • renard-wx/pages/goods/goods.js has 547 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — renard-wx/pages/goods/goods.js:1
  • litemall-admin/src/views/mall/order.vue has 532 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — litemall-admin/src/views/mall/order.vue:1
  • litemall-vue/src/api/api.js has 429 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — litemall-vue/src/api/api.js:1
  • litemall-vue/src/views/home/tabbar-home.vue has 412 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — litemall-vue/src/views/home/tabbar-home.vue: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 351 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).
R6 · Tooling6.7 / 10Adequate✓ Tool-verified

React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each package.json script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.

Method: package.json scanned for test/lint/typecheck script wiring. Deterministic presence check.

  • test ✓ · lint ✓ · typecheck ✗ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.

What to do

  • Add type checking (adopt TypeScript, or type-check the existing JavaScript with `checkJs`) as package.json scripts and run them in CI.
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 145 application, 90 tooling and 0 test entry point(s) detected in this repo. Gate removals on `npm run build` — an undetected custom entry would make these reachable.
  • no import path from any entry point (145 application, 90 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 (×39) — REDACTED, REDACTED, litemall-vue/src/api/api.js, …

What to do

  • Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
R8 · Dependency Hygiene0.0 / 10Critical✓ Tool-verified

React / JS · Readiness — npm dependency truthfulness (D-386): unused dependencies, imports not declared anywhere, and type-/test-only packages shipped as production deps.

Method: npm dependency truthfulness: unused dependencies, imports declared nowhere, and type-/test-only packages shipped as production deps — from the manifest + import graph. Deterministic.

  • Imported but not declared in any reachable package.json — installs work only by hoisting accident. (×8) — litemall-wx/lib/wxParse/wxParse.js:16, litemall-wx/lib/wxParse/wxParse.js:15, litemall-admin/src/api/order.js:2, …
  • Declared in litemall-admin/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×9)
  • Declared in litemall-vue/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×4)

What to do

  • Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports0.9 / 10Critical✓ 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.

  • litemall-admin/src/utils/request.js → litemall-admin/src/store/index.js → litemall-admin/src/store/modules/permission.js → REDACTED → litemall-admin/src/views/config/express.vue → litemall-admin/src/api/config.js → litemall-admin/src/utils/request.js (one verified cycle inside a mutually-dependent group of 76 files) — litemall-admin/src/utils/request.js:3

What to do

  • Break each cycle by extracting the shared piece into a module both sides can import.
S1 · Web-Security Posture8.0 / 10Strong✓ Tool-verified

Other · Security — Only what this repository's own non-C# files could be read for was assessed — 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.

  • None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. This is reported because `nginx.conf` is committed to this repository and declares the server that serves it, so the configuration that would carry these headers is in this repository and was read in full. (−2.0 on this card.) — doc/conf/nginx.conf:61

What to do

  • Set security response headers on the surface this repository serves: an `add_header` directive per header in the nginx/Caddy/Apache config, a `_headers` / `vercel.json` / `netlify.toml` entry for a static host, or `helmet()` in the HTTP server. `Content-Security-Policy` is the one that pays for itself first — it is what contains an injected script once one reaches the page — followed by `X-Content-Type-Options: nosniff` and a frame policy (`X-Frame-Options: DENY`, or CSP `frame-ancestors`). Where the app is served from a build container, the header configuration belongs in the image beside the built assets, so it ships with them rather than depending on where it lands.
X1 · Async correctness3.5 / 10Weak✓ Tool-verified

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.

  • The function passed to `new Promise(…)` is `async`. The constructor ignores what its executor returns, so anything this executor throws — every throw inside an `async` function, including after an `await` — rejects a Promise nobody holds instead of the one being constructed: the outer Promise never settles, whoever awaits it hangs, and the error is reported nowhere. If the body needs `await`, it does not need `new Promise` at all: make the enclosing function `async` and `return` the value (or `throw`) directly. If it wraps a callback API, keep the executor synchronous — call the API and `resolve`/`reject` from its callback — and do the awaiting outside it. — litemall-admin/src/store/modules/user.js:104

What to do

  • `async` Promise executor
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.

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.

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.

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.

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 unescaped4.8 / 10Weak✓ Tool-verified

Other · Security — Whether text read out of the document being converted is escaped before it is written into generated markup — a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.

Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF — the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.

  • `val` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — litemall-admin/src/utils/index.js:153
  • `textareas[k2].value` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — litemall-admin/src/utils/print.js:63
  • `goodsDetail` is text this program did not author, and it is written into the text of an element through Vue's `v-html` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — litemall-admin/src/views/goods/list.vue:65
  • `notice.content` is text this program did not author, and it is written into the text of an element through Vue's `v-html` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — litemall-admin/src/views/profile/notice.vue:47
  • `contentDetail` is text this program did not author, and it is written into the text of an element through Vue's `v-html` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. (×2) — litemall-admin/src/views/promotion/topic.vue:37, litemall-admin/src/views/sys/notice.vue:26
  • `goods.info.detail` is text this program did not author, and it is written into the text of an element through Vue's `v-html` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — litemall-vue/src/views/items/detail/index.vue:48
  • `topic.content` is text this program did not author, and it is written into the text of an element through Vue's `v-html` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — litemall-vue/src/views/items/topic/index.vue:4
  • `url` is text this program did not author, and it is written into the start of a URL attribute, where it chooses the scheme through markup this function returns with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. HTML encoding does not help here — a `javascript:` URL contains nothing it changes; allow only http(s) or a relative path. (×4) — REDACTED:1146, REDACTED:1946, REDACTED:1146, …

What to do

  • Each finding names the expression, the attribute it lands in and the line. Confirm the value's origin from the read this analyzer traced, then escape it at the sink or validate it against the shape the attribute accepts before interpolating.
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 handling5.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. (×16) — renard-wx/utils/util.js:44, renard-wx/pages/ucenter/addressAdd/addressAdd.js:349, renard-wx/pages/ucenter/address/address.js:46, …
  • `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it. (×14) — litemall-wx/lib/vant-weapp/picker/index.js:21, litemall-wx/lib/vant-weapp/mixins/transition.js:70, litemall-wx/lib/vant-weapp/mixins/transition.js:100, …
  • `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. — litemall-core/src/main/java/org/linlinjava/litemall/core/util/IpUtil.java:47
  • `.catch(_ => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it. — litemall-admin/src/views/mall/order.vue:460

What to do

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

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 Health28%Weak — gated by R1, R7, X1, X5Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture62%Adequate — gated by R9Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Maturity48%Weak — gated by D34, M2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness21%Critical — gated by D13, R4, R8, P3, P7Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security69%Adequate — gated by D28, D29Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Accessibility34%Weak — gated by AC1, AC4Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Unscored — 3 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.

  • D36 Supply-chain Provenance & Signing — 1 observation(s) recorded · The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files). 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.
  • SC1 Supply-chain hygiene — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X10 Duplicated predicate — 17 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 3 control(s) we could not find positive evidence for

These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.

  • C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
Not included — 52 check(s) not relevant to this codebase

These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.

  • AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • AX7 Slice cohesion — not applicable — not a vertical-slice architecture
  • AX8 Test isolation — no test/production split to check
  • AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
  • AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • AXR1 Runtime accessibility — compose up failed (exit 17 — an image could not be built) — failed to solve: openjdk:8-jre: failed to resolve source metadata for docker.io/library/openjdk:8-jre: docker.io/library/openjdk:8-jre: not found; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
  • C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • D11 Test Reliability — Test reliability not included — the .java suite was found but not re-run
  • D16 Bus Factor — dormant codebase — no living knowledge left to concentrate
  • D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
  • D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; Java, JavaScript not measured.
  • D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
  • D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
  • D25 ADR Conformance — no ADRs to check
  • D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
  • D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
  • D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
  • D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
  • D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
  • D8 Code Coverage — Coverage not included — suite not readable by the collector
  • DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (a Domain/Aggregates/ValueObjects layer)
  • 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.
  • IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
  • P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
  • P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
  • PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `@Benchmark` in a Java, Kotlin or Scala file importing JMH or kotlinx-benchmark, Jetpack Benchmark's `measureRepeated` in a file importing androidx.benchmark, or JMH/kotlinx-benchmark/androidx.benchmark in a REDACTED, Gradle or sbt build, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
  • PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
  • PF3 Async & latency hygiene — Not applicable: this repository declares no async functions, so there is no asynchronous code for a blocking call to stall.
  • 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
  • X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X2 Cancellation propagation — no C# was loaded; this repository's 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
  • X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X27 Collection changed while being enumerated — X27 reached only 26% of this repository's production lines — javascript (49,727 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
  • X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Java was read, and it logs through none that an assembled message defeats: java.util.logging's level methods, log4j 1, commons-logging, JBoss Logging and Flogger take one finished message (as log4net does in C#), or it makes no call through a named logger at all. Calls made through SLF4J or log4j 2 (`org.slf4j.Logger`, `org.apache.logging.log4j.Logger`, Lombok's `@Slf4j`) would be judged.
  • X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

Appendix A — Findings (grouped)

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

Critical — 167 finding(s)
AC1 · Text alternatives · <img> without a text alternative · ×27
  • <img> without a text alternative litemall-admin/src/views/errorPage/401.vue:24 — 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 litemall-admin/src/views/goods/create.vue:46 — 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 litemall-admin/src/views/goods/create.vue:173 — 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 litemall-admin/src/views/goods/create.vue:238 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative litemall-admin/src/views/goods/edit.vue:49 — 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 litemall-admin/src/views/goods/edit.vue:143 — 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 litemall-admin/src/views/goods/edit.vue:201 — 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 litemall-admin/src/views/layout/components/Navbar.vue:24 — 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 litemall-admin/src/views/mall/brand.vue:58 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative litemall-admin/src/views/mall/category.vue:74 — 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 litemall-admin/src/views/mall/category.vue:86 — 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 litemall-admin/src/views/promotion/ad.vue:67 — 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 litemall-admin/src/views/promotion/topicCreate.vue:19 — 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 litemall-admin/src/views/promotion/topicEdit.vue:19 — 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 litemall-admin/src/views/sys/admin.vue:58 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative litemall-vue/src/views/home/tabbar-home.vue:12 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative litemall-vue/src/views/home/tabbar-home.vue:22 — 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 litemall-vue/src/views/home/tabbar-home.vue:92 — 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 litemall-vue/src/views/home/tabbar-home.vue: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.
  • <img> without a text alternative litemall-vue/src/views/home/tabbar-home.vue:161 — 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 litemall-vue/src/views/items/brand-list/index.vue:13 — 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 litemall-vue/src/views/items/brand/index.vue:5 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative litemall-vue/src/views/items/brand/index.vue:23 — 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 litemall-vue/src/views/items/detail/index.vue:5 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative litemall-vue/src/views/items/tabbar-catalog.vue:19 — 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 more in this group — see findings.md.
D30 · Dependency Vulnerabilities · High CVE · ×24
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
AC4 · Keyboard semantics · Click handler on a non-interactive <div> · ×23
  • Click handler on a non-interactive <div> litemall-admin/src/components/BackToTop/index.vue:3 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> litemall-admin/src/views/dashboard/index.vue:6 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> litemall-admin/src/views/dashboard/index.vue:17 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> litemall-admin/src/views/dashboard/index.vue:28 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> litemall-admin/src/views/dashboard/index.vue:39 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> litemall-admin/src/views/layout/Layout.vue:3 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> litemall-vue/src/views/home/tabbar-home.vue:18 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> litemall-vue/src/views/home/tabbar-home.vue:30 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> litemall-vue/src/views/items/brand-list/index.vue:8 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> litemall-vue/src/views/items/search/index.vue:13 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> litemall-vue/src/views/items/tabbar-catalog.vue:5 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> litemall-vue/src/views/items/tabbar-catalog.vue:25 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> litemall-vue/src/views/items/topic-list/index.vue:8 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> litemall-vue/src/views/login/forget/index.vue:13 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> litemall-vue/src/views/login/register-submit/index.vue:4 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> litemall-vue/src/views/order/tabbar-cart.vue:25 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> litemall-vue/src/views/user/tabbar-user-coupon.vue:11 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> litemall-vue/src/views/user/tabbar-user-coupon.vue:17 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> litemall-vue/src/views/user/tabbar-user-coupon.vue:23 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> litemall-vue/src/views/user/tabbar-user-order.vue:10 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> litemall-vue/src/views/user/tabbar-user-order.vue:16 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> litemall-vue/src/views/user/tabbar-user-order.vue:22 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> litemall-vue/src/views/user/tabbar-user-order.vue:28 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
D28 · Secrets (history) · REDACTED · ×18
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D30 · Dependency Vulnerabilities · Critical CVE · ×12
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D28 · Secrets (history) · High secret · ×11
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
AC2 · Forms & labels · Custom control with no accessible name on <div> · ×8
  • Custom control with no accessible name on <div> litemall-vue/src/views/items/tabbar-catalog.vue:5 — This <div> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.
  • Custom control with no accessible name on <div> litemall-vue/src/views/user/tabbar-user-coupon.vue:11 — This <div> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.
  • Custom control with no accessible name on <div> litemall-vue/src/views/user/tabbar-user-coupon.vue:17 — This <div> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.
  • Custom control with no accessible name on <div> litemall-vue/src/views/user/tabbar-user-coupon.vue:23 — This <div> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.
  • Custom control with no accessible name on <div> litemall-vue/src/views/user/tabbar-user-order.vue:10 — This <div> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.
  • Custom control with no accessible name on <div> litemall-vue/src/views/user/tabbar-user-order.vue:16 — This <div> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.
  • Custom control with no accessible name on <div> litemall-vue/src/views/user/tabbar-user-order.vue:22 — This <div> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.
  • Custom control with no accessible name on <div> litemall-vue/src/views/user/tabbar-user-order.vue:28 — This <div> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
AC4 · Keyboard semantics · Click handler on a non-interactive <li> · ×5
  • Click handler on a non-interactive <li> litemall-admin/src/views/layout/components/TagsView/index.vue:20 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <li> litemall-admin/src/views/layout/components/TagsView/index.vue:21 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <li> litemall-admin/src/views/layout/components/TagsView/index.vue:22 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <li> litemall-admin/src/views/layout/components/TagsView/index.vue:23 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <li> litemall-vue/src/views/items/tabbar-catalog.vue:10 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
D13 · REDACTED Scanning · Leaked secret · ×5
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
AC2 · Forms & labels · Custom control with no accessible name on <i> · ×4
  • Custom control with no accessible name on <i> litemall-admin/src/components/Notice/index.vue:4 — This <i> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.
  • Custom control with no accessible name on <i> litemall-admin/src/components/Notice/index.vue — This <i> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.
  • Custom control with no accessible name on <i> litemall-admin/src/components/Screenfull/index.vue:3 — This <i> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.
  • Custom control with no accessible name on <i> litemall-admin/src/components/Screenfull/index.vue — This <i> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.
AC4 · Keyboard semantics · Click handler on a non-interactive <i> · ×4
  • Click handler on a non-interactive <i> litemall-admin/src/components/Notice/index.vue:4 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <i> litemall-admin/src/components/Notice/index.vue — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <i> litemall-admin/src/components/Screenfull/index.vue:3 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <i> litemall-admin/src/components/Screenfull/index.vue — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
AC4 · Keyboard semantics · Click handler on a non-interactive <span> · ×3
  • Click handler on a non-interactive <span> litemall-vue/src/views/order/tabbar-cart.vue:5 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <span> litemall-vue/src/views/user/user-information-set/set-mobile/index.vue:23 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <span> litemall-vue/src/views/user/user-information-set/set-password/index.vue:17 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
AC3 · Page structure · Viewport restricts zoom · ×2
  • Viewport restricts zoom litemall-admin/public/index.html:7 — user-scalable=no/0 or a maximum-scale below 2 stops low-vision users zooming to 200%. Remove the zoom restriction from the viewport meta.
  • Viewport restricts zoom litemall-vue/public/index.html:8 — user-scalable=no/0 or a maximum-scale below 2 stops low-vision users zooming to 200%. Remove the zoom restriction from the viewport meta.
AC2 · Forms & labels · Custom control with no accessible name on <svg> · ×1
  • Custom control with no accessible name on <svg> litemall-admin/src/components/Hamburger/index.vue — This <svg> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.
AC2 · Forms & labels · <input> without a programmatic label · ×1
  • <input> without a programmatic label litemall-vue/src/components/field/index.vue:5 — 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 · ×1
  • <html> without a lang litemall-admin/public/index.html:2 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
AC4 · Keyboard semantics · Click handler on a non-interactive <svg> · ×1
  • Click handler on a non-interactive <svg> litemall-admin/src/components/Hamburger/index.vue — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
D31 · IaC & Container Security · High IaC · ×1
  • REDACTED
R8 · Dependency Hygiene · Unlisted import 'html2json.js' · ×1
  • Unlisted import 'html2json.js' litemall-wx/lib/wxParse/wxParse.js:16 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import 'REDACTED' · ×1
  • Unlisted import 'REDACTED' litemall-wx/lib/wxParse/wxParse.js:15 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import 'qs' · ×1
  • Unlisted import 'qs' litemall-admin/src/api/order.js:2 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import '@/assets' · ×1
  • Unlisted import '@/assets' litemall-vue/src/main.js:5 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import '@/components' · ×1
  • Unlisted import '@/components' litemall-vue/src/App.vue:12 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import '@/filter' · ×1
  • Unlisted import '@/filter' litemall-vue/src/main.js:12 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import '@/utils' · ×1
  • Unlisted import '@/utils' litemall-vue/src/router/index.js:3 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import '@/views' · ×1
  • Unlisted import '@/views' litemall-vue/src/router/home.js:8 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
R9 · Circular Imports · Import cycle (6 files) · ×1
  • Import cycle (6 files) litemall-admin/src/utils/request.js:3 — litemall-admin/src/utils/request.js → litemall-admin/src/store/index.js → litemall-admin/src/store/modules/permission.js → REDACTED → litemall-admin/src/views/config/express.vue → litemall-admin/src/api/config.js → litemall-admin/src/utils/request.js (one verified cycle inside a mutually-dependent group of 76 files)
Serious — 451 finding(s)
X3 · Exception handling · Swallowed exception (empty catch) · ×31
  • Swallowed exception (empty catch) renard-wx/utils/util.js:44 — 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) renard-wx/pages/ucenter/addressAdd/addressAdd.js:349 — 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) renard-wx/pages/ucenter/address/address.js:46 — 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) renard-wx/pages/goods/goods.js:484 — 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) renard-wx/pages/cart/cart.js:258 — 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) litemall-wx/utils/util.js:44 — 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) litemall-wx/pages/ucenter/order/order.js:21 — 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) litemall-wx/pages/ucenter/index/index.js:65 — 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) litemall-wx/pages/ucenter/index/index.js:83 — 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) litemall-wx/pages/ucenter/couponSelect/couponSelect.js:144 — 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) litemall-wx/pages/ucenter/couponSelect/couponSelect.js:155 — 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) litemall-wx/pages/ucenter/addressAdd/addressAdd.js:349 — 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) litemall-wx/pages/ucenter/address/address.js:41 — 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) litemall-wx/pages/goods/goods.js:546 — 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) litemall-wx/pages/checkout/checkout.js:152 — 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) litemall-wx/pages/cart/cart.js:256 — 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) litemall-wx/lib/vant-weapp/picker/index.js:21 — `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
  • Swallowed exception (empty catch) litemall-wx/lib/vant-weapp/mixins/transition.js:70 — `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
  • Swallowed exception (empty catch) litemall-wx/lib/vant-weapp/mixins/transition.js:100 — `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
  • Swallowed exception (empty catch) litemall-wx/lib/vant-weapp/area/index.js:168 — `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
  • Swallowed exception (empty catch) litemall-wx/lib/vant-weapp/area/index.js:174 — `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
  • Swallowed exception (empty catch) litemall-vue/src/views/user/order-list/index.vue:128 — `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
  • Swallowed exception (empty catch) litemall-vue/src/views/user/order-list/index.vue:139 — `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
  • Swallowed exception (empty catch) litemall-vue/src/views/user/order-list/index.vue:150 — `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
  • Swallowed exception (empty catch) litemall-vue/src/views/user/order-list/index.vue:163 — `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
  • + 6 more in this group — see findings.md.
D17 · Explicit Debt · TodoComment · ×12
  • TodoComment litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxCartController.java:63 — // TODO — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/util/PermissionUtil.java:78 — // TODO — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/util/PermissionUtil.java:137 — // TODO — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/service/WxOrderService.java:513 — //TODO 发送邮件和短信通知,这里采用异步发送 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/service/WxOrderService.java:813 — //TODO 发送邮件和短信通知,这里采用异步发送 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/service/WxOrderService.java:863 — //TODO 发送邮件和短信通知,这里采用异步发送 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/service/AdminOrderService.java:174 — //TODO 发送邮件和短信通知,这里采用异步发送 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/service/AdminOrderService.java:220 — //TODO 发送邮件和短信通知,这里采用异步发送 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallAftersaleService.java:92 — // TODO 这里应该产生一个唯一的编号,但是实际上这里仍然存在两个售后编号相同的可能性 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallOrderService.java:66 — // TODO 这里应该产生一个唯一的订单,但是实际上这里仍然存在两个订单相同的可能性 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment litemall-core/src/main/java/org/linlinjava/litemall/core/qcode/QCodeService.java:174 — //TODO 注意,这里的字体必须安装在服务器上 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminAftersaleController.java:225 — // TODO 注意订单号只发后6位 — 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.
X24 · Document value interpolated into markup unescaped · Untrusted text written into markup unescaped · ×12
  • Untrusted text written into markup unescaped litemall-admin/src/utils/index.js:153 — `val` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped litemall-admin/src/utils/print.js:63 — `textareas[k2].value` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped litemall-admin/src/views/goods/list.vue:65 — `goodsDetail` is text this program did not author, and it is written into the text of an element through Vue's `v-html` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped litemall-admin/src/views/profile/notice.vue:47 — `notice.content` is text this program did not author, and it is written into the text of an element through Vue's `v-html` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped litemall-admin/src/views/promotion/topic.vue:37 — `contentDetail` is text this program did not author, and it is written into the text of an element through Vue's `v-html` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped litemall-admin/src/views/sys/notice.vue:26 — `contentDetail` is text this program did not author, and it is written into the text of an element through Vue's `v-html` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped litemall-vue/src/views/items/detail/index.vue:48 — `goods.info.detail` is text this program did not author, and it is written into the text of an element through Vue's `v-html` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped litemall-vue/src/views/items/topic/index.vue:4 — `topic.content` is text this program did not author, and it is written into the text of an element through Vue's `v-html` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped REDACTED:1146 — `url` is text this program did not author, and it is written into the start of a URL attribute, where it chooses the scheme through markup this function returns with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. HTML encoding does not help here — a `javascript:` URL contains nothing it changes; allow only http(s) or a relative path.
  • Untrusted text written into markup unescaped REDACTED:1946 — `url` is text this program did not author, and it is written into the start of a URL attribute, where it chooses the scheme through markup this function returns with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. HTML encoding does not help here — a `javascript:` URL contains nothing it changes; allow only http(s) or a relative path.
  • Untrusted text written into markup unescaped REDACTED:1146 — `url` is text this program did not author, and it is written into the start of a URL attribute, where it chooses the scheme through markup this function returns with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. HTML encoding does not help here — a `javascript:` URL contains nothing it changes; allow only http(s) or a relative path.
  • Untrusted text written into markup unescaped REDACTED:1924 — `url` is text this program did not author, and it is written into the start of a URL attribute, where it chooses the scheme through markup this function returns with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. HTML encoding does not help here — a `javascript:` URL contains nothing it changes; allow only http(s) or a relative path.
AC6 · Visual & motion safety · Animation without a prefers-reduced-motion guard · ×10
  • Animation without a prefers-reduced-motion guard litemall-admin/src/views/errorPage/404.vue:62 — `.wscn-http404 .pic-404__child.left` moves (`animation-name: cloudLeft`) 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 litemall-admin/src/views/errorPage/404.vue:73 — `.wscn-http404 .pic-404__child.mid` moves (`animation-name: cloudMid`) 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 litemall-admin/src/views/errorPage/404.vue:84 — `.wscn-http404 .pic-404__child.right` moves (`animation-name: cloudRight`) 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 litemall-admin/src/views/errorPage/404.vue:171 — `.wscn-http404 .bullshit__oops` moves (`animation-name: slideUp`) 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 litemall-admin/src/views/errorPage/404.vue:182 — `.wscn-http404 .bullshit__headline` moves (`animation-name: slideUp`) 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 litemall-admin/src/views/errorPage/404.vue:193 — `.wscn-http404 .bullshit__info` moves (`animation-name: slideUp`) 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 litemall-admin/src/views/errorPage/404.vue:211 — `.wscn-http404 .bullshit__return-home` moves (`animation-name: slideUp`) 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 litemall-admin/src/styles/sidebar.scss:5 — `#app .main-container` moves (`transition: margin-left .28s`) 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 litemall-admin/src/styles/sidebar.scss:11 — `#app .sidebar-container` moves (`transition: width 0.28s`) 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 litemall-admin/src/styles/sidebar.scss:168 — `#app .mobile .sidebar-container` moves (`transition: transform .28s`) 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.
D30 · Dependency Vulnerabilities · Medium CVE · ×10
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Duplicated block (5 lines × 2) · ×7
  • Duplicated block (5 lines × 2) litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminNoticeController.java:62 — litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminNoticeController.java:62-66 | litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminProfileController.java:74-78 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (5 lines × 2) litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminStorageController.java:49 — litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminStorageController.java:49-54 | litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxStorageController.java:54-58 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (5 lines × 2) litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallGrouponRulesService.java:28 — litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallGrouponRulesService.java:28-32 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallGrouponService.java:125-129 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (5 lines × 2) litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallAddressService.java:19 — litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallAddressService.java:19-23 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallCartService.java:37-41 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (5 lines × 2) litemall-core/src/main/java/org/linlinjava/litemall/core/util/bcrypt/BCrypt.java:561 — litemall-core/src/main/java/org/linlinjava/litemall/core/util/bcrypt/BCrypt.java:561-565 | litemall-core/src/main/java/org/linlinjava/litemall/core/util/bcrypt/BCrypt.java:568-572 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (5 lines × 2) litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallOrderService.java:256 — litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallOrderService.java:256-260 | litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxGoodsController.java:285-289 — 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) litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/service/WxOrderService.java:194 — litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/service/WxOrderService.java:194-198 | litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxGrouponController.java:111-115 — 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.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Duplicated block (9 lines × 2) · ×6
  • Duplicated block (9 lines × 2) litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/service/AdminGoodsService.java:145 — litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/service/AdminGoodsService.java:145-153 | litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/service/AdminGoodsService.java:233-241 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (9 lines × 2) litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/util/PermissionUtil.java:48 — litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/util/PermissionUtil.java:48-56 | litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/util/PermissionUtil.java:64-72 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/util/PermissionUtil.java:48` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 2) litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminCategoryController.java:38 — litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminCategoryController.java:38-46 | litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminCategoryController.java:50-58 — 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 `litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminCategoryController.java:38` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 2) litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/service/WxOrderService.java:184 — litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/service/WxOrderService.java:184-192 | litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxGrouponController.java:102-110 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/service/WxOrderService.java:193` calls `put`, `getMessage` and `litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxGrouponController.java:111` 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 (9 lines × 2) litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxCatalogController.java:72 — litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxCatalogController.java:72-80 | litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxCatalogController.java:112-120 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxCatalogController.java:121` calls `put`, `loadData` and `litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxCatalogController.java:81` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (9 lines × 2) litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/config/AdminSwagger2Configuration.java:39 — litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/config/AdminSwagger2Configuration.java:39-47 | litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/config/WxSwagger2Configuration.java:38-46 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
R11 · Import Boundaries · Boundary violation [package · ×6
  • Boundary violation [package:third-party-deep-import] litemall-admin/src/locales/en.js:2 — litemall-admin/src/locales/en.js:2 imports element-ui/lib/locale/lang/en, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] litemall-admin/src/locales/zh-Hans.js:2 — litemall-admin/src/locales/zh-Hans.js:2 imports element-ui/lib/locale/lang/zh-CN, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] litemall-admin/src/main.js:9 — litemall-admin/src/main.js:9 imports element-ui/lib/locale, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] litemall-admin/src/views/stat/goods.vue:9 — litemall-admin/src/views/stat/goods.vue:9 imports v-charts/lib/line, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] litemall-admin/src/views/stat/order.vue:9 — litemall-admin/src/views/stat/order.vue:9 imports v-charts/lib/line, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] litemall-admin/src/views/stat/user.vue:9 — litemall-admin/src/views/stat/user.vue:9 imports v-charts/lib/histogram, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
D4 · Code Duplication · Duplicated block (8 lines × 2) · ×5
  • Duplicated block (8 lines × 2) litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminRegionController.java:52 — litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminRegionController.java:52-59 | litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminRegionController.java:61-68 — 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) litemall-core/src/main/java/org/linlinjava/litemall/core/util/bcrypt/BCrypt.java:287 — litemall-core/src/main/java/org/linlinjava/litemall/core/util/bcrypt/BCrypt.java:287-294 | litemall-core/src/main/java/org/linlinjava/litemall/core/util/bcrypt/BCrypt.java:295-302 — 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) litemall-core/src/main/java/org/linlinjava/litemall/core/util/bcrypt/BCrypt.java:594 — litemall-core/src/main/java/org/linlinjava/litemall/core/util/bcrypt/BCrypt.java:594-601 | litemall-core/src/main/java/org/linlinjava/litemall/core/util/bcrypt/BCrypt.java:624-631 — 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 `litemall-core/src/main/java/org/linlinjava/litemall/core/util/bcrypt/BCrypt.java:594` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `litemall-core/src/main/java/org/linlinjava/litemall/core/util/bcrypt/BCrypt.java:632` calls `streamtoword` and `litemall-core/src/main/java/org/linlinjava/litemall/core/util/bcrypt/BCrypt.java:602` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (8 lines × 2) litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/service/WxOrderService.java:211 — litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/service/WxOrderService.java:211-218 | litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxGrouponController.java:138-145 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/service/WxOrderService.java:211` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 2) litemall-core/src/main/java/org/linlinjava/litemall/core/storage/AliyunStorage.java:123 — litemall-core/src/main/java/org/linlinjava/litemall/core/storage/AliyunStorage.java:123-130 | litemall-core/src/main/java/org/linlinjava/litemall/core/storage/TencentStorage.java:124-131 — 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.
AC6 · Visual & motion safety · Focus outline removed in CSS without a · ×4
  • Focus outline removed in CSS without a :focus replacement litemall-admin/src/views/layout/components/Navbar.vue:116 — `.navbar .right-menu: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 litemall-admin/src/styles/btn.scss:50 — `.pan-btn` 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 litemall-admin/src/styles/btn.scss:94 — `.custom-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 litemall-admin/src/styles/index.scss:45 — `a: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.
D2 · Cognitive Complexity · (anonymous) · ×4
  • (anonymous)::writeImageTag (cognitive 22) REDACTED:1910 — (anonymous)::writeImageTag has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (15 pts), ternaries 2 (4 pts), boolean chains 3 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • (anonymous)::writeImageTag (cognitive 22) REDACTED:1888 — (anonymous)::writeImageTag has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (15 pts), ternaries 2 (4 pts), boolean chains 3 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • (anonymous)::writeAnchorTag (cognitive 16) REDACTED:1113 — (anonymous)::writeAnchorTag has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 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)::writeAnchorTag (cognitive 16) REDACTED:1113 — (anonymous)::writeAnchorTag has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 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.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Duplicated block (12 lines × 2) · ×4
  • Duplicated block (12 lines × 2) litemall-db/src/main/java/org/linlinjava/litemall/db/util/DbUtil.java:18 — litemall-db/src/main/java/org/linlinjava/litemall/db/util/DbUtil.java:18-29 | litemall-db/src/main/java/org/linlinjava/litemall/db/util/DbUtil.java:39-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. Read the line range as the matched WINDOW rather than a finished unit: at `litemall-db/src/main/java/org/linlinjava/litemall/db/util/DbUtil.java:18` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12 lines × 2) litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/service/WxOrderService.java:357 — litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/service/WxOrderService.java:357-368 | litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxCartController.java:510-521 — 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 (12 lines × 2) litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxAuthController.java:97 — litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxAuthController.java:97-108 | litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxAuthController.java:314-325 — 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 `litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxAuthController.java:97` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (12 lines × 2) litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxAuthController.java:196 — litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxAuthController.java:196-207 | litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxAuthController.java:353-364 — 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 `litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxAuthController.java:196` 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 (7 lines × 2) · ×4
  • Duplicated block (7 lines × 2) litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminCategoryController.java:147 — litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminCategoryController.java:147-153 | litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminRoleController.java:67-74 — 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 `litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminCategoryController.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 `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (7 lines × 2) litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallCommentService.java:30 — litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallCommentService.java:30-36 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallCommentService.java:43-49 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (7 lines × 2) litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminCouponController.java:59 — litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminCouponController.java:59-65 | litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminRoleController.java:85-92 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. 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) litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminStorageController.java:59 — litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminStorageController.java:59-65 | litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxBrandController.java:57-64 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
AX2 · Stateful singletons · Stateful singleton · ×3
  • Stateful singleton: LocalStorage litemall-core/src/main/java/org/linlinjava/litemall/core/storage/LocalStorage.java:21 — `LocalStorage` is a singleton (@Bean: the container shares one instance across every request thread) but mutates instance state outside any lock (storagePath, rootLocation; e.g. `storagePath` in `setStoragePath` at line 35).
  • Stateful singleton: QiniuStorage litemall-core/src/main/java/org/linlinjava/litemall/core/storage/QiniuStorage.java:19 — `QiniuStorage` is a singleton (@Bean: the container shares one instance across every request thread) but mutates instance state outside any lock (auth, bucketManager, uploadManager; e.g. `auth` in `delete` at line 108).
  • Stateful singleton: TencentStorage litemall-core/src/main/java/org/linlinjava/litemall/core/storage/TencentStorage.java:24 — `TencentStorage` is a singleton (@Bean: the container shares one instance across every request thread) but mutates instance state outside any lock (cosClient; e.g. `cosClient` in `getCOSClient` at line 67).
D10 · Test Quality · No assertions · ×3
  • No assertions: test litemall-all/src/test/java/org/linlinjava/litemall/allinone/AllinoneConfigTest.java:19 — 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: test litemall-wx-api/src/test/java/org/linlinjava/litemall/wx/BigDecimalTest.java:13 — 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: test litemall-wx-api/src/test/java/org/linlinjava/litemall/wx/WxConfigTest.java:19 — 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.
D3 · God Classes · FileTooLong · ×3
  • FileTooLong: REDACTED REDACTED — FileTooLong — 1140 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 640 over it, 2.28× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: REDACTED REDACTED — FileTooLong — 1140 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 640 over it, 2.28× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: service/WxOrderService.java litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/service/WxOrderService.java — FileTooLong — 605 significant lines (blank, comment-only and punctuation-only lines excluded), about 92% of them inside a single declaration: WxOrderService (69-1072). The bar is 500 significant lines; this is 105 over it, 1.21× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
D4 · Code Duplication · Edited copy of a member (14 corresponding lines) · ×3
  • Edited copy of a member (14 corresponding lines) litemall-core/src/main/java/org/linlinjava/litemall/core/storage/AliyunStorage.java:81 — litemall-core/src/main/java/org/linlinjava/litemall/core/storage/AliyunStorage.java:81-94 | litemall-core/src/main/java/org/linlinjava/litemall/core/storage/TencentStorage.java:84-97 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallGrouponRulesService.java:106 — litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallGrouponRulesService.java:106-119 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallGrouponService.java:142-155 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminCouponController.java:70 — litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminCouponController.java:70-84 | litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminRoleController.java:97-110 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (7 corresponding lines) · ×3
  • Edited copy of a member (7 corresponding lines) litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallOrderService.java:150 — litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallOrderService.java:150-156 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallOrderService.java:196-202 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) REDACTED:44 — REDACTED:44-50 | litemall-core/src/main/java/org/linlinjava/litemall/core/notify/NotifyService.java:102-110 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminKeywordController.java:41 — litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminKeywordController.java:41-47 | litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminNoticeController.java:54-60 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (5 corresponding lines) · ×3
  • Edited copy of a member (5 corresponding lines) litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallAdminService.java:21 — litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallAdminService.java:21-25 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallUserService.java:76-80 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallCouponUserService.java:95 — litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallCouponUserService.java:95-99 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallOrderGoodsService.java:23-27 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallGoodsService.java:159 — litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallGoodsService.java:159-163 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallTopicService.java:40-44 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (16 lines × 2) · ×3
  • Duplicated block (16 lines × 2) litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/service/WxOrderService.java:615 — litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/service/WxOrderService.java:615-630 | litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/service/WxOrderService.java:677-692 — 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 `litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/service/WxOrderService.java:615` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (16 lines × 2) litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxAuthController.java:383 — litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxAuthController.java:383-398 | litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxAuthController.java:437-452 — 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 `litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxAuthController.java:383` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (16 lines × 2) litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/service/WxOrderService.java:500 — litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/service/WxOrderService.java:500-515 | litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/service/WxOrderService.java:800-815 — 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 `litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/service/WxOrderService.java:500` 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 (14 lines × 2) · ×3
  • Duplicated block (14 lines × 2) litemall-core/src/main/java/org/linlinjava/litemall/core/notify/TencentSmsSender.java:32 — litemall-core/src/main/java/org/linlinjava/litemall/core/notify/TencentSmsSender.java:32-45 | litemall-core/src/main/java/org/linlinjava/litemall/core/notify/TencentSmsSender.java:51-64 — 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 `litemall-core/src/main/java/org/linlinjava/litemall/core/notify/TencentSmsSender.java:32` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (14 lines × 2) litemall-core/src/main/java/org/linlinjava/litemall/core/storage/StorageService.java:63 — litemall-core/src/main/java/org/linlinjava/litemall/core/storage/StorageService.java:63-76 | litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxStorageController.java:38-51 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (14 lines × 2) litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallAftersaleService.java:36 — litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallAftersaleService.java:36-49 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallAftersaleService.java:60-73 — 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 `litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallAftersaleService.java:36` 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 × 6) · ×3
  • Duplicated block (10 lines × 6) litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallAddressService.java:68 — litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallAddressService.java:68-77 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallBrandService.java:46-55 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallCategoryService.java:63-72 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallGoodsService.java:140-149 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallRoleService.java:44-53 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallStorageService.java:53-62 — 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. Note first that the copies are not typed on the same thing: `StringUtils` names `com.alibaba.druid.util.StringUtils` in one and `org.springframework.util.StringUtils` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (10 lines × 6) litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/service/WxOrderService.java:550 — litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/service/WxOrderService.java:550-559 | litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/service/WxOrderService.java:610-619 | litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/service/WxOrderService.java:672-681 | litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/service/WxOrderService.java:836-845 | litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/service/WxOrderService.java:881-890 | litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/service/WxOrderService.java:924-933 — 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 `litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/service/WxOrderService.java:550` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/service/WxOrderService.java:846` calls `badArgument`, `getUserId`, `equals` and `litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/service/WxOrderService.java:560` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (10 lines × 6) litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminAdController.java:76 — litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminAdController.java:76-86 | litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminBrandController.java:83-92 | litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminCouponController.java:97-106 | litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminIssueController.java:75-85 | litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminKeywordController.java:72-81 | litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminTopicController.java:100-109 — before extracting anything, compare `litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminAdController.java` and `litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminIssueController.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 39 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. 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 (10 lines × 2) · ×3
  • Duplicated block (10 lines × 2) litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/util/PermissionUtil.java:35 — litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/util/PermissionUtil.java:35-44 | litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/util/PermissionUtil.java:50-59 — 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 `litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/util/PermissionUtil.java:35` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 2) litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallAdService.java:32 — litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallAdService.java:32-41 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallNoticeService.java:29-38 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (10 lines × 2) litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallAdminService.java:35 — litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallAdminService.java:35-44 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallFeedbackService.java:36-45 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
R10 · Code Duplication · Duplicated block (53 lines × 2 locations) · ×3
  • Duplicated block (53 lines × 2 locations) litemall-admin/src/views/user/footprint.vue:37 — litemall-admin/src/views/user/footprint.vue:37 · litemall-admin/src/views/user/history.vue:36 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
  • Duplicated block (53 lines × 2 locations) litemall-wx/pages/brandDetail/brandDetail.js:5 — litemall-wx/pages/brandDetail/brandDetail.js:5 · renard-wx/pages/brandDetail/brandDetail.js:4 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
  • Duplicated block (53 lines × 2 locations) litemall-wx/pages/ucenter/aftersaleList/aftersaleList.js:13 — litemall-wx/pages/ucenter/aftersaleList/aftersaleList.js:13 · litemall-wx/pages/ucenter/order/order.js:23 — 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.
R7 · Dead Code · Dead file (~75 LoC) · ×3
  • Dead file (~75 LoC) litemall-vue/src/views/items/brand-list/index.vue — no import path from any entry point (145 application, 90 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 (~75 LoC) REDACTED — no import path from any entry point (145 application, 90 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 (~75 LoC) litemall-vue/src/views/items/topic-list/index.vue — no import path from any entry point (145 application, 90 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 · Page without a main landmark · ×2
  • Page without a main landmark litemall-admin/public/index.html:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="app">, so there is no content here to wrap — render the <main> from the component mounted into it.
  • Page without a main landmark litemall-vue/public/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>.
D1 · Cyclomatic Complexity · showdown.showdown.Converter (cyclomatic 46) · ×2
  • showdown.showdown.Converter (cyclomatic 46) REDACTED:708 — showdown.showdown.Converter has cyclomatic complexity 46 (threshold 15). Most of this is not in the body itself: 3 of the 46 points are its own statements and the rest belongs to 8 function items inside it that branch (_parseExtension, _constructor, legacyExtensionLoading, …). 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.
  • showdown.showdown.Converter (cyclomatic 46) REDACTED:708 — showdown.showdown.Converter has cyclomatic complexity 46 (threshold 15). Most of this is not in the body itself: 3 of the 46 points are its own statements and the rest belongs to 8 function items inside it that branch (_parseExtension, _constructor, legacyExtensionLoading, …). 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.
D1 · Cyclomatic Complexity · htmlparser.HTMLParser (cyclomatic 36) · ×2
  • htmlparser.HTMLParser (cyclomatic 36) litemall-wx/lib/wxParse/htmlparser.js:35 — htmlparser.HTMLParser has cyclomatic complexity 36 (threshold 15). Of this number, 16 points are the body's own statements and 20 belong to 4 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.
  • htmlparser.HTMLParser (cyclomatic 36) renard-wx/lib/wxParse/htmlparser.js:35 — htmlparser.HTMLParser has cyclomatic complexity 36 (threshold 15). Of this number, 16 points are the body's own statements and 20 belong to 4 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.
D1 · Cyclomatic Complexity · showdown.validate (cyclomatic 26) · ×2
  • showdown.validate (cyclomatic 26) REDACTED:307 — showdown.validate has cyclomatic complexity 26 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
  • showdown.validate (cyclomatic 26) REDACTED:307 — showdown.validate has cyclomatic complexity 26 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · showdown.showdown.subParser("tables") (cyclomatic 21) · ×2
  • showdown.showdown.subParser("tables") (cyclomatic 21) REDACTED:2387 — showdown.showdown.subParser("tables") has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 2 of the 21 points are its own statements and the rest belongs to 4 function items inside it that branch (a function literal at line 2446, parseStyles, buildTable, …). 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.
  • showdown.showdown.subParser("tables") (cyclomatic 21) REDACTED:2365 — showdown.showdown.subParser("tables") has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 2 of the 21 points are its own statements and the rest belongs to 4 function items inside it that branch (a function literal at line 2424, parseStyles, buildTable, …). 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.
D1 · Cyclomatic Complexity · (anonymous) (cyclomatic 21) · ×2
  • (anonymous) (cyclomatic 21) REDACTED:2387 — (anonymous) has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 2 of the 21 points are its own statements and the rest belongs to 8 function items inside it that branch (a function literal at line 2446, parseStyles, buildTable, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
  • (anonymous) (cyclomatic 21) REDACTED:2365 — (anonymous) has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 2 of the 21 points are its own statements and the rest belongs to 8 function items inside it that branch (a function literal at line 2424, parseStyles, buildTable, …). 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.
D1 · Cyclomatic Complexity · html2json.html2json (cyclomatic 20) · ×2
  • html2json.html2json (cyclomatic 20) litemall-wx/lib/wxParse/html2json.js:54 — html2json.html2json has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 1 of the 20 points is its own statement and the rest belongs to 5 function literals inside it that branch (lines 67, 84, 147, …). 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.
  • html2json.html2json (cyclomatic 20) renard-wx/lib/wxParse/html2json.js:54 — html2json.html2json has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 1 of the 20 points is its own statement and the rest belongs to 5 function literals inside it that branch (lines 67, 84, 147, …). 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.
D1 · Cyclomatic Complexity · showdown.showdown.subParser("lists") (cyclomatic 18) · ×2
  • showdown.showdown.subParser("lists") (cyclomatic 18) REDACTED:2003 — showdown.showdown.subParser("lists") has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 2 of the 18 points are its own statements and the rest belongs to 7 function items inside it that branch (processListItems, a function literal at line 2046, parseConsecutiveLists, …). 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.
  • showdown.showdown.subParser("lists") (cyclomatic 18) REDACTED:1981 — showdown.showdown.subParser("lists") has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 2 of the 18 points are its own statements and the rest belongs to 7 function items inside it that branch (processListItems, a function literal at line 2024, parseConsecutiveLists, …). 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.
D1 · Cyclomatic Complexity · (anonymous) (cyclomatic 18) · ×2
  • (anonymous) (cyclomatic 18) REDACTED:2003 — (anonymous) has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 2 of the 18 points are its own statements and the rest belongs to 7 function items inside it that branch (a function literal at line 2046, parseConsecutiveLists, parseConsecutiveLists::parseCL, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
  • (anonymous) (cyclomatic 18) REDACTED:1981 — (anonymous) has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 2 of the 18 points are its own statements and the rest belongs to 7 function items inside it that branch (a function literal at line 2024, parseConsecutiveLists, parseConsecutiveLists::parseCL, …). 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.
D10 · Test Quality · Test project verifies nothing · ×2
  • Test project verifies nothing: litemall-all litemall-all/src/test/java/org/linlinjava/litemall/allinone/AllinoneConfigTest.java:19 — No conventional assertion call was detected in 1 of 1 tests in `litemall-all` — 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: litemall-wx-api litemall-wx-api/src/test/java/org/linlinjava/litemall/wx/BigDecimalTest.java:13 — No conventional assertion call was detected in 2 of 2 tests in `litemall-wx-api` — 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 · HTMLParser (cognitive 79) · ×2
  • HTMLParser (cognitive 79) litemall-wx/lib/wxParse/htmlparser.js:35 — HTMLParser has cognitive complexity 79 (threshold 15). Drivers by points: if/else 23 (52 pts), ternaries 6 (16 pts), loops 4 (7 pts), boolean chains 4 (nesting depth added 42). Of this number, 44 points are the body's own statements and 35 belong to 5 function items inside it that branch. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
  • HTMLParser (cognitive 79) renard-wx/lib/wxParse/htmlparser.js:35 — HTMLParser has cognitive complexity 79 (threshold 15). Drivers by points: if/else 23 (52 pts), ternaries 6 (16 pts), loops 4 (7 pts), boolean chains 4 (nesting depth added 42). Of this number, 44 points are the body's own statements and 35 belong to 5 function items inside it that branch. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · showdown.validate (cognitive 56) · ×2
  • showdown.validate (cognitive 56) REDACTED:307 — showdown.validate has cognitive complexity 56 (threshold 15). Drivers by points: if/else 20 (49 pts), loops 2 (4 pts), boolean chains 2, ternaries 1 (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.
  • showdown.validate (cognitive 56) REDACTED:307 — showdown.validate has cognitive complexity 56 (threshold 15). Drivers by points: if/else 20 (49 pts), loops 2 (4 pts), boolean chains 2, ternaries 1 (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.
D2 · Cognitive Complexity · html2json (cognitive 33) · ×2
  • html2json (cognitive 33) litemall-wx/lib/wxParse/html2json.js:54 — html2json has cognitive complexity 33 (threshold 15). Drivers by points: if/else 23 (32 pts), boolean chains 1 (nesting depth added 9). None of this is in the body itself: all 33 points belong to 5 function items inside it that branch (start, a function literal at line 84, end, …). 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.
  • html2json (cognitive 33) renard-wx/lib/wxParse/html2json.js:54 — html2json has cognitive complexity 33 (threshold 15). Drivers by points: if/else 23 (32 pts), boolean chains 1 (nesting depth added 9). None of this is in the body itself: all 33 points belong to 5 function items inside it that branch (start, a function literal at line 84, end, …). 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 · (anonymous) (cognitive 32) · ×2
  • (anonymous) (cognitive 32) REDACTED:2003 — (anonymous) has cognitive complexity 32 (threshold 15). Drivers by points: if/else 13 (16 pts), ternaries 5 (11 pts), boolean chains 3, loops 1 (2 pts) (nesting depth added 10). Most of this is not in the body itself: 2 of the 32 points are its own statements and the rest belongs to 7 function items inside it that branch (a function literal at line 2046, parseConsecutiveLists::parseCL, parseConsecutiveLists, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
  • (anonymous) (cognitive 32) REDACTED:1981 — (anonymous) has cognitive complexity 32 (threshold 15). Drivers by points: if/else 13 (16 pts), ternaries 5 (11 pts), boolean chains 3, loops 1 (2 pts) (nesting depth added 10). Most of this is not in the body itself: 2 of the 32 points are its own statements and the rest belongs to 7 function items inside it that branch (a function literal at line 2024, parseConsecutiveLists::parseCL, parseConsecutiveLists, …). 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 · (anonymous) (cognitive 29) · ×2
  • (anonymous) (cognitive 29) REDACTED:2387 — (anonymous) has cognitive complexity 29 (threshold 15). Drivers by points: if/else 12 (18 pts), loops 9 (11 pts) (nesting depth added 8). Most of this is not in the body itself: 1 of the 29 points is its own statement and the rest belongs to 8 function items inside it that branch (a function literal at line 2446, parseStyles, buildTable, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
  • (anonymous) (cognitive 29) REDACTED:2365 — (anonymous) has cognitive complexity 29 (threshold 15). Drivers by points: if/else 12 (18 pts), loops 9 (11 pts) (nesting depth added 8). Most of this is not in the body itself: 1 of the 29 points is its own statement and the rest belongs to 8 function items inside it that branch (a function literal at line 2424, parseStyles, buildTable, …). 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 · rgxFindMatchPos (cognitive 23) · ×2
  • rgxFindMatchPos (cognitive 23) REDACTED:545 — rgxFindMatchPos has cognitive complexity 23 (threshold 15). Drivers by points: if/else 5 (17 pts), loops 3 (4 pts), boolean chains 2 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • rgxFindMatchPos (cognitive 23) REDACTED:545 — rgxFindMatchPos has cognitive complexity 23 (threshold 15). Drivers by points: if/else 5 (17 pts), loops 3 (4 pts), boolean chains 2 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · showdown.showdown.Converter · ×2
  • showdown.showdown.Converter::_parseExtension (cognitive 21) REDACTED:778 — showdown.showdown.Converter::_parseExtension has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (14 pts), loops 2 (4 pts), match/switch 1 (2 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • showdown.showdown.Converter::_parseExtension (cognitive 21) REDACTED:778 — showdown.showdown.Converter::_parseExtension has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (14 pts), loops 2 (4 pts), match/switch 1 (2 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · showdown.showdown.subParser("paragraphs") (cognitive 19) · ×2
  • showdown.showdown.subParser("paragraphs") (cognitive 19) REDACTED:2184 — showdown.showdown.subParser("paragraphs") has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (15 pts), loops 3 (4 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • showdown.showdown.subParser("paragraphs") (cognitive 19) REDACTED:2162 — showdown.showdown.subParser("paragraphs") has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (15 pts), loops 3 (4 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · (anonymous) (cognitive 19) · ×2
  • (anonymous) (cognitive 19) REDACTED:2184 — (anonymous) has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (15 pts), loops 3 (4 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • (anonymous) (cognitive 19) REDACTED:2162 — (anonymous) has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (15 pts), loops 3 (4 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · showdown.showdown.subParser("images") · ×2
  • showdown.showdown.subParser("images")::writeImageTag (cognitive 18) REDACTED:1910 — showdown.showdown.subParser("images")::writeImageTag has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 3 (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.
  • showdown.showdown.subParser("images")::writeImageTag (cognitive 18) REDACTED:1888 — showdown.showdown.subParser("images")::writeImageTag has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 3 (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.
D2 · Cognitive Complexity · clickSkuValue (cognitive 17) · ×2
  • clickSkuValue (cognitive 17) litemall-wx/pages/goods/goods.js:257 — clickSkuValue has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (13 pts), loops 2 (4 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • clickSkuValue (cognitive 17) renard-wx/pages/goods/goods.js:203 — clickSkuValue has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (13 pts), loops 2 (4 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · showdown.showdown.subParser("anchors") · ×2
  • showdown.showdown.subParser("anchors")::writeAnchorTag (cognitive 16) REDACTED:1113 — showdown.showdown.subParser("anchors")::writeAnchorTag has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 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.
  • showdown.showdown.subParser("anchors")::writeAnchorTag (cognitive 16) REDACTED:1113 — showdown.showdown.subParser("anchors")::writeAnchorTag has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 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.
D31 · IaC & Container Security · Medium IaC · ×2
  • REDACTED
  • REDACTED
D4 · Code Duplication · Edited copy of a member (20 corresponding lines) · ×2
  • Edited copy of a member (20 corresponding lines) litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxAuthController.java:187 — litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxAuthController.java:187-207 | litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxAuthController.java:337-364 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (20 corresponding lines) litemall-db/src/main/java/org/linlinjava/litemall/db/util/DbUtil.java:10 — litemall-db/src/main/java/org/linlinjava/litemall/db/util/DbUtil.java:10-29 | litemall-db/src/main/java/org/linlinjava/litemall/db/util/DbUtil.java:31-50 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Members sharing a duplicated core (6 members, 50+ identical tokens) · ×2
  • Members sharing a duplicated core (6 members, 50+ identical tokens) litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallAddressService.java:61 — litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallAddressService.java:61-79 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallBrandService.java:39-57 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallCategoryService.java:56-74 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallGoodsService.java:130-151 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallRoleService.java:40-55 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallStorageService.java:46-64 — 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.
  • Members sharing a duplicated core (6 members, 50+ identical tokens) litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/service/WxOrderService.java:549 — litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/service/WxOrderService.java:549-595 | litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/service/WxOrderService.java:609-660 | litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/service/WxOrderService.java:671-714 | litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/service/WxOrderService.java:835-868 | litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/service/WxOrderService.java:880-911 | litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/service/WxOrderService.java:923-952 — 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 (5 members, 50+ identical tokens) · ×2
  • Members sharing a duplicated core (5 members, 50+ identical tokens) litemall-core/src/main/java/org/linlinjava/litemall/core/util/CharUtil.java:7 — litemall-core/src/main/java/org/linlinjava/litemall/core/util/CharUtil.java:7-16 | litemall-core/src/main/java/org/linlinjava/litemall/core/util/CharUtil.java:18-27 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallAftersaleService.java:75-84 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallCouponService.java:145-156 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallOrderService.java:49-58 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallSystemConfigService.java:19 — litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallSystemConfigService.java:19-30 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallSystemConfigService.java:32-41 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallSystemConfigService.java:43-52 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallSystemConfigService.java:54-63 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallSystemConfigService.java:65-74 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
D4 · Code Duplication · Edited copy of a member (22 corresponding lines) · ×2
  • Edited copy of a member (22 corresponding lines) litemall-core/src/main/java/org/linlinjava/litemall/core/util/bcrypt/BCrypt.java:591 — litemall-core/src/main/java/org/linlinjava/litemall/core/util/bcrypt/BCrypt.java:591-612 | litemall-core/src/main/java/org/linlinjava/litemall/core/util/bcrypt/BCrypt.java:621-646 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (22 corresponding lines) litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxCartController.java:316 — litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxCartController.java:316-337 | litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxFootprintController.java:45-68 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (17 corresponding lines) · ×2
  • Edited copy of a member (17 corresponding lines) litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxStorageController.java:67 — litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxStorageController.java:67-83 | litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxStorageController.java:92-110 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (17 corresponding lines) litemall-core/src/main/java/org/linlinjava/litemall/core/notify/TencentSmsSender.java:29 — litemall-core/src/main/java/org/linlinjava/litemall/core/notify/TencentSmsSender.java:29-45 | litemall-core/src/main/java/org/linlinjava/litemall/core/notify/TencentSmsSender.java:48-64 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (16 corresponding lines) · ×2
  • Edited copy of a member (16 corresponding lines) litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/task/AdminTaskStartupRunner.java:25 — litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/task/AdminTaskStartupRunner.java:25-40 | litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/task/TaskStartupRunner.java:27-43 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminAdminController.java:100 — litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminAdminController.java:100-120 | litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxAddressController.java:170-185 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (11 corresponding lines) · ×2
  • Edited copy of a member (11 corresponding lines) litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallCommentService.java:27 — litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallCommentService.java:27-39 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallCommentService.java:41-51 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) litemall-db/src/main/java/org/linlinjava/litemall/db/mybatis/JsonIntegerArrayTypeHandler.java:47 — litemall-db/src/main/java/org/linlinjava/litemall/db/mybatis/JsonIntegerArrayTypeHandler.java:47-57 | litemall-db/src/main/java/org/linlinjava/litemall/db/mybatis/JsonStringArrayTypeHandler.java:47-57 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (15 corresponding lines) · ×2
  • Edited copy of a member (15 corresponding lines) litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminBrandController.java:42 — litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminBrandController.java:42-58 | litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminTopicController.java:51-65 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminGrouponController.java:92 — litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminGrouponController.java:92-111 | litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxAftersaleController.java:209-223 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (9 corresponding lines) · ×2
  • Edited copy of a member (9 corresponding lines) litemall-core/src/main/java/org/linlinjava/litemall/core/storage/config/StorageAutoConfiguration.java:48 — litemall-core/src/main/java/org/linlinjava/litemall/core/storage/config/StorageAutoConfiguration.java:48-56 | litemall-core/src/main/java/org/linlinjava/litemall/core/storage/config/StorageAutoConfiguration.java:70-78 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallAftersaleService.java:93 — litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallAftersaleService.java:93-101 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallOrderService.java:67-75 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (19 lines × 2) · ×2
  • Duplicated block (19 lines × 2) litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxCouponController.java:193 — litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxCouponController.java:193-211 | litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxCouponController.java:272-290 — 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 (19 lines × 2) litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxCouponController.java:216 — litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxCouponController.java:216-234 | litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxCouponController.java:295-313 — 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 `litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxCouponController.java:216` 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 (14 lines × 3) · ×2
  • Duplicated block (14 lines × 3) litemall-db/src/main/java/org/linlinjava/litemall/db/service/CouponAssignService.java:39 — litemall-db/src/main/java/org/linlinjava/litemall/db/service/CouponAssignService.java:39-52 | litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxCouponController.java:229-242 | litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxCouponController.java:308-321 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart.
  • Duplicated block (14 lines × 3) litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/service/WxOrderService.java:551 — litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/service/WxOrderService.java:551-564 | litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/service/WxOrderService.java:611-624 | litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/service/WxOrderService.java:673-686 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/service/WxOrderService.java:551` 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.
D4 · Code Duplication · Duplicated block (11 lines × 2) · ×2
  • Duplicated block (11 lines × 2) litemall-core/src/main/java/org/linlinjava/litemall/core/qcode/QCodeService.java:44 — litemall-core/src/main/java/org/linlinjava/litemall/core/qcode/QCodeService.java:44-54 | litemall-core/src/main/java/org/linlinjava/litemall/core/qcode/QCodeService.java:79-89 — 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 `litemall-core/src/main/java/org/linlinjava/litemall/core/qcode/QCodeService.java:44` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (11 lines × 2) litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminAdController.java:41 — litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminAdController.java:41-51 | litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminIssueController.java:41-51 — before extracting anything, compare `litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminAdController.java` and `litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminIssueController.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 39 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. 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.
D5 · Coupling · Off the main sequence · ×2
  • Off the main sequence: litemall-db — litemall-db: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 5 project(s), so it's rigid to change.
  • Off the main sequence: litemall-core — litemall-core: abstractness 0.08, instability 0.20, distance 0.72 — zone of pain — concrete and depended on by 4 project(s), so it's rigid to change.
R10 · Code Duplication · Duplicated block with local edits (70 matched lines × 2 locations) · ×2
  • Duplicated block with local edits (70 matched lines × 2 locations) litemall-wx/pages/auth/accountLogin/accountLogin.js:5 — litemall-wx/pages/auth/accountLogin/accountLogin.js:5 · litemall-wx/pages/auth/reset/reset.js:4 — the two spans are one implementation copied and then locally edited — 319 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
  • Duplicated block with local edits (70 matched lines × 2 locations) litemall-wx/pages/goods/goods.js:55 — litemall-wx/pages/goods/goods.js:55 · renard-wx/pages/goods/goods.js:40 — the two spans are one implementation copied and then locally edited — 423 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block (54 lines × 2 locations) · ×2
  • Duplicated block (54 lines × 2 locations) litemall-wx/pages/auth/login/login.js:5 — litemall-wx/pages/auth/login/login.js:5 · renard-wx/pages/auth/login/login.js:5 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
  • Duplicated block (54 lines × 2 locations) litemall-wx/utils/area.js:3227 — litemall-wx/utils/area.js:3227 · renard-wx/utils/area.js:3227 — 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.
R2 · Cyclomatic Complexity · Complex function validate (cyclomatic 26, cognitive 56) · ×2
  • Complex function validate (cyclomatic 26, cognitive 56) REDACTED:307 — validate has cyclomatic complexity 26 and cognitive complexity 56; 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 validate (cyclomatic 26, cognitive 56) REDACTED:307 — validate has cyclomatic complexity 26 and cognitive complexity 56; 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 HTMLParser (cyclomatic 16, cognitive 44) · ×2
  • Complex function HTMLParser (cyclomatic 16, cognitive 44) litemall-wx/lib/wxParse/htmlparser.js:35 — HTMLParser has cyclomatic complexity 16 and cognitive complexity 44; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
  • Complex function HTMLParser (cyclomatic 16, cognitive 44) renard-wx/lib/wxParse/htmlparser.js:35 — HTMLParser has cyclomatic complexity 16 and cognitive complexity 44; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function writeImageTag (cyclomatic 14, cognitive 22) · ×2
  • Complex function writeImageTag (cyclomatic 14, cognitive 22) REDACTED:1910 — writeImageTag has cyclomatic complexity 14 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 writeImageTag (cyclomatic 14, cognitive 22) REDACTED:1888 — writeImageTag has cyclomatic complexity 14 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 _parseExtension (cyclomatic 14, cognitive 21) · ×2
  • Complex function _parseExtension (cyclomatic 14, cognitive 21) REDACTED:778 — _parseExtension has cyclomatic complexity 14 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
  • Complex function _parseExtension (cyclomatic 14, cognitive 21) REDACTED:778 — _parseExtension has cyclomatic complexity 14 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 13, cognitive 19) · ×2
  • Complex function (anonymous) (cyclomatic 13, cognitive 19) REDACTED:2446 — (anonymous) has cyclomatic complexity 13 and cognitive complexity 19; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
  • Complex function (anonymous) (cyclomatic 13, cognitive 19) REDACTED:2424 — (anonymous) has cyclomatic complexity 13 and cognitive complexity 19; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function rgxFindMatchPos (cyclomatic 11, cognitive 23) · ×2
  • Complex function rgxFindMatchPos (cyclomatic 11, cognitive 23) REDACTED:545 — rgxFindMatchPos has cyclomatic complexity 11 and cognitive complexity 23; 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 rgxFindMatchPos (cyclomatic 11, cognitive 23) REDACTED:545 — rgxFindMatchPos has cyclomatic complexity 11 and cognitive complexity 23; 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.
R7 · Dead Code · Dead file (~241 LoC) · ×2
  • Dead file (~241 LoC) litemall-wx/lib/wxParse/html2json.js — no import path from any entry point (145 application, 90 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 (~241 LoC) renard-wx/lib/wxParse/html2json.js — no import path from any entry point (145 application, 90 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 (~206 LoC) · ×2
  • Dead file (~206 LoC) litemall-wx/lib/wxParse/wxDiscode.js — no import path from any entry point (145 application, 90 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 (~206 LoC) renard-wx/lib/wxParse/wxDiscode.js — no import path from any entry point (145 application, 90 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 (~182 LoC) · ×2
  • Dead file (~182 LoC) litemall-wx/lib/wxParse/htmlparser.js — no import path from any entry point (145 application, 90 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 (~182 LoC) renard-wx/lib/wxParse/htmlparser.js — no import path from any entry point (145 application, 90 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 (~109 LoC) · ×2
  • Dead file (~109 LoC) litemall-vue/src/views/login/register-submit/index.vue — no import path from any entry point (145 application, 90 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 (~109 LoC) litemall-vue/src/views/user/user-information-set/set-password/index.vue — no import path from any entry point (145 application, 90 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
R8 · Dependency Hygiene · Unused dependency '@vue/cli-plugin-babel' · ×2
  • Unused dependency '@vue/cli-plugin-babel' — Declared in litemall-admin/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
  • Unused dependency '@vue/cli-plugin-babel' — Declared in litemall-vue/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
R8 · Dependency Hygiene · Unused dependency '@vue/cli-service' · ×2
  • Unused dependency '@vue/cli-service' — Declared in litemall-admin/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
  • Unused dependency '@vue/cli-service' — Declared in litemall-vue/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
R8 · Dependency Hygiene · Unused dependency 'vue-template-compiler' · ×2
  • Unused dependency 'vue-template-compiler' — Declared in litemall-admin/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
  • Unused dependency 'vue-template-compiler' — Declared in litemall-vue/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
SC1 · Supply-chain hygiene · JavaScript dependencies are not locked · ×2
  • JavaScript dependencies are not locked litemall-admin/package.json:45 — litemall-admin/package.json declares dependencies that no committed lockfile resolves — there is no package-lock.json / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
  • JavaScript dependencies are not locked litemall-vue/package.json:16 — litemall-vue/package.json declares dependencies that no committed lockfile resolves — there is no package-lock.json / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
AC3 · Page structure · Heading level jumps from h2 to h6 · ×1
  • Heading level jumps from h2 to h6 litemall-admin/src/views/errorPage/401.vue:9 — Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
AC4 · Keyboard semantics · Anchor without href · ×1
  • Anchor without href litemall-admin/src/components/Breadcrumb/index.vue:6 — An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
AC4 · Keyboard semantics · Positive tabindex (1) · ×1
  • Positive tabindex (1) litemall-admin/src/views/login/index.vue:14 — A positive tabindex forces a manual tab order that fights the DOM and is fragile. Use tabindex="0" (or restructure the DOM).
AC4 · Keyboard semantics · Positive tabindex (2) · ×1
  • Positive tabindex (2) litemall-admin/src/views/login/index.vue:21 — A positive tabindex forces a manual tab order that fights the DOM and is fragile. Use tabindex="0" (or restructure the DOM).
AC6 · Visual & motion safety · Low contrast colour pair in CSS (1.9 · ×1
  • Low contrast colour pair in CSS (1.9:1) litemall-admin/src/views/layout/components/TagsView/index.vue:282 — `&:hover` sets color: #fff on background-color: #b4bccc — 1.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 (3.8 · ×1
  • Low contrast colour pair in CSS (3.8:1) litemall-admin/src/views/errorPage/404.vue:198 — `&__return-home` sets color: #ffffff on background-color: #1482f0 — 3.8:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
D1 · Cyclomatic Complexity · WxOrderService.submit (cyclomatic 48) · ×1
  • WxOrderService.submit (cyclomatic 48) litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/service/WxOrderService.java:248 — WxOrderService.submit has cyclomatic complexity 48 (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 · CouponVerifyService.checkCoupon (cyclomatic 22) · ×1
  • CouponVerifyService.checkCoupon (cyclomatic 22) litemall-db/src/main/java/org/linlinjava/litemall/db/service/CouponVerifyService.java:32 — CouponVerifyService.checkCoupon 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.
D1 · Cyclomatic Complexity · WxCartController.checkout (cyclomatic 21) · ×1
  • WxCartController.checkout (cyclomatic 21) litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxCartController.java:409 — WxCartController.checkout has cyclomatic complexity 21 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · AdminGoodsService.validate (cyclomatic 20) · ×1
  • AdminGoodsService.validate (cyclomatic 20) litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/service/AdminGoodsService.java:51 — AdminGoodsService.validate has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D2 · Cognitive Complexity · WxOrderService.submit (cognitive 82) · ×1
  • WxOrderService.submit (cognitive 82) litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/service/WxOrderService.java:248 — WxOrderService.submit has cognitive complexity 82 (threshold 15). Drivers by points: if/else 40 (65 pts), boolean chains 10, loops 4 (7 pts) (nesting depth added 28). 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 · CouponVerifyService.checkCoupon (cognitive 33) · ×1
  • CouponVerifyService.checkCoupon (cognitive 33) litemall-db/src/main/java/org/linlinjava/litemall/db/service/CouponVerifyService.java:32 — CouponVerifyService.checkCoupon has cognitive complexity 33 (threshold 15). Drivers by points: if/else 14 (19 pts), loops 3 (7 pts), boolean chains 4, ternaries 1 (3 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · WxCartController.checkout (cognitive 31) · ×1
  • WxCartController.checkout (cognitive 31) litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxCartController.java:409 — WxCartController.checkout has cognitive complexity 31 (threshold 15). Drivers by points: if/else 19 (25 pts), boolean chains 4, loops 2 (nesting depth added 6). 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 · getHtml (cognitive 29) · ×1
  • getHtml (cognitive 29) litemall-admin/src/utils/print.js:42 — getHtml has cognitive complexity 29 (threshold 15). Drivers by points: if/else 10 (22 pts), loops 4 (6 pts), boolean chains 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · AdminGoodsService.validate (cognitive 28) · ×1
  • AdminGoodsService.validate (cognitive 28) litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/service/AdminGoodsService.java:51 — AdminGoodsService.validate has cognitive complexity 28 (threshold 15). Drivers by points: if/else 13 (22 pts), boolean chains 3, loops 3 (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.
D2 · Cognitive Complexity · PermissionUtil.listPermVo (cognitive 25) · ×1
  • PermissionUtil.listPermVo (cognitive 25) litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/util/PermissionUtil.java:21 — PermissionUtil.listPermVo has cognitive complexity 25 (threshold 15). Drivers by points: if/else 8 (18 pts), loops 4 (7 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · (anonymous) (cognitive 22) · ×1
  • (anonymous) (cognitive 22) litemall-admin/src/permission.js:19 — (anonymous) has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (17 pts), error handling 1 (4 pts), boolean chains 1 (nesting depth added 10). Of this number, 21 points are the body's own statements and 1 belongs to 4 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · getGoodsInfo (cognitive 22) · ×1
  • getGoodsInfo (cognitive 22) litemall-wx/pages/goods/goods.js:130 — getGoodsInfo has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (19 pts), loops 1 (3 pts) (nesting depth added 13). None of this is in the body itself: all 22 points belong to one function literal inside it that branches (line 134). 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.
D2 · Cognitive Complexity · WxOrderService.payNotify (cognitive 19) · ×1
  • WxOrderService.payNotify (cognitive 19) litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/service/WxOrderService.java:728 — WxOrderService.payNotify has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (13 pts), loops 1 (3 pts), error handling 2, boolean chains 1 (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.
D2 · Cognitive Complexity · WxCartController.fastadd (cognitive 19) · ×1
  • WxCartController.fastadd (cognitive 19) litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxCartController.java:187 — WxCartController.fastadd has cognitive complexity 19 (threshold 15). Drivers by points: if/else 12 (16 pts), boolean chains 2, ternaries 1 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · getGoodsInfo (cognitive 19) · ×1
  • getGoodsInfo (cognitive 19) renard-wx/pages/goods/goods.js:85 — getGoodsInfo has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (16 pts), loops 1 (3 pts) (nesting depth added 12). None of this is in the body itself: all 19 points belong to 2 function literals inside it that branch (lines 97, 90). 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 · AdminGoodsService.update (cognitive 18) · ×1
  • AdminGoodsService.update (cognitive 18) litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/service/AdminGoodsService.java:144 — AdminGoodsService.update has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (12 pts), loops 5, boolean chains 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PermissionUtil.listPermission (cognitive 18) · ×1
  • PermissionUtil.listPermission (cognitive 18) litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/util/PermissionUtil.java:88 — PermissionUtil.listPermission has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (14 pts), loops 2 (3 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 · WxAuthController.register (cognitive 18) · ×1
  • WxAuthController.register (cognitive 18) litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxAuthController.java:236 — WxAuthController.register has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 3, error handling 1 (2 pts) (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 · WxCartController.add (cognitive 18) · ×1
  • WxCartController.add (cognitive 18) litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxCartController.java:113 — WxCartController.add has cognitive complexity 18 (threshold 15). Drivers by points: if/else 12 (16 pts), boolean chains 2 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · permission.router.beforeEach() (cognitive 18) · ×1
  • permission.router.beforeEach() (cognitive 18) litemall-admin/src/permission.js:19 — permission.router.beforeEach() has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (17 pts), boolean chains 1 (nesting depth added 7). Of this number, 17 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · startUpload (cognitive 18) · ×1
  • startUpload (cognitive 18) litemall-wx/lib/vant-weapp/uploader/index.js:70 — startUpload has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (11 pts), ternaries 4 (7 pts) (nesting depth added 5). Most of this is not in the body itself: 3 of the 18 points are its own statements and the rest belongs to 5 function items inside it that branch (a function literal at line 98, a function literal at line 79, a function literal at line 89, …). 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 · IpUtil.getIpAddr (cognitive 16) · ×1
  • IpUtil.getIpAddr (cognitive 16) litemall-core/src/main/java/org/linlinjava/litemall/core/util/IpUtil.java:17 — IpUtil.getIpAddr has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (8 pts), boolean chains 4, error handling 2 (4 pts) (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · addToCart (cognitive 16) · ×1
  • addToCart (cognitive 16) litemall-wx/pages/goods/goods.js:558 — addToCart has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 1 (nesting depth added 6). Of this number, 9 points are the body's own statements and 7 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D3 · God Classes · MethodTooLong · ×1
  • MethodTooLong: WxOrderService.submit litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/service/WxOrderService.java:248 — MethodTooLong — submit runs 173 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 73 over it, 1.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.
D3 · God Classes · ClassTooLong · ×1
  • ClassTooLong: WxOrderService litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/service/WxOrderService.java:69 — ClassTooLong — 559 significant lines (blank, comment-only and punctuation-only lines excluded), 13 methods. The bar is 400 significant lines; this is 159 over it, 1.40× 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.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D4 · Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (4 members, 50+ identical tokens) litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallAftersaleService.java:32 — litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallAftersaleService.java:32-49 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallAftersaleService.java:51-73 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallCouponService.java:107-128 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallCouponUserService.java:38-61 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication · Edited copy of a member (69 corresponding lines) · ×1
  • Edited copy of a member (69 corresponding lines) litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxCouponController.java:177 — litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxCouponController.java:177-245 | litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxCouponController.java:255-324 — These two members are one piece of code written twice and then edited apart: 69 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (61 corresponding lines) · ×1
  • Edited copy of a member (61 corresponding lines) litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxCartController.java:113 — litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxCartController.java:113-173 | litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxCartController.java:187-247 — These two members are one piece of code written twice and then edited apart: 61 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (34 corresponding lines) · ×1
  • Edited copy of a member (34 corresponding lines) litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxAuthController.java:382 — litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxAuthController.java:382-415 | litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxAuthController.java:433-468 — These two members are one piece of code written twice and then edited apart: 34 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (33 corresponding lines) · ×1
  • Edited copy of a member (33 corresponding lines) litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallGoodsService.java:91 — litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallGoodsService.java:91-128 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallGoodsService.java:215-247 — These two members are one piece of code written twice and then edited apart: 33 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (24 corresponding lines) · ×1
  • Edited copy of a member (24 corresponding lines) litemall-core/src/main/java/org/linlinjava/litemall/core/qcode/QCodeService.java:31 — litemall-core/src/main/java/org/linlinjava/litemall/core/qcode/QCodeService.java:31-54 | litemall-core/src/main/java/org/linlinjava/litemall/core/qcode/QCodeService.java:64-89 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 19+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 19+ corresponding lines) litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallCollectService.java:65 — litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallCollectService.java:65-83 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallCommentService.java:59-80 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallFootprintService.java:47-65 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallSearchHistoryService.java:38-56 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 19 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (6 members, 18+ corresponding lines) · ×1
  • Edited copies of one member (6 members, 18+ corresponding lines) litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallAdService.java:25 — litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallAdService.java:25-43 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallKeywordService.java:39-57 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallNoticeService.java:22-40 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallRegionService.java:36-53 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallTopicService.java:66-84 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallUserService.java:49-67 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 18 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (19 corresponding lines) · ×1
  • Edited copy of a member (19 corresponding lines) litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallCartService.java:83 — litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallCartService.java:83-101 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallFeedbackService.java:29-47 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 18+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 18+ corresponding lines) litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminAftersaleController.java:72 — litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminAftersaleController.java:72-89 | litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminAftersaleController.java:94-117 | litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminAftersaleController.java:122-139 | litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminAftersaleController.java:144-163 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 18 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (12 corresponding lines) · ×1
  • Edited copy of a member (12 corresponding lines) litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminCategoryController.java:142 — litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminCategoryController.java:142-153 | litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminRoleController.java:62-74 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 16+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 16+ corresponding lines) litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallPermissionService.java:23 — litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallPermissionService.java:23-38 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallPermissionService.java:41-56 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallPermissionService.java:58-73 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (13 corresponding lines) · ×1
  • Edited copy of a member (13 corresponding lines) litemall-core/src/main/java/org/linlinjava/litemall/core/storage/QiniuStorage.java:67 — litemall-core/src/main/java/org/linlinjava/litemall/core/storage/QiniuStorage.java:67-81 | litemall-core/src/main/java/org/linlinjava/litemall/core/storage/QiniuStorage.java:108-120 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (8 members, 12+ corresponding lines) · ×1
  • Edited copies of one member (8 members, 12+ corresponding lines) litemall-core/src/main/java/org/linlinjava/litemall/core/util/JacksonUtil.java:18 — litemall-core/src/main/java/org/linlinjava/litemall/core/util/JacksonUtil.java:18-30 | litemall-core/src/main/java/org/linlinjava/litemall/core/util/JacksonUtil.java:33-47 | litemall-core/src/main/java/org/linlinjava/litemall/core/util/JacksonUtil.java:49-61 | litemall-core/src/main/java/org/linlinjava/litemall/core/util/JacksonUtil.java:63-77 | litemall-core/src/main/java/org/linlinjava/litemall/core/util/JacksonUtil.java:80-92 | litemall-core/src/main/java/org/linlinjava/litemall/core/util/JacksonUtil.java:94-108 | litemall-core/src/main/java/org/linlinjava/litemall/core/util/JacksonUtil.java:110-124 | litemall-core/src/main/java/org/linlinjava/litemall/core/util/JacksonUtil.java:126-137 — These 8 members are one piece of code written 8 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 8 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (8 corresponding lines) · ×1
  • Edited copy of a member (8 corresponding lines) litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminStatController.java:43 — litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminStatController.java:43-51 | litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminStatController.java:56-63 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 12+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 12+ corresponding lines) litemall-core/src/main/java/org/linlinjava/litemall/core/storage/AliyunStorage.java:107 — litemall-core/src/main/java/org/linlinjava/litemall/core/storage/AliyunStorage.java:107-120 | litemall-core/src/main/java/org/linlinjava/litemall/core/storage/LocalStorage.java:81-94 | litemall-core/src/main/java/org/linlinjava/litemall/core/storage/QiniuStorage.java:94-105 | litemall-core/src/main/java/org/linlinjava/litemall/core/storage/TencentStorage.java:110-121 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (8 members, 8+ corresponding lines) · ×1
  • Edited copies of one member (8 members, 8+ corresponding lines) litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallAftersaleService.java:109 — litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallAftersaleService.java:109-116 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallAftersaleService.java:122-129 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallNoticeAdminService.java:70-77 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallNoticeAdminService.java:79-86 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallNoticeAdminService.java:100-107 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallNoticeAdminService.java:109-116 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallNoticeService.java:61-68 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallTopicService.java:104-111 — These 8 members are one piece of code written 8 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 8 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 4+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 4+ corresponding lines) litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/service/AdminGoodsService.java:46 — litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/service/AdminGoodsService.java:46-49 | litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminAftersaleController.java:64-67 | litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminCouponController.java:41-44 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (6 members, 5+ corresponding lines) · ×1
  • Edited copies of one member (6 members, 5+ corresponding lines) litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallAddressService.java:31 — litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallAddressService.java:31-35 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallCollectService.java:59-63 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallCommentService.java:53-57 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallFeedbackService.java:23-27 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallOrderGoodsService.java:17-21 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallOrderService.java:27-31 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 5 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 5+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 5+ corresponding lines) litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallGoodsAttributeService.java:17 — litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallGoodsAttributeService.java:17-21 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallGoodsProductService.java:21-25 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallGoodsSpecificationService.java:20-24 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 5 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (6 members, 4+ corresponding lines) · ×1
  • Edited copies of one member (6 members, 4+ corresponding lines) litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminAdminController.java:45 — litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminAdminController.java:45-48 | litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminGrouponController.java:87-90 | litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminIssueController.java:36-39 | litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminLogController.java:37-40 | litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminRoleController.java:56-59 | litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxIssueController.java:36-39 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication · Duplicated block (47 lines × 2) · ×1
  • Duplicated block (47 lines × 2) litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxCartController.java:114 — litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxCartController.java:114-160 | litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxCartController.java:188-234 — 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 `litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxCartController.java:114` 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 (4–22 lines × 3) · ×1
  • Duplicated block (4–22 lines × 3) litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/service/WxOrderService.java:333 — litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/service/WxOrderService.java:333-336 | litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxCartController.java:433-454 | litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxCouponController.java:131-152 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/service/WxOrderService.java:333` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (20 lines × 2) · ×1
  • Duplicated block (20 lines × 2) litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallGoodsService.java:100 — litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallGoodsService.java:100-119 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallGoodsService.java:220-239 — 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 (18 lines × 2) · ×1
  • Duplicated block (18 lines × 2) litemall-core/src/main/java/org/linlinjava/litemall/core/util/ResponseUtil.java:59 — litemall-core/src/main/java/org/linlinjava/litemall/core/util/ResponseUtil.java:59-76 | litemall-core/src/main/java/org/linlinjava/litemall/core/util/ResponseUtil.java:79-96 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (17 lines × 2) · ×1
  • Duplicated block (17 lines × 2) litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/service/AdminOrderService.java:124 — litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/service/AdminOrderService.java:124-140 | litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminAftersaleController.java:187-203 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (16 lines × 3) · ×1
  • Duplicated block (16 lines × 3) litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/service/WxOrderService.java:837 — litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/service/WxOrderService.java:837-852 | litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/service/WxOrderService.java:882-897 | litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/service/WxOrderService.java:925-940 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/service/WxOrderService.java:837` 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 (14–15 lines × 2) · ×1
  • Duplicated block (14–15 lines × 2) litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxStorageController.java:68 — litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxStorageController.java:68-81 | litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxStorageController.java:93-107 — 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 (10–14 lines × 2) · ×1
  • Duplicated block (10–14 lines × 2) litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminAftersaleController.java:95 — litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminAftersaleController.java:95-108 | litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminAftersaleController.java:145-154 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminAftersaleController.java:95` 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.
D4 · Code Duplication · Duplicated block (13–14 lines × 2) · ×1
  • Duplicated block (13–14 lines × 2) litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxGoodsController.java:168 — litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxGoodsController.java:168-180 | litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxHomeController.java:120-133 — 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 `litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxGoodsController.java:168` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxGoodsController.java:181` calls `put` and `litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxHomeController.java:134` 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 (13 lines × 2) · ×1
  • Duplicated block (13 lines × 2) litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/service/AdminOrderService.java:151 — litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/service/AdminOrderService.java:151-163 | litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/service/WxOrderService.java:577-589 — 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.
D4 · Code Duplication · Duplicated block (11–12 lines × 2) · ×1
  • Duplicated block (11–12 lines × 2) litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/service/WxOrderService.java:642 — litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/service/WxOrderService.java:642-652 | litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/service/WxOrderService.java:699-710 — 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 `litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/service/WxOrderService.java:642` 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 (10–11 lines × 2) · ×1
  • Duplicated block (10–11 lines × 2) litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallOrderService.java:83 — litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallOrderService.java:83-92 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallOrderService.java:111-121 — 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 `litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallOrderService.java:83` 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 (9–10 lines × 2) · ×1
  • Duplicated block (9–10 lines × 2) litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/util/PermissionUtil.java:117 — litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/util/PermissionUtil.java:117-126 | litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/util/PermissionUtil.java:128-136 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. 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 (8 lines × 5) · ×1
  • Duplicated block (8 lines × 5) litemall-core/src/main/java/org/linlinjava/litemall/core/util/CharUtil.java:9 — litemall-core/src/main/java/org/linlinjava/litemall/core/util/CharUtil.java:9-16 | litemall-core/src/main/java/org/linlinjava/litemall/core/util/CharUtil.java:20-27 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallAftersaleService.java:77-84 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallCouponService.java:149-156 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallOrderService.java:51-58 — there are 5 copies across 4 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 5 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `litemall-core/src/main/java/org/linlinjava/litemall/core/util/CharUtil.java:9` 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 × 5) · ×1
  • Duplicated block (7 lines × 5) litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallSystemConfigService.java:23 — litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallSystemConfigService.java:23-30 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallSystemConfigService.java:35-41 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallSystemConfigService.java:46-52 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallSystemConfigService.java:57-63 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallSystemConfigService.java:68-74 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallSystemConfigService.java:23` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 × 3) · ×1
  • Duplicated block (7 lines × 3) litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallAftersaleService.java:60 — litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallAftersaleService.java:60-66 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallCouponService.java:117-124 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallCouponUserService.java:47-54 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Note first that the copies are not typed on the same thing: `StringUtils` names `com.alibaba.druid.util.StringUtils` in one and `org.springframework.util.StringUtils` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallAftersaleService.java:68` calls `setOrderByClause`, `desc` and `litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallCouponService.java:126` 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 (3–7 lines × 3) · ×1
  • Duplicated block (3–7 lines × 3) litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/service/WxOrderService.java:338 — litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/service/WxOrderService.java:338-345 | litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxCartController.java:456-462 | litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxCouponController.java:153-155 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/service/WxOrderService.java:338` 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.
D4 · Code Duplication · Duplicated block (6 lines × 3) · ×1
  • Duplicated block (6 lines × 3) litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminRegionController.java:51 — litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminRegionController.java:51-56 | litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminRegionController.java:60-65 | litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminRegionController.java:69-74 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminRegionController.java:51` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (6 lines × 2) · ×1
  • Duplicated block (6 lines × 2) litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/service/WxOrderService.java:490 — litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/service/WxOrderService.java:490-495 | litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/service/WxOrderService.java:790-795 — 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 `litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/service/WxOrderService.java:490` 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 (26 lines × 2) · ×1
  • Duplicated block (26 lines × 2) litemall-core/src/main/java/org/linlinjava/litemall/core/validator/OrderValidator.java:1 — litemall-core/src/main/java/org/linlinjava/litemall/core/validator/OrderValidator.java:1-26 | litemall-core/src/main/java/org/linlinjava/litemall/core/validator/SortValidator.java:1-26 — 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 `litemall-core/src/main/java/org/linlinjava/litemall/core/validator/OrderValidator.java:1` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (8 lines × 6) · ×1
  • Duplicated block (8 lines × 6) litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminAdController.java:56 — litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminAdController.java:56-63 | litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminBrandController.java:63-70 | litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminCategoryController.java:96-103 | litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminIssueController.java:56-63 | litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminKeywordController.java:52-59 | litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminTopicController.java:70-77 — before extracting anything, compare `litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminAdController.java` and `litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminIssueController.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 39 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. 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, `litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminAdController.java:66` calls `RequiresPermissionsDesc` and `litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminIssueController.java:66` 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 × 7) · ×1
  • Duplicated block (8 lines × 7) litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminAdController.java:91 — litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminAdController.java:91-98 | litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminBrandController.java:97-104 | litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminCategoryController.java:131-138 | litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminCommentController.java:42-49 | litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminGrouponController.java:181-189 | litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminIssueController.java:90-97 | litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminKeywordController.java:86-93 — before extracting anything, compare `litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminAdController.java` and `litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminIssueController.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 39 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. 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 × 24) · ×1
  • Duplicated block (5 lines × 24) litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallAdService.java:54 — litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallAdService.java:54-58 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallAdminService.java:57-61 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallAftersaleService.java:103-107 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallBrandService.java:68-72 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallCartService.java:26-30 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallCategoryService.java:85-89 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallCouponService.java:130-134 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallCouponUserService.java:32-36 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallFootprintService.java:41-45 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallGoodsAttributeService.java:23-27 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallGoodsProductService.java:35-39 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallGoodsService.java:198-202 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallGoodsSpecificationService.java:36-40 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallIssueService.java:23-27 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallKeywordService.java:59-63 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallLogService.java:24-28 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallNoticeAdminService.java:49-53 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallNoticeService.java:51-55 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallPermissionService.java:101-105 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallRoleService.java:61-65 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallSearchHistoryService.java:19-23 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallStorageService.java:25-29 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallTopicService.java:97-101 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallUserService.java:38-42 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 24 call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallKeywordService.java:65` calls `findById`, `selectByPrimaryKey` and `litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallCartService.java:32` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (5 lines × 6) · ×1
  • Duplicated block (5 lines × 6) litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallAddressService.java:25 — litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallAddressService.java:25-29 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallAftersaleService.java:26-30 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallAftersaleService.java:136-140 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallFootprintService.java:31-35 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallGrouponService.java:90-94 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallOrderService.java:43-47 — there are 6 copies across 5 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, `litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallFootprintService.java:37` calls `deleteById`, `logicalDeleteByPrimaryKey` and `litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallAddressService.java:31` 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 × 4) · ×1
  • Duplicated block (5 lines × 4) litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallAftersaleService.java:86 — litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallAftersaleService.java:86-90 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallCollectService.java:43-47 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallCouponUserService.java:26-30 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallOrderService.java:60-64 — 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. 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 × 5) · ×1
  • Duplicated block (5 lines × 5) litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallGoodsProductService.java:41 — litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallGoodsProductService.java:41-45 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallGoodsService.java:209-213 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallOrderService.java:138-142 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallTopicService.java:34-38 | litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallUserService.java:69-74 — 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. 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 × 3) · ×1
  • Duplicated block (5 lines × 3) litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/service/WxOrderService.java:150 — litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/service/WxOrderService.java:150-154 | litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxGrouponController.java:123-127 | litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxGrouponController.java:261-265 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/service/WxOrderService.java:150` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxGrouponController.java:128` calls `put`, `getOrderId`, `getGoodsId` and `litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/service/WxOrderService.java:155` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D44 · Platform End-of-Life · End-of-life framework · ×1
  • End-of-life framework: Spring Boot 2 REDACTED:1 — REDACTED depends on `org.springframework.boot` at a version that pins Spring Boot 2, and Spring Boot 2.x, open-source support ended 2023-11-24. The constraint cannot admit a different major, so this repository stays on it until the declaration is edited. An end-of-life framework receives no further releases, including security releases.
P7 · Outbound HTTP resilience · Outbound HTTP without resilience · ×1
  • Outbound HTTP without resilience litemall-core/src/main/java/org/linlinjava/litemall/core/util/HttpUtil.java:37 — `.openConnection(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
R1 · Type Safety · Type Safety · ×1
  • Type Safety — 0 typed · 364 plain JS — the untyped files are litemall-admin/src/App.vue, litemall-admin/src/api/ad.js, litemall-admin/src/api/admin.js, litemall-admin/src/api/aftersale.js, litemall-admin/src/api/brand.js, litemall-admin/src/api/category.js (+358 more).
R10 · Code Duplication · Duplication concentrated across 4 sibling directories (61 clone groups) · ×1
  • Duplication concentrated across 4 sibling directories (61 clone groups) REDACTED:12 — 61 duplicated blocks under the repository root have copies in at least two of the sibling directories litemall-admin, litemall-vue, litemall-wx, renard-wx — 49 of them are reported below, and 12 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 61 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 61 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 61 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Duplication concentrated across 6 sibling directories (21 clone groups) · ×1
  • Duplication concentrated across 6 sibling directories (21 clone groups) litemall-admin/src/views/mall/keyword.vue:113 — 21 duplicated blocks under litemall-admin/src/views/ have copies in at least two of the sibling directories goods, mall, profile, promotion, sys, user — 18 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 21 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 21 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 21 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Duplication concentrated across 5 sibling directories (8 clone groups) · ×1
  • Duplication concentrated across 5 sibling directories (8 clone groups) litemall-vue/src/views/order/order-detail/index.vue:114 — 8 duplicated blocks under litemall-vue/src/views/ have copies in at least two of the sibling directories home, items, login, order, user — 6 of them are reported below, and 2 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 8 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 8 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 8 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Duplication concentrated across 11 sibling directories (7 clone groups) · ×1
  • Duplication concentrated across 11 sibling directories (7 clone groups) litemall-wx/lib/vant-weapp/checkbox-group/index.js:2 — 7 of the duplicated blocks reported below have copies in at least two of the sibling directories checkbox-group, collapse, dialog, dropdown-menu, goods-action, grid (+5 more sibling(s) not listed) under litemall-wx/lib/vant-weapp/. That concentration is one structural fact, not 7 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 7 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Wholesale file copy (1082 identical lines × 2 files) · ×1
  • Wholesale file copy (1082 identical lines × 2 files) REDACTED:12 — REDACTED:12 · REDACTED:12 — these 2 files are line-for-line copies of one another — 1082 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Duplicated block with local edits (325 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (325 matched lines × 2 locations) litemall-wx/pages/goods/goods.js:175 — litemall-wx/pages/goods/goods.js:175 · renard-wx/pages/goods/goods.js:131 — the two spans are one implementation copied and then locally edited — 1792 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Wholesale file copy (241 identical lines × 2 files) · ×1
  • Wholesale file copy (241 identical lines × 2 files) litemall-wx/pages/ucenter/addressAdd/addressAdd.js:1 — litemall-wx/pages/ucenter/addressAdd/addressAdd.js:1 · renard-wx/pages/ucenter/addressAdd/addressAdd.js:1 — these 2 files are line-for-line copies of one another — 241 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Wholesale file copy (216 identical lines × 2 files) · ×1
  • Wholesale file copy (216 identical lines × 2 files) litemall-wx/pages/cart/cart.js:1 — litemall-wx/pages/cart/cart.js:1 · renard-wx/pages/cart/cart.js:1 — these 2 files are line-for-line copies of one another — 216 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Wholesale file copy (174 identical lines × 2 files) · ×1
  • Wholesale file copy (174 identical lines × 2 files) litemall-wx/lib/wxParse/wxDiscode.js:2 — litemall-wx/lib/wxParse/wxDiscode.js:2 · renard-wx/lib/wxParse/wxDiscode.js:2 — these 2 files are line-for-line copies of one another — 174 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Wholesale file copy (151 identical lines × 2 files) · ×1
  • Wholesale file copy (151 identical lines × 2 files) litemall-wx/pages/ucenter/orderDetail/orderDetail.js:1 — litemall-wx/pages/ucenter/orderDetail/orderDetail.js:1 · renard-wx/pages/ucenter/orderDetail/orderDetail.js:1 — these 2 files are line-for-line copies of one another — 151 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Wholesale file copy (148 identical lines × 2 files) · ×1
  • Wholesale file copy (148 identical lines × 2 files) litemall-wx/pages/search/search.js:1 — litemall-wx/pages/search/search.js:1 · renard-wx/pages/search/search.js:1 — these 2 files are line-for-line copies of one another — 148 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Wholesale file copy (140 identical lines × 2 files) · ×1
  • Wholesale file copy (140 identical lines × 2 files) litemall-wx/lib/wxParse/html2json.js:12 — litemall-wx/lib/wxParse/html2json.js:12 · renard-wx/lib/wxParse/html2json.js:12 — these 2 files are line-for-line copies of one another — 140 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Wholesale file copy (114 identical lines × 2 files) · ×1
  • Wholesale file copy (114 identical lines × 2 files) litemall-admin/src/views/promotion/topicCreate.vue:118 — litemall-admin/src/views/promotion/topicCreate.vue:118 · litemall-admin/src/views/promotion/topicEdit.vue:118 — these 2 files are line-for-line copies of one another — 114 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Duplicated block (114 lines × 2 locations) · ×1
  • Duplicated block (114 lines × 2 locations) litemall-admin/src/views/sys/notice.vue:137 — litemall-admin/src/views/sys/notice.vue:137 · litemall-admin/src/views/sys/role.vue:109 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block with local edits (114 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (114 matched lines × 2 locations) litemall-wx/pages/auth/register/register.js:13 — litemall-wx/pages/auth/register/register.js:13 · litemall-wx/pages/auth/reset/reset.js:12 — the two spans are one implementation copied and then locally edited — 471 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Wholesale file copy (106 identical lines × 3 files) · ×1
  • Wholesale file copy (106 identical lines × 3 files) litemall-wx/pages/commentPost/commentPost.js:2 — litemall-wx/pages/commentPost/commentPost.js:2 · litemall-wx/pages/topicCommentPost/topicCommentPost.js:2 · renard-wx/pages/commentPost/commentPost.js:2 — these 3 files are line-for-line copies of one another — 106 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Duplicated block (100 lines × 3 locations) · ×1
  • Duplicated block (100 lines × 3 locations) litemall-admin/src/views/mall/keyword.vue:113 — litemall-admin/src/views/mall/keyword.vue:113 · litemall-admin/src/views/sys/notice.vue:138 · litemall-admin/src/views/sys/role.vue:110 — the 3 copies are spread across 3 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 · Wholesale file copy (97 identical lines × 2 files) · ×1
  • Wholesale file copy (97 identical lines × 2 files) litemall-wx/pages/comment/comment.js:1 — litemall-wx/pages/comment/comment.js:1 · litemall-wx/pages/topicComment/topicComment.js:1 — these 2 files are line-for-line copies of one another — 97 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Wholesale file copy (94 identical lines × 2 files) · ×1
  • Wholesale file copy (94 identical lines × 2 files) litemall-wx/lib/wxParse/htmlparser.js:12 — litemall-wx/lib/wxParse/htmlparser.js:12 · renard-wx/lib/wxParse/htmlparser.js:12 — these 2 files are line-for-line copies of one another — 94 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Duplicated block (92 lines × 2 locations) · ×1
  • Duplicated block (92 lines × 2 locations) litemall-admin/src/views/goods/create.vue:404 — litemall-admin/src/views/goods/create.vue:404 · litemall-admin/src/views/goods/edit.vue:413 — 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 (86 lines × 2 locations) · ×1
  • Duplicated block (86 lines × 2 locations) litemall-admin/src/views/mall/issue.vue:113 — litemall-admin/src/views/mall/issue.vue:113 · litemall-admin/src/views/sys/admin.vue:208 — 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 · Wholesale file copy (80 identical lines × 2 files) · ×1
  • Wholesale file copy (80 identical lines × 2 files) litemall-wx/lib/wxParse/wxParse.js:15 — litemall-wx/lib/wxParse/wxParse.js:15 · renard-wx/lib/wxParse/wxParse.js:15 — these 2 files are line-for-line copies of one another — 80 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Duplicated block (76 lines × 3 locations) · ×1
  • Duplicated block (76 lines × 3 locations) litemall-admin/src/views/sys/admin.vue:208 — litemall-admin/src/views/sys/admin.vue:208 · litemall-admin/src/views/sys/notice.vue:168 · litemall-admin/src/views/sys/role.vue:140 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block with local edits (73 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (73 matched lines × 2 locations) litemall-wx/pages/checkout/checkout.js:98 — litemall-wx/pages/checkout/checkout.js:98 · renard-wx/pages/shopping/checkout/checkout.js:80 — the two spans are one implementation copied and then locally edited — 375 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Wholesale file copy (72 identical lines × 4 files) · ×1
  • Wholesale file copy (72 identical lines × 4 files) litemall-wx/pages/hotGoods/hotGoods.js:1 — litemall-wx/pages/hotGoods/hotGoods.js:1 · litemall-wx/pages/newGoods/newGoods.js:1 · REDACTED:1 · REDACTED:1 — these 4 files are line-for-line copies of one another — 72 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Duplicated block with local edits (72 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (72 matched lines × 2 locations) litemall-wx/pages/index/index.js:6 — litemall-wx/pages/index/index.js:6 · renard-wx/pages/index/index.js:6 — the two spans are one implementation copied and then locally edited — 370 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block (68 lines × 4 locations) · ×1
  • Duplicated block (68 lines × 4 locations) litemall-admin/src/views/mall/brand.vue:197 — litemall-admin/src/views/mall/brand.vue:197 · litemall-admin/src/views/sys/admin.vue:216 · litemall-admin/src/views/sys/notice.vue:176 · litemall-admin/src/views/sys/role.vue:148 — the 4 copies are spread across 4 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 · Wholesale file copy (60 identical lines × 2 files) · ×1
  • Wholesale file copy (60 identical lines × 2 files) litemall-wx/pages/groupon/grouponList/grouponList.js:2 — litemall-wx/pages/groupon/grouponList/grouponList.js:2 · renard-wx/pages/groupon/grouponList/grouponList.js:2 — these 2 files are line-for-line copies of one another — 60 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Wholesale file copy (58 identical lines × 2 files) · ×1
  • Wholesale file copy (58 identical lines × 2 files) litemall-wx/pages/topic/topic.js:1 — litemall-wx/pages/topic/topic.js:1 · renard-wx/pages/topic/topic.js:1 — these 2 files are line-for-line copies of one another — 58 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Duplicated block (55 lines × 3 locations) · ×1
  • Duplicated block (55 lines × 3 locations) litemall-wx/pages/coupon/coupon.js:4 — litemall-wx/pages/coupon/coupon.js:4 · litemall-wx/pages/groupon/grouponList/grouponList.js:4 · renard-wx/pages/groupon/grouponList/grouponList.js:4 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block with local edits (54 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (54 matched lines × 2 locations) litemall-vue/src/views/order/order-detail/index.vue:114 — litemall-vue/src/views/order/order-detail/index.vue:114 · litemall-vue/src/views/user/order-list/index.vue:116 — the two spans are one implementation copied and then locally edited — 317 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Wholesale file copy (53 identical lines × 2 files) · ×1
  • Wholesale file copy (53 identical lines × 2 files) litemall-wx/utils/user.js:4 — litemall-wx/utils/user.js:4 · renard-wx/utils/user.js:4 — these 2 files are line-for-line copies of one another — 53 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Wholesale file copy (52 identical lines × 2 files) · ×1
  • Wholesale file copy (52 identical lines × 2 files) litemall-wx/pages/ucenter/address/address.js:1 — litemall-wx/pages/ucenter/address/address.js:1 · renard-wx/pages/ucenter/address/address.js:1 — these 2 files are line-for-line copies of one another — 52 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R2 · Cyclomatic Complexity · Complex function getHtml (cyclomatic 13, cognitive 29) · ×1
  • Complex function getHtml (cyclomatic 13, cognitive 29) litemall-admin/src/utils/print.js:42 — getHtml has cyclomatic complexity 13 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 specToProduct (cyclomatic 13, cognitive 24) · ×1
  • Complex function specToProduct (cyclomatic 13, cognitive 24) litemall-admin/src/views/goods/create.vue:533 — specToProduct has cyclomatic complexity 13 and cognitive complexity 24; 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 moveToTarget (cyclomatic 12, cognitive 17) · ×1
  • Complex function moveToTarget (cyclomatic 12, cognitive 17) litemall-admin/src/components/ScrollPane/index.vue:23 — moveToTarget has cyclomatic complexity 12 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 · litemall-wx/utils/area.js · ×1
  • litemall-wx/utils/area.js: 3285 lines of code litemall-wx/utils/area.js:1 — litemall-wx/utils/area.js has 3285 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 · renard-wx/utils/area.js · ×1
  • renard-wx/utils/area.js: 3284 lines of code renard-wx/utils/area.js:1 — renard-wx/utils/area.js has 3284 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 · REDACTED · ×1
  • REDACTED: 2174 lines of code REDACTED:1 — REDACTED has 2174 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 · REDACTED · ×1
  • REDACTED: 2154 lines of code REDACTED:1 — REDACTED has 2154 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 · litemall-admin/src/views/promotion/coupon.vue · ×1
  • litemall-admin/src/views/promotion/coupon.vue: 623 lines of code litemall-admin/src/views/promotion/coupon.vue:1 — litemall-admin/src/views/promotion/coupon.vue has 623 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 · REDACTED · ×1
  • REDACTED: 609 lines of code REDACTED:1 — REDACTED has 609 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 · litemall-wx/pages/goods/goods.js · ×1
  • litemall-wx/pages/goods/goods.js: 602 lines of code litemall-wx/pages/goods/goods.js:1 — litemall-wx/pages/goods/goods.js has 602 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 · litemall-admin/src/views/goods/create.vue · ×1
  • litemall-admin/src/views/goods/create.vue: 591 lines of code litemall-admin/src/views/goods/create.vue:1 — litemall-admin/src/views/goods/create.vue has 591 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 · litemall-admin/src/views/goods/edit.vue · ×1
  • litemall-admin/src/views/goods/edit.vue: 555 lines of code litemall-admin/src/views/goods/edit.vue:1 — litemall-admin/src/views/goods/edit.vue has 555 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 · renard-wx/pages/goods/goods.js · ×1
  • renard-wx/pages/goods/goods.js: 547 lines of code renard-wx/pages/goods/goods.js:1 — renard-wx/pages/goods/goods.js has 547 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 · litemall-admin/src/views/mall/order.vue · ×1
  • litemall-admin/src/views/mall/order.vue: 532 lines of code litemall-admin/src/views/mall/order.vue:1 — litemall-admin/src/views/mall/order.vue has 532 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 · litemall-vue/src/api/api.js · ×1
  • litemall-vue/src/api/api.js: 429 lines of code litemall-vue/src/api/api.js:1 — litemall-vue/src/api/api.js has 429 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 · litemall-vue/src/views/home/tabbar-home.vue · ×1
  • litemall-vue/src/views/home/tabbar-home.vue: 412 lines of code litemall-vue/src/views/home/tabbar-home.vue:1 — litemall-vue/src/views/home/tabbar-home.vue has 412 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 351 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
R6 · Tooling · No typecheck script · ×1
  • No typecheck script — test ✓ · lint ✓ · typecheck ✗ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
R7 · Dead Code · Dead file (~2529 LoC) · ×1
  • Dead file (~2529 LoC) REDACTED — no import path from any entry point (145 application, 90 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 (~2507 LoC) · ×1
  • Dead file (~2507 LoC) REDACTED — no import path from any entry point (145 application, 90 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 (~453 LoC) · ×1
  • Dead file (~453 LoC) litemall-vue/src/api/api.js — no import path from any entry point (145 application, 90 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 (~345 LoC) · ×1
  • Dead file (~345 LoC) litemall-vue/src/views/items/detail/index.vue — no import path from any entry point (145 application, 90 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 (~268 LoC) · ×1
  • Dead file (~268 LoC) litemall-vue/src/views/home/tabbar-home.vue — no import path from any entry point (145 application, 90 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 (~237 LoC) · ×1
  • Dead file (~237 LoC) litemall-vue/src/views/order/checkout.vue — no import path from any entry point (145 application, 90 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 (~213 LoC) · ×1
  • Dead file (~213 LoC) litemall-vue/src/views/order/tabbar-cart.vue — no import path from any entry point (145 application, 90 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 (~189 LoC) · ×1
  • Dead file (~189 LoC) litemall-vue/src/views/user/order-list/index.vue — no import path from any entry point (145 application, 90 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 (~188 LoC) · ×1
  • Dead file (~188 LoC) litemall-vue/src/views/order/order-detail/index.vue — no import path from any entry point (145 application, 90 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 (~187 LoC) · ×1
  • Dead file (~187 LoC) litemall-vue/src/views/order/payment/index.vue — no import path from any entry point (145 application, 90 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 (~147 LoC) · ×1
  • Dead file (~147 LoC) litemall-vue/src/views/items/search/index.vue — no import path from any entry point (145 application, 90 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 (~142 LoC) · ×1
  • Dead file (~142 LoC) litemall-vue/src/views/login/login.vue — no import path from any entry point (145 application, 90 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) litemall-vue/src/views/user/refund-list/index.vue — no import path from any entry point (145 application, 90 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 (~116 LoC) · ×1
  • Dead file (~116 LoC) litemall-vue/src/views/items/category/index.vue — no import path from any entry point (145 application, 90 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 (~107 LoC) · ×1
  • Dead file (~107 LoC) litemall-vue/src/views/user/coupon-list/index.vue — no import path from any entry point (145 application, 90 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 (~103 LoC) · ×1
  • Dead file (~103 LoC) litemall-vue/src/views/user/user-information-set/index.vue — no import path from any entry point (145 application, 90 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 (~89 LoC) · ×1
  • Dead file (~89 LoC) litemall-vue/src/views/user/user-information-set/set-mobile/index.vue — no import path from any entry point (145 application, 90 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 (~87 LoC) · ×1
  • Dead file (~87 LoC) litemall-vue/src/components/Tabbar/index.vue — no import path from any entry point (145 application, 90 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 (~86 LoC) · ×1
  • Dead file (~86 LoC) REDACTED — no import path from any entry point (145 application, 90 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 (~84 LoC) · ×1
  • Dead file (~84 LoC) litemall-vue/src/views/user/module-collect/index.vue — no import path from any entry point (145 application, 90 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 (~82 LoC) · ×1
  • Dead file (~82 LoC) litemall-vue/src/views/items/tabbar-catalog.vue — no import path from any entry point (145 application, 90 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 (~78 LoC) · ×1
  • Dead file (~78 LoC) litemall-vue/src/views/user/module-feedback/index.vue — no import path from any entry point (145 application, 90 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 (~77 LoC) · ×1
  • Dead file (~77 LoC) litemall-vue/src/views/items/brand/index.vue — no import path from any entry point (145 application, 90 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 (~76 LoC) · ×1
  • Dead file (~76 LoC) REDACTED — no import path from any entry point (145 application, 90 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 (~74 LoC) · ×1
  • Dead file (~74 LoC) litemall-admin/src/components/ScrollPane/index.vue — no import path from any entry point (145 application, 90 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 (~68 LoC) · ×1
  • Dead file (~68 LoC) litemall-vue/src/views/items/topic/index.vue — no import path from any entry point (145 application, 90 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 (~66 LoC) · ×1
  • Dead file (~66 LoC) litemall-wx/lib/vant-weapp/toast/toast.js — no import path from any entry point (145 application, 90 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 (~65 LoC) · ×1
  • Dead file (~65 LoC) litemall-vue/src/views/login/register-status/index.vue — no import path from any entry point (145 application, 90 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
R8 · Dependency Hygiene · Unused dependency '@vue/cli-plugin-unit-jest' · ×1
  • Unused dependency '@vue/cli-plugin-unit-jest' — Declared in litemall-admin/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
R8 · Dependency Hygiene · Unused dependency 'chokidar' · ×1
  • Unused dependency 'chokidar' — Declared in litemall-admin/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
R8 · Dependency Hygiene · Unused dependency 'core-js' · ×1
  • Unused dependency 'core-js' — Declared in litemall-admin/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
R8 · Dependency Hygiene · Unused dependency 'echarts' · ×1
  • Unused dependency 'echarts' — Declared in litemall-admin/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
R8 · Dependency Hygiene · Unused dependency 'file-saver' · ×1
  • Unused dependency 'file-saver' — Declared in litemall-admin/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
R8 · Dependency Hygiene · Unused dependency 'xlsx' · ×1
  • Unused dependency 'xlsx' — Declared in litemall-admin/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
R8 · Dependency Hygiene · Unused dependency 'vuelidate' · ×1
  • Unused dependency 'vuelidate' — Declared in litemall-vue/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
X1 · Async correctness · `async` Promise executor · ×1
  • `async` Promise executor litemall-admin/src/store/modules/user.js:104 — The function passed to `new Promise(…)` is `async`. The constructor ignores what its executor returns, so anything this executor throws — every throw inside an `async` function, including after an `await` — rejects a Promise nobody holds instead of the one being constructed: the outer Promise never settles, whoever awaits it hangs, and the error is reported nowhere. If the body needs `await`, it does not need `new Promise` at all: make the enclosing function `async` and `return` the value (or `throw`) directly. If it wraps a callback API, keep the executor synchronous — call the API and `resolve`/`reject` from its callback — and do the awaiting outside it.
X3 · Exception handling · Swallowed exception (caught, then discarded) · ×1
  • Swallowed exception (caught, then discarded) litemall-core/src/main/java/org/linlinjava/litemall/core/util/IpUtil.java:47 — `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.
Minor — 369 finding(s)
D34 · Knowledge Freshness · Orphaned file · ×247
  • Orphaned file litemall-core/src/main/java/org/linlinjava/litemall/core/util/bcrypt/BCrypt.java:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file litemall-admin/src/locales/zh-Hans.js: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 litemall-admin/src/locales/en.js: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 litemall-admin/src/views/promotion/coupon.vue: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 litemall-admin/src/views/goods/create.vue: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 litemall-admin/src/views/mall/order.vue: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 litemall-admin/src/views/goods/edit.vue: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 litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxCartController.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 litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxAuthController.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 litemall-wx/pages/goods/goods.js:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file REDACTED:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file renard-wx/pages/goods/goods.js: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 litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/service/AdminGoodsService.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 litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/service/AdminOrderService.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 litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxCouponController.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 litemall-admin/src/views/mall/aftersale.vue: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 litemall-admin/src/views/promotion/ad.vue: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 litemall-admin-api/src/main/java/org/linlinjava/litemall/admin/web/AdminAftersaleController.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 litemall-core/src/main/java/org/linlinjava/litemall/core/util/RegexUtil.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 litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxGrouponController.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 litemall-admin/src/views/promotion/topicEdit.vue: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 litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallOrderService.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 litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxGoodsController.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 litemall-admin/src/views/sys/notice.vue: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 litemall-vue/src/views/home/tabbar-home.vue: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.
  • + 222 more in this group — see findings.md.
D10 · Test Quality · No direct assertions · ×42
  • No direct assertions: test litemall-admin-api/src/test/java/org/linlinjava/litemall/admin/AdminConfigTest.java:19 — No conventional assertion call was detected, and 6 of 7 tests in `litemall-admin-api` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: test litemall-admin-api/src/test/java/org/linlinjava/litemall/admin/CreateShareImageTest.java:23 — No conventional assertion call was detected, and 6 of 7 tests in `litemall-admin-api` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: test litemall-admin-api/src/test/java/org/linlinjava/litemall/admin/DbTest.java:23 — No conventional assertion call was detected, and 6 of 7 tests in `litemall-admin-api` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: testFileCreate litemall-admin-api/src/test/java/org/linlinjava/litemall/admin/DbTest.java:36 — No conventional assertion call was detected, and 6 of 7 tests in `litemall-admin-api` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: testFileDelete litemall-admin-api/src/test/java/org/linlinjava/litemall/admin/DbTest.java:47 — No conventional assertion call was detected, and 6 of 7 tests in `litemall-admin-api` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: test litemall-admin-api/src/test/java/org/linlinjava/litemall/admin/PermissionTest.java:25 — No conventional assertion call was detected, and 6 of 7 tests in `litemall-admin-api` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: testGensaltTooLittleRounds litemall-core/src/test/java/org/linlinjava/litemall/core/util/bcrypt/BCryptTest.java:101 — No conventional assertion call was detected, and 28 of 31 tests in `litemall-core` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: testGensaltTooManyRounds litemall-core/src/test/java/org/linlinjava/litemall/core/util/bcrypt/BCryptTest.java:107 — No conventional assertion call was detected, and 28 of 31 tests in `litemall-core` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: testHashpwInvalidSaltRevision litemall-core/src/test/java/org/linlinjava/litemall/core/util/bcrypt/BCryptTest.java:45 — No conventional assertion call was detected, and 28 of 31 tests in `litemall-core` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: testHashpwInvalidSaltRevision2 litemall-core/src/test/java/org/linlinjava/litemall/core/util/bcrypt/BCryptTest.java:51 — No conventional assertion call was detected, and 28 of 31 tests in `litemall-core` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: testHashpwInvalidSaltVersion litemall-core/src/test/java/org/linlinjava/litemall/core/util/bcrypt/BCryptTest.java:33 — No conventional assertion call was detected, and 28 of 31 tests in `litemall-core` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: testHashpwInvalidSaltVersion2 litemall-core/src/test/java/org/linlinjava/litemall/core/util/bcrypt/BCryptTest.java:39 — No conventional assertion call was detected, and 28 of 31 tests in `litemall-core` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: testHashpwMissingSaltRounds litemall-core/src/test/java/org/linlinjava/litemall/core/util/bcrypt/BCryptTest.java:63 — No conventional assertion call was detected, and 28 of 31 tests in `litemall-core` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: testHashpwSaltIsNull litemall-core/src/test/java/org/linlinjava/litemall/core/util/bcrypt/BCryptTest.java:21 — No conventional assertion call was detected, and 28 of 31 tests in `litemall-core` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: testHashpwSaltTooShort litemall-core/src/test/java/org/linlinjava/litemall/core/util/bcrypt/BCryptTest.java:27 — No conventional assertion call was detected, and 28 of 31 tests in `litemall-core` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: testHashpwSaltTooShort2 litemall-core/src/test/java/org/linlinjava/litemall/core/util/bcrypt/BCryptTest.java:57 — No conventional assertion call was detected, and 28 of 31 tests in `litemall-core` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: testHashpwTooLittleRounds litemall-core/src/test/java/org/linlinjava/litemall/core/util/bcrypt/BCryptTest.java:69 — No conventional assertion call was detected, and 28 of 31 tests in `litemall-core` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: testHashpwTooManyRounds litemall-core/src/test/java/org/linlinjava/litemall/core/util/bcrypt/BCryptTest.java:75 — No conventional assertion call was detected, and 28 of 31 tests in `litemall-core` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: test litemall-core/src/test/java/org/linlinjava/litemall/core/AliyunStorageTest.java:28 — No conventional assertion call was detected, and 28 of 31 tests in `litemall-core` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: test litemall-core/src/test/java/org/linlinjava/litemall/core/AsyncTest.java:23 — No conventional assertion call was detected, and 28 of 31 tests in `litemall-core` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: test litemall-core/src/test/java/org/linlinjava/litemall/core/CoreConfigTest.java:23 — No conventional assertion call was detected, and 28 of 31 tests in `litemall-core` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: test litemall-core/src/test/java/org/linlinjava/litemall/core/ExpressTest.java:25 — No conventional assertion call was detected, and 28 of 31 tests in `litemall-core` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: test litemall-core/src/test/java/org/linlinjava/litemall/core/IntegerTest.java:7 — No conventional assertion call was detected, and 28 of 31 tests in `litemall-core` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: test litemall-core/src/test/java/org/linlinjava/litemall/core/LocalStorageTest.java:29 — No conventional assertion call was detected, and 28 of 31 tests in `litemall-core` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: testMail litemall-core/src/test/java/org/linlinjava/litemall/core/MailTest.java:38 — No conventional assertion call was detected, and 28 of 31 tests in `litemall-core` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • + 17 more in this group — see findings.md.
AX6 · Interface segregation · Fat interface · ×33
  • Fat interface: LitemallAdMapper (18 abstract methods) litemall-db/src/main/java/org/linlinjava/litemall/db/dao/LitemallAdMapper.java:8 — `LitemallAdMapper` declares 18 abstract methods: `countByExample`, `deleteByExample`, `deleteByPrimaryKey`, `insert`, `insertSelective`, `logicalDeleteByExample`, `logicalDeleteByPrimaryKey`, `selectByExample`, `selectByExampleSelective`, `selectByPrimaryKey`, `selectByPrimaryKeySelective`, `selectByPrimaryKeyWithLogicalDelete`, `selectOneByExample`, `selectOneByExampleSelective`, `updateByExample`, `updateByExampleSelective`, `updateByPrimaryKey`, `updateByPrimaryKeySelective`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: LitemallAddressMapper (18 abstract methods) litemall-db/src/main/java/org/linlinjava/litemall/db/dao/LitemallAddressMapper.java:8 — `LitemallAddressMapper` declares 18 abstract methods: `countByExample`, `deleteByExample`, `deleteByPrimaryKey`, `insert`, `insertSelective`, `logicalDeleteByExample`, `logicalDeleteByPrimaryKey`, `selectByExample`, `selectByExampleSelective`, `selectByPrimaryKey`, `selectByPrimaryKeySelective`, `selectByPrimaryKeyWithLogicalDelete`, `selectOneByExample`, `selectOneByExampleSelective`, `updateByExample`, `updateByExampleSelective`, `updateByPrimaryKey`, `updateByPrimaryKeySelective`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: LitemallAdminMapper (18 abstract methods) litemall-db/src/main/java/org/linlinjava/litemall/db/dao/LitemallAdminMapper.java:8 — `LitemallAdminMapper` declares 18 abstract methods: `countByExample`, `deleteByExample`, `deleteByPrimaryKey`, `insert`, `insertSelective`, `logicalDeleteByExample`, `logicalDeleteByPrimaryKey`, `selectByExample`, `selectByExampleSelective`, `selectByPrimaryKey`, `selectByPrimaryKeySelective`, `selectByPrimaryKeyWithLogicalDelete`, `selectOneByExample`, `selectOneByExampleSelective`, `updateByExample`, `updateByExampleSelective`, `updateByPrimaryKey`, `updateByPrimaryKeySelective`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: LitemallAftersaleMapper (18 abstract methods) litemall-db/src/main/java/org/linlinjava/litemall/db/dao/LitemallAftersaleMapper.java:8 — `LitemallAftersaleMapper` declares 18 abstract methods: `countByExample`, `deleteByExample`, `deleteByPrimaryKey`, `insert`, `insertSelective`, `logicalDeleteByExample`, `logicalDeleteByPrimaryKey`, `selectByExample`, `selectByExampleSelective`, `selectByPrimaryKey`, `selectByPrimaryKeySelective`, `selectByPrimaryKeyWithLogicalDelete`, `selectOneByExample`, `selectOneByExampleSelective`, `updateByExample`, `updateByExampleSelective`, `updateByPrimaryKey`, `updateByPrimaryKeySelective`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: LitemallBrandMapper (18 abstract methods) litemall-db/src/main/java/org/linlinjava/litemall/db/dao/LitemallBrandMapper.java:8 — `LitemallBrandMapper` declares 18 abstract methods: `countByExample`, `deleteByExample`, `deleteByPrimaryKey`, `insert`, `insertSelective`, `logicalDeleteByExample`, `logicalDeleteByPrimaryKey`, `selectByExample`, `selectByExampleSelective`, `selectByPrimaryKey`, `selectByPrimaryKeySelective`, `selectByPrimaryKeyWithLogicalDelete`, `selectOneByExample`, `selectOneByExampleSelective`, `updateByExample`, `updateByExampleSelective`, `updateByPrimaryKey`, `updateByPrimaryKeySelective`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: LitemallCartMapper (18 abstract methods) litemall-db/src/main/java/org/linlinjava/litemall/db/dao/LitemallCartMapper.java:8 — `LitemallCartMapper` declares 18 abstract methods: `countByExample`, `deleteByExample`, `deleteByPrimaryKey`, `insert`, `insertSelective`, `logicalDeleteByExample`, `logicalDeleteByPrimaryKey`, `selectByExample`, `selectByExampleSelective`, `selectByPrimaryKey`, `selectByPrimaryKeySelective`, `selectByPrimaryKeyWithLogicalDelete`, `selectOneByExample`, `selectOneByExampleSelective`, `updateByExample`, `updateByExampleSelective`, `updateByPrimaryKey`, `updateByPrimaryKeySelective`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: LitemallCategoryMapper (18 abstract methods) litemall-db/src/main/java/org/linlinjava/litemall/db/dao/LitemallCategoryMapper.java:8 — `LitemallCategoryMapper` declares 18 abstract methods: `countByExample`, `deleteByExample`, `deleteByPrimaryKey`, `insert`, `insertSelective`, `logicalDeleteByExample`, `logicalDeleteByPrimaryKey`, `selectByExample`, `selectByExampleSelective`, `selectByPrimaryKey`, `selectByPrimaryKeySelective`, `selectByPrimaryKeyWithLogicalDelete`, `selectOneByExample`, `selectOneByExampleSelective`, `updateByExample`, `updateByExampleSelective`, `updateByPrimaryKey`, `updateByPrimaryKeySelective`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: LitemallCollectMapper (18 abstract methods) litemall-db/src/main/java/org/linlinjava/litemall/db/dao/LitemallCollectMapper.java:8 — `LitemallCollectMapper` declares 18 abstract methods: `countByExample`, `deleteByExample`, `deleteByPrimaryKey`, `insert`, `insertSelective`, `logicalDeleteByExample`, `logicalDeleteByPrimaryKey`, `selectByExample`, `selectByExampleSelective`, `selectByPrimaryKey`, `selectByPrimaryKeySelective`, `selectByPrimaryKeyWithLogicalDelete`, `selectOneByExample`, `selectOneByExampleSelective`, `updateByExample`, `updateByExampleSelective`, `updateByPrimaryKey`, `updateByPrimaryKeySelective`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: LitemallCommentMapper (18 abstract methods) litemall-db/src/main/java/org/linlinjava/litemall/db/dao/LitemallCommentMapper.java:8 — `LitemallCommentMapper` declares 18 abstract methods: `countByExample`, `deleteByExample`, `deleteByPrimaryKey`, `insert`, `insertSelective`, `logicalDeleteByExample`, `logicalDeleteByPrimaryKey`, `selectByExample`, `selectByExampleSelective`, `selectByPrimaryKey`, `selectByPrimaryKeySelective`, `selectByPrimaryKeyWithLogicalDelete`, `selectOneByExample`, `selectOneByExampleSelective`, `updateByExample`, `updateByExampleSelective`, `updateByPrimaryKey`, `updateByPrimaryKeySelective`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: LitemallCouponMapper (18 abstract methods) litemall-db/src/main/java/org/linlinjava/litemall/db/dao/LitemallCouponMapper.java:8 — `LitemallCouponMapper` declares 18 abstract methods: `countByExample`, `deleteByExample`, `deleteByPrimaryKey`, `insert`, `insertSelective`, `logicalDeleteByExample`, `logicalDeleteByPrimaryKey`, `selectByExample`, `selectByExampleSelective`, `selectByPrimaryKey`, `selectByPrimaryKeySelective`, `selectByPrimaryKeyWithLogicalDelete`, `selectOneByExample`, `selectOneByExampleSelective`, `updateByExample`, `updateByExampleSelective`, `updateByPrimaryKey`, `updateByPrimaryKeySelective`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: LitemallCouponUserMapper (18 abstract methods) litemall-db/src/main/java/org/linlinjava/litemall/db/dao/LitemallCouponUserMapper.java:8 — `LitemallCouponUserMapper` declares 18 abstract methods: `countByExample`, `deleteByExample`, `deleteByPrimaryKey`, `insert`, `insertSelective`, `logicalDeleteByExample`, `logicalDeleteByPrimaryKey`, `selectByExample`, `selectByExampleSelective`, `selectByPrimaryKey`, `selectByPrimaryKeySelective`, `selectByPrimaryKeyWithLogicalDelete`, `selectOneByExample`, `selectOneByExampleSelective`, `updateByExample`, `updateByExampleSelective`, `updateByPrimaryKey`, `updateByPrimaryKeySelective`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: LitemallFeedbackMapper (18 abstract methods) litemall-db/src/main/java/org/linlinjava/litemall/db/dao/LitemallFeedbackMapper.java:8 — `LitemallFeedbackMapper` declares 18 abstract methods: `countByExample`, `deleteByExample`, `deleteByPrimaryKey`, `insert`, `insertSelective`, `logicalDeleteByExample`, `logicalDeleteByPrimaryKey`, `selectByExample`, `selectByExampleSelective`, `selectByPrimaryKey`, `selectByPrimaryKeySelective`, `selectByPrimaryKeyWithLogicalDelete`, `selectOneByExample`, `selectOneByExampleSelective`, `updateByExample`, `updateByExampleSelective`, `updateByPrimaryKey`, `updateByPrimaryKeySelective`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: LitemallFootprintMapper (18 abstract methods) litemall-db/src/main/java/org/linlinjava/litemall/db/dao/LitemallFootprintMapper.java:8 — `LitemallFootprintMapper` declares 18 abstract methods: `countByExample`, `deleteByExample`, `deleteByPrimaryKey`, `insert`, `insertSelective`, `logicalDeleteByExample`, `logicalDeleteByPrimaryKey`, `selectByExample`, `selectByExampleSelective`, `selectByPrimaryKey`, `selectByPrimaryKeySelective`, `selectByPrimaryKeyWithLogicalDelete`, `selectOneByExample`, `selectOneByExampleSelective`, `updateByExample`, `updateByExampleSelective`, `updateByPrimaryKey`, `updateByPrimaryKeySelective`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: LitemallGoodsAttributeMapper (18 abstract methods) litemall-db/src/main/java/org/linlinjava/litemall/db/dao/LitemallGoodsAttributeMapper.java:8 — `LitemallGoodsAttributeMapper` declares 18 abstract methods: `countByExample`, `deleteByExample`, `deleteByPrimaryKey`, `insert`, `insertSelective`, `logicalDeleteByExample`, `logicalDeleteByPrimaryKey`, `selectByExample`, `selectByExampleSelective`, `selectByPrimaryKey`, `selectByPrimaryKeySelective`, `selectByPrimaryKeyWithLogicalDelete`, `selectOneByExample`, `selectOneByExampleSelective`, `updateByExample`, `updateByExampleSelective`, `updateByPrimaryKey`, `updateByPrimaryKeySelective`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: LitemallGoodsMapper (22 abstract methods) litemall-db/src/main/java/org/linlinjava/litemall/db/dao/LitemallGoodsMapper.java:8 — `LitemallGoodsMapper` declares 22 abstract methods: `countByExample`, `deleteByExample`, `deleteByPrimaryKey`, `insert`, `insertSelective`, `logicalDeleteByExample`, `logicalDeleteByPrimaryKey`, `selectByExample`, `selectByExampleSelective`, `selectByExampleWithBLOBs`, `selectByPrimaryKey`, `selectByPrimaryKeySelective`, `selectByPrimaryKeyWithLogicalDelete`, `selectOneByExample`, `selectOneByExampleSelective`, `selectOneByExampleWithBLOBs`, `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.
  • Fat interface: LitemallGoodsProductMapper (18 abstract methods) litemall-db/src/main/java/org/linlinjava/litemall/db/dao/LitemallGoodsProductMapper.java:8 — `LitemallGoodsProductMapper` declares 18 abstract methods: `countByExample`, `deleteByExample`, `deleteByPrimaryKey`, `insert`, `insertSelective`, `logicalDeleteByExample`, `logicalDeleteByPrimaryKey`, `selectByExample`, `selectByExampleSelective`, `selectByPrimaryKey`, `selectByPrimaryKeySelective`, `selectByPrimaryKeyWithLogicalDelete`, `selectOneByExample`, `selectOneByExampleSelective`, `updateByExample`, `updateByExampleSelective`, `updateByPrimaryKey`, `updateByPrimaryKeySelective`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: LitemallGoodsSpecificationMapper (18 abstract methods) litemall-db/src/main/java/org/linlinjava/litemall/db/dao/LitemallGoodsSpecificationMapper.java:8 — `LitemallGoodsSpecificationMapper` declares 18 abstract methods: `countByExample`, `deleteByExample`, `deleteByPrimaryKey`, `insert`, `insertSelective`, `logicalDeleteByExample`, `logicalDeleteByPrimaryKey`, `selectByExample`, `selectByExampleSelective`, `selectByPrimaryKey`, `selectByPrimaryKeySelective`, `selectByPrimaryKeyWithLogicalDelete`, `selectOneByExample`, `selectOneByExampleSelective`, `updateByExample`, `updateByExampleSelective`, `updateByPrimaryKey`, `updateByPrimaryKeySelective`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: LitemallGrouponMapper (18 abstract methods) litemall-db/src/main/java/org/linlinjava/litemall/db/dao/LitemallGrouponMapper.java:8 — `LitemallGrouponMapper` declares 18 abstract methods: `countByExample`, `deleteByExample`, `deleteByPrimaryKey`, `insert`, `insertSelective`, `logicalDeleteByExample`, `logicalDeleteByPrimaryKey`, `selectByExample`, `selectByExampleSelective`, `selectByPrimaryKey`, `selectByPrimaryKeySelective`, `selectByPrimaryKeyWithLogicalDelete`, `selectOneByExample`, `selectOneByExampleSelective`, `updateByExample`, `updateByExampleSelective`, `updateByPrimaryKey`, `updateByPrimaryKeySelective`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: LitemallGrouponRulesMapper (18 abstract methods) litemall-db/src/main/java/org/linlinjava/litemall/db/dao/LitemallGrouponRulesMapper.java:8 — `LitemallGrouponRulesMapper` declares 18 abstract methods: `countByExample`, `deleteByExample`, `deleteByPrimaryKey`, `insert`, `insertSelective`, `logicalDeleteByExample`, `logicalDeleteByPrimaryKey`, `selectByExample`, `selectByExampleSelective`, `selectByPrimaryKey`, `selectByPrimaryKeySelective`, `selectByPrimaryKeyWithLogicalDelete`, `selectOneByExample`, `selectOneByExampleSelective`, `updateByExample`, `updateByExampleSelective`, `updateByPrimaryKey`, `updateByPrimaryKeySelective`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: LitemallIssueMapper (18 abstract methods) litemall-db/src/main/java/org/linlinjava/litemall/db/dao/LitemallIssueMapper.java:8 — `LitemallIssueMapper` declares 18 abstract methods: `countByExample`, `deleteByExample`, `deleteByPrimaryKey`, `insert`, `insertSelective`, `logicalDeleteByExample`, `logicalDeleteByPrimaryKey`, `selectByExample`, `selectByExampleSelective`, `selectByPrimaryKey`, `selectByPrimaryKeySelective`, `selectByPrimaryKeyWithLogicalDelete`, `selectOneByExample`, `selectOneByExampleSelective`, `updateByExample`, `updateByExampleSelective`, `updateByPrimaryKey`, `updateByPrimaryKeySelective`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: LitemallKeywordMapper (18 abstract methods) litemall-db/src/main/java/org/linlinjava/litemall/db/dao/LitemallKeywordMapper.java:8 — `LitemallKeywordMapper` declares 18 abstract methods: `countByExample`, `deleteByExample`, `deleteByPrimaryKey`, `insert`, `insertSelective`, `logicalDeleteByExample`, `logicalDeleteByPrimaryKey`, `selectByExample`, `selectByExampleSelective`, `selectByPrimaryKey`, `selectByPrimaryKeySelective`, `selectByPrimaryKeyWithLogicalDelete`, `selectOneByExample`, `selectOneByExampleSelective`, `updateByExample`, `updateByExampleSelective`, `updateByPrimaryKey`, `updateByPrimaryKeySelective`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: LitemallLogMapper (18 abstract methods) litemall-db/src/main/java/org/linlinjava/litemall/db/dao/LitemallLogMapper.java:8 — `LitemallLogMapper` declares 18 abstract methods: `countByExample`, `deleteByExample`, `deleteByPrimaryKey`, `insert`, `insertSelective`, `logicalDeleteByExample`, `logicalDeleteByPrimaryKey`, `selectByExample`, `selectByExampleSelective`, `selectByPrimaryKey`, `selectByPrimaryKeySelective`, `selectByPrimaryKeyWithLogicalDelete`, `selectOneByExample`, `selectOneByExampleSelective`, `updateByExample`, `updateByExampleSelective`, `updateByPrimaryKey`, `updateByPrimaryKeySelective`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: LitemallNoticeAdminMapper (18 abstract methods) litemall-db/src/main/java/org/linlinjava/litemall/db/dao/LitemallNoticeAdminMapper.java:8 — `LitemallNoticeAdminMapper` declares 18 abstract methods: `countByExample`, `deleteByExample`, `deleteByPrimaryKey`, `insert`, `insertSelective`, `logicalDeleteByExample`, `logicalDeleteByPrimaryKey`, `selectByExample`, `selectByExampleSelective`, `selectByPrimaryKey`, `selectByPrimaryKeySelective`, `selectByPrimaryKeyWithLogicalDelete`, `selectOneByExample`, `selectOneByExampleSelective`, `updateByExample`, `updateByExampleSelective`, `updateByPrimaryKey`, `updateByPrimaryKeySelective`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: LitemallNoticeMapper (18 abstract methods) litemall-db/src/main/java/org/linlinjava/litemall/db/dao/LitemallNoticeMapper.java:8 — `LitemallNoticeMapper` declares 18 abstract methods: `countByExample`, `deleteByExample`, `deleteByPrimaryKey`, `insert`, `insertSelective`, `logicalDeleteByExample`, `logicalDeleteByPrimaryKey`, `selectByExample`, `selectByExampleSelective`, `selectByPrimaryKey`, `selectByPrimaryKeySelective`, `selectByPrimaryKeyWithLogicalDelete`, `selectOneByExample`, `selectOneByExampleSelective`, `updateByExample`, `updateByExampleSelective`, `updateByPrimaryKey`, `updateByPrimaryKeySelective`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: LitemallOrderGoodsMapper (18 abstract methods) litemall-db/src/main/java/org/linlinjava/litemall/db/dao/LitemallOrderGoodsMapper.java:8 — `LitemallOrderGoodsMapper` declares 18 abstract methods: `countByExample`, `deleteByExample`, `deleteByPrimaryKey`, `insert`, `insertSelective`, `logicalDeleteByExample`, `logicalDeleteByPrimaryKey`, `selectByExample`, `selectByExampleSelective`, `selectByPrimaryKey`, `selectByPrimaryKeySelective`, `selectByPrimaryKeyWithLogicalDelete`, `selectOneByExample`, `selectOneByExampleSelective`, `updateByExample`, `updateByExampleSelective`, `updateByPrimaryKey`, `updateByPrimaryKeySelective`. 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.
  • + 8 more in this group — see findings.md.
X10 · Duplicated predicate · Duplicated predicate · ×17
  • Duplicated predicate litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/service/WxOrderService.java:1004 — `!OrderUtil.isConfirmStatus(order) && !OrderUtil.isAutoConfirmStatus(order)` appears character-identically in 2 files — litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/service/WxOrderService.java, litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxAftersaleController.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 litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallAdService.java:37 — `!StringUtils.isEmpty(sort) && !StringUtils.isEmpty(order)` appears character-identically in 26 files — litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallAdService.java, litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallAddressService.java, litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallAdminService.java, litemall-db/src/main/java/org/linlinjava/litemall/db/service/LitemallAftersaleService.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 litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxCartController.java:454 — `grouponRules != null && grouponRules.getGoodsId().equals(cart.getGoodsId())` appears character-identically in 2 files — litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxCartController.java, litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/web/WxCouponController.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 litemall-core/src/main/java/org/linlinjava/litemall/core/storage/AliyunStorage.java:111 — `resource.exists() || resource.isReadable()` appears character-identically in 4 files — litemall-core/src/main/java/org/linlinjava/litemall/core/storage/AliyunStorage.java, litemall-core/src/main/java/org/linlinjava/litemall/core/storage/LocalStorage.java, litemall-core/src/main/java/org/linlinjava/litemall/core/storage/QiniuStorage.java, litemall-core/src/main/java/org/linlinjava/litemall/core/storage/TencentStorage.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 litemall-wx/pages/goods/goods.js:373 — `!checkedProductArray || checkedProductArray.length <= 0` appears character-identically in 2 files — litemall-wx/pages/goods/goods.js, renard-wx/pages/goods/goods.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 litemall-wx/lib/vant-weapp/button/index.js:63 — `!this.data.disabled && !this.data.loading` appears character-identically in 2 files — litemall-wx/lib/vant-weapp/button/index.js, litemall-wx/lib/vant-weapp/switch/index.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate REDACTED:453 — `a && getType.toString.call(a) === '[object Function]'` appears character-identically in 2 files — REDACTED, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate litemall-wx/lib/wxParse/htmlparser.js:120 — `closeSelf[tagName] && stack.last() == tagName` appears character-identically in 2 files — litemall-wx/lib/wxParse/htmlparser.js, renard-wx/lib/wxParse/htmlparser.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 litemall-wx/pages/category/category.js:71 — `currentIndex > navListCount / 2 && navListCount > 5` appears character-identically in 2 files — litemall-wx/pages/category/category.js, renard-wx/pages/category/category.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate REDACTED:2370 — `options.parseImgDimensions && width && height` appears character-identically in 2 files — REDACTED, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate litemall-wx/pages/ucenter/addressAdd/addressAdd.js:172 — `regionTypeIndex + 1 == this.data.regionType || (regionTypeIndex - 1 >= 0 && selectRegionList[regionTypeIndex - 1].code <= 0)` appears character-identically in 2 files — litemall-wx/pages/ucenter/addressAdd/addressAdd.js, renard-wx/pages/ucenter/addressAdd/addressAdd.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate REDACTED:359 — `showdown.helper.isUndefined(ext.filter) && showdown.helper.isUndefined(ext.regex)` appears character-identically in 2 files — REDACTED, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate litemall-wx/pages/auth/register/register.js:130 — `this.data.mobile.length == 0 || this.data.code.length == 0` appears character-identically in 2 files — litemall-wx/pages/auth/register/register.js, litemall-wx/pages/auth/reset/reset.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 litemall-wx/lib/wxParse/wxParse.js:51 — `typeof (tagFrom) != 'undefined' && tagFrom.length > 0` appears character-identically in 2 files — litemall-wx/lib/wxParse/wxParse.js, renard-wx/lib/wxParse/wxParse.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate REDACTED:441 — `typeof a === 'string' || a instanceof String` appears character-identically in 2 files — REDACTED, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate litemall-admin/src/directive/permission/permission.js:9 — `value && value instanceof Array && value.length > 0` appears character-identically in 2 files — litemall-admin/src/directive/permission/permission.js, litemall-admin/src/utils/permission.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 litemall-wx/utils/user.js:79 — `wx.getStorageSync('userInfo') && wx.getStorageSync('token')` appears character-identically in 2 files — litemall-wx/utils/user.js, renard-wx/utils/user.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.
D28 · Secrets (history) · REDACTED · ×6
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D34 · Knowledge Freshness · Most significant orphaned file · ×3
  • Most significant orphaned file REDACTED: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 REDACTED: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 litemall-wx-api/src/main/java/org/linlinjava/litemall/wx/service/WxOrderService.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.
D13 · REDACTED Scanning · REDACTED
  • REDACTED
  • REDACTED
D24 · Comment Value · redundant comment · ×2
  • redundant comment REDACTED:978 — "stripBlankLines" repeats the code it sits on: 3 of its 3 words (strip, blank, lines) are already in `text = showdown.subParser('stripBlankLines')(text, options, globals);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment REDACTED:978 — "stripBlankLines" repeats the code it sits on: 3 of its 3 words (strip, blank, lines) are already in `text = showdown.subParser('stripBlankLines')(text, options, globals);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
D30 · Dependency Vulnerabilities · Low CVE · ×2
  • REDACTED
  • REDACTED
D20 · ADR Quality · No ADRs found · ×1
  • No ADRs found litemall-wx-api/pom.xml:83 — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`. ADRs are expected here because `litemall-wx-api/pom.xml` makes this repository a deployable product (line 83).
D26 · Project Cohesion · Projects may be oversized for their cohesion · ×1
  • Projects may be oversized for their cohesion — 1 of 9 project(s) overshoot their size bounds, lowering Project Cohesion to 7.8/10. The most over is `(repository root)` (27710 LoC, 36 module-visible types across 19 directories). Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
D28 · Secrets (history) · Rotate the exposed credentials · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D31 · IaC & Container Security · Low IaC · ×1
  • REDACTED
D34 · Knowledge Freshness · Dormant codebase · ×1
  • Dormant codebase — 250 of 250 significant files have no living knowledge — the codebase as a whole is dormant, not 250 separate risks. Counted over 250 of the 566 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 3/5 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `litemall-all`, `litemall-all-war`.
P3 · Security & performance tooling · No SAST · ×1
  • No SAST REDACTED:3 — No static application security testing detected. For this repository's stack, add spotbugs with find-sec-bugs (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 1 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
P3 · Security & performance tooling · No dependency-update automation · ×1
  • No dependency-update automation litemall-admin/package.json:45 — `litemall-admin/package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`.
P4 · Deployment & Rollback · No release approval gate · ×1
  • No release approval gate — Deployment is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever reaches the release trigger goes to production unreviewed, so a mistaken merge or tag is live before anyone can stop it.
S1 · Web-Security Posture · No security response headers detected · ×1
  • No security response headers detected doc/conf/nginx.conf:61 — None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. This is reported because `nginx.conf` is committed to this repository and declares the server that serves it, so the configuration that would carry these headers is in this repository and was read in full. (−2.0 on this card.)
X5 · Nullable reference types · Java packages are not null-marked everywhere · ×1
  • Java packages are not null-marked everywhere — 0/40 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 — 154 finding(s)
D12 · Dependency Hygiene · Outdated (compile -- module commons.collections (auto)) · ×2
  • Outdated (compile -- module commons.collections (auto)): commons-collections:commons-collections — commons-collections:commons-collections 3.2.1 → 20040616 available.
  • Outdated (compile -- module commons.collections (auto)): commons-collections:commons-collections — commons-collections:commons-collections 3.2.2 → 20040616 available.
D12 · Dependency Hygiene · Outdated (compile -- module commons.logging (auto)) · ×2
  • Outdated (compile -- module commons.logging (auto)): commons-logging:commons-logging — commons-logging:commons-logging 1.1.1 → 1.4.0 available.
  • Outdated (compile -- module commons.logging (auto)): commons-logging:commons-logging — commons-logging:commons-logging 1.2 → 1.4.0 available.
D24 · Comment Value · doc comments repeat the names · ×2
  • doc comments repeat the names REDACTED:773 — 0 of 0 documented parameters and 2 of 18 summaries in `.` only repeat the member or parameter name (e.g. "Parse extension" for `_parseExtension`). Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names litemall-admin/src/utils/index.js:100 — 0 of 5 documented parameters and 1 of 8 summaries in `litemall-admin` only repeat the member or parameter name (e.g. "get getByteLen" for `getByteLen`). 3 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
D12 · Dependency Hygiene · Outdated (compile (optional) -- module spring.boot.devtools [auto]) · ×1
  • Outdated (compile (optional) -- module spring.boot.devtools [auto]): org.springframework.boot:spring-boot-devtools — org.springframework.boot:spring-boot-devtools 2.1.5.RELEASE → 4.1.2 available.
D12 · Dependency Hygiene · Outdated (compile -- module spring.boot [auto]) · ×1
  • Outdated (compile -- module spring.boot [auto]): org.springframework.boot:spring-boot — org.springframework.boot:spring-boot 2.1.5.RELEASE → 4.1.2 available.
D12 · Dependency Hygiene · Outdated (compile -- module spring.context [auto]) · ×1
  • Outdated (compile -- module spring.context [auto]): org.springframework:spring-context — org.springframework:spring-context 5.1.7.RELEASE → 7.0.10 available.
D12 · Dependency Hygiene · Outdated (compile -- module spring.aop [auto]) · ×1
  • Outdated (compile -- module spring.aop [auto]): org.springframework:spring-aop — org.springframework:spring-aop 5.1.7.RELEASE → 7.0.10 available.
D12 · Dependency Hygiene · Outdated (compile -- module spring.beans [auto]) · ×1
  • Outdated (compile -- module spring.beans [auto]): org.springframework:spring-beans — org.springframework:spring-beans 5.1.7.RELEASE → 7.0.10 available.
D12 · Dependency Hygiene · Outdated (compile -- module spring.expression [auto]) · ×1
  • Outdated (compile -- module spring.expression [auto]): org.springframework:spring-expression — org.springframework:spring-expression 5.1.7.RELEASE → 7.0.10 available.
D12 · Dependency Hygiene · Outdated (compile -- module spring.boot.autoconfigure [auto]) · ×1
  • Outdated (compile -- module spring.boot.autoconfigure [auto]): org.springframework.boot:spring-boot-autoconfigure — org.springframework.boot:spring-boot-autoconfigure 2.1.5.RELEASE → 4.1.2 available.
D12 · Dependency Hygiene · Outdated (test -- module spring.boot.starter.test [auto]) · ×1
  • Outdated (test -- module spring.boot.starter.test [auto]): org.springframework.boot:spring-boot-starter-test — org.springframework.boot:spring-boot-starter-test 2.1.5.RELEASE → 4.1.2 available.
D12 · Dependency Hygiene · Outdated (test -- module spring.boot.starter [auto]) · ×1
  • Outdated (test -- module spring.boot.starter [auto]): org.springframework.boot:spring-boot-starter — org.springframework.boot:spring-boot-starter 2.1.5.RELEASE → 4.1.2 available.
D12 · Dependency Hygiene · Outdated (test -- module spring.boot.starter.logging [auto]) · ×1
  • Outdated (test -- module spring.boot.starter.logging [auto]): org.springframework.boot:spring-boot-starter-logging — org.springframework.boot:spring-boot-starter-logging 2.1.5.RELEASE → 4.1.2 available.
D12 · Dependency Hygiene · Outdated (test -- module logback.classic (auto)) · ×1
  • Outdated (test -- module logback.classic (auto)): ch.qos.logback:logback-classic — ch.qos.logback:logback-classic 1.2.3 → 1.6.6 available.
D12 · Dependency Hygiene · Outdated (test -- module logback.core (auto)) · ×1
  • Outdated (test -- module logback.core (auto)): ch.qos.logback:logback-core — ch.qos.logback:logback-core 1.2.3 → 1.6.6 available.
D12 · Dependency Hygiene · Outdated (test -- module org.apache.logging.slf4j [auto]) · ×1
  • Outdated (test -- module org.apache.logging.slf4j [auto]): org.apache.logging.log4j:log4j-to-slf4j — org.apache.logging.log4j:log4j-to-slf4j 2.11.2 → 2.26.1 available.
D12 · Dependency Hygiene · Outdated (test -- module org.apache.logging.log4j) · ×1
  • Outdated (test -- module org.apache.logging.log4j): org.apache.logging.log4j:log4j-api — org.apache.logging.log4j:log4j-api 2.11.2 → 2.26.1 available.
D12 · Dependency Hygiene · Outdated (test -- module jul.to.slf4j (auto)) · ×1
  • Outdated (test -- module jul.to.slf4j (auto)): org.slf4j:jul-to-slf4j — org.slf4j:jul-to-slf4j 1.7.26 → 2.0.20 available.
D12 · Dependency Hygiene · Outdated (test -- module snakeyaml (auto)) · ×1
  • Outdated (test -- module snakeyaml (auto)): org.yaml:snakeyaml — org.yaml:snakeyaml 1.23 → 2.7 available.
D12 · Dependency Hygiene · Outdated (test -- module spring.boot.test [auto]) · ×1
  • Outdated (test -- module spring.boot.test [auto]): org.springframework.boot:spring-boot-test — org.springframework.boot:spring-boot-test 2.1.5.RELEASE → 4.1.2 available.
D12 · Dependency Hygiene · Outdated (test -- module spring.boot.test.autoconfigure [auto]) · ×1
  • Outdated (test -- module spring.boot.test.autoconfigure [auto]): org.springframework.boot:spring-boot-test-autoconfigure — org.springframework.boot:spring-boot-test-autoconfigure 2.1.5.RELEASE → 4.1.2 available.
D12 · Dependency Hygiene · Outdated (test -- module json.path (auto)) · ×1
  • Outdated (test -- module json.path (auto)): com.jayway.jsonpath:json-path — com.jayway.jsonpath:json-path 2.4.0 → 3.0.0 available.
D12 · Dependency Hygiene · Outdated (test -- module json.smart (auto)) · ×1
  • Outdated (test -- module json.smart (auto)): net.minidev:json-smart — net.minidev:json-smart 2.3 → 2.6.1 available.
D12 · Dependency Hygiene · Outdated (test -- module accessors.smart (auto)) · ×1
  • Outdated (test -- module accessors.smart (auto)): net.minidev:accessors-smart — net.minidev:accessors-smart 1.2 → 2.6.1 available.
D12 · Dependency Hygiene · Outdated (test -- module asm (auto)) · ×1
  • Outdated (test -- module asm (auto)): org.ow2.asm:asm — org.ow2.asm:asm 5.0.4 → 9.11.1 available.
D12 · Dependency Hygiene · Outdated (test -- module slf4j.api (auto)) · ×1
  • Outdated (test -- module slf4j.api (auto)): org.slf4j:slf4j-api — org.slf4j:slf4j-api 1.7.26 → 2.0.20 available.
D12 · Dependency Hygiene · Outdated (test -- module junit (auto)) · ×1
  • Outdated (test -- module junit (auto)): junit:junit — junit:junit 4.12 → 4.13.2 available.
D12 · Dependency Hygiene · Outdated (test -- module org.assertj.core [auto]) · ×1
  • Outdated (test -- module org.assertj.core [auto]): org.assertj:assertj-core — org.assertj:assertj-core 3.11.1 → 3.27.7 available.
D12 · Dependency Hygiene · Outdated (test -- module hamcrest.core (auto)) · ×1
  • Outdated (test -- module hamcrest.core (auto)): org.hamcrest:hamcrest-core — org.hamcrest:hamcrest-core 1.3 → 3.0 available.
D12 · Dependency Hygiene · Outdated (test -- module hamcrest.library (auto)) · ×1
  • Outdated (test -- module hamcrest.library (auto)): org.hamcrest:hamcrest-library — org.hamcrest:hamcrest-library 1.3 → 3.0 available.
D12 · Dependency Hygiene · Outdated (test -- module jsonassert (auto)) · ×1
  • Outdated (test -- module jsonassert (auto)): org.skyscreamer:jsonassert — org.skyscreamer:jsonassert 1.5.0 → 1.5.3 available.
D12 · Dependency Hygiene · Outdated (compile -- module spring.core [auto]) · ×1
  • Outdated (compile -- module spring.core [auto]): org.springframework:spring-core — org.springframework:spring-core 5.1.7.RELEASE → 7.0.10 available.
D12 · Dependency Hygiene · Outdated (compile -- module spring.jcl [auto]) · ×1
  • Outdated (compile -- module spring.jcl [auto]): org.springframework:spring-jcl — org.springframework:spring-jcl 5.1.7.RELEASE → 6.2.19 available.
D12 · Dependency Hygiene · Outdated (test -- module spring.test [auto]) · ×1
  • Outdated (test -- module spring.test [auto]): org.springframework:spring-test — org.springframework:spring-test 5.1.7.RELEASE → 7.0.10 available.
D12 · Dependency Hygiene · Outdated (test -- module org.xmlunit [auto]) · ×1
  • Outdated (test -- module org.xmlunit [auto]): org.xmlunit:xmlunit-core — org.xmlunit:xmlunit-core 2.6.2 → 2.14.0 available.
D12 · Dependency Hygiene · Outdated (test -- module powermock.api.mockito (auto)) · ×1
  • Outdated (test -- module powermock.api.mockito (auto)): org.powermock:powermock-api-mockito — org.powermock:powermock-api-mockito 1.6.6 → 1.7.4 available.
D12 · Dependency Hygiene · Outdated (test -- module powermock.api.mockito.common (auto)) · ×1
  • Outdated (test -- module powermock.api.mockito.common (auto)): org.powermock:powermock-api-mockito-common — org.powermock:powermock-api-mockito-common 1.6.6 → 1.7.4 available.
D12 · Dependency Hygiene · Outdated (test -- module powermock.api.support (auto)) · ×1
  • Outdated (test -- module powermock.api.support (auto)): org.powermock:powermock-api-support — org.powermock:powermock-api-support 1.6.6 → 2.0.9 available.
D12 · Dependency Hygiene · Outdated (test -- module powermock.module.junit4 (auto)) · ×1
  • Outdated (test -- module powermock.module.junit4 (auto)): org.powermock:powermock-module-junit4 — org.powermock:powermock-module-junit4 1.6.6 → 2.0.9 available.
D12 · Dependency Hygiene · Outdated (test -- module powermock.module.junit4.common (auto)) · ×1
  • Outdated (test -- module powermock.module.junit4.common (auto)): org.powermock:powermock-module-junit4-common — org.powermock:powermock-module-junit4-common 1.6.6 → 2.0.9 available.
D12 · Dependency Hygiene · Outdated (test -- module powermock.core (auto)) · ×1
  • Outdated (test -- module powermock.core (auto)): org.powermock:powermock-core — org.powermock:powermock-core 1.6.6 → 2.0.9 available.
D12 · Dependency Hygiene · Outdated (test -- module javassist (auto)) · ×1
  • Outdated (test -- module javassist (auto)): org.javassist:javassist — org.javassist:javassist 3.21.0-GA → 3.33.0-GA available.
D12 · Dependency Hygiene · Outdated (test -- module powermock.reflect (auto)) · ×1
  • Outdated (test -- module powermock.reflect (auto)): org.powermock:powermock-reflect — org.powermock:powermock-reflect 1.6.6 → 2.0.9 available.
D12 · Dependency Hygiene · Outdated (test -- module mockito.core (auto)) · ×1
  • Outdated (test -- module mockito.core (auto)): org.mockito:mockito-core — org.mockito:mockito-core 1.10.19 → 5.24.0 available.
D12 · Dependency Hygiene · Outdated (test -- module objenesis (auto)) · ×1
  • Outdated (test -- module objenesis (auto)): org.objenesis:objenesis — org.objenesis:objenesis 2.1 → 3.6 available.
D12 · Dependency Hygiene · Outdated (compile -- module spring.boot.starter.json [auto]) · ×1
  • Outdated (compile -- module spring.boot.starter.json [auto]): org.springframework.boot:spring-boot-starter-json — org.springframework.boot:spring-boot-starter-json 2.1.5.RELEASE → 4.1.2 available.
D12 · Dependency Hygiene · Outdated (compile -- module spring.web [auto]) · ×1
  • Outdated (compile -- module spring.web [auto]): org.springframework:spring-web — org.springframework:spring-web 5.1.7.RELEASE → 7.0.10 available.
D12 · Dependency Hygiene · Outdated (compile -- module com.fasterxml.jackson.databind [auto]) · ×1
  • Outdated (compile -- module com.fasterxml.jackson.databind [auto]): com.fasterxml.jackson.core:jackson-databind — com.fasterxml.jackson.core:jackson-databind 2.9.8 → 2.23.0 available.
D12 · Dependency Hygiene · Outdated (compile -- module jackson.annotations (auto)) · ×1
  • Outdated (compile -- module jackson.annotations (auto)): com.fasterxml.jackson.core:jackson-annotations — com.fasterxml.jackson.core:jackson-annotations 2.9.0 → 2.23 available.
D12 · Dependency Hygiene · Outdated (compile -- module com.fasterxml.jackson.core [auto]) · ×1
  • Outdated (compile -- module com.fasterxml.jackson.core [auto]): com.fasterxml.jackson.core:jackson-core — com.fasterxml.jackson.core:jackson-core 2.9.8 → 2.23.0 available.
D12 · Dependency Hygiene · Outdated (compile -- module com.fasterxml.jackson.datatype.jdk8 [auto]) · ×1
  • Outdated (compile -- module com.fasterxml.jackson.datatype.jdk8 [auto]): com.fasterxml.jackson.datatype:jackson-datatype-jdk8 — com.fasterxml.jackson.datatype:jackson-datatype-jdk8 2.9.8 → 2.23.0 available.
D12 · Dependency Hygiene · Outdated (compile -- module com.fasterxml.jackson.datatype.jsr310 [auto]) · ×1
  • Outdated (compile -- module com.fasterxml.jackson.datatype.jsr310 [auto]): com.fasterxml.jackson.datatype:jackson-datatype-jsr310 — com.fasterxml.jackson.datatype:jackson-datatype-jsr310 2.9.8 → 2.23.0 available.
D12 · Dependency Hygiene · Outdated (compile -- module com.fasterxml.jackson.module.paramnames [auto]) · ×1
  • Outdated (compile -- module com.fasterxml.jackson.module.paramnames [auto]): com.fasterxml.jackson.module:jackson-module-parameter-names — com.fasterxml.jackson.module:jackson-module-parameter-names 2.9.8 → 2.23.0 available.
D12 · Dependency Hygiene · Outdated (compile -- module mybatis.spring.boot.starter (auto)) · ×1
  • Outdated (compile -- module mybatis.spring.boot.starter (auto)): org.mybatis.spring.boot:mybatis-spring-boot-starter — org.mybatis.spring.boot:mybatis-spring-boot-starter 1.3.2 → 4.1.0 available.
D12 · Dependency Hygiene · Outdated (compile -- module spring.boot.starter.jdbc [auto]) · ×1
  • Outdated (compile -- module spring.boot.starter.jdbc [auto]): org.springframework.boot:spring-boot-starter-jdbc — org.springframework.boot:spring-boot-starter-jdbc 2.1.5.RELEASE → 4.1.2 available.
D12 · Dependency Hygiene · Outdated (compile -- module com.zaxxer.hikari [auto]) · ×1
  • Outdated (compile -- module com.zaxxer.hikari [auto]): com.zaxxer:HikariCP — com.zaxxer:HikariCP 3.2.0 → 7.1.0 available.
D12 · Dependency Hygiene · Outdated (compile -- module spring.jdbc [auto]) · ×1
  • Outdated (compile -- module spring.jdbc [auto]): org.springframework:spring-jdbc — org.springframework:spring-jdbc 5.1.7.RELEASE → 7.0.10 available.
D12 · Dependency Hygiene · Outdated (compile -- module spring.tx [auto]) · ×1
  • Outdated (compile -- module spring.tx [auto]): org.springframework:spring-tx — org.springframework:spring-tx 5.1.7.RELEASE → 7.0.10 available.
D12 · Dependency Hygiene · Outdated (compile -- module mybatis.spring.boot.autoconfigure (auto)) · ×1
  • Outdated (compile -- module mybatis.spring.boot.autoconfigure (auto)): org.mybatis.spring.boot:mybatis-spring-boot-autoconfigure — org.mybatis.spring.boot:mybatis-spring-boot-autoconfigure 1.3.2 → 4.1.0 available.
D12 · Dependency Hygiene · Outdated (compile -- module mybatis (auto)) · ×1
  • Outdated (compile -- module mybatis (auto)): org.mybatis:mybatis — org.mybatis:mybatis 3.4.6 → 3.6.0 available.
D12 · Dependency Hygiene · Outdated (compile -- module mybatis.spring (auto)) · ×1
  • Outdated (compile -- module mybatis.spring (auto)): org.mybatis:mybatis-spring — org.mybatis:mybatis-spring 1.3.2 → 4.1.0 available.
D12 · Dependency Hygiene · Outdated (compile -- module pagehelper.spring.boot.starter (auto)) · ×1
  • Outdated (compile -- module pagehelper.spring.boot.starter (auto)): com.github.pagehelper:pagehelper-spring-boot-starter — com.github.pagehelper:pagehelper-spring-boot-starter 1.2.5 → 4.1.1 available.
D12 · Dependency Hygiene · Outdated (compile -- module pagehelper.spring.boot.autoconfigure (auto)) · ×1
  • Outdated (compile -- module pagehelper.spring.boot.autoconfigure (auto)): com.github.pagehelper:pagehelper-spring-boot-autoconfigure — com.github.pagehelper:pagehelper-spring-boot-autoconfigure 1.2.5 → 4.1.1 available.
D12 · Dependency Hygiene · Outdated (compile -- module pagehelper (auto)) · ×1
  • Outdated (compile -- module pagehelper (auto)): com.github.pagehelper:pagehelper — com.github.pagehelper:pagehelper 5.1.4 → 6.1.1 available.
D12 · Dependency Hygiene · Outdated (compile -- module jsqlparser (auto)) · ×1
  • Outdated (compile -- module jsqlparser (auto)): com.github.jsqlparser:jsqlparser — com.github.jsqlparser:jsqlparser 1.0 → 5.4 available.
D12 · Dependency Hygiene · Outdated (compile -- module mysql.connector.java (auto)) · ×1
  • Outdated (compile -- module mysql.connector.java (auto)): mysql:mysql-connector-java — mysql:mysql-connector-java 8.0.28 → 8.0.33 available.
D12 · Dependency Hygiene · Outdated (compile -- module com.google.protobuf [auto]) · ×1
  • Outdated (compile -- module com.google.protobuf [auto]): com.google.protobuf:protobuf-java — com.google.protobuf:protobuf-java 3.11.4 → 4.36.2 available.
D12 · Dependency Hygiene · Outdated (compile -- module druid.spring.boot.starter (auto)) · ×1
  • Outdated (compile -- module druid.spring.boot.starter (auto)): com.alibaba:druid-spring-boot-starter — com.alibaba:druid-spring-boot-starter 1.2.1 → 1.2.28 available.
D12 · Dependency Hygiene · Outdated (compile -- module druid (auto)) · ×1
  • Outdated (compile -- module druid (auto)): com.alibaba:druid — com.alibaba:druid 1.2.1 → 1.2.28 available.
D12 · Dependency Hygiene · Outdated (compile -- module org.hibernate.validator [auto]) · ×1
  • Outdated (compile -- module org.hibernate.validator [auto]): org.hibernate.validator:hibernate-validator — org.hibernate.validator:hibernate-validator 6.2.0.Final → 9.1.6.Final available.
D12 · Dependency Hygiene · Outdated (compile -- module java.validation [auto]) · ×1
  • Outdated (compile -- module java.validation [auto]): jakarta.validation:jakarta.validation-api — jakarta.validation:jakarta.validation-api 2.0.2 → 3.1.1 available.
D12 · Dependency Hygiene · Outdated (compile -- module org.jboss.logging [auto]) · ×1
  • Outdated (compile -- module org.jboss.logging [auto]): org.jboss.logging:jboss-logging — org.jboss.logging:jboss-logging 3.3.2.Final → 3.6.3.Final available.
D12 · Dependency Hygiene · Outdated (compile -- module com.fasterxml.classmate [auto]) · ×1
  • Outdated (compile -- module com.fasterxml.classmate [auto]): com.fasterxml:classmate — com.fasterxml:classmate 1.4.0 → 1.8.0 available.
D12 · Dependency Hygiene · Outdated (compile -- module aliyun.java.sdk.core (auto)) · ×1
  • Outdated (compile -- module aliyun.java.sdk.core (auto)): com.aliyun:aliyun-java-sdk-core — com.aliyun:aliyun-java-sdk-core 4.0.3 → 4.7.10 available.
D12 · Dependency Hygiene · Outdated (compile -- module gson (auto)) · ×1
  • Outdated (compile -- module gson (auto)): com.google.code.gson:gson — com.google.code.gson:gson 2.8.5 → 2.15.0 available.
D12 · Dependency Hygiene · Outdated (compile -- module org.apache.httpcomponents.httpclient [auto]) · ×1
  • Outdated (compile -- module org.apache.httpcomponents.httpclient [auto]): org.apache.httpcomponents:httpclient — org.apache.httpcomponents:httpclient 4.5.8 → 4.5.14 available.
D12 · Dependency Hygiene · Outdated (compile -- module org.apache.httpcomponents.httpcore [auto]) · ×1
  • Outdated (compile -- module org.apache.httpcomponents.httpcore [auto]): org.apache.httpcomponents:httpcore — org.apache.httpcomponents:httpcore 4.4.11 → 4.4.16 available.
D12 · Dependency Hygiene · Outdated (compile -- module jaxb.core (auto)) · ×1
  • Outdated (compile -- module jaxb.core (auto)): com.sun.xml.bind:jaxb-core — com.sun.xml.bind:jaxb-core 2.1.14 → 4.0.9 available.
D12 · Dependency Hygiene · Outdated (compile -- module jaxb.impl (auto)) · ×1
  • Outdated (compile -- module jaxb.impl (auto)): com.sun.xml.bind:jaxb-impl — com.sun.xml.bind:jaxb-impl 2.1 → 4.0.9 available.
D12 · Dependency Hygiene · Outdated (compile -- module spring.boot.starter.web [auto]) · ×1
  • Outdated (compile -- module spring.boot.starter.web [auto]): org.springframework.boot:spring-boot-starter-web — org.springframework.boot:spring-boot-starter-web 2.1.5.RELEASE → 4.1.2 available.
D12 · Dependency Hygiene · Outdated (compile -- module spring.boot.starter.tomcat [auto]) · ×1
  • Outdated (compile -- module spring.boot.starter.tomcat [auto]): org.springframework.boot:spring-boot-starter-tomcat — org.springframework.boot:spring-boot-starter-tomcat 2.1.5.RELEASE → 4.1.2 available.
D12 · Dependency Hygiene · Outdated (compile -- module tomcat.embed.core (auto)) · ×1
  • Outdated (compile -- module tomcat.embed.core (auto)): org.apache.tomcat.embed:tomcat-embed-core — org.apache.tomcat.embed:tomcat-embed-core 9.0.19 → 11.0.27 available.
D12 · Dependency Hygiene · Outdated (compile -- module tomcat.embed.el (auto)) · ×1
  • Outdated (compile -- module tomcat.embed.el (auto)): org.apache.tomcat.embed:tomcat-embed-el — org.apache.tomcat.embed:tomcat-embed-el 9.0.19 → 11.0.27 available.
D12 · Dependency Hygiene · Outdated (compile -- module tomcat.embed.websocket (auto)) · ×1
  • Outdated (compile -- module tomcat.embed.websocket (auto)): org.apache.tomcat.embed:tomcat-embed-websocket — org.apache.tomcat.embed:tomcat-embed-websocket 9.0.19 → 11.0.27 available.
D12 · Dependency Hygiene · Outdated (compile -- module spring.webmvc [auto]) · ×1
  • Outdated (compile -- module spring.webmvc [auto]): org.springframework:spring-webmvc — org.springframework:spring-webmvc 5.1.7.RELEASE → 7.0.10 available.
D12 · Dependency Hygiene · Outdated (compile -- module spring.boot.starter.mail [auto]) · ×1
  • Outdated (compile -- module spring.boot.starter.mail [auto]): org.springframework.boot:spring-boot-starter-mail — org.springframework.boot:spring-boot-starter-mail 2.1.5.RELEASE → 4.1.2 available.
D12 · Dependency Hygiene · Outdated (compile -- module spring.context.support [auto]) · ×1
  • Outdated (compile -- module spring.context.support [auto]): org.springframework:spring-context-support — org.springframework:spring-context-support 5.1.7.RELEASE → 7.0.10 available.
D12 · Dependency Hygiene · Outdated (compile -- module qcloudsms (auto)) · ×1
  • Outdated (compile -- module qcloudsms (auto)): com.github.qcloudsms:qcloudsms — com.github.qcloudsms:qcloudsms 1.0.5 → 1.0.6 available.
D12 · Dependency Hygiene · Outdated (compile -- module json (auto)) · ×1
  • Outdated (compile -- module json (auto)): org.json:json — org.json:json 20170516 → 20260814 available.
D12 · Dependency Hygiene · Outdated (compile -- module org.apache.httpcomponents.httpmime [auto]) · ×1
  • Outdated (compile -- module org.apache.httpcomponents.httpmime [auto]): org.apache.httpcomponents:httpmime — org.apache.httpcomponents:httpmime 4.5.8 → 4.5.14 available.
D12 · Dependency Hygiene · Outdated (compile -- module org.apache.commons.codec [auto]) · ×1
  • Outdated (compile -- module org.apache.commons.codec [auto]): commons-codec:commons-codec — commons-codec:commons-codec 1.11 → 1.23.0 available.
D12 · Dependency Hygiene · Outdated (compile -- module cos.api (auto)) · ×1
  • Outdated (compile -- module cos.api (auto)): com.qcloud:cos_api — com.qcloud:cos_api 5.6.24 → 5.6.283 available.
D12 · Dependency Hygiene · Outdated (compile -- module org.joda.time [auto]) · ×1
  • Outdated (compile -- module org.joda.time [auto]): joda-time:joda-time — joda-time:joda-time 2.10.2 → 2.15.1 available.
D12 · Dependency Hygiene · Outdated (compile -- module org.bouncycastle.provider) · ×1
  • Outdated (compile -- module org.bouncycastle.provider): org.bouncycastle:bcprov-jdk15on — org.bouncycastle:bcprov-jdk15on 1.64 → 1.70 available.
D12 · Dependency Hygiene · Outdated (compile -- module aliyun.sdk.oss (auto)) · ×1
  • Outdated (compile -- module aliyun.sdk.oss (auto)): com.aliyun.oss:aliyun-sdk-oss — com.aliyun.oss:aliyun-sdk-oss 2.5.0 → 3.18.5 available.
D12 · Dependency Hygiene · Outdated (compile) · ×1
  • Outdated (compile): org.jdom:jdom — org.jdom:jdom 1.1 → 2.0.2 available.
D12 · Dependency Hygiene · Outdated (compile -- module qiniu.java.sdk (auto)) · ×1
  • Outdated (compile -- module qiniu.java.sdk (auto)): com.qiniu:qiniu-java-sdk — com.qiniu:qiniu-java-sdk 7.2.29 → 7.19.0 available.
D12 · Dependency Hygiene · Outdated (runtime -- module okhttp3 [auto]) · ×1
  • Outdated (runtime -- module okhttp3 [auto]): com.squareup.okhttp3:okhttp — com.squareup.okhttp3:okhttp 3.14.4 → 5.5.1 available.
D12 · Dependency Hygiene · Outdated (runtime -- module okio [auto]) · ×1
  • Outdated (runtime -- module okio [auto]): com.squareup.okio:okio — com.squareup.okio:okio 1.17.2 → 3.18.2 available.
D12 · Dependency Hygiene · Outdated (compile -- module weixin.java.miniapp (auto)) · ×1
  • Outdated (compile -- module weixin.java.miniapp (auto)): com.github.binarywang:weixin-java-miniapp — com.github.binarywang:weixin-java-miniapp 4.1.0 → 4.8.6-20260825.155844 available.
D12 · Dependency Hygiene · Outdated (compile -- module weixin.java.common (auto)) · ×1
  • Outdated (compile -- module weixin.java.common (auto)): com.github.binarywang:weixin-java-common — com.github.binarywang:weixin-java-common 4.1.0 → 4.8.6-20260825.155844 available.
D12 · Dependency Hygiene · Outdated (compile -- module xstream (auto)) · ×1
  • Outdated (compile -- module xstream (auto)): com.thoughtworks.xstream:xstream — com.thoughtworks.xstream:xstream 1.4.17 → 1.4.21 available.
D12 · Dependency Hygiene · Outdated (compile -- module io.github.xstream.mxparser [auto]) · ×1
  • Outdated (compile -- module io.github.xstream.mxparser [auto]): io.github.x-stream:mxparser — io.github.x-stream:mxparser 1.2.1 → 1.2.3 available.
D12 · Dependency Hygiene · Outdated (compile -- module xmlpull (auto)) · ×1
  • Outdated (compile -- module xmlpull (auto)): xmlpull:xmlpull — xmlpull:xmlpull 1.1.3.1 → 1.1.3.4a available.
D12 · Dependency Hygiene · Outdated (compile -- module jcl.over.slf4j (auto)) · ×1
  • Outdated (compile -- module jcl.over.slf4j (auto)): org.slf4j:jcl-over-slf4j — org.slf4j:jcl-over-slf4j 1.7.26 → 2.0.20 available.
D12 · Dependency Hygiene · Outdated (compile -- module org.apache.commons.io [auto]) · ×1
  • Outdated (compile -- module org.apache.commons.io [auto]): commons-io:commons-io — commons-io:commons-io 2.7 → 2.22.0 available.
D12 · Dependency Hygiene · Outdated (compile -- module com.google.common [auto]) · ×1
  • Outdated (compile -- module com.google.common [auto]): com.google.guava:guava — com.google.guava:guava 32.0.0-jre → 33.8.0-android available.
D12 · Dependency Hygiene · Outdated (compile -- module failureaccess (auto)) · ×1
  • Outdated (compile -- module failureaccess (auto)): com.google.guava:failureaccess — com.google.guava:failureaccess 1.0.1 → 1.0.3 available.
D12 · Dependency Hygiene · Outdated (compile -- module org.checkerframework.checker.qual [auto]) · ×1
  • Outdated (compile -- module org.checkerframework.checker.qual [auto]): org.checkerframework:checker-qual — org.checkerframework:checker-qual 3.33.0 → 4.4.0 available.
D12 · Dependency Hygiene · Outdated (compile -- module com.google.errorprone.annotations [auto]) · ×1
  • Outdated (compile -- module com.google.errorprone.annotations [auto]): com.google.errorprone:error_prone_annotations — com.google.errorprone:error_prone_annotations 2.18.0 → 2.52.0 available.
D12 · Dependency Hygiene · Outdated (compile -- module j2objc.annotations (auto)) · ×1
  • Outdated (compile -- module j2objc.annotations (auto)): com.google.j2objc:j2objc-annotations — com.google.j2objc:j2objc-annotations 2.8 → 3.1 available.
D12 · Dependency Hygiene · Outdated (compile -- module dom4j (auto)) · ×1
  • Outdated (compile -- module dom4j (auto)): org.dom4j:dom4j — org.dom4j:dom4j 2.1.3 → 2.2.0 available.
D12 · Dependency Hygiene · Outdated (compile -- module org.bouncycastle.pkix) · ×1
  • Outdated (compile -- module org.bouncycastle.pkix): org.bouncycastle:bcpkix-jdk15on — org.bouncycastle:bcpkix-jdk15on 1.68 → 1.70 available.
D12 · Dependency Hygiene · Outdated (compile -- module weixin.java.pay (auto)) · ×1
  • Outdated (compile -- module weixin.java.pay (auto)): com.github.binarywang:weixin-java-pay — com.github.binarywang:weixin-java-pay 4.1.0 → 4.8.6-20260825.155844 available.
D12 · Dependency Hygiene · Outdated (compile -- module qrcode.utils (auto)) · ×1
  • Outdated (compile -- module qrcode.utils (auto)): com.github.binarywang:qrcode-utils — com.github.binarywang:qrcode-utils 1.1 → 1.3 available.
D12 · Dependency Hygiene · Outdated (compile -- module core (auto)) · ×1
  • Outdated (compile -- module core (auto)): com.google.zxing:core — com.google.zxing:core 3.2.1 → 3.5.4 available.
D12 · Dependency Hygiene · Outdated (compile -- module jodd.http (auto)) · ×1
  • Outdated (compile -- module jodd.http (auto)): org.jodd:jodd-http — org.jodd:jodd-http 5.2.0 → 6.3.0 available.
D12 · Dependency Hygiene · Outdated (compile -- module jodd.core (auto)) · ×1
  • Outdated (compile -- module jodd.core (auto)): org.jodd:jodd-core — org.jodd:jodd-core 5.2.0 → 5.3.0 available.
D12 · Dependency Hygiene · Outdated (compile -- module jodd.util (auto)) · ×1
  • Outdated (compile -- module jodd.util (auto)): org.jodd:jodd-util — org.jodd:jodd-util 6.0.0 → 6.3.0 available.
D12 · Dependency Hygiene · Outdated (compile -- module org.apache.commons.lang3 [auto]) · ×1
  • Outdated (compile -- module org.apache.commons.lang3 [auto]): org.apache.commons:commons-lang3 — org.apache.commons:commons-lang3 3.8.1 → 3.22.0 available.
D12 · Dependency Hygiene · Outdated (compile -- module commons.beanutils (auto)) · ×1
  • Outdated (compile -- module commons.beanutils (auto)): commons-beanutils:commons-beanutils — commons-beanutils:commons-beanutils 1.9.4 → 1.11.0 available.
D12 · Dependency Hygiene · Outdated (compile -- module activation (auto)) · ×1
  • Outdated (compile -- module activation (auto)): javax.activation:activation — javax.activation:activation 1.1 → 1.1.1 available.
D12 · Dependency Hygiene · Outdated (compile -- module springfox.swagger2 (auto)) · ×1
  • Outdated (compile -- module springfox.swagger2 (auto)): io.springfox:springfox-swagger2 — io.springfox:springfox-swagger2 2.9.2 → 3.0.0 available.
D12 · Dependency Hygiene · Outdated (compile -- module swagger.annotations (auto)) · ×1
  • Outdated (compile -- module swagger.annotations (auto)): io.swagger:swagger-annotations — io.swagger:swagger-annotations 1.5.20 → 1.6.16 available.
D12 · Dependency Hygiene · Outdated (compile -- module swagger.models (auto)) · ×1
  • Outdated (compile -- module swagger.models (auto)): io.swagger:swagger-models — io.swagger:swagger-models 1.5.20 → 1.6.16 available.
D12 · Dependency Hygiene · Outdated (compile -- module springfox.spi (auto)) · ×1
  • Outdated (compile -- module springfox.spi (auto)): io.springfox:springfox-spi — io.springfox:springfox-spi 2.9.2 → 3.0.0 available.
D12 · Dependency Hygiene · Outdated (compile -- module springfox.core (auto)) · ×1
  • Outdated (compile -- module springfox.core (auto)): io.springfox:springfox-core — io.springfox:springfox-core 2.9.2 → 3.0.0 available.
D12 · Dependency Hygiene · Outdated (compile -- module net.bytebuddy) · ×1
  • Outdated (compile -- module net.bytebuddy): net.bytebuddy:byte-buddy — net.bytebuddy:byte-buddy 1.9.12 → 1.18.17 available.
D12 · Dependency Hygiene · Outdated (compile -- module springfox.schema (auto)) · ×1
  • Outdated (compile -- module springfox.schema (auto)): io.springfox:springfox-schema — io.springfox:springfox-schema 2.9.2 → 3.0.0 available.
D12 · Dependency Hygiene · Outdated (compile -- module springfox.swagger.common (auto)) · ×1
  • Outdated (compile -- module springfox.swagger.common (auto)): io.springfox:springfox-swagger-common — io.springfox:springfox-swagger-common 2.9.2 → 3.0.0 available.
D12 · Dependency Hygiene · Outdated (compile -- module springfox.spring.web (auto)) · ×1
  • Outdated (compile -- module springfox.spring.web (auto)): io.springfox:springfox-spring-web — io.springfox:springfox-spring-web 2.9.2 → 3.0.0 available.
D12 · Dependency Hygiene · Outdated (compile -- module spring.plugin.core (auto)) · ×1
  • Outdated (compile -- module spring.plugin.core (auto)): org.springframework.plugin:spring-plugin-core — org.springframework.plugin:spring-plugin-core 1.2.0.RELEASE → 4.1.0 available.
D12 · Dependency Hygiene · Outdated (compile -- module spring.plugin.metadata (auto)) · ×1
  • Outdated (compile -- module spring.plugin.metadata (auto)): org.springframework.plugin:spring-plugin-metadata — org.springframework.plugin:spring-plugin-metadata 1.2.0.RELEASE → 3.0.0 available.
D12 · Dependency Hygiene · Outdated (compile -- module org.mapstruct [auto]) · ×1
  • Outdated (compile -- module org.mapstruct [auto]): org.mapstruct:mapstruct — org.mapstruct:mapstruct 1.2.0.Final → 1.6.3 available.
D12 · Dependency Hygiene · Outdated (compile -- module springfox.swagger.ui (auto)) · ×1
  • Outdated (compile -- module springfox.swagger.ui (auto)): io.springfox:springfox-swagger-ui — io.springfox:springfox-swagger-ui 2.10.0 → 3.0.0 available.
D12 · Dependency Hygiene · Outdated (compile -- module javassist (auto)) · ×1
  • Outdated (compile -- module javassist (auto)): org.javassist:javassist — org.javassist:javassist 3.25.0-GA → 3.33.0-GA available.
D12 · Dependency Hygiene · Outdated (compile -- module java.jwt (auto)) · ×1
  • Outdated (compile -- module java.jwt (auto)): com.auth0:java-jwt — com.auth0:java-jwt 3.4.1 → 4.6.2 available.
D12 · Dependency Hygiene · Outdated (compile -- module shiro.spring.boot.web.starter (auto)) · ×1
  • Outdated (compile -- module shiro.spring.boot.web.starter (auto)): org.apache.shiro:shiro-spring-boot-web-starter — org.apache.shiro:shiro-spring-boot-web-starter 1.6.0 → 3.0.2 available.
D12 · Dependency Hygiene · Outdated (compile -- module shiro.spring.boot.starter (auto)) · ×1
  • Outdated (compile -- module shiro.spring.boot.starter (auto)): org.apache.shiro:shiro-spring-boot-starter — org.apache.shiro:shiro-spring-boot-starter 1.6.0 → 3.0.2 available.
D12 · Dependency Hygiene · Outdated (compile -- module shiro.spring (auto)) · ×1
  • Outdated (compile -- module shiro.spring (auto)): org.apache.shiro:shiro-spring — org.apache.shiro:shiro-spring 1.6.0 → 3.0.2 available.
D12 · Dependency Hygiene · Outdated (compile -- module shiro.core (auto)) · ×1
  • Outdated (compile -- module shiro.core (auto)): org.apache.shiro:shiro-core — org.apache.shiro:shiro-core 1.6.0 → 3.0.2 available.
D12 · Dependency Hygiene · Outdated (compile -- module shiro.lang (auto)) · ×1
  • Outdated (compile -- module shiro.lang (auto)): org.apache.shiro:shiro-lang — org.apache.shiro:shiro-lang 1.6.0 → 3.0.2 available.
D12 · Dependency Hygiene · Outdated (compile -- module shiro.cache (auto)) · ×1
  • Outdated (compile -- module shiro.cache (auto)): org.apache.shiro:shiro-cache — org.apache.shiro:shiro-cache 1.6.0 → 3.0.2 available.
D12 · Dependency Hygiene · Outdated (compile -- module shiro.crypto.hash (auto)) · ×1
  • Outdated (compile -- module shiro.crypto.hash (auto)): org.apache.shiro:shiro-crypto-hash — org.apache.shiro:shiro-crypto-hash 1.6.0 → 3.0.2 available.
D12 · Dependency Hygiene · Outdated (compile -- module shiro.crypto.core (auto)) · ×1
  • Outdated (compile -- module shiro.crypto.core (auto)): org.apache.shiro:shiro-crypto-core — org.apache.shiro:shiro-crypto-core 1.6.0 → 3.0.2 available.
D12 · Dependency Hygiene · Outdated (compile -- module shiro.crypto.cipher (auto)) · ×1
  • Outdated (compile -- module shiro.crypto.cipher (auto)): org.apache.shiro:shiro-crypto-cipher — org.apache.shiro:shiro-crypto-cipher 1.6.0 → 3.0.2 available.
D12 · Dependency Hygiene · Outdated (compile -- module shiro.config.core (auto)) · ×1
  • Outdated (compile -- module shiro.config.core (auto)): org.apache.shiro:shiro-config-core — org.apache.shiro:shiro-config-core 1.6.0 → 3.0.2 available.
D12 · Dependency Hygiene · Outdated (compile -- module shiro.config.ogdl (auto)) · ×1
  • Outdated (compile -- module shiro.config.ogdl (auto)): org.apache.shiro:shiro-config-ogdl — org.apache.shiro:shiro-config-ogdl 1.6.0 → 3.0.2 available.
D12 · Dependency Hygiene · Outdated (compile -- module shiro.event (auto)) · ×1
  • Outdated (compile -- module shiro.event (auto)): org.apache.shiro:shiro-event — org.apache.shiro:shiro-event 1.6.0 → 3.0.2 available.
D12 · Dependency Hygiene · Outdated (compile -- module shiro.web (auto)) · ×1
  • Outdated (compile -- module shiro.web (auto)): org.apache.shiro:shiro-web — org.apache.shiro:shiro-web 1.6.0 → 3.0.2 available.
D12 · Dependency Hygiene · Outdated (compile -- module encoder (auto)) · ×1
  • Outdated (compile -- module encoder (auto)): org.owasp.encoder:encoder — org.owasp.encoder:encoder 1.2.2 → 1.6.0 available.

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/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-3bd7de93d04940dda73a12dfadcf9953/history.json --exit-code 0 --source .51artifacts/raw/gitleaks-history.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-3bd7de93d04940dda73a12dfadcf9953/tree.json --exit-code 0 --source .9artifacts/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/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude litemall-admin/build --exclude litemall-admin/public/tinymce4.7.5/langs --exclude litemall-admin/public/tinymce4.7.5/plugins/codesample --exclude litemall-admin/public/tinymce4.7.5/plugins/visualblocks --exclude litemall-db/src/main/java/org/linlinjava/litemall/db/dao --exclude litemall-db/src/main/java/org/linlinjava/litemall/db/domain --exclude litemall-db/src/main/resources/org .33artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** .48artifacts/raw/trivy-fs.json
D31 · IaC & Container Securitytrivy—trivy config --format json --quiet .4artifacts/raw/trivy-config.json
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—
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 Dependenciestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** .0artifacts/raw/trivy-fs.json

Run 01a1d53a-cbb6-77ef-8825-bb63e0bd1cbe · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

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