Executive summary
EastWorld/wechat-app-mall falls short of our standard for production because it has images with no text description. It scores 25 out of 100 and is rated Critical, and none of its six critical findings concern security.
Accessibility, at 10, is the weakest lens and counts most in the score. The best first step is adding text alternatives, worth about 13 points. Improving the documentation comes next, worth about 4 points. Raising Accessibility to 70 would lift the score to about 36.
Two images have no description for people who can't see them. Describing the images would close this risk. The four uses of packages that aren't listed need adding to the project's list of dependencies.
The product code is 36,773 lines, about €31,000 to rebuild.
If Accessibility rose from 10 to 70, the lowest score rated Strong, the score would rise from 25 to about 36.
New since the last survey: 8 findings
- Cyclomatic Complexity · Complex function drawBlock (cyclomatic 11, cognitive 19) miniprogram_npm/wxa-plugin-canvas/index/index.js
- Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 11, cognitive 17) miniprogram_npm/@vant/weapp/uploader/utils.js
- Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 11, cognitive 16) packageFx/pages/hehuorenfenxiao/index.js
- Cyclomatic Complexity · Complex function bindSave (cyclomatic 11, cognitive 13) pages/withdraw/index.js
- Cyclomatic Complexity · Complex function calculateGoodsPrice (cyclomatic 11, cognitive 12) components/goods-pop/index.js
- Cyclomatic Complexity · Complex function onLoad (cyclomatic 11, cognitive 12) pages/goods-details/vop.js
- Cyclomatic Complexity · Complex function loadDetail (cyclomatic 11, cognitive 11) marketing/listing/edit.js
- Cyclomatic Complexity · Complex function orderDetail (cyclomatic 11, cognitive 9) pages/order-details/index.js
Fixed since the last survey: 129 findings
- Code Duplication · Duplicated block (21 lines × 2 locations) components/goods-pop/index.js
- Code Duplication · Duplicated block (21 lines × 3 locations) packageStreamMedia/pages/live-anchor/list.js
- Code Duplication · Duplicated block (20 lines × 2 locations) pages/coupons/index.js
- Code Duplication · Duplicated block (20 lines × 3 locations) pages/idCheck/index.js
- Code Duplication · Duplicated block (19 lines × 3 locations) packageFx/pages/hehuorenfenxiao/index.js
- Code Duplication · Duplicated block (19 lines × 2 locations) pages/about/index.js
- Code Duplication · Duplicated block (19 lines × 2 locations) pages/category/category.js
- Code Duplication · Duplicated block (19 lines × 2 locations) pages/coupons/index.js
- Code Duplication · Duplicated block (19 lines × 2 locations) pages/goods-details/day.js
- Code Duplication · Duplicated block (19 lines × 2 locations) pages/invoice/apply.js
- Code Duplication · Duplicated block (19 lines × 2 locations) pages/my/info-menu.js
- Code Duplication · Duplicated block (18 lines × 2 locations) packageFx/pages/hehuorenfenxiao/fxmember.js
- Code Duplication · Duplicated block (18 lines × 2 locations) pages/my/feedback.js
- Code Duplication · Duplicated block with local edits (18 matched lines × 2 locations) pages/order-list/index.js
- Code Duplication · Duplicated block (18 lines × 2 locations) pages/score-excharge/growth.js
- Code Duplication · Duplicated block (17 lines × 2 locations) pages/category/category.js
- Code Duplication · Duplicated block with local edits (17 matched lines × 2 locations) pages/my/info.js
- Code Duplication · Duplicated block (17 lines × 2 locations) pages/qingdan/index.js
- Code Duplication · Duplicated block with local edits (17 matched lines × 2 locations) pages/recycle/index.js
- Code Duplication · Duplicated block (17 lines × 2 locations) utils/auth.js
- Code Duplication · Duplicated block (16 lines × 6 locations) components/goods-pop/index.js
- Code Duplication · Duplicated block with local edits (16 matched lines × 2 locations) miniprogram_npm/@vant/weapp/common/version.js
- Code Duplication · Duplicated block (16 lines × 2 locations) packageFx/pages/apply/index.js
- Code Duplication · Duplicated block (16 lines × 2 locations) pages/about/index.js
- Code Duplication · Duplicated block (16 lines × 3 locations) pages/address-add/index.js
- Code Duplication · Duplicated block (16 lines × 3 locations) pages/coupons/index.js
- Code Duplication · Duplicated block (16 lines × 2 locations) pages/goods-details/index.js
- Code Duplication · Duplicated block (16 lines × 2 locations) pages/to-pay-order/index.js
- Code Duplication · Duplicated block (16 lines × 2 locations) pages/to-pay-order/index.js
- Code Duplication · Duplicated block (16 lines × 2 locations) utils/address_parse.js
- Code Duplication · Duplicated block (15 lines × 3 locations) marketing/listing/detail.js
- Code Duplication · Duplicated block (15 lines × 2 locations) marketing/listing/detail.js
- Code Duplication · Duplicated block (15 lines × 3 locations) pages/address-add/index.js
- Code Duplication · Duplicated block (15 lines × 2 locations) pages/asset/index.js
- Code Duplication · Duplicated block (15 lines × 2 locations) pages/category/category.js
- Code Duplication · Duplicated block (15 lines × 2 locations) pages/idCheck/index.js
- Code Duplication · Duplicated block (15 lines × 3 locations) pages/invoice/list.js
- Code Duplication · Duplicated block (15 lines × 2 locations) pages/order-details/index.js
- Code Duplication · Duplicated block (15 lines × 4 locations) utils/address_parse.js
- Code Duplication · Duplicated block with local edits (14 matched lines × 2 locations) miniprogram_npm/@vant/weapp/toast/toast.js
- Code Duplication · Duplicated block (14 lines × 4 locations) packageCps/pages/order-list/cps.js
- Code Duplication · Duplicated block with local edits (14 matched lines × 2 locations) packageFx/pages/apply/index.js
- Code Duplication · Duplicated block (14 lines × 3 locations) packageFx/pages/myusers/index.js
- Code Duplication · Duplicated block (14 lines × 2 locations) pages/address-add/index.js
- Code Duplication · Duplicated block (14 lines × 2 locations) pages/goods-details/index.js
- Code Duplication · Duplicated block (14 lines × 2 locations) pages/goods/list-vop.js
- Code Duplication · Duplicated block (14 lines × 2 locations) pages/my/index.js
- Code Duplication · Duplicated block (13 lines × 11 locations) miniprogram_npm/@vant/weapp/area/index.js
- Code Duplication · Duplicated block with local edits (13 matched lines × 2 locations) packageFx/pages/apply/form.js
- Code Duplication · Duplicated block with local edits (13 matched lines × 2 locations) packageStreamMedia/pages/live-anchor/list.js
- Code Duplication · Duplicated block with local edits (13 matched lines × 2 locations) packageStreamMedia/pages/live-anchor/list.js
- Code Duplication · Duplicated block (13 lines × 2 locations) pages/asset/index.js
- Code Duplication · Duplicated block (13 lines × 2 locations) pages/coupons/index.js
- Code Duplication · Duplicated block with local edits (13 matched lines × 2 locations) pages/coupons/merge.js
- Code Duplication · Duplicated block (13 lines × 4 locations) pages/goods/fav.js
- Code Duplication · Duplicated block with local edits (13 matched lines × 2 locations) pages/shop-cart/index.js
- Code Duplication · Duplicated block (12 lines × 2 locations) components/goods-pop/index.js
- Code Duplication · Duplicated block (12 lines × 2 locations) marketing/listing/index.js
- Code Duplication · Duplicated block (12 lines × 2 locations) miniprogram_npm/@vant/weapp/calendar/index.js
- Code Duplication · Duplicated block (12 lines × 2 locations) miniprogram_npm/@vant/weapp/common/utils.js
- Code Duplication · Duplicated block (12 lines × 2 locations) miniprogram_npm/@vant/weapp/index-bar/index.js
- Code Duplication · Duplicated block (12 lines × 2 locations) miniprogram_npm/@vant/weapp/uploader/utils.js
- Code Duplication · Duplicated block with local edits (12 matched lines × 2 locations) packageFx/pages/apply/index.js
- Code Duplication · Duplicated block with local edits (12 matched lines × 2 locations) packageFx/pages/apply/index.js
- Code Duplication · Duplicated block (12 lines × 2 locations) packageFx/pages/hehuorenfenxiao/index.js
- Code Duplication · Duplicated block (12 lines × 2 locations) packageFx/pages/myusers/index.js
- Code Duplication · Duplicated block (12 lines × 3 locations) packageFx/pages/myusers/index.js
- Code Duplication · Duplicated block (12 lines × 2 locations) packageStreamMedia/components/TRTCCalling/controller/user-controller.js
- Code Duplication · Duplicated block with local edits (12 matched lines × 2 locations) pages/about/index.js
- Code Duplication · Duplicated block with local edits (12 matched lines × 2 locations) pages/goods-details/vop.js
- Code Duplication · Duplicated block (12 lines × 3 locations) pages/index/index.js
- Code Duplication · Duplicated block (12 lines × 3 locations) pages/my/index.js
- Code Duplication · Duplicated block with local edits (12 matched lines × 2 locations) pages/peisong/orders.js
- Code Duplication · Duplicated block (12 lines × 2 locations) pages/raffle/index.js
- Code Duplication · Duplicated block (11 lines × 3 locations) marketing/listing/edit.js
- Code Duplication · Duplicated block (11 lines × 5 locations) miniprogram_npm/@vant/weapp/area/index.js
- Code Duplication · Duplicated block (11 lines × 2 locations) miniprogram_npm/@vant/weapp/field/index.js
- Code Duplication · Duplicated block with local edits (11 matched lines × 2 locations) miniprogram_npm/@vant/weapp/slider/index.js
- Code Duplication · Duplicated block (11 lines × 2 locations) miniprogram_npm/@vant/weapp/uploader/index.js
- Code Duplication · Duplicated block (11 lines × 2 locations) miniprogram_npm/wxa-plugin-canvas/index/index.js
- Code Duplication · Duplicated block with local edits (11 matched lines × 2 locations) packageFx/pages/myusers/myusers-detail.js
- Code Duplication · Duplicated block with local edits (11 matched lines × 2 locations) packageStreamMedia/pages/live-anchor/list.js
- Code Duplication · Duplicated block with local edits (11 matched lines × 2 locations) packageStreamMedia/pages/videoCall/videoCall.js
- Code Duplication · Duplicated block (10 lines × 2 locations) components/goods-pop/index.js
- Code Duplication · Duplicated block (10 lines × 2 locations) components/payment/index.js
- Code Duplication · Duplicated block with local edits (10 matched lines × 2 locations) miniprogram_npm/@vant/weapp/checkbox-group/index.js
- Code Duplication · Duplicated block with local edits (10 matched lines × 2 locations) miniprogram_npm/@vant/weapp/checkbox-group/index.js
- Code Duplication · Duplicated block (10 lines × 2 locations) pages/address-add/index.js
- Code Duplication · Duplicated block (10 lines × 2 locations) pages/category/category.js
- Code Duplication · Duplicated block (10 lines × 2 locations) pages/maidan/index.js
- Code Duplication · Duplicated block with local edits (10 matched lines × 2 locations) pages/my/feedback.js
- Code Duplication · Duplicated block (10 lines × 3 locations) pages/my/index.js
- Code Duplication · Duplicated block (10 lines × 2 locations) pages/pwd-pay/reset.js
- Code Duplication · Duplicated block with local edits (10 matched lines × 2 locations) pages/recycle/index.js
- Code Duplication · Duplicated block (10 lines × 2 locations) pages/to-pay-order/index.js
- Code Duplication · Duplicated block (10 lines × 2 locations) utils/auth.js
- Code Duplication · Duplicated block (9 lines × 5 locations) components/goods-pop/index.js
- Code Duplication · Duplicated block (9 lines × 2 locations) marketing/listing/edit.js
- Code Duplication · Duplicated block (9 lines × 3 locations) miniprogram_npm/@vant/weapp/calendar/components/header/index.js
- Code Duplication · Duplicated block (9 lines × 2 locations) miniprogram_npm/@vant/weapp/nav-bar/index.js
Rebuild cost: about €31,000 · Estimate
| Cost to rebuild | €10,000 to €52,000, for 173 to 550 hours of work, about 0.2 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 25. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Medium: 36,773 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Accessibility
At a glance — Performance
Roadmap
Top priorities: 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; Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md; 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.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| 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. | +13.4 pts | Medium | Text alternatives |
| Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md. | +3.8 pts | Low | Documentation Quality |
| 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. | +2.4 pts | Medium | Architecture documentation |
| Add a CI workflow that builds and runs the test suite on every push/PR. | +1.9 pts | Medium | CI/CD gates |
| Adopt pino (or winston) and log at meaningful points in the services you run. | +1.9 pts | Medium | Observability |
| Add a test runner (vitest / jest / playwright) and eslint and type checking (adopt TypeScript, or type-check the existing JavaScript with `checkJs`) as package.json scripts and run them in CI. | +1.9 pts | Medium | Tooling |
| 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. | +1.8 pts | Medium | Type Safety |
| 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. | +1.8 pts | Medium | Code Duplication |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| pages/to-pay-order/index.js | 7.1 | Mixed | Cyclomatic Complexity: createOrder (cyclomatic 99) |
| pages/goods-details/index.js | 7.2 | Mixed | Cyclomatic Complexity: getGoodsDetailAndKanjieInfo (cyclomatic 23) |
| pages/order-list/index.js | 7.2 | Mixed | Cyclomatic Complexity: orderList (cyclomatic 16) |
| utils/address_parse.js | 7.4 | Mixed | Cyclomatic Complexity: address_parse.smatrAddress (cyclomatic 44) |
| pages/address-add/index.js | 7.8 | Mixed | Cyclomatic Complexity: bindSave (cyclomatic 23) |
| marketing/listing/detail.js | 7.8 | Mixed | Cyclomatic Complexity: loadPageData (cyclomatic 20) |
| marketing/listing/edit.js | 7.8 | Mixed | Cyclomatic Complexity: submit (cyclomatic 19) |
| pages/wuliu/index.js | 7.8 | Mixed | Cyclomatic Complexity: orderDetail (cyclomatic 19) |
| miniprogram_npm/@vant/weapp/mixins/transition.js | 7.8 | Mixed | Cyclomatic Complexity: transition.transition (cyclomatic 17) |
| app.js | 7.8 | Mixed | Cyclomatic Complexity: onShow (cyclomatic 16) |
| miniprogram_npm/wxa-plugin-canvas/index/index.js | 7.8 | Mixed | Cognitive Complexity: _drawSingleText (cognitive 37) |
| miniprogram_npm/@vant/weapp/calendar/index.js | 7.8 | Mixed | Cognitive Complexity: onClickDay (cognitive 23) |
| pages/order-details/index.js | 7.8 | Mixed | Cognitive Complexity: submitReputation (cognitive 18) |
| pages/qingdan/index.js | 8.5 | Near-clean | Cyclomatic Complexity: rebuildDisplay (cyclomatic 16) |
| components/goods-pop/index.js | 8.5 | Near-clean | Cognitive Complexity: calculateGoodsPrice (cognitive 21) |
| packageFx/pages/commisionLog/index.js | 8.5 | Near-clean | Cognitive Complexity: getCommisionLog (cognitive 20) |
| packageFx/pages/myusers/index.js | 8.5 | Near-clean | Cognitive Complexity: fxMembers (cognitive 20) |
| utils/auth.js | 8.5 | Near-clean | Cognitive Complexity: auth.login (cognitive 18) |
| miniprogram_npm/@vant/weapp/uploader/utils.js | 8.5 | Near-clean | Cognitive Complexity: utils.chooseFile (cognitive 17) |
| pages/live/index.js | 8.5 | Near-clean | Cognitive Complexity: shouldUseFingerprintEmoji (cognitive 17) |
How the grades work
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.
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.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
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 48 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.7, the weighted average across measured dimensions.
What we checked — 48 dimensions across the health lenses
- 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, 177 of 189 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: the test suite could not be built/run in-image (commonly external-service dependencies — a database, a broker — we won't provision). To have it measured, make the suite runnable without them. For context only, test code is ≈ 0% of production LoC (9 test / 36,773 production) — a rough proxy, NOT a coverage measurement, so it is excluded from the score. You can widen what we reach: optional: make the suite runnable without a database, broker or other service we do not provision, and real coverage is measured on the next scan.
- D12 Dependency Hygiene — 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. This repository's 1 package.json manifest(s) WERE read and their pinning discipline assessed; what went unanswered is the currency half, because answering it needs a lockfile resolved to CONCRETE versions and this repository commits none — a package.json states version RANGES, and a range names no particular release to be behind. So registry.npmjs.org was never asked, and there was nothing here for it to grade. This is a true statement about the repository and NOT a gap on our side: no lockfile reader we could write would find anything here to read, so there is no capability behind this row to build.
- D14 License Compliance — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — this repository declares package.json manifests but commits no lockfile this pass can resolve (npm, pnpm, yarn and bun each write a different one, and `bun.lockb` is a binary format with no published shape), so the set of packages it actually ships is not resolvable from the checkout: its declarations carry version RANGES, and grading whichever release happens to be newest today would be a verdict about a dependency graph this repository has not pinned. Commit the lock and this dimension grades its production dependencies against registry.npmjs.org. NOT a finding that this repository's licences are compliant: this dimension asserts nothing about its licensing in either direction.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (30 contributor(s) across 715 commit(s) sampled, automation and bot accounts excluded). One of them holds 88% of the history; the other 29 hold 0.4% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D22 Internal API Consistency — not measured this run — 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: it declares a published package (package.json), but 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.
- D26 Project Cohesion — 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. `(repository root)` (36093 LoC, 48 module-visible types across 32 directories) is over its size bounds, and whether one unit is a coherent whole or a grab-bag is read from its type references: the parts of it that reach the rest only through its shared core. Those are read over the C#/VB code model, which this unit's source did not supply. Its size alone is no verdict on its cohesion, so none is published.
- D30 Dependency Vulnerabilities — measured, with a gap in what it reached — 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. The scanner produced no output at all, so no dependency was actually scanned. 1 of 2 declared ecosystem(s) (npm) WERE scanned and every vulnerability they reported is included in this result; osv was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that osv is free of known-vulnerable dependencies. osv: the scanner produced no output at all, so no dependency was actually scanned. This is reported as a measurement gap rather than a clean pass. osv-scanner documents exit 128 as "no package sources found" — but this scan only invoked it because the tree declares a source it supports (`pom.xml` and the resolved lockfiles among them), so the tool's report and this repository disagree. Check that those sources are reachable from the directory the scan ran in before concluding anything is missing. If this tree really does commit only range-pinned manifests, commit the lockfile your package manager produces — but only where your ecosystem HAS one and commits it: Maven has none at all (osv-scanner reads `pom.xml` directly) and Gradle writes one only under opt-in dependency locking, while a published Composer package and a published Dart library both deliberately exclude theirs. In those three, generate one in CI before the scan instead — a resolved dependency list or an SBOM fed to the scanner.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `packageStreamMedia/components/TRTCCalling/utils/tsignaling-wx.js` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- D43 Malicious Dependencies — measured, with a gap in what it reached — 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. The scanner produced no output at all, so no dependency was actually scanned. 1 of 2 declared ecosystem(s) (npm) WERE scanned and every vulnerability they reported is included in this result; osv was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that osv is free of known-vulnerable dependencies. osv: the scanner produced no output at all, so no dependency was actually scanned. This is reported as a measurement gap rather than a clean pass. osv-scanner documents exit 128 as "no package sources found" — but this scan only invoked it because the tree declares a source it supports (`pom.xml` and the resolved lockfiles among them), so the tool's report and this repository disagree. Check that those sources are reachable from the directory the scan ran in before concluding anything is missing. If this tree really does commit only range-pinned manifests, commit the lockfile your package manager produces — but only where your ecosystem HAS one and commits it: Maven has none at all (osv-scanner reads `pom.xml` directly) and Gradle writes one only under opt-in dependency locking, while a published Composer package and a published Dart library both deliberately exclude theirs. In those three, generate one in CI before the scan instead — a resolved dependency list or an SBOM fed to the scanner.
- AXB1 Runtime evidence locked — no reproducible boot — 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. Subject: 1 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates. The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. We then boot it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
- P5 DR & Backup — 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. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and none applies: this repository publishes a library and deploys nothing (no container, IaC or deployment manifest), so it holds no runtime state of its own. Any data-access dependency it declares is the store it is a CLIENT for, not one it operates. The DR control belongs to whoever runs that data.
- 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. 128 further occurrence(s) are not listed individually; the score already reflects all 168.
- S1 Web-Security Posture — 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. 221 JavaScript/TypeScript file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled certificate validation, obsolete TLS versions, plaintext password storage and session cookies set without HttpOnly, Secure or SameSite, and none was found. The server controls this dimension also scores were not assessed, so no score is given.
- X2 Cancellation propagation — 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, and JavaScript/TypeScript, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded, and no named async function in this repository's JavaScript/TypeScript, nor any Go, PHP or Dart function or Kotlin suspend function, makes a request that can be cancelled (fetch, axios, ky, ofetch, got, undici, node:http; net/http, net.Dial; amphp; Dio; Ktor, OkHttp), so there is nothing to judge, 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.
- X4 Structured logging — 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, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP make no call through a named logger, 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.
- X5 Nullable reference types — 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 and MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, and Kotlin source only, and no C# was loaded, no TypeScript was found, and this repository's Vue components 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.
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
- 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.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- 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.
- 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.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
- 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.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
13 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was createOrder at 99. A further 1 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being _pusherStateChangeHandler at 28 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: packageStreamMedia/components/TRTCCalling/TRTCCalling.js (_pusherStateChangeHandler at 28). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 1 body over 60 down to 60 or less in Cyclomatic Complexity — start with createOrder (cyclomatic 99). — Refactoring it lifts Cyclomatic Complexity from 7.0 to about 7.5/10.
D2 · Cognitive Complexity
35 method(s) exceeded the cognitive complexity threshold of 15; the worst was createOrder at 231.
What to do
- Bring the 1 body over 120 down to 120 or less in Cognitive Complexity — start with createOrder (cognitive 231). — Refactoring it lifts Cognitive Complexity from 5.1 to about 5.8/10.
D3 · God Classes
2 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 1 FileTooLong finding(s) in God Classes — start with index.js. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 FunctionTooLong finding(s) in God Classes — start with address_parse.js. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
0 duplicated block group(s) detected. 0.0 % of the production lines (0 of 36,773) are in a reported copy.
D6 · Cohesion (LCOM4)
0 of 3 classes have LCOM4 above 3.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D19 · Documentation Quality
0 of 1 documentation facets pass in full; short on: F2 example. 1 document(s) read across 1 unit(s).
What to do
- Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md. — One of this dimension's main actionable groups (1 recommendation-level).
D24 · Comment Value
1 of 35 judged comments only repeat the code they sit on (2.9 %). 1065 comment(s) in another language or script were not judged.
What to do
- Resolve the 1 redundant comment finding(s) in Comment Value — start with environment.js. — One of this dimension's main actionable groups (1 recommendation-level).
D27 · Navigability
5 % of calls cross a namespace and 0 % 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.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
semgrep found no security issues. semgrep hit a parse error in 2 file(s) — `miniprogram_npm/apifm-wxapi/index.js`, `packageStreamMedia/components/TRTCCalling/utils/tsignaling-wx.js` — so no absence of findings in them is evidence of anything, and nothing in them was analysed. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
D30 · Dependency Vulnerabilities
No known-vulnerable dependencies in the 1 ecosystem(s) that were scanned (npm). Partial dependency scan: 1 of 2 declared ecosystem(s) were scanned (npm), and the findings above are real and complete for them. osv was not scanned (osv: the scanner produced no output at all, so no dependency was actually scanned), so this is not the whole dependency surface and the result is reported at reduced confidence.
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 96 of the 221 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
Strongest change-coupling: config.js↔apply.js 95%; config.js↔index.js 93%; config.js↔index.js 87%
What to do
- Resolve the 1 Change-coupling hub finding(s) in Change Coupling — start with config.js. — One of this dimension's main actionable groups (1 warning-level).
D43 · Malicious Dependencies
No known-vulnerable dependencies in the 1 ecosystem(s) that were scanned (npm). Partial dependency scan: 1 of 2 declared ecosystem(s) were scanned (npm), and the findings above are real and complete for them. osv was not scanned (osv: the scanner produced no output at all, so no dependency was actually scanned), so this is not the whole dependency surface and the result is reported at reduced confidence.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 0 platform declaration(s) and 6 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.
Frontend & cross-cutting dimensions
AC1 · Text alternatives
- 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) — pages/huodong/index.vue:7, pages/huodong/index.vue:95
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.
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
- A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead. (×2) — miniprogram_npm/@vant/weapp/mixins/touch.js:4, miniprogram_npm/@vant/weapp/mixins/transition.js:4
- `onClick` has an empty body — confirm it's an intentional no-op and not an unfinished method. — miniprogram_npm/@vant/weapp/notify/notify.js:25
- `onOpened` has an empty body — confirm it's an intentional no-op and not an unfinished method. — miniprogram_npm/@vant/weapp/notify/notify.js:26
- `onClose` has an empty body — confirm it's an intentional no-op and not an unfinished method. — miniprogram_npm/@vant/weapp/notify/notify.js:27
What to do
- Clear the softer debt: re-enable or delete skipped tests, decide whether each empty function is a deliberate no-op (and say so in a comment), and replace blanket `eslint-disable` / `@ts-nocheck` with targeted, justified suppressions.
M1 · Documentation (README)
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 documentation
- 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 structure
- Most of the production code is in directories of its own, but 2 application file(s) sit at the repository root beside the build and tooling files (`app.js`, `config.js`).
P1 · CI/CD gates
- No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.
What to do
- Add a CI workflow that builds and runs the test suite on every push/PR.
P10 · Library API & versioning
P2 · Observability
- No logging call was found in the 228 JavaScript/TypeScript production file(s) this check read across 1 module(s). Each was searched for its ecosystem's logging libraries (JavaScript/TypeScript: pino, winston, bunyan, log4js, loglevel, consola, the NestJS Logger) and for a call on a receiver named `log`/`logger` (or ending in `Logger`/`_logger`) with a level verb. It cannot see logging through a repo-local wrapper named otherwise, or in source it did not read — this is 'no logging found by this walk', not a verdict that nothing here logs. If it is right, production issues will be hard to diagnose.
What to do
- Adopt pino (or winston) and log at meaningful points in the services you run.
- Add a health-check endpoint (@godaddy/terminus or a /health route) so orchestrators and load balancers can probe liveness/readiness.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add CodeQL's javascript-typescript pack, `semgrep --config=p/javascript`, or eslint-plugin-security — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
- `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`. — package.json:6
What to do
- Run what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/javascript`, or eslint-plugin-security — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- The release 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 the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
What to do
- Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
PF3 · Async & latency hygiene
R1 · Type Safety
- 0 typed · 223 plain JS — the untyped files are app.js, components/bind-mobile/index.js, components/date-time-selecter/index.js, components/fuwuxieyi/index.js, components/goods-pop/index.js, components/login/index.js (+217 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 Duplication
- 45 duplicated blocks under pages/ have copies in at least two of the sibling directories about, address-add, asset, card, category, cms (+27 more sibling(s) not listed) — 37 of them are reported below, and 8 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 45 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 45 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 45 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. — pages/order-details/index.js:121
- 29 duplicated blocks under the repository root have copies in at least two of the sibling directories components, marketing, miniprogram_npm, packageCps, packageFx, packageStreamMedia (+1 more sibling(s) not listed) — 27 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 29 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 29 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 29 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. — packageCps/pages/goods-details/cps-jd.js:6
- 27 duplicated blocks under miniprogram_npm/@vant/weapp/ have copies in at least two of the sibling directories action-sheet, area, calendar, cascader, cell-group, checkbox (+37 more sibling(s) not listed) — 20 of them are reported below, and 7 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 27 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 27 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 27 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — miniprogram_npm/@vant/weapp/toast/toast.js:1
- 7 of the duplicated blocks reported below have copies in at least two of the sibling directories apply, hehuorenfenxiao, index, myusers, report under packageFx/pages/. 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. — packageFx/pages/hehuorenfenxiao/index.js:5
- packageCps/pages/goods-details/cps-jd.js:1 · packageCps/pages/goods-details/cps-pdd.js:1 · packageCps/pages/goods-details/cps-taobao.js:1 — these 3 files are line-for-line copies of one another — 415 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. — packageCps/pages/goods-details/cps-jd.js:1
- packageFx/pages/hehuorenfenxiao/index.js:5 · packageFx/pages/index/index.js:4 — the two spans are one implementation copied and then locally edited — 1122 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. — packageFx/pages/hehuorenfenxiao/index.js:5
- packageStreamMedia/pages/live-anchor/index.js:352 · packageStreamMedia/pages/live-client/client.js:249 — the two spans are one implementation copied and then locally edited — 685 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. — packageStreamMedia/pages/live-anchor/index.js:352
- packageStreamMedia/pages/live-anchor/index.js:32 · packageStreamMedia/pages/live-client/client.js:67 — the two spans are one implementation copied and then locally edited — 613 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. — packageStreamMedia/pages/live-anchor/index.js:32
- pages/goods-details/index.js:455 · pages/goods-details/vop.js:347 — 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. — pages/goods-details/index.js:455
- pages/goods/fav.js:50 · pages/goods/his.js:58 — the two spans are one implementation copied and then locally edited — 552 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. — pages/goods/fav.js:50
- packageCps/pages/goods-details/cps-jd.js:6 · pages/goods-details/vop.js:7 — 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. — packageCps/pages/goods-details/cps-jd.js:6
- pages/pwd-pay/modify.js:3 · pages/pwd-pay/set.js:3 — 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. — pages/pwd-pay/modify.js:3
- pages/recycle/index.js:66 · pages/recycle/index.js:112 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — pages/recycle/index.js:66
- packageFx/pages/report/city.js:14 · packageFx/pages/report/team.js:13 — 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. — packageFx/pages/report/city.js:14
- pages/goods-details/index.js:317 · pages/goods-details/vop.js:254 — 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. — pages/goods-details/index.js:317
- pages/order-details/index.js:121 · pages/peisong/detail.js:78 — the two spans are one implementation copied and then locally edited — 278 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. — pages/order-details/index.js:121
- pages/huodong/index.js:50 · pages/huodong/index.vue:180 — the two spans are one implementation copied and then locally edited — 311 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. — pages/huodong/index.js:50
- pages/maidan/index.js:66 · pages/recharge/index.js:42 — the two spans are one implementation copied and then locally edited — 181 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. — pages/maidan/index.js:66
- components/login/index.js:41 · pages/my/index.js:195 — the two spans are one implementation copied and then locally edited — 170 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. — components/login/index.js:41
- packageFx/pages/hehuorenfenxiao/index.js:472 · packageFx/pages/index/index.js:245 — 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. — packageFx/pages/hehuorenfenxiao/index.js:472
- components/bind-mobile/index.js:42 · pages/login/index.js:77 — 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. — components/bind-mobile/index.js:42
- pages/goods-details/day.js:43 · pages/goods-details/times02.js:33 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — pages/goods-details/day.js:43
- pages/address-add/index.js:155 · pages/invoice/apply.js:88 — the two spans are one implementation copied and then locally edited — 81 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. — pages/address-add/index.js:155
- pages/goods/his.js:195 · pages/goods/list.js:136 — 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. — pages/goods/his.js:195
- components/goods-pop/index.js:181 · packageCps/pages/goods-details/cps-jd.js:359 · packageCps/pages/goods-details/cps-pdd.js:320 · packageCps/pages/goods-details/cps-taobao.js:276 · +2 more site(s) not listed — the 6 copies are spread across 3 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 6 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — components/goods-pop/index.js:181
- pages/asset/index.js:121 · pages/asset/index.js:149 — 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. — pages/asset/index.js:121
- pages/peisong/detail.js:276 · pages/peisong/detail.js:303 — 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. — pages/peisong/detail.js:276
- pages/goods-details/index.js:1203 · pages/goods-details/vop.js:828 — 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. — pages/goods-details/index.js:1203
- pages/goods-details/index.js:573 · pages/goods-details/index.js:664 — the two spans are one implementation copied and then locally edited — 113 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — pages/goods-details/index.js:573
- miniprogram_npm/@vant/weapp/mixins/transition.js:67 · miniprogram_npm/@vant/weapp/mixins/transition.js:98 — the two spans are one implementation copied and then locally edited — 139 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — miniprogram_npm/@vant/weapp/mixins/transition.js:67
- packageFx/pages/hehuorenfenxiao/fxmember.js:59 · packageFx/pages/hehuorenfenxiao/index.js:172 — 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. — packageFx/pages/hehuorenfenxiao/fxmember.js:59
- pages/recycle/orders.js:35 · pages/recycle/orders.js:61 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — pages/recycle/orders.js:35
- pages/card/logs.js:26 · pages/goods/list-vop.js:67 — 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. — pages/card/logs.js:26
- packageFx/pages/hehuorenfenxiao/index.js:253 · pages/score/index.js:54 — 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. — packageFx/pages/hehuorenfenxiao/index.js:253
- packageFx/pages/hehuorenfenxiao/index.js:433 · packageFx/pages/index/index.js:204 — 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. — packageFx/pages/hehuorenfenxiao/index.js:433
- packageStreamMedia/components/TRTCCalling/TRTCCalling.js:238 · packageStreamMedia/components/TRTCCalling/TRTCCalling.js:265 — 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. — packageStreamMedia/components/TRTCCalling/TRTCCalling.js:238
- pages/live/index.js:82 · pages/sign/index.js:75 — the two spans are one implementation copied and then locally edited — 188 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. — pages/live/index.js:82
- pages/peisong/detail.js:149 · pages/peisong/detail.js:177 — 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. — pages/peisong/detail.js:149
- pages/to-pay-order/index.js:530 · pages/to-pay-order/index.js:647 — 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. — pages/to-pay-order/index.js:530
- utils/auth.js:75 · utils/auth.js:99 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — utils/auth.js:75
What to do
- Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
R2 · Cyclomatic Complexity
- createOrder has cyclomatic complexity 88 and cognitive complexity 174; 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. — pages/to-pay-order/index.js:308
- bindSave has cyclomatic complexity 23 and cognitive complexity 25; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — pages/address-add/index.js:154
- getGoodsDetailAndKanjieInfo has cyclomatic complexity 22 and cognitive complexity 43; 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. — pages/goods-details/index.js:216
- smatrAddress has cyclomatic complexity 21 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. — utils/address_parse.js:34
- loadPageData has cyclomatic complexity 20 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. — marketing/listing/detail.js:102
- orderDetail has cyclomatic complexity 19 and cognitive complexity 26; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — pages/wuliu/index.js:14
- submit has cyclomatic complexity 16 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. — marketing/listing/edit.js:235
- shouldUseFingerprintEmoji has cyclomatic complexity 15 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. (×2) — pages/live/index.js:84, pages/sign/index.js:77
- onCellTap has cyclomatic complexity 15 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — game/numberBomb/index.js:99
- _drawSingleText has cyclomatic complexity 14 and cognitive complexity 36; 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. — miniprogram_npm/wxa-plugin-canvas/index/index.js:178
- getInitialDate has cyclomatic complexity 14 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. — miniprogram_npm/@vant/weapp/calendar/index.js:197
- updateValue has cyclomatic complexity 14 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — miniprogram_npm/@vant/weapp/slider/index.js:141
- addShopCar has cyclomatic complexity 13 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — pages/goods/fav.js:100
- submitForm has cyclomatic complexity 13 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — pages/qingdan/index.js:323
- orderList 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. — pages/order-list/index.js:244
- processYunfei has cyclomatic complexity 12 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — pages/to-pay-order/index.js:844
- addShopCar has cyclomatic complexity 12 and cognitive complexity 12; 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. — pages/goods/his.js:122
- getRangeDayType has cyclomatic complexity 12 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — miniprogram_npm/@vant/weapp/calendar/components/month/index.js:99
- drawBlock has cyclomatic complexity 11 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. — miniprogram_npm/wxa-plugin-canvas/index/index.js:6
- (anonymous) has cyclomatic complexity 11 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. — miniprogram_npm/@vant/weapp/uploader/utils.js:59
- (anonymous) has cyclomatic complexity 11 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packageFx/pages/hehuorenfenxiao/index.js:175
- bindSave has cyclomatic complexity 11 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — pages/withdraw/index.js:38
- calculateGoodsPrice has cyclomatic complexity 11 and cognitive complexity 12; 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. — components/goods-pop/index.js:210
- onLoad has cyclomatic complexity 11 and cognitive complexity 12; 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. — pages/goods-details/vop.js:51
- loadDetail has cyclomatic complexity 11 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — marketing/listing/edit.js:53
- orderDetail has cyclomatic complexity 11 and cognitive complexity 9; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — pages/order-details/index.js:60
R3 · Large Files
- pages/to-pay-order/index.js has 1346 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — pages/to-pay-order/index.js:1
- pages/goods-details/index.js has 1217 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — pages/goods-details/index.js:1
- pages/goods-details/vop.js has 851 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — pages/goods-details/vop.js:1
- packageStreamMedia/components/TRTCCalling/TRTCCalling.js has 829 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packageStreamMedia/components/TRTCCalling/TRTCCalling.js:1
- packageCps/pages/goods-details/cps-jd.js has 727 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packageCps/pages/goods-details/cps-jd.js:1
- packageCps/pages/goods-details/cps-pdd.js has 683 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packageCps/pages/goods-details/cps-pdd.js:1
- pages/huodong/index.vue has 680 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — pages/huodong/index.vue:1
- packageCps/pages/goods-details/cps-taobao.js has 675 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packageCps/pages/goods-details/cps-taobao.js:1
- packageFx/pages/hehuorenfenxiao/index.js has 625 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packageFx/pages/hehuorenfenxiao/index.js:1
- pages/index/index.js has 508 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — pages/index/index.js:1
- marketing/listing/detail.js has 505 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — marketing/listing/detail.js:1
- miniprogram_npm/wxa-plugin-canvas/index/index.js has 503 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — miniprogram_npm/wxa-plugin-canvas/index/index.js:1
- packageStreamMedia/pages/live-client/client.js has 479 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packageStreamMedia/pages/live-client/client.js:1
- packageStreamMedia/pages/live-anchor/index.js has 469 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packageStreamMedia/pages/live-anchor/index.js:1
- pages/qingdan/index.js has 450 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — pages/qingdan/index.js:1
- pages/address-add/index.js has 439 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — pages/address-add/index.js:1
- pages/order-list/index.js has 406 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — pages/order-list/index.js:1
What to do
- Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
R6 · Tooling
- 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 a test runner (vitest / jest / playwright) and eslint and type checking (adopt TypeScript, or type-check the existing JavaScript with `checkJs`) as package.json scripts and run them in CI.
R7 · Dead Code
- Unreachable from the 180 application, 99 tooling and 1 test entry point(s) detected in this repo. Nothing this repository declares compiles or type-checks these files, so a wrong deletion here would raise no compile error — gate removals on `npm test`, which loads the modules, and note that it only covers what it exercises. An undetected custom entry would make these reachable.
- no import path from any entry point (180 application, 99 tooling, 1 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 (×8) — pages/huodong/index.vue, miniprogram_npm/@vant/weapp/dialog/dialog.js, miniprogram_npm/@vant/weapp/notify/notify.js, …
- This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it. — packageFx/pages/index/index.js:6
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 Hygiene
- Imported but not declared in any reachable package.json — installs work only by hoisting accident. (×4) — app.js:2, miniprogram_npm/@vant/weapp/common/component.d.ts:2, packageStreamMedia/components/TRTCCalling/TRTCCalling.js:4, …
- Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
What to do
- Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports
X1 · Async correctness
X12 · Unreachable branch
X16 · Unfloored truncation loop
X21 · Side-effecting pattern guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
- 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. (×2) — pages/sign/index.js:101, pages/live/index.js:106
- `.catch(function(){})` 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. (×4) — miniprogram_npm/@vant/weapp/sticky/index.js:84, miniprogram_npm/@vant/weapp/picker/index.js:34, miniprogram_npm/@vant/weapp/area/index.js:179, …
What to do
- Swallowed exception (empty catch)
X30 · Support guard that admits what it rejects
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC1 · Text alternatives | 1.1.1, 1.2.2, 1.2.5 | Partial signal |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 39% | Weak — gated by R1, R10 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 100% | Exemplary | Solid. |
| Maturity | 48% | Weak — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 15% | Critical — gated by R6, R8, P1, P2, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 100% | Exemplary | Strongest area. |
| Accessibility | 10% | Critical — gated by AC1 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Solid. |
Unscored — 2 check(s) recorded observations but carry no score
- SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X10 Duplicated predicate — 18 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 77 check(s) not relevant to this codebase
- AC2 Forms & labels — No form control/button found in the parsed markup — AC2 not applicable here.
- AC3 Page structure — No structural check found in the parsed markup — AC3 not applicable here.
- AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
- AC5 ARIA correctness — No ARIA usage found in the parsed markup — AC5 not applicable here.
- AC6 Visual & motion safety — No styled element found in the parsed markup — AC6 not applicable here.
- AX1 Captive dependencies — Not applicable: this repository's JavaScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- AX2 Stateful singletons — Not applicable: TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- 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
- AX6 Interface segregation — not applicable — JavaScript has no interface declaration, so there is no declared member list whose width this check could measure
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no data at rest for these controls to protect. If it does persist personal data (through a hosted backend configured outside this repository, for instance), the controls belong to wherever that data is stored.
- C2 Access Controls — No access-control surface detected in the analyzed source — this repository stands up no server (no Express, Fastify, Koa, Hono, NestJS or similar app, no Next.js/SvelteKit/Nuxt server route, no edge function), creates no Supabase tables and talks to no hosted backend. Access control is therefore N/A here — a browser application or library is authorized by the server it calls, not by itself; a client-side route guard hides a page and authorizes nothing. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a hosted backend configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound. If it does (through a hosted backend configured outside this repository, for instance), the limit belongs wherever that data is stored.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over. If it does (through a hosted backend configured outside this repository, for instance), the rights are served wherever that data is stored.
- D10 Test Quality — No tests were found in the analyzed repository to assess for quality.
- D11 Test Reliability — No test suite was found to re-run, so reliability couldn't be assessed. Two searches produced that zero and both came back empty: the classifier that reads the loaded workspace recognised no suite it could run, and a walk of the source on disk — which covers the JS/TS `*.test.*` and `*.spec.*` conventions and probes for a Pester suite — found no test source in any other ecosystem either. Neither search reaches a suite that is missing from the loaded workspace and carries no name either walk recognises, so this is 'no suite found by those two searches', not a verdict that the repository has none.
- D12 Dependency Hygiene — Dependency currency not established — this repository commits no lockfile to resolve
- D14 License Compliance — npm licences not graded — this npm repository commits no lockfile this pass can resolve
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D17 Explicit Debt — explicit-debt markers are read through a C# workspace today, so they were not read for this repository's language — this asserts nothing about how many markers the code carries. Not scored — this is a gap in the analyzer, not a finding about this repository
- 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.
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D21 Naming Consistency — N/A — too few peers to establish a naming convention (322 declarations, no unit with a dominant convention).
- 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
- D26 Project Cohesion — D26 could not read how the parts of this repository's one build unit reference each other, so its cohesion was not measured. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — 1 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D5 Coupling — Not applicable — this npm build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not measured
- DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this lens looks for
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- M4 Documentation accuracy — Not applicable: the 1 current-state document(s) make no claim of a kind M4 checks.
- P12 CI test-gate honesty — no CI workflow found
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript source, so there is no service whose uptime a failing dependency could take down
- 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 tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a package.json, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
- R4 Test Coverage — 1 test file(s) reach none of 218 production file(s) via imports — exercised outside the JS import graph (integration/bundled), not import-reachable
- 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
- S1 Web-Security Posture — Not assessed: 221 JavaScript/TypeScript file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation, obsolete TLS versions, passwords stored or checked as plaintext and session cookies set without HttpOnly, Secure or SameSite, and none was found. That half of the dimension is clean, but it is not scored on its own: a C# repository with the same clean reading is scored on its server controls as well, or is N/A for having no web surface, and neither can be decided here. Of the server controls, two are read where the source shows them: every session or sign-in cookie the code sets is read for HttpOnly, Secure and SameSite at the line that sets it (a raw `Set-Cookie` header, Express, Fastify, Hono, Koa, Next.js, `cookie.serialize`, express-session and cookie-session), and every Node listener for HTTPS enforcement. HSTS, security response headers and input validation are NOT assessed for JavaScript/TypeScript: each is scored as an absence, an absence is only reportable over the production HTTP server, and in this ecosystem the file that opens the port is build output or a framework launcher rather than a file in the source tree. Their absence here is not a finding about this repository.
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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 — 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
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- 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
- X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
- X27 Collection changed while being enumerated — Not applicable: this check looks for a loop whose body adds to or removes from the very collection the loop is walking, invalidating the enumerator it holds, and in this repository's languages that cannot happen. JavaScript and TypeScript have no iterator that a change can invalidate: an `Array` is walked by index against its live length, and a `Map` or `Set` by the ECMAScript specification's live entry list, so a body that adds to, removes from or empties what it walks raises nothing — every loop form (`for…of`, `for…in`, `forEach`, `map`, `filter`, `reduce`, `entries()`) on every built-in collection (`Array`, `Map`, `Set`, plain objects, `URLSearchParams`, `Headers`, `FormData`) runs to completion. Such a loop can still skip an element or never end, which is a different defect and not the one this check asks about. Not a gap in the analyzer and not a finding about your code.
- 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
- 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 — 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
- X5 Nullable reference types — 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
- 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)
Critical — 6 finding(s)
- <img> without a text alternative pages/huodong/index.vue:7
- <img> without a text alternative pages/huodong/index.vue:95
- Unlisted import 'config.js' app.js:2
- Unlisted import 'definitions' miniprogram_npm/@vant/weapp/common/component.d.ts:2
- Unlisted import 'libs' packageStreamMedia/components/TRTCCalling/TRTCCalling.js:4
- Unlisted import 'utils' app.js:3
Serious — 149 finding(s)
- Duplicated block (22 lines × 2 locations) packageFx/pages/hehuorenfenxiao/index.js:253
- Duplicated block (22 lines × 2 locations) packageFx/pages/hehuorenfenxiao/index.js:433
- Duplicated block (22 lines × 2 locations) packageStreamMedia/components/TRTCCalling/TRTCCalling.js:238
- Duplicated block (22 lines × 2 locations) pages/peisong/detail.js:149
- Duplicated block (22 lines × 2 locations) pages/to-pay-order/index.js:530
- Duplicated block (22 lines × 2 locations) utils/auth.js:75
- Swallowed exception (empty catch) pages/sign/index.js:101
- Swallowed exception (empty catch) pages/live/index.js:106
- Swallowed exception (empty catch) miniprogram_npm/@vant/weapp/sticky/index.js:84
- Swallowed exception (empty catch) miniprogram_npm/@vant/weapp/picker/index.js:34
- Swallowed exception (empty catch) miniprogram_npm/@vant/weapp/area/index.js:179
- Swallowed exception (empty catch) miniprogram_npm/@vant/weapp/area/index.js:181
- Dead file (~2 LoC) miniprogram_npm/@vant/weapp/definitions/index.js
- Dead file (~2 LoC) miniprogram_npm/@vant/weapp/dropdown-item/shared.js
- Dead file (~2 LoC) miniprogram_npm/@vant/weapp/field/types.js
- shouldUseFingerprintEmoji (cognitive 17) pages/live/index.js:84
- shouldUseFingerprintEmoji (cognitive 17) pages/sign/index.js:77
- Duplicated block (45 lines × 2 locations) packageFx/pages/report/city.js:14
- Duplicated block (45 lines × 2 locations) pages/goods-details/index.js:317
- Duplicated block with local edits (39 matched lines × 2 locations) pages/huodong/index.js:50
- Duplicated block with local edits (39 matched lines × 2 locations) pages/maidan/index.js:66
- Duplicated block (24 lines × 2 locations) packageFx/pages/hehuorenfenxiao/fxmember.js:59
- Duplicated block (24 lines × 2 locations) pages/recycle/orders.js:35
- Complex function shouldUseFingerprintEmoji (cyclomatic 15, cognitive 17) pages/live/index.js:84
- Complex function shouldUseFingerprintEmoji (cyclomatic 15, cognitive 17) pages/sign/index.js:77
- createOrder (cyclomatic 99) pages/to-pay-order/index.js:308
- address_parse.smatrAddress (cyclomatic 44) utils/address_parse.js:34
- bindSave (cyclomatic 23) pages/address-add/index.js:154
- getGoodsDetailAndKanjieInfo (cyclomatic 23) pages/goods-details/index.js:216
- loadPageData (cyclomatic 20) marketing/listing/detail.js:102
- submit (cyclomatic 19) marketing/listing/edit.js:235
- orderDetail (cyclomatic 19) pages/wuliu/index.js:14
- transition.transition (cyclomatic 17) miniprogram_npm/@vant/weapp/mixins/transition.js:13
- onShow (cyclomatic 16) app.js:93
- orderList (cyclomatic 16) pages/order-list/index.js:244
- rebuildDisplay (cyclomatic 16) pages/qingdan/index.js:228
- createOrder (cognitive 231) pages/to-pay-order/index.js:308
- address_parse.smatrAddress (cognitive 71) utils/address_parse.js:34
- getGoodsDetailAndKanjieInfo (cognitive 46) pages/goods-details/index.js:216
- onShow (cognitive 41) app.js:93
- _drawSingleText (cognitive 37) miniprogram_npm/wxa-plugin-canvas/index/index.js:178
- orderList (cognitive 30) pages/order-list/index.js:244
- orderDetail (cognitive 26) pages/wuliu/index.js:14
- submit (cognitive 25) marketing/listing/edit.js:235
- bindSave (cognitive 25) pages/address-add/index.js:154
- loadPageData (cognitive 24) marketing/listing/detail.js:102
- buyNow (cognitive 23) pages/goods-details/index.js:646
- processAfterCreateOrder (cognitive 23) pages/to-pay-order/index.js:726
- onClickDay (cognitive 23) miniprogram_npm/@vant/weapp/calendar/index.js:260
- calculateGoodsPrice (cognitive 21) components/goods-pop/index.js:210
- doneShow (cognitive 21) pages/to-pay-order/index.js:139
- getCommisionLog (cognitive 20) packageFx/pages/commisionLog/index.js:18
- fxMembers (cognitive 20) packageFx/pages/myusers/index.js:31
- drawBlock (cognitive 19) miniprogram_npm/wxa-plugin-canvas/index/index.js:6
- auth.login (cognitive 18) utils/auth.js:67
- addShopCar (cognitive 18) pages/goods-details/index.js:561
- submitReputation (cognitive 18) pages/order-details/index.js:141
- rebuyOrder (cognitive 18) pages/order-list/index.js:342
- utils.chooseFile (cognitive 17) miniprogram_npm/@vant/weapp/uploader/utils.js:57
- toPayTap (cognitive 17) pages/order-list/index.js:71
- getInitialDate (cognitive 17) miniprogram_npm/@vant/weapp/calendar/index.js:197
- transition.transition (cognitive 16) miniprogram_npm/@vant/weapp/mixins/transition.js:13
- orderDetail (cognitive 16) pages/order-details/index.js:60
- getUserApiInfo (cognitive 16) packageFx/pages/hehuorenfenxiao/index.js:173
- _initEventEmitter (cognitive 16) packageStreamMedia/components/TRTCCalling/TRTCCalling.js:66
- FileTooLong: to-pay-order/index.js pages/to-pay-order/index.js
- FunctionTooLong: address_parse.smatrAddress utils/address_parse.js:34
- Change-coupling hub: config.js → index.js, index.js, list.js, apply.js config.js
- No CI pipeline
- No structured logging
- Type Safety
- Duplication concentrated across 33 sibling directories (45 clone groups) pages/order-details/index.js:121
- Duplication concentrated across 7 sibling directories (29 clone groups) packageCps/pages/goods-details/cps-jd.js:6
- Duplication concentrated across 43 sibling directories (27 clone groups) miniprogram_npm/@vant/weapp/toast/toast.js:1
- Duplication concentrated across 5 sibling directories (7 clone groups) packageFx/pages/hehuorenfenxiao/index.js:5
- Wholesale file copy (415 identical lines × 3 files) packageCps/pages/goods-details/cps-jd.js:1
- Duplicated block with local edits (187 matched lines × 2 locations) packageFx/pages/hehuorenfenxiao/index.js:5
- Duplicated block with local edits (126 matched lines × 2 locations) packageStreamMedia/pages/live-anchor/index.js:352
- Duplicated block with local edits (121 matched lines × 2 locations) packageStreamMedia/pages/live-anchor/index.js:32
- Duplicated block (95 lines × 2 locations) pages/goods-details/index.js:455
- Duplicated block with local edits (89 matched lines × 2 locations) pages/goods/fav.js:50
- Duplicated block (52 lines × 2 locations) packageCps/pages/goods-details/cps-jd.js:6
- Duplicated block (50 lines × 2 locations) pages/pwd-pay/modify.js:3
- Duplicated block (46 lines × 2 locations) pages/recycle/index.js:66
- Duplicated block with local edits (44 matched lines × 2 locations) pages/order-details/index.js:121
- Duplicated block with local edits (37 matched lines × 2 locations) components/login/index.js:41
- Duplicated block (34 lines × 2 locations) packageFx/pages/hehuorenfenxiao/index.js:472
- Duplicated block (33 lines × 2 locations) components/bind-mobile/index.js:42
- Duplicated block (32 lines × 2 locations) pages/goods-details/day.js:43
- Duplicated block with local edits (31 matched lines × 2 locations) pages/address-add/index.js:155
- Duplicated block (31 lines × 2 locations) pages/goods/his.js:195
- Duplicated block (29 lines × 6 locations) components/goods-pop/index.js:181
- Duplicated block (28 lines × 2 locations) pages/asset/index.js:121
- Duplicated block (27 lines × 2 locations) pages/peisong/detail.js:276
- Duplicated block (25 lines × 2 locations) pages/goods-details/index.js:1203
- Duplicated block with local edits (25 matched lines × 2 locations) pages/goods-details/index.js:573
- Duplicated block with local edits (24 matched lines × 2 locations) miniprogram_npm/@vant/weapp/mixins/transition.js:67
- Duplicated block (23 lines × 2 locations) pages/card/logs.js:26
- Duplicated block with local edits (22 matched lines × 2 locations) pages/live/index.js:82
- Complex function createOrder (cyclomatic 88, cognitive 174) pages/to-pay-order/index.js:308
- Complex function bindSave (cyclomatic 23, cognitive 25) pages/address-add/index.js:154
- Complex function getGoodsDetailAndKanjieInfo (cyclomatic 22, cognitive 43) pages/goods-details/index.js:216
- Complex function smatrAddress (cyclomatic 21, cognitive 23) utils/address_parse.js:34
- Complex function loadPageData (cyclomatic 20, cognitive 24) marketing/listing/detail.js:102
- Complex function orderDetail (cyclomatic 19, cognitive 26) pages/wuliu/index.js:14
- Complex function submit (cyclomatic 16, cognitive 17) marketing/listing/edit.js:235
- Complex function onCellTap (cyclomatic 15, cognitive 14) game/numberBomb/index.js:99
- Complex function _drawSingleText (cyclomatic 14, cognitive 36) miniprogram_npm/wxa-plugin-canvas/index/index.js:178
- Complex function getInitialDate (cyclomatic 14, cognitive 17) miniprogram_npm/@vant/weapp/calendar/index.js:197
- Complex function updateValue (cyclomatic 14, cognitive 14) miniprogram_npm/@vant/weapp/slider/index.js:141
- Complex function addShopCar (cyclomatic 13, cognitive 13) pages/goods/fav.js:100
- Complex function submitForm (cyclomatic 13, cognitive 12) pages/qingdan/index.js:323
- Complex function orderList (cyclomatic 12, cognitive 17) pages/order-list/index.js:244
- Complex function processYunfei (cyclomatic 12, cognitive 14) pages/to-pay-order/index.js:844
- Complex function addShopCar (cyclomatic 12, cognitive 12) pages/goods/his.js:122
- Complex function getRangeDayType (cyclomatic 12, cognitive 11) miniprogram_npm/@vant/weapp/calendar/components/month/index.js:99
- Complex function drawBlock (cyclomatic 11, cognitive 19) miniprogram_npm/wxa-plugin-canvas/index/index.js:6
- Complex function (anonymous) (cyclomatic 11, cognitive 17) miniprogram_npm/@vant/weapp/uploader/utils.js:59
- Complex function (anonymous) (cyclomatic 11, cognitive 16) packageFx/pages/hehuorenfenxiao/index.js:175
- Complex function bindSave (cyclomatic 11, cognitive 13) pages/withdraw/index.js:38
- Complex function calculateGoodsPrice (cyclomatic 11, cognitive 12) components/goods-pop/index.js:210
- Complex function onLoad (cyclomatic 11, cognitive 12) pages/goods-details/vop.js:51
- Complex function loadDetail (cyclomatic 11, cognitive 11) marketing/listing/edit.js:53
- Complex function orderDetail (cyclomatic 11, cognitive 9) pages/order-details/index.js:60
- pages/to-pay-order/index.js: 1346 lines of code pages/to-pay-order/index.js:1
- pages/goods-details/index.js: 1217 lines of code pages/goods-details/index.js:1
- pages/goods-details/vop.js: 851 lines of code pages/goods-details/vop.js:1
- packageStreamMedia/components/TRTCCalling/TRTCCalling.js: 829 lines of code packageStreamMedia/components/TRTCCalling/TRTCCalling.js:1
- packageCps/pages/goods-details/cps-jd.js: 727 lines of code packageCps/pages/goods-details/cps-jd.js:1
- packageCps/pages/goods-details/cps-pdd.js: 683 lines of code packageCps/pages/goods-details/cps-pdd.js:1
- pages/huodong/index.vue: 680 lines of code pages/huodong/index.vue:1
- packageCps/pages/goods-details/cps-taobao.js: 675 lines of code packageCps/pages/goods-details/cps-taobao.js:1
- packageFx/pages/hehuorenfenxiao/index.js: 625 lines of code packageFx/pages/hehuorenfenxiao/index.js:1
- pages/index/index.js: 508 lines of code pages/index/index.js:1
- marketing/listing/detail.js: 505 lines of code marketing/listing/detail.js:1
- miniprogram_npm/wxa-plugin-canvas/index/index.js: 503 lines of code miniprogram_npm/wxa-plugin-canvas/index/index.js:1
- packageStreamMedia/pages/live-client/client.js: 479 lines of code packageStreamMedia/pages/live-client/client.js:1
- packageStreamMedia/pages/live-anchor/index.js: 469 lines of code packageStreamMedia/pages/live-anchor/index.js:1
- pages/qingdan/index.js: 450 lines of code pages/qingdan/index.js:1
- pages/address-add/index.js: 439 lines of code pages/address-add/index.js:1
- pages/order-list/index.js: 406 lines of code pages/order-list/index.js:1
- No test, lint or typecheck script
- Dead file (~255 LoC) pages/huodong/index.vue
- Dead file (~92 LoC) miniprogram_npm/@vant/weapp/dialog/dialog.js
- Dead file (~67 LoC) miniprogram_npm/@vant/weapp/notify/notify.js
- Dead file (~29 LoC) miniprogram_npm/wxa-plugin-canvas/poster/poster.js
- Dead file (~0 LoC) pages/template-cart/template-cart.js
- Unused dependency '@vant/weapp'
- JavaScript dependencies are not locked package.json:6
Minor — 33 finding(s)
- Duplicated predicate pages/category/category.js:273
- Duplicated predicate components/bind-mobile/index.js:66
- Duplicated predicate miniprogram_npm/@vant/weapp/nav-bar/index.js:56
- Duplicated predicate miniprogram_npm/@vant/weapp/common/relation.js:30
- Duplicated predicate packageFx/pages/hehuorenfenxiao/fxmember.js:74
- Duplicated predicate pages/goods/fav.js:189
- Duplicated predicate pages/goods/fav.js:134
- Duplicated predicate pages/live/index.js:98
- Duplicated predicate marketing/listing/edit.js:57
- Duplicated predicate marketing/listing/detail.js:185
- Duplicated predicate packageStreamMedia/pages/live-anchor/index.js:397
- Duplicated predicate packageFx/pages/hehuorenfenxiao/fxmember.js:77
- Duplicated predicate pages/maidan/index.js:68
- Duplicated predicate packageFx/pages/hehuorenfenxiao/fxmember.js:70
- Duplicated predicate pages/maidan/index.js:56
- Duplicated predicate packageCps/pages/goods-details/cps-jd.js:293
- Duplicated predicate pages/my/index.js:80
- Duplicated predicate packageCps/pages/goods-details/cps-jd.js:40
- Empty method body miniprogram_npm/@vant/weapp/notify/notify.js:25
- Empty method body miniprogram_npm/@vant/weapp/notify/notify.js:26
- Empty method body miniprogram_npm/@vant/weapp/notify/notify.js:27
- Blanket warning suppression miniprogram_npm/@vant/weapp/mixins/touch.js:4
- Blanket warning suppression miniprogram_npm/@vant/weapp/mixins/transition.js:4
- Documentation: no build, run or usage example README.md:1
- redundant comment packageStreamMedia/components/TRTCCalling/utils/environment.js:11
- No ADRs
- No architecture diagram/doc
- No src/ separation
- No SAST
- No dependency-update automation package.json:6
- No release approval gate
- No changelog
- Unused module-local declaration 'sliderWidth' packageFx/pages/index/index.js:6
Minor — 1 finding(s)
- Dependency hygiene PARTLY measured — npm pinning read, dependency currency not (no committed lockfile, so no resolved version to grade)
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-16566c95b7ae44339a4a68545bcfd964/history.json --exit-code 0 --source . | 0 | artifacts/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-16566c95b7ae44339a4a68545bcfd964/tree.json --exit-code 0 --source . | 0 | artifacts/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 . | 0 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | — |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 0 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 1 file(s) — `packageStreamMedia/components/TRTCCalling/utils/tsignaling-wx.js` — so the PII/GDPR sweep did not cover them at all. | 0 | — |
| D36 · Supply-chain Provenance & Signing | provenance | — | provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-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 Confinement | runtime-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 Enforcement | runtime-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 Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 0 | artifacts/raw/trivy-fs.json |