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

Jehuty-ML/prd_xiaozhi_server

Measured 17 November 2026, 07:09 UTC, at code version 5471afe

First survey, so nothing to compare with yet
CAI score 38.9out of 100 At risk

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

A large codebase: 166,358 lines of product code in 2 projects, tests not counted · Estimated rebuild effort: about 1.0 person-years · Weakest lens: Code Health, 33.0

Findings by how serious they are

211 critical 681 serious 268 minor

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

This survey was produced by

Assert small markCanine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
17 November 2026, 07:09 UTC

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

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

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

76of 76 dimensions measured by tools.
981of 1160 findings point to an exact file and line, so you can open each one in the code. The other 179 concern the repository as a whole, such as missing documentation.
76dimensions across 7 lenses, read from 166,358 lines of product code in 2 projects.
Chapters

Executive summary

Jehuty-ML/prd_xiaozhi_server is rated At risk because critical security findings are open, most of them in the packages it uses. It scores 38.9 out of 100, which the At risk rating leaves unchanged.

Code Health, at 33.0, is the weakest lens and counts most in the score. The best first step is fixing the password or key in the code, worth about 4.5 points. Splitting the oversized files would lift Code Health itself, worth about 2.9 points. Raising Code Health to 70 would lift the score to about 44.2.

Ninety-nine known security holes in the packages the code depends on can be used by attackers. Eleven pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with, and forty controls can't be used without a mouse. Updating the vulnerable packages, pinning each tool to an exact version and making the controls work with a keyboard would close these risks. Fixing the weaknesses the scanner points to would fix the seven security weaknesses in the code, and limiting each secret to its own step would deal with the three secrets exposed to more of the pipeline than needed. The 15 form fields without a label need a label.

The product code is 166,358 lines, about €150,000 to rebuild.

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

How the score is built: what each lens counts for The lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
Code Health 33.0 · counts for 46%Production Readiness 33.3 · counts for 25%Accessibility 42.8 · counts for 14%Security and Compliance 58.5 · counts for 8%Performance 60.0 · counts for 4%Maturity 72.1 · counts for 2%Architecture 74.1 · counts for 1%

If Code Health rose from 33.0 to 70, the lowest score rated Strong, the score would rise from 38.9 to about 44.2.

Code composition: what the lines of code are
Product code 96%Tests 4%
Rebuild cost: about €150,000 · Estimate
Cost to rebuild€49,000 to €250,000, for 814 to 2,581 hours of work, about 1.0 person-years for 1 to 2 engineers
Difficulty of the problemStandard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor×0.7 at a score of 39. 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.
SizeLarge: 166,358 lines of product code
What it is notNot a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.

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

Top priorities

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

1
Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED.
Raises the score by about 4.5 points · Low effort · REDACTED Scanning
2
Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
Raises the score by about 2.9 points · Medium effort · Large Files
3
Add a SAST step to CI running what this repository's stack ships: bandit, `semgrep --config=p/python`, or CodeQL's python pack — so a security regression fails the build instead of landing.
Raises the score by about 2.7 points · Medium effort · Security & performance tooling

Diagnosis: what the measurements show together

Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.

Where the investment is most exposed · Value at risk
This code would cost about €150,000 to build again, about 1.0 person-years of work. Its weakest lens is Code Health, at 33.0 (Weak). Code Health is about how easy the code is to read and change safely, and code that is hard to read is slow and risky to change, so every future change costs more than it should. Because the weakest lens counts most in the score, work on Code Health also moves the score most.
Based on: the rebuild estimate · the Code Health grade · how much each lens counts
What to do: Start with the Code Health actions in Top priorities.
If you do one thing first · First action
Resolve the 1 Leaked secret finding(s) in REDACTED Scanning. Of all the actions in this report, it raises the score most for the work it takes: about 4.5 points for low effort, because it clears the 1 REDACTED Scanning findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort

Architecture: which parts of the code depend on which

The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.

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

The table shows the 40 modules with the most connections; 273 more are left out to keep it readable.

Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
uses →1 main.xiaozhi-server.core.handle.textMessageType2 main.xiaozhi-server.core.providers.asr.base3 main.xiaozhi-server.core.providers.llm.base4 main.xiaozhi-server.core.providers.tts.base5 main.xiaozhi-server.plugins_func.register6 xiaozhi.common.page7 xiaozhi.modules.agent.dto8 xiaozhi.modules.model.entity9 main.xiaozhi-server.core.handle.textMessageHandler10 main.xiaozhi-server.core.providers.tools.base.tool_executor11 xiaozhi.common.service12 xiaozhi.modules.agent.entity13 xiaozhi.modules.correctword.service14 xiaozhi.modules.knowledge.rag15 xiaozhi.common.service.impl16 xiaozhi.modules.agent.vo17 xiaozhi.modules.device.service18 xiaozhi.modules.knowledge.service19 xiaozhi.modules.model.service20 xiaozhi.modules.security.service21 xiaozhi.modules.sys.service22 xiaozhi.modules.timbre.service23 xiaozhi.common.utils24 xiaozhi.modules.agent.dao25 xiaozhi.modules.agent.service26 xiaozhi.modules.voiceclone.service.impl27 xiaozhi.common.redis28 xiaozhi.modules.correctword.service.impl29 xiaozhi.modules.model.controller30 xiaozhi.modules.agent.controller31 xiaozhi.modules.agent.service.impl32 xiaozhi.modules.config.service.impl33 xiaozhi.modules.device.controller34 xiaozhi.modules.device.service.impl35 xiaozhi.modules.knowledge.service.impl36 xiaozhi.modules.model.service.impl37 xiaozhi.modules.security.service.impl38 xiaozhi.modules.sys.controller39 xiaozhi.modules.sys.service.impl40 xiaozhi.modules.timbre.service.impl
1 main.xiaozhi-server.core.handle.textMessageType
2 main.xiaozhi-server.core.providers.asr.base
3 main.xiaozhi-server.core.providers.llm.base
4 main.xiaozhi-server.core.providers.tts.base
5 main.xiaozhi-server.plugins_func.register
6 xiaozhi.common.page
7 xiaozhi.modules.agent.dto
8 xiaozhi.modules.model.entity
9 main.xiaozhi-server.core.handle.textMessageHandler1
10 main.xiaozhi-server.core.providers.tools.base.tool_executor1
11 xiaozhi.common.service1
12 xiaozhi.modules.agent.entity1
13 xiaozhi.modules.correctword.service1
14 xiaozhi.modules.knowledge.rag1
15 xiaozhi.common.service.impl22
16 xiaozhi.modules.agent.vo23
17 xiaozhi.modules.device.service22
18 xiaozhi.modules.knowledge.service211
19 xiaozhi.modules.model.service211
20 xiaozhi.modules.security.service111
21 xiaozhi.modules.sys.service44
22 xiaozhi.modules.timbre.service11
23 xiaozhi.common.utils11
24 xiaozhi.modules.agent.dao61
25 xiaozhi.modules.agent.service310354
26 xiaozhi.modules.voiceclone.service.impl1111
27 xiaozhi.common.redis1
28 xiaozhi.modules.correctword.service.impl1111
29 xiaozhi.modules.model.controller23121
30 xiaozhi.modules.agent.controller3124516142
31 xiaozhi.modules.agent.service.impl32019245215219291
32 xiaozhi.modules.config.service.impl111111151
33 xiaozhi.modules.device.controller15322
34 xiaozhi.modules.device.service.impl22832
35 xiaozhi.modules.knowledge.service.impl2122612
36 xiaozhi.modules.model.service.impl212311
37 xiaozhi.modules.security.service.impl113211
38 xiaozhi.modules.sys.controller42551
39 xiaozhi.modules.sys.service.impl451822
40 xiaozhi.modules.timbre.service.impl1111
Uses a module listed above itPart of a loopThe module itself
1 main.xiaozhi-server.core.handle.textMessageType2 main.xiaozhi-server.core.providers.asr.base3 main.xiaozhi-server.core.providers.llm.base4 main.xiaozhi-server.core.providers.tts.base5 main.xiaozhi-server.plugins_func.register6 xiaozhi.common.page7 xiaozhi.modules.agent.dto8 xiaozhi.modules.model.entity9 main.xiaozhi-server.core.handle.textMessageHandler10 main.xiaozhi-server.core.providers.tools.base.tool_executor11 xiaozhi.common.service12 xiaozhi.modules.agent.entity13 xiaozhi.modules.correctword.service14 xiaozhi.modules.knowledge.rag15 xiaozhi.common.service.impl16 xiaozhi.modules.agent.vo17 xiaozhi.modules.device.service18 xiaozhi.modules.knowledge.service19 xiaozhi.modules.model.service20 xiaozhi.modules.security.service21 xiaozhi.modules.sys.service22 xiaozhi.modules.timbre.service23 xiaozhi.common.utils24 xiaozhi.modules.agent.dao25 xiaozhi.modules.agent.service26 xiaozhi.modules.voiceclone.service.impl27 xiaozhi.common.redis28 xiaozhi.modules.correctword.service.impl29 xiaozhi.modules.model.controller30 xiaozhi.modules.agent.controller31 xiaozhi.modules.agent.service.impl32 xiaozhi.modules.config.service.impl33 xiaozhi.modules.device.controller34 xiaozhi.modules.device.service.impl35 xiaozhi.modules.knowledge.service.impl36 xiaozhi.modules.model.service.impl37 xiaozhi.modules.security.service.impl38 xiaozhi.modules.sys.controller39 xiaozhi.modules.sys.service.impl40 xiaozhi.modules.timbre.service.implmain.xiaozhi-server.core.handle.textMessageType1main.xiaozhi-server.core.providers.asr.base2main.xiaozhi-server.core.providers.llm.base3main.xiaozhi-server.core.providers.tts.base4main.xiaozhi-server.plugins_func.register5xiaozhi.common.page6xiaozhi.modules.agent.dto7xiaozhi.modules.model.entity8main.xiaozhi-server.core.handle.textMessageHandler9main.xiaozhi-server.core.providers.tools.base.tool_executor10xiaozhi.common.service11xiaozhi.modules.agent.entity12xiaozhi.modules.correctword.service13xiaozhi.modules.knowledge.rag14xiaozhi.common.service.impl15xiaozhi.modules.agent.vo16xiaozhi.modules.device.service17xiaozhi.modules.knowledge.service18xiaozhi.modules.model.service19xiaozhi.modules.security.service20xiaozhi.modules.sys.service21xiaozhi.modules.timbre.service22xiaozhi.common.utils23xiaozhi.modules.agent.dao24xiaozhi.modules.agent.service25xiaozhi.modules.voiceclone.service.impl26xiaozhi.common.redis27xiaozhi.modules.correctword.service.impl28xiaozhi.modules.model.controller29xiaozhi.modules.agent.controller30xiaozhi.modules.agent.service.impl31xiaozhi.modules.config.service.impl32xiaozhi.modules.device.controller33xiaozhi.modules.device.service.impl34xiaozhi.modules.knowledge.service.impl35xiaozhi.modules.model.service.impl36xiaozhi.modules.security.service.impl37xiaozhi.modules.sys.controller38xiaozhi.modules.sys.service.impl39xiaozhi.modules.timbre.service.impl40111111222322211211111441111613103541111111112312131245161423201924521521929111111115115322228322122612212311113211425514518221111+273 more modules (most-connected shown)

At a glance — Code Health · 33.0 · Weak · gated by R1, R3, X5 ·

At a glance — Architecture · 74.1 · Strong ·

At a glance — Maturity · 72.1 · Adequate · gated by M2 ·

At a glance — Readiness · 33.3 · Weak · gated by R8, P3, P7 ·

At a glance — Security · 58.5 · Adequate · gated by D28, D29, D36 ·

At a glance — Accessibility · 42.8 · Weak · gated by AC4 ·

At a glance — Performance · 60.0 · Adequate ·

Security & Compliance — OWASP Top-10 mapping

Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).

OWASP categoryFindingsSeverity
A03:2025 — Software Supply Chain Failures157High / Critical
A05:2025 — Injection55High / Critical
A02:2025 — Security Misconfiguration15High / Critical
A07:2025 — Authentication Failures11High / Critical

Roadmap

Top priorities: Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED; Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package; Add a SAST step to CI running what this repository's stack ships: bandit, `semgrep --config=p/python`, or CodeQL's python pack — so a security regression fails the build instead of landing.

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

Do thisHelpsEffortDimension
Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED.+4.5 ptsLowREDACTED Scanning
Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.+2.9 ptsMediumLarge Files
Add a SAST step to CI running what this repository's stack ships: bandit, `semgrep --config=p/python`, or CodeQL's python pack — so a security regression fails the build instead of landing.+2.7 ptsMediumSecurity & performance tooling
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.+2.7 ptsMediumDependency Hygiene
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.+2.4 ptsMediumKeyboard semantics
The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`).+1.8 ptsMediumNullable reference types
Set connect and read timeouts on every client (`RestTemplateBuilder.connectTimeout/readTimeout`, WebClient `responseTimeout`, `HttpRequest.Builder.timeout`, `HttpURLConnection.setReadTimeout`, Feign `connectTimeout`/`readTimeout` in configuration), and wrap calls to dependencies in resilience4j `@Retry`/`@CircuitBreaker`/`@TimeLimiter` (or Spring Retry).+1.5 ptsMediumOutbound HTTP resilience
Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.+1.0 ptsMediumForms & labels

File quality

Per-file score 0–10 — a quality signature. Of 122 files carrying findings, judged against the Production bar: 7% slop · 58% mixed · 35% near-clean.

FileScoreBandWorst signal
REDACTED0.0SlopDependency Vulnerabilities: Critical CVE: REDACTED
REDACTED0.0SlopDependency Vulnerabilities: Critical CVE: REDACTED
REDACTED0.0SlopDependency Vulnerabilities: Critical CVE: REDACTED
REDACTED2.0SlopREDACTED Scanning: Leaked secret: REDACTED
REDACTED2.3SlopStatic Analysis (SAST): High: REDACTED
REDACTED2.5SlopDependency Vulnerabilities: Critical CVE: REDACTED
REDACTED2.8SlopIaC & Container Security: High IaC: REDACTED
REDACTED3.1SlopStatic Analysis (SAST): High: REDACTED
REDACTED3.7SlopStatic Analysis (SAST): High: REDACTED
REDACTED4.0MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED4.1MixedIaC & Container Security: High IaC: REDACTED
REDACTED4.2MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED4.6MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED4.6MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.1MixedSecrets (history): REDACTED: REDACTED
REDACTED5.1MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.1MixedIaC & Container Security: High IaC: REDACTED
main/xiaozhi-server/core/connection.py5.5MixedCode Duplication: Duplicated block (18–19 lines × 2)
REDACTED5.7MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED5.7MixedStatic Analysis (SAST): Medium: REDACTED

How the grades work

Every finding carries one of four grades. Three say how serious it is. The fourth says this survey could not settle it — and it is a grade, not a gap.

Critical — 211

A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.

Serious — 681

Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.

Minor — 268

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

Could not be resolved — 18

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 76 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.

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

What we checked — 76 dimensions across the health lenses
D4D5D6D10D12D13D14D15D16D17D19D20D21D24D28D29D30D31D34D35D36D43D44AC1AC2AC3AC4AC5AX1AX10AX2AX3AX4AX6M1M2M3M4P1P2P3P4P6P7P8PF3R1R10R11R2R3R4R5R6R7R8R9S1X1X12X13X14X16X17X18X19X2X21X23X24X25X28X29X3X4X5

Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.

How to trust any code-health report — three questions
  1. Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 981 of 1160 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
  2. Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
  3. Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.

This report answers yes to all three. That's the bar to hold any assessment to.

Tools & methods

The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.

MethodBacksVersionEvaluator
Roslyn static analysisComplexity, cohesion, coupling, dead code, API surface, layering5.3.0✓ deterministic
Native secret scannerHardcoded secrets / credentials1.0.0✓ deterministic
Canine Code Analyzer duplication detector (in-process)Code duplication1.0.0✓ deterministic
Coverage (coverlet / dotnet-coverage)Line & branch coverage10.0.400✓ deterministic
NuGet / dotnetOutdated, vulnerable & deprecated dependencies10.0.400✓ deterministic
git / LibGit2SharpChurn hotspots, knowledge concentration, history2.43.0 · 0.31.0✓ deterministic
gitleaks · semgrep · trivy · checkovSecrets in history, SAST, CVEs, IaC & container, PII / GDPR1.86.0 · 0.69.3 · 3.2.533✓ deterministic

Every finding is locatable in findings.md. Run 01a1e856-b0e6-75c3-a87f-8d2858abaef5.

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

Run transparency — what happened this run

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

  • D1 Cyclomatic Complexity — 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. Most of this repository's production source (.js, .vue) had no cyclomatic complexity computed for it: no method bodies were exposed for those file kinds by any language model this pass could load.
  • D2 Cognitive Complexity — 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. Most of this repository's production source (.js, .vue) had no cognitive complexity computed for it: no method bodies were exposed for those file kinds by any language model this pass could load.
  • 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 JavaScript/TypeScript half could not be measured — the dependency install for main/manager-web/ was timed out after 2624.4s, so the suite never ran. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo.
  • D10 Test Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 41 test(s) behind this row are the ones the JavaScript/TypeScript census could read, and this repository also carries at least 32 test source file(s) (.py, .java) that it cannot: it reads JavaScript/TypeScript test declarations off disk, so a JUnit/pytest-style suite is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
  • D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability NOT MEASURED: the JavaScript/TypeScript suite could not be re-run in the analyzer sandbox — the dependency install for main/manager-web/ was timed out after 2624.4s, so the suite never ran. This is OUR limitation, not a defect in the repo — it is excluded from the score.
  • D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the its own test command under node's V8 coverage suite in main/manager-web/ was NOT MEASURED: the dependency install for main/manager-web/ was timed out after 2624.4s, so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
  • D12 Dependency Hygiene — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Currency was graded against Maven Central, but whether an artifact is DEPRECATED is not: Maven Central publishes no deprecation marker, exactly as rubygems.org does not. Whether one is UNMAINTAINED is not graded either — no registry publishes a maintenance status, and release age does not stand in for one. Two of this dimension's four signals are therefore unread on a Maven tree, and its score reflects currency alone.
  • D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
  • D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
  • D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. D21's naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
  • D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
  • D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
  • D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is a COLLECTOR gap, not an environment fault: no published-package marker D22 reads admitted any project here, so this ecosystem's public API has no collector, and the remedy is to write one — no change to the scan image can close it.
  • D24 Comment Value — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. D24 compares a comment's words with the identifiers, literals and constructs of the code it annotates, using English function-word and rationale lexicons. Comments in another script or language were left unread rather than counted as clean.
  • D24 Comment Value — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
  • 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. Project size and spread are measured over build units (a .NET project, a Maven or Gradle module, an npm, Deno or JSR package, a Go module, a Cargo crate, a Python, Composer, Bundler, RubyGems, Mix, rebar3, sbt, SwiftPM or pub package, an OTP application, an Xcode project or XcodeGen spec, or a checkout that declares no build at all) whose source a code model reads. This repository's production source is in a language no model reads, or in units whose build tool D26 does not recognise. That is a gap in this analyzer's language reach — not a finding that the repository's projects are cohesive.
  • D27 Navigability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
  • D28 Secrets (history) — 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. D28's config-credential rule (WD-SECRET-0002) parses each committed `.json` config as a document and reads credential-named values; `main/digital-human/resources/natori_pro_zh/runtime/exp/Angry.exp3.json`, `main/digital-human/resources/natori_pro_zh/runtime/exp/Blushing.exp3.json`, `main/digital-human/resources/natori_pro_zh/runtime/exp/Normal.exp3.json`, `main/digital-human/resources/natori_pro_zh/runtime/exp/Sad.exp3.json`, `main/digital-human/resources/natori_pro_zh/runtime/exp/Smile.exp3.json` and 13 more did not parse (JSON5, a template, several concatenated documents), so a credential bound there is UNMEASURED by that rule. gitleaks still scanned the same files as text.
  • 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. `main/digital-human/js/utils/libopus.js`, `main/manager-web/public/generator/assets/index-Guo1hQ-y.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.
  • AC4 Keyboard semantics — 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. 20 further occurrence(s) are not listed individually; the score already reflects all 60.
  • AC6 Visual & motion safety — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Visual & motion safety could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository. Engine failure: ArgumentOutOfRangeException: Specified argument was out of the range of valid values. (Parameter 'length').
  • AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DockerCompose (main/xiaozhi-server/docker-compose.prod.yml). compose up failed (exit 15 — the compose project is invalid) — service "xiaozhi-esp32-server" has neither an image nor a build context specified: invalid compose project; runtime evidence skipped.
  • C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
  • C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
  • C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
  • C4 Data Retention — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
  • C5 Data-Subject Rights — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
  • GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java source only, and this repository's Python, Vue components, lua is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby, Scala and Rust source only, and this repository's Python, Vue components, lua is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
  • 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. 99 further occurrence(s) are not listed individually; the score already reflects all 139.
  • R2 Cyclomatic Complexity — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 13 further occurrence(s) are not listed individually; the score already reflects all 53.
  • R3 Large Files — 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. 6 further occurrence(s) are not listed individually; the score already reflects all 46.
  • R4 Test Coverage — 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. 22 further occurrence(s) are not listed individually; the score already reflects all 62.
  • R7 Dead Code — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 19 further occurrence(s) are not listed individually; the score already reflects all 59.
  • X1 Async correctness — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
  • X12 Unreachable branch — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
  • X16 Unfloored truncation loop — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
  • X17 Uncapped recursion over a caller-supplied document — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
  • X18 Disposal-pattern correctness — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
  • X27 Collection changed while being enumerated — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • X29 Per-element action decided by a fixed element — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
  • X3 Exception handling — 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. 103 further occurrence(s) are not listed individually; the score already reflects all 143.

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

Limitations & what we did not check

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

Per-dimension blind spots

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

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

Dimensions

D4 · Code Duplication8.7 / 10Strong✓ Tool-verified

What it measures: How much of the production code is copy-pasted: the share of production lines inside a reported copy (every copy of a duplicated block or of an edited member, each line once), 10 at none and 0 at a quarter of the lines.

Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), scored on the share of production lines inside a reported copy (each line once; 10 at none, 0 at a quarter). Deterministic.

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

134 duplicated block group(s) detected. 3.1 % of the production lines (5,219 of 166,358) are in a reported copy. A further 72 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. Measured on part of this repository only: .js, .vue (61% of production source) was not exposed to THIS dimension's token comparison and is not in this count; duplication there is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream.

Duplicated block (7 lines × 2) · ×8main/xiaozhi-server/core/websocket_server.py:83
Edited copy of a member (10 corresponding lines) · ×6main/xiaozhi-server/plugins_func/functions/hass_get_state.py:34
Duplicated block (12 lines × 2) · ×6main/xiaozhi-server/core/utils/resilience.py:899
Duplicated block (8 lines × 2) · ×6main/xiaozhi-server/core/handle/reportHandle.py:110
Members sharing a duplicated core (4 members, 50+ identical tokens) · ×5REDACTED:37

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

What to do

  1. Resolve the 8 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with websocket_server.py, doubao_stream.py, fun_local.py. — One of this dimension's main actionable groups (8 warning-level).
  2. Resolve the 6 Edited copy of a member (10 corresponding lines) finding(s) in Code Duplication — start with hass_get_state.py, AgentController.java, hass_play_music.py. — One of this dimension's main actionable groups (6 warning-level).
  3. Resolve the 6 Duplicated block (12 lines × 2) finding(s) in Code Duplication — start with resilience.py (2), util.py, doubao_stream.py. — One of this dimension's main actionable groups (6 warning-level).

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

D5 · Coupling10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

2 production modules (Maven+npm), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 0 module(s) off the main sequence, with abstractness counted on 1 of the 2 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).

✓ On the Gold path — maintain.

Detailed fixes: d5_recommendation.md.

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

What it measures: Whether a class's methods are focused on a single responsibility.

Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.

Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.

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

1 of 95 classes have LCOM4 above 3.

Low cohesion: TTSProviderBase (LCOM4 4)main/xiaozhi-server/core/providers/tts/base.py:39

What to do

  1. Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with base.py. — One of this dimension's main actionable groups (1 warning-level).

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

D10 · Test Quality10.0 / 10Exemplary✓ Tool-verified

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

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

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

0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 41 tests. Measured on the JavaScript/TypeScript suite only — at least 32 test source file(s) (.py, .java) went unread, so its test quality is unmeasured and is not in these counts.

✓ On the Gold path — maintain.

Detailed fixes: d10_recommendation.md.

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

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

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

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

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

Outdated (compile): com.alibaba:druid-spring-boot-3-starter · ×2
Outdated (compile -- module org.apache.shiro.core [auto]): org.apache.shiro:shiro-core
Outdated (compile -- module org.apache.shiro.lang [auto]): org.apache.shiro:shiro-lang
Outdated (compile -- module org.apache.shiro.cache [auto]): org.apache.shiro:shiro-cache
Outdated (compile -- module org.apache.shiro.crypto.hash [auto]): org.apache.shiro:shiro-crypto-hash

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

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

D13 · REDACTED Scanning5.0 / 10Adequate✓ Tool-verified

What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.

Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.

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

1 secret(s) detected. 1 detection(s) were excluded as holding no minted credential in material that runs: a name, reference or comparison rather than a value, a readable phrase or pattern, a value that declares itself fake, or development, test, example, mock or demo material.

REDACTED

What to do

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

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

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

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

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

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

0 of 23 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 1 Maven/Gradle manifest(s) declare with a version resolvable from the manifest itself — the same declaration-site closure this analysis reads for dependency currency. The JVM has no lockfile a checkout is guaranteed to carry, so this is deliberately NOT the transitive closure. 12 further coordinate(s) are declared with no version at the declaration site — inherited from a parent POM, a BOM or an unresolved Gradle version reference — and are NOT graded: this verdict covers what the checkout pins, not the full transitive graph.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

D15 · Churn × Complexity Hotspots9.3 / 10Stronggated by 20 serious findings✓ Tool-verified

What it measures: Files that change often and are also complex — the riskiest hotspots.

Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.

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

Top hotspots: main/xiaozhi-server/core/connection.py (20×86=1720); main/manager-api/src/main/java/xiaozhi/modules/agent/service/impl/AgentServiceImpl.java (9×41=369); main/xiaozhi-server/config/config_loader.py (9×33=297) Repeated repair below the complexity floor: main/manager-api/src/main/java/xiaozhi/modules/device/vo/UserShowDeviceListVO.java (5 of 5 changes were fixes); main/manager-api/src/main/java/xiaozhi/modules/agent/controller/AgentController.java (3 of 5 changes were fixes); main/manager-api/src/main/java/xiaozhi/modules/agent/service/impl/AgentChatHistoryServiceImpl.java (3 of 5 changes were fixes)

Hotspot: main/xiaozhi-server/core/connection.py · ×16main/xiaozhi-server/core/connection.py:1389
Repeated repair: main/manager-api/src/main/java/xiaozhi/modules/device/vo/UserShowDeviceListVO.java · ×4main/manager-api/src/main/java/xiaozhi/modules/device/vo/UserShowDeviceListVO.java:12

What to do

  1. Resolve the 16 Hotspot finding(s) in Churn × Complexity Hotspots — start with base.py (2), connection.py, AgentServiceImpl.java. — One of this dimension's main actionable groups (16 warning-level).
  2. Resolve the 4 Repeated repair finding(s) in Churn × Complexity Hotspots — start with UserShowDeviceListVO.java, AgentController.java, AgentChatHistoryServiceImpl.java. — One of this dimension's main actionable groups (4 warning-level).

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

D16 · Bus Factor9.2 / 10Exemplary✓ Tool-verified

What it measures: Whether knowledge is concentrated in too few people (the "bus factor").

Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.

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

18 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is main/xiaozhi-server/core/utils/resilience.py. Counted over 229 of the 521 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Off-boarding risk: anonymized user #1
Further sole-owners (lower concentration)

✓ On the Gold path — maintain.

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

D17 · Explicit Debt10.0 / 10Stronggated by 3 serious findings✓ Tool-verified

What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.

Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.

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

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

TodoComment · ×3main/xiaozhi-server/core/providers/tools/server_mcp/mcp_client.py:196

What to do

  1. Resolve the 3 TodoComment finding(s) in Explicit Debt — start with mcp_client.py, interceptor.ts, tabbarList.ts. — One of this dimension's main actionable groups (3 warning-level).

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

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d19_recommendation.md.

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

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

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

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

No architecture decision records were found.

No ADRs foundREDACTED:274

What to do

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

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

D21 · Naming Consistency9.0 / 10Strong✓ Tool-verified

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

Method: Seven vocabulary-free rules (N1-N7) mine each naming convention from the repository and flag a name that breaks a convention its structural peers in the same unit follow; production C# and TypeScript, each its own population. Deterministic, no model, no sample. Advisory.

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

1 naming inconsistencies among 97 declarations measured against a convention their peers follow.

`currentDtoClass` spells `Dto` where 106 names in the project spell it `DTO`main/manager-api/src/main/java/xiaozhi/common/service/impl/CrudServiceImpl.java:28

What to do

  1. Resolve the 1 `currentDtoClass` spells `Dto` where 106 names in the project spell it… finding(s) in Naming Consistency — start with CrudServiceImpl.java. — One of this dimension's main actionable groups (1 recommendation-level).

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

D24 · Comment Value0.8 0.2 / 10Critical✓ Tool-verified

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

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

Maturity: Documented → Verified → Prevented · effective 0.2 / 10 · rule-coverage 26% · ceiling Documented

10 of 109 judged comments only repeat the code they sit on (9.2 %). 1092 comment(s) in another language or script were not judged.

redundant comment · ×4main/digital-human/js/core/audio/recorder.js:90
doc comments repeat the namesmain/manager-web/src/utils/index.js:22

What to do

  1. Resolve the 4 redundant comment finding(s) in Comment Value — start with recorder.js (3), controller.js. — One of this dimension's main actionable groups (4 recommendation-level).

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

D28 · Secrets (history)3.0 / 10Weak✓ Tool-verified

What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.

Method: REDACTED scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.

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

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

REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 7 REDACTED finding(s) in Secrets (history) — start with REDACTED (7). — One of this dimension's main actionable groups (7 issue-level).
  2. Resolve the 2 REDACTED finding(s) in Secrets (history) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 recommendation-level).
  3. Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).

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

D29 · Static Analysis (SAST)0.3 / 10Critical✓ Tool-verified

What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.

Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.

Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).

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

55 finding(s): 0 critical, 23 high, 27 medium, 5 low. 11 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 3 file(s) — `main/digital-human/js/utils/libopus.js`, `main/manager-web/public/generator/assets/index-Guo1hQ-y.js`, `main/manager-web/public/index.html` (line 12, lines 14–15, lines 17–18, …) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

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

What to do

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

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

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

What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.

Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.

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

150 finding(s): 19 critical, 80 high, 41 medium, 10 low.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

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

What to do

  1. Resolve the 77 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (34), REDACTED (27), REDACTED (13). — One of this dimension's main actionable groups (77 issue-level).
  2. Resolve the 19 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (6), REDACTED (6), REDACTED (4). — One of this dimension's main actionable groups (19 issue-level).
  3. Resolve the 3 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 issue-level).

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

D31 · IaC & Container Security7.9 / 10Adequategated by 3 critical findings✓ Tool-verified

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

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

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

15 finding(s): 0 critical, 3 high, 11 medium, 1 low.

REDACTED
REDACTED
REDACTED

What to do

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

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

D34 · Knowledge Freshness9.4 / 10Exemplary✓ Tool-verified

What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.

Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.

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

14 of 229 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is main/manager-api/src/main/java/xiaozhi/modules/agent/service/impl/AgentVoicePrintServiceImpl.java. Counted over 229 of the 521 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned file · ×14main/manager-api/src/main/java/xiaozhi/modules/agent/service/impl/AgentVoicePrintServiceImpl.java:1
Orphaned files with no living knowledge

✓ On the Gold path — maintain.

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

D35 · Change Coupling9.8 / 10Stronggated by 9 serious findings✓ Tool-verified

What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.

Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.

Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.

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

Strongest change-coupling: Constant.java↔index.vue 67%; Constant.java↔logger.py 59%; intentHandler.py↔REDACTED 58%

Change coupling: Constant.java ↔ index.vue · ×9main/manager-api/src/main/java/xiaozhi/common/constant/Constant.java:1

What to do

  1. Resolve the 9 Change coupling finding(s) in Change Coupling — start with Constant.java (2), connection.py (2), intentHandler.py. — One of this dimension's main actionable groups (9 warning-level).

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

D36 · Supply-chain Provenance & Signing0.0 / 10Critical✓ Tool-verified

What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.

Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.

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

0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

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

What to do

  1. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
  2. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
  3. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).

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

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

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

What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.

Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.

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

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

✓ On the Gold path — maintain.

Detailed fixes: d44_recommendation.md.

Frontend & cross-cutting dimensions

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

AC1 · Text alternatives5.3 / 10Adequate✓ Tool-verified

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

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

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

  • A <canvas> with no aria-label/title and no inner fallback content can't be described by assistive tech. Add a name or fallback content. (×2) — main/digital-human/index.html:82, main/manager-web/src/components/VoiceCloneDialog.vue:51
  • An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative. (×7) — main/manager-mobile/src/components/custom-tabs/index.vue:45, main/manager-mobile/src/pages/forgot-password/index.vue:358, main/manager-mobile/src/pages/login/index.vue:375, …

What to do

  • Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
AC2 · Forms & labels4.9 / 10Weak✓ Tool-verified

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

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

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

  • This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id. — main/digital-human/index.html:298
  • This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label. (×10) — main/digital-human/js/ui/controller.js:844, main/digital-human/js/ui/controller.js:845, main/manager-mobile/src/pages/agent/edit.vue:1296, …
  • This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×5) — main/manager-mobile/src/pages/agent/tools.vue:421, main/manager-web/src/components/AudioPlayer.vue:63, main/manager-web/src/views/AddressBookManagement.vue:73, …
  • A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one). (×2) — main/manager-web/src/components/AudioPlayer.vue:13, main/manager-web/src/components/AudioPlayer.vue:44
  • This <div> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label. (×4) — main/manager-web/src/components/AudioPlayer.vue:29, main/manager-web/src/components/TtsModel.vue:87, main/manager-web/src/views/KnowledgeBaseManagement.vue:29, …
  • This <i> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label. (×4) — main/manager-web/src/components/ChatHistoryDialog.vue:65, main/manager-web/src/views/AddressBookManagement.vue:85, main/manager-web/src/views/AddressBookManagement.vue:115, …
  • This <img> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label. — main/manager-web/src/components/HeaderBar.vue:159

What to do

  • Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
AC3 · Page structure5.4 / 10Adequate✓ Tool-verified

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

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

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

  • No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. (×6) — main/digital-human/index.html:2, main/manager-web/public/offline.html:2, main/manager-web/public/privacy-policy-en.html:2, …
  • The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). (×2) — main/manager-mobile/index.html:2, main/manager-web/public/index.html:2
  • No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="app">, so there is no content here to wrap — render the <main> from the component mounted into it. (×3) — main/manager-mobile/index.html:2, main/manager-web/public/generator/index.html:2, main/manager-web/public/index.html:2
  • Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one. (×3) — main/manager-web/src/views/AddressBookManagement.vue:140, main/manager-web/src/views/DictManagement.vue:20, main/manager-web/src/views/KnowledgeBaseManagement.vue:170

What to do

  • Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC4 · Keyboard semantics1.0 / 10Critical✓ Tool-verified

Other · Accessibility — Whether interactive behaviour is keyboard-reachable — no click handler on a non-interactive element lacking a role, tabindex and key handler, no element the repo's own CSS styles `cursor: pointer` without giving it any of the three, no unfocusable element whose only binding is a mouse enter/leave pair or a double-click, no positive tabindex, no href-less anchor, no placeholder-href (#/javascript) link acting as a button. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: click handlers on non-interactive elements lacking role+tabindex+key handler, positive tabindex values, and href-less anchors. Components skipped, spreads suppressed. Deterministic, hard fact per element.

Coverage: Population: elements that pose a keyboard-semantics question, in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) — a non-natively-interactive element carrying a click handler, a double-click or hover enter/leave binding, a pointer-only gesture on a tabindex="0" element, or `cursor: pointer` from the repo's own CSS; an href-less or placeholder-href (#, javascript:) anchor; and any element with a positive tabindex. Natively interactive elements used correctly (<button>, <a href>, form controls) are NOT in the population — there is nothing to judge — so a page of nothing but correct controls gives AC4 nothing to measure. Keyboard reachability is judged from the markup, never from a rendered page. ★ An interactive element declared in a tagged-template (html`…`) or hyperscript frontend is NOT in this population — no producer reads either — so an empty population is reported as an analyzer gap, never as "this repository has no interactive elements".

  • A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler. (×39) — main/digital-human/js/core/mcp/tools.js:120, main/manager-mobile/src/pages/login/index.vue:388, main/manager-mobile/src/pages/login/index.vue:394, …
  • This <div> binds mouse-enter and mouse-leave and nothing else — no click, no key handler, no focus handler, and no tabindex="0", so it cannot even take focus. A keyboard user cannot hover, so whatever the pair reveals or highlights is reachable with a mouse only. Bind the same state to focus/blur as well, and add tabindex="0"="0" so the element can receive that focus. — main/manager-web/src/components/AudioPlayer.vue:55

What to do

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

Other · Accessibility — Whether ARIA is used correctly — valid non-abstract roles, the ARIA state a role requires, valid (non-misspelled) aria-* attribute names, in-enum values for token-typed aria-* attributes, and no aria-hidden on (or wrapping) a focusable element. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: role values checked against the WAI-ARIA role set (abstract/invalid flagged), required ARIA state for a role, and aria-hidden on a focusable element. Deterministic, role/attribute level.

Coverage: Population: elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) that carry a role or an aria-* attribute; roles and token values are checked against the ARIA enums exhaustively within that set. An expression-valued (dynamic) role or aria-* value is skipped rather than guessed, and markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

AX1 · Captive dependencies10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

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

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

AX2 · Stateful singletons10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether singleton services avoid mutable shared instance state that concurrent callers would race on.

Method: Roslyn scan: singleton field mutations unguarded by lock or Interlocked, per type; syntax-based guard detection. Deterministic, traceable per field.

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

Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).

Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.

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

Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.

Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.

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

Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').

Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.

  • `AgentService` declares 16 abstract methods under just 13 distinct name(s): `adminAgentList`, `checkAgentPermission`, `createAgent`, `deleteAgent`, `deleteAgentById`, `deleteAgentByUserId`, `getAgentById`, `getAgentById`, `getDefaultAgentByMacAddress`, `getDeviceCountByAgentId`, `getUserAgents`, `insert`, `updateAgentById`, `updateAgentById`, `updateAgentById`, `updateAgentMemoryByDeviceMacAddress`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. That is an OVERLOAD SET, not 16 separate responsibilities: a caller binds to 13 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 16 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface. — main/manager-api/src/main/java/xiaozhi/modules/agent/service/AgentService.java:22
  • `DeviceService` declares 19 abstract methods: `callDeviceTool`, `checkDeviceActive`, `deleteByAgentId`, `deleteByUserId`, `deviceActivation`, `geCodeByDeviceId`, `generateWebSocketToken`, `getDeviceByMacAddress`, `getDeviceOnlineData`, `getDeviceTools`, `getLatestLastConnectionTime`, `getUserDeviceList`, `getUserDevices`, `manualAddDevice`, `page`, `searchDevicesByMacAddress`, `selectCountByUserId`, `unbindDevice`, `updateDeviceConnectionInfo`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — main/manager-api/src/main/java/xiaozhi/modules/device/service/DeviceService.java:16

What to do

  • Split fat interfaces into focused role-interfaces so clients depend only on what they use.
  • Where the width is an overload set rather than separate responsibilities, collapse the overloads instead — segregating those relieves no caller.
M1 · Documentation (README)10.0 / 10Exemplary✓ Tool-verified

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

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

M2 · Architecture documentation2.0 / 10Critical✓ Tool-verified

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

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

  • No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.

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.
M3 · Folder & project structure10.0 / 10Exemplary✓ Tool-verified

Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.

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

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

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

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

P1 · CI/CD gates10.0 / 10Exemplary○ Nothing flagged

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

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

P2 · Observability9.2 / 10Exemplary✓ Tool-verified

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

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

  • Only 3/4 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `.`.

What to do

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

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

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

  • No static application security testing detected. For this repository's stack, add bandit, `semgrep --config=p/python`, or CodeQL's python pack as a CI step. What was searched, so you can tell an absence from a miss: the 3 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:9
  • `REDACTED` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — REDACTED:78

What to do

  • Add a SAST step to CI running what this repository's stack ships: bandit, `semgrep --config=p/python`, or CodeQL's python pack — so a security regression fails the build instead of landing.
  • Enable Dependabot/Renovate or a dependency-review gate.
  • Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback8.0 / 10Strong✓ Tool-verified

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

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

What to do

  • Add an approval/environment gate (required reviewers / protection rules) before production promotion.
P6 · Release Hygiene5.0 / 10Adequate✓ Tool-verified

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

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

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

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

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

  • `new RestTemplate(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. — main/manager-api/src/main/java/xiaozhi/modules/llm/service/impl/OpenAIStyleLLMServiceImpl.java:47
  • `HttpClient.newHttpClient(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. — main/manager-api/src/main/java/xiaozhi/modules/voiceclone/service/impl/VoiceCloneServiceImpl.java:340
  • `requests.get(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. (×8) — REDACTED:78, REDACTED:62, main/xiaozhi-server/core/providers/llm/gemini/gemini.py:21, …
  • `requests.post(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. (×13) — main/xiaozhi-server/core/providers/asr/openai.py:51, main/xiaozhi-server/core/providers/asr/tencent.py:188, main/xiaozhi-server/core/providers/llm/dify/dify.py:49, …
  • `requests.request(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. (×2) — main/xiaozhi-server/core/providers/tts/cozecn.py:49, main/xiaozhi-server/core/providers/tts/siliconflow.py:41

What to do

  • Set connect and read timeouts on every client (`RestTemplateBuilder.connectTimeout/readTimeout`, WebClient `responseTimeout`, `HttpRequest.Builder.timeout`, `HttpURLConnection.setReadTimeout`, Feign `connectTimeout`/`readTimeout` in configuration), and wrap calls to dependencies in resilience4j `@Retry`/`@CircuitBreaker`/`@TimeLimiter` (or Spring Retry).
  • Pass `timeout=` on every `requests`/`httpx` call (requests has no default and will wait forever), mount an `HTTPAdapter(max_retries=Retry(...))` on shared sessions, and wrap calls to flaky dependencies in `tenacity` retries or a `pybreaker` circuit breaker.
P8 · Schema migrations10.0 / 10Exemplary○ Nothing flagged

Readiness · Readiness — Whether database schema changes go through versioned migrations rather than being auto-created from the model at startup.

Method: Roslyn scan: EF Core DbContext for a versioned migrations directory versus bare EnsureCreated usage; off .NET, a file scan of dependency manifests, migration histories (Flyway, Liquibase, Alembic, Django, Rails, Prisma, TypeORM, Knex/Sequelize, golang-migrate, goose, Laravel, Doctrine, Diesel/sqlx) and schema auto-create in production source or config. Exhaustive, deterministic.

PF3 · Async & latency hygiene6.0 / 10Adequate✓ Tool-verified

Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.

Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from each language's code model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.

  • `speech_to_text` is async and calls time.sleep — a blocking call inside async code stalls the event loop — every other task on it waits for as long as it runs. — main/xiaozhi-server/core/providers/asr/fun_local.py:71
  • `speech_to_text` is async and calls requests.post — a blocking call inside async code stalls the event loop — every other task on it waits for as long as it runs. — main/xiaozhi-server/core/providers/asr/openai.py:27
  • `text_to_speak` is async and calls requests.post — a blocking call inside async code stalls the event loop — every other task on it waits for as long as it runs. (×6) — REDACTED:173, main/xiaozhi-server/core/providers/tts/doubao.py:56, main/xiaozhi-server/core/providers/tts/fishspeech.py:137, …
  • `text_to_speak` is async and calls requests.request — a blocking call inside async code stalls the event loop — every other task on it waits for as long as it runs. (×2) — main/xiaozhi-server/core/providers/tts/cozecn.py:33, main/xiaozhi-server/core/providers/tts/siliconflow.py:29
  • `text_to_speak` is async and calls requests.post, requests.get — a blocking call inside async code stalls the event loop — every other task on it waits for as long as it runs. — main/xiaozhi-server/core/providers/tts/custom.py:33
  • `text_to_speak` is async and calls requests.get — a blocking call inside async code stalls the event loop — every other task on it waits for as long as it runs. — main/xiaozhi-server/core/providers/tts/gpt_sovits_v3.py:37

What to do

  • Python: await the async equivalent (asyncio.sleep, an async HTTP client such as httpx.AsyncClient or aiohttp, asyncio.create_subprocess_exec), or move the blocking call off the loop with `await asyncio.to_thread(...)`; never call asyncio.run inside a coroutine — await the coroutine.
R1 · Type Safety3.6 / 10Weak✓ Tool-verified

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

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

  • 69 typed · 124 plain JS — the untyped files are main/digital-human/js/app.js, main/digital-human/js/config/manager.js, main/digital-human/js/core/audio/opus-codec.js, main/digital-human/js/core/audio/player.js, main/digital-human/js/core/audio/recorder.js, main/digital-human/js/core/audio/stream-context.js (+118 more).
R10 · Code Duplication5.8 / 10Adequate✓ Tool-verified

React / JS · Code Health — The share of the scored frontend lines inside a near-exact copy-pasted block of substantial extent (the D4 clone algorithm over JS/TS tokens, D-386; each line once, 10 at none and 0 at a quarter of the lines, as D4): a block is reported only where its copies still agree on most of their own identifiers and literals, or were renamed as they were pasted but kept most of their constants, and where the copies carry enough code to stand on their own or the copied extent reaches 30 lines — so a re-implementation sharing neither names nor values, and a small pasted declaration, are both found and deliberately not reported, and a clean R10 is not a claim that nothing was copied.

Method: Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm run over JS/TS tokens). Masking finds the candidates; a block is reported when its copies still agree on most of their own identifiers and literals, or when a renamed copy still agrees on most of its constants, AND the copies carry enough code to stand on their own — or when the copied extent reaches 30 lines. So a re-implementation sharing neither names nor values, and a small pasted declaration, are deliberately not counted. Scored on the share of the scored frontend lines inside a reported copy, on the same curve as D4. Deterministic.

  • 16 duplicated blocks under main/manager-web/src/ have copies in at least two of the sibling directories components, views — 8 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 16 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 16 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 16 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. — main/manager-web/src/components/HeaderBar.vue:233
  • 9 duplicated blocks under main/manager-mobile/src/pages/ have copies in at least two of the sibling directories agent, chat-history, device, forgot-password, index, login (+2 more sibling(s) not listed) — 8 of them are reported below, and 1 is counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 9 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 9 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 9 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. — main/manager-mobile/src/pages/forgot-password/index.vue:154
  • 6 duplicated blocks under main/ have copies in at least two of the sibling directories manager-mobile, manager-web — 5 of them are reported below, and 1 is counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 6 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 6 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 6 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — main/manager-mobile/src/pages/agent/components/agentSnapshotUtils.mjs:112
  • main/manager-web/src/views/OtaManagement.vue:130 · main/manager-web/src/views/VoiceResourceManagement.vue:105 — the two spans are one implementation copied and then locally edited — 792 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. — main/manager-web/src/views/OtaManagement.vue:130
  • main/manager-web/src/views/register.vue:134 · main/manager-web/src/views/retrievePassword.vue:111 — the two spans are one implementation copied and then locally edited — 635 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. — main/manager-web/src/views/register.vue:134
  • main/manager-mobile/src/pages/forgot-password/index.vue:154 · main/manager-mobile/src/pages/register/index.vue:165 — the two spans are one implementation copied and then locally edited — 480 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. — main/manager-mobile/src/pages/forgot-password/index.vue:154
  • main/manager-mobile/src/pages/login/index.vue:63 · main/manager-mobile/src/pages/register/index.vue:74 — the two spans are one implementation copied and then locally edited — 362 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. — main/manager-mobile/src/pages/login/index.vue:63
  • main/digital-human/js/live2d/live2d.js:158 · main/digital-human/js/live2d/live2d.js:609 — the two spans are one implementation copied and then locally edited — 530 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. — main/digital-human/js/live2d/live2d.js:158
  • main/manager-mobile/src/pages/chat-history/detail.vue:127 · main/manager-mobile/src/pages/chat-history/index.vue:119 — 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. — main/manager-mobile/src/pages/chat-history/detail.vue:127
  • main/manager-mobile/src/pages/device-config/components/ultrasonic-config.vue:177 · main/manager-mobile/src/pages/device-config/components/ultrasonic-config.vue:299 — 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. — main/manager-mobile/src/pages/device-config/components/ultrasonic-config.vue:177
  • main/manager-web/src/components/HeaderBar.vue:233 · main/manager-web/src/views/login.vue:174 — 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. — main/manager-web/src/components/HeaderBar.vue:233
  • main/manager-web/src/apis/module/agent.js:83 · main/manager-web/src/apis/module/agent.js:533 — the two spans are one implementation copied and then locally edited — 186 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. — main/manager-web/src/apis/module/agent.js:83
  • main/manager-web/src/components/AgentSnapshotDialog.vue:1289 · main/manager-web/src/components/AgentSnapshotDialog.vue:1382 — the two spans are one implementation copied and then locally edited — 162 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. — main/manager-web/src/components/AgentSnapshotDialog.vue:1289
  • main/manager-web/src/components/TtsModel.vue:497 · main/manager-web/src/views/VoiceResourceManagement.vue:223 — 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. — main/manager-web/src/components/TtsModel.vue:497
  • main/manager-mobile/src/pages/forgot-password/index.vue:23 · main/manager-mobile/src/pages/register/index.vue:22 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of MODULE-LEVEL DECLARATIONS — bindings the module declares and exports — rather than statements with a call site. Do not read this as an extract-a-helper row: a call expression cannot stand where a declaration was, and putting one there would delete the names themselves, which are what the rest of the codebase imports. What actually repeats here is the INITIALISER — the same expression shape written once per binding. So give that expression one name (a small helper the initialisers call, or a shared base value they are each derived from) and keep every binding under the name it already has. Where the run is an enumeration — one binding per distinct thing, differing precisely in the thing each one names — the repetition IS the enumeration and collapsing it would delete entries; consider instead whether the set belongs in one exported table the individual names are read out of. Reported because the copies drift apart the first time only one of them is edited. — main/manager-mobile/src/pages/forgot-password/index.vue:23
  • main/manager-web/src/apis/module/model.js:328 · main/manager-web/src/apis/module/model.js:359 — 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. — main/manager-web/src/apis/module/model.js:328
  • main/manager-web/src/apis/module/model.js:122 · main/manager-web/src/apis/module/model.js:193 — 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. — main/manager-web/src/apis/module/model.js:122
  • main/manager-web/src/components/DictDataDialog.vue:87 · main/manager-web/src/components/DictTypeDialog.vue:70 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — main/manager-web/src/components/DictDataDialog.vue:87
  • main/manager-mobile/src/api/agent/agent.ts:158 · main/manager-mobile/src/api/voiceprint/voiceprint.ts:9 — 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. — main/manager-mobile/src/api/agent/agent.ts:158
  • main/manager-mobile/src/utils/index.ts:148 · main/manager-mobile/src/utils/index.ts:181 — 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. — main/manager-mobile/src/utils/index.ts:148
  • main/manager-web/src/apis/module/agent.js:139 · main/manager-web/src/apis/module/agent.js:167 — 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. — main/manager-web/src/apis/module/agent.js:139
  • main/manager-web/src/apis/module/timbre.js:31 · main/manager-web/src/apis/module/timbre.js:74 — 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. — main/manager-web/src/apis/module/timbre.js:31
  • main/manager-web/src/components/DictDataDialog.vue:62 · main/manager-web/src/components/DictTypeDialog.vue:53 — 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. — main/manager-web/src/components/DictDataDialog.vue:62
  • main/manager-web/src/utils/featureManager.js:111 · main/manager-web/src/utils/featureManager.js:145 — 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. — main/manager-web/src/utils/featureManager.js:111
  • main/manager-web/src/views/roleConfig.vue:763 · main/manager-web/src/views/roleConfig.vue:1838 — 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. — main/manager-web/src/views/roleConfig.vue:763
  • main/manager-mobile/src/pages/chat-history/detail.vue:238 · main/manager-web/src/components/ChatHistoryDialog.vue:197 — the two spans are one implementation copied and then locally edited — 122 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. — main/manager-mobile/src/pages/chat-history/detail.vue:238
  • main/manager-mobile/src/pages/device/index.vue:280 · main/manager-mobile/src/pages/device/index.vue:324 — the two spans are one implementation copied and then locally edited — 120 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. — main/manager-mobile/src/pages/device/index.vue:280
  • main/manager-web/src/views/DeviceManagement.vue:233 · main/manager-web/src/views/UserManagement.vue:194 — the two spans are one implementation copied and then locally edited — 79 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. — main/manager-web/src/views/DeviceManagement.vue:233
  • main/manager-mobile/src/pages/forgot-password/index.vue:106 · main/manager-mobile/src/pages/register/index.vue:116 — 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. — main/manager-mobile/src/pages/forgot-password/index.vue:106
  • main/manager-web/src/views/roleConfig.vue:1660 · main/manager-web/src/views/roleConfig.vue:1750 — 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. — main/manager-web/src/views/roleConfig.vue:1660
  • main/manager-mobile/src/pages/agent/components/agentSnapshotUtils.mjs:60 · main/manager-web/src/components/agentSnapshotDisplayUtils.mjs:5 — the two spans are one implementation copied and then locally edited — 134 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. — main/manager-mobile/src/pages/agent/components/agentSnapshotUtils.mjs:60
  • main/manager-web/src/apis/module/model.js:161 · main/manager-web/src/apis/module/model.js:415 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — main/manager-web/src/apis/module/model.js:161
  • main/manager-web/src/apis/module/user.js:46 · main/manager-web/src/apis/module/user.js:66 — 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. — main/manager-web/src/apis/module/user.js:46
  • main/manager-mobile/src/pages/agent/index.vue:22 · main/manager-mobile/src/pages/chat-history/detail.vue:21 — 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. — main/manager-mobile/src/pages/agent/index.vue:22
  • main/manager-mobile/src/pages/chat-history/index.vue:14 · main/manager-mobile/src/pages/voiceprint/index.vue:18 — 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. — main/manager-mobile/src/pages/chat-history/index.vue:14
  • main/manager-web/src/apis/module/agent.js:543 · main/manager-web/src/apis/module/model.js:156 — 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. — main/manager-web/src/apis/module/agent.js:543
  • main/digital-human/js/core/audio/opus-codec.js:151 · main/digital-human/js/core/audio/player.js:114 — the two spans are one implementation copied and then locally edited — 79 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. — main/digital-human/js/core/audio/opus-codec.js:151
  • main/manager-mobile/src/pages/agent/components/AgentSnapshotPanel.vue:376 · main/manager-mobile/src/pages/agent/components/AgentSnapshotPanel.vue:437 — 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. — main/manager-mobile/src/pages/agent/components/AgentSnapshotPanel.vue:376
  • main/manager-web/src/components/ContextProviderDialog.vue:130 · main/manager-web/src/components/TtsAdvancedSettings.vue:134 — 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. — main/manager-web/src/components/ContextProviderDialog.vue:130
  • main/manager-web/src/components/ParamDialog.vue:142 · main/manager-web/src/components/ReplacementWordDialog.vue:228 — 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. — main/manager-web/src/components/ParamDialog.vue:142

What to do

  • Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
R11 · Import Boundaries4.7 / 10Weak✓ Tool-verified

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

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

  • main/manager-mobile/src/App.vue:8 imports abortcontroller-polyfill/dist/abortcontroller-polyfill-only, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — main/manager-mobile/src/App.vue:8
  • main/manager-web/src/apis/httpRequest.js:1 imports flyio/dist/npm/fly, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — main/manager-web/src/apis/httpRequest.js:1
  • main/manager-web/src/i18n/index.js:10 imports element-ui/lib/locale/lang/en, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — main/manager-web/src/i18n/index.js:10
  • main/manager-web/src/i18n/index.js:11 imports element-ui/lib/locale/lang/zh-CN, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — main/manager-web/src/i18n/index.js:11
  • main/manager-web/src/i18n/index.js:12 imports element-ui/lib/locale/lang/zh-TW, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — main/manager-web/src/i18n/index.js:12
  • main/manager-web/src/i18n/index.js:13 imports element-ui/lib/locale/lang/de, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — main/manager-web/src/i18n/index.js:13
  • main/manager-web/src/i18n/index.js:14 imports element-ui/lib/locale/lang/vi, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — main/manager-web/src/i18n/index.js:14
  • main/manager-web/src/i18n/index.js:15 imports element-ui/lib/locale/lang/pt-br, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — main/manager-web/src/i18n/index.js:15
  • main/manager-web/src/main.js:9 imports element-ui/lib/locale, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — main/manager-web/src/main.js:9

What to do

  • Fix the listed violations: import through public entries (package exports / slice index), never reach into another layer or package's internals.
R2 · Cyclomatic Complexity7.8 / 10Strong✓ Tool-verified

React / JS · Code Health — Per-function cyclomatic/cognitive complexity from the token-level function scanner (D-386) — real branching, not a regex heuristic.

Method: Per-function cyclomatic/cognitive complexity from a token-level function scanner (real branching, not a regex heuristic), computed over every frontend function. Deterministic.

  • animateMouth has cyclomatic complexity 29 and cognitive complexity 46; 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. — main/digital-human/js/live2d/live2d.js:418
  • selectRoleTemplate has cyclomatic complexity 28 and cognitive complexity 33; 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. — main/manager-mobile/src/pages/agent/edit.vue:724
  • handleTextMessage has cyclomatic complexity 25 and cognitive complexity 40; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — main/digital-human/js/core/network/websocket.js:97
  • saveAgent has cyclomatic complexity 23 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. — main/manager-mobile/src/pages/agent/edit.vue:986
  • applyTemplateData has cyclomatic complexity 23 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — main/manager-web/src/views/roleConfig.vue:865
  • redactCapabilityPath has cyclomatic complexity 22 and cognitive complexity 28; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — main/manager-mobile/src/pages/agent/components/agentSnapshotUtils.mjs:196
  • confirmRestoreSnapshot has cyclomatic complexity 22 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — main/manager-mobile/src/pages/agent/components/AgentSnapshotPanel.vue:533
  • onPickerConfirm has cyclomatic complexity 22 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — main/manager-mobile/src/pages/agent/edit.vue:789
  • (anonymous) has cyclomatic complexity 21 and cognitive complexity 71; 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. — main/manager-web/src/utils/featureManager.js:95
  • playVoicePreview has cyclomatic complexity 20 and cognitive complexity 25; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — main/manager-web/src/views/roleConfig.vue:1578
  • (anonymous) has cyclomatic complexity 20 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. — main/digital-human/js/live2d/live2d.js:206
  • (anonymous) has cyclomatic complexity 20 and cognitive complexity 19; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — main/manager-web/src/views/roleConfig.vue:960
  • formatDisplayValue has cyclomatic complexity 20 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — main/manager-mobile/src/pages/agent/components/AgentSnapshotPanel.vue:780
  • (anonymous) has cyclomatic complexity 18 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — main/digital-human/js/live2d/live2d.js:662
  • handleConnect has cyclomatic complexity 17 and cognitive complexity 27; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — main/digital-human/js/ui/controller.js:679
  • fetchAllLanguag has cyclomatic complexity 17 and cognitive complexity 18; 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. — main/manager-mobile/src/pages/agent/edit.vue:622
  • buildTtsDraft has cyclomatic complexity 17 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. — main/manager-web/src/views/roleConfig.vue:1147
  • (anonymous) has cyclomatic complexity 17 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — main/manager-web/src/views/AgentTemplateManagement.vue:247
  • updateDialButton has cyclomatic complexity 16 and cognitive complexity 29; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — main/digital-human/js/ui/controller.js:325
  • handleRegister has cyclomatic complexity 16 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — main/manager-mobile/src/pages/register/index.vue:193
  • buildSavedVersionDetail has cyclomatic complexity 15 and cognitive complexity 10; 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. — main/manager-mobile/src/pages/agent/components/AgentSnapshotPanel.vue:483
  • handleMCPMessage has cyclomatic complexity 14 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — main/digital-human/js/core/network/websocket.js:270
  • (anonymous) 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. — main/digital-human/js/app.js:267
  • handleApplyWakeword has cyclomatic complexity 14 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. — main/digital-human/js/ui/controller.js:544
  • onmessage 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. — main/digital-human/js/core/network/wakeword-bridge.js:42
  • loadSnapshots 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. — main/manager-mobile/src/pages/agent/components/AgentSnapshotPanel.vue:286
  • loadConfig has cyclomatic complexity 14 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — main/digital-human/js/config/manager.js:20
  • handlePointerUp has cyclomatic complexity 13 and cognitive complexity 19; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — main/digital-human/js/live2d/live2d.js:303
  • handleTTSMessage has cyclomatic complexity 13 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. — main/digital-human/js/core/network/websocket.js:173
  • validateContent has cyclomatic complexity 13 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. — main/manager-web/src/components/ReplacementWordDialog.vue:86
  • (anonymous) 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. — main/digital-human/js/live2d/live2d.js:178
  • previewRestoreSnapshot 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. — main/manager-mobile/src/pages/agent/components/AgentSnapshotPanel.vue:400
  • filterVoicesByLanguage 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. — main/manager-web/src/views/roleConfig.vue:1266
  • confirm 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. — main/manager-web/src/components/AddModelDialog.vue:190
  • saveConfig 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. — main/manager-web/src/views/roleConfig.vue:628
  • handleModelChange 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. — main/manager-web/src/views/roleConfig.vue:1347
  • normalizeValueForField has cyclomatic complexity 12 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. — main/manager-web/src/components/AgentSnapshotDialog.vue:1923
  • (anonymous) has cyclomatic complexity 12 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. — main/manager-web/src/views/KnowledgeBaseManagement.vue:604
  • start 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. — main/digital-human/js/core/audio/recorder.js:203
  • stop 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. — main/digital-human/js/core/audio/recorder.js:282
R3 · Large Files0.0 / 10Critical✓ Tool-verified

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

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

  • main/manager-web/src/components/AgentSnapshotDialog.vue has 2542 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — main/manager-web/src/components/AgentSnapshotDialog.vue:1
  • main/manager-web/src/views/roleConfig.vue has 2283 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — main/manager-web/src/views/roleConfig.vue:1
  • main/manager-mobile/src/pages/agent/edit.vue has 1552 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — main/manager-mobile/src/pages/agent/edit.vue:1
  • main/manager-mobile/src/pages/agent/components/AgentSnapshotPanel.vue has 1344 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — main/manager-mobile/src/pages/agent/components/AgentSnapshotPanel.vue:1
  • main/manager-web/src/views/AddressBookManagement.vue has 1188 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — main/manager-web/src/views/AddressBookManagement.vue:1
  • main/manager-web/src/views/KnowledgeBaseManagement.vue has 1148 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — main/manager-web/src/views/KnowledgeBaseManagement.vue:1
  • main/manager-web/src/views/ParamsManagement.vue has 986 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — main/manager-web/src/views/ParamsManagement.vue:1
  • main/manager-web/src/views/ModelConfig.vue has 900 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — main/manager-web/src/views/ModelConfig.vue:1
  • main/manager-mobile/src/pages/login/index.vue has 895 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — main/manager-mobile/src/pages/login/index.vue:1
  • main/manager-web/src/views/home.vue has 815 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — main/manager-web/src/views/home.vue:1
  • main/digital-human/js/ui/controller.js has 811 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — main/digital-human/js/ui/controller.js:1
  • main/manager-mobile/src/pages/register/index.vue has 805 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — main/manager-mobile/src/pages/register/index.vue:1
  • main/manager-web/src/components/FunctionDialog.vue has 798 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — main/manager-web/src/components/FunctionDialog.vue:1
  • main/manager-mobile/src/pages/forgot-password/index.vue has 754 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — main/manager-mobile/src/pages/forgot-password/index.vue:1
  • main/digital-human/js/live2d/live2d.js has 705 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — main/digital-human/js/live2d/live2d.js:1
  • main/manager-mobile/src/pages/index/index.vue has 703 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — main/manager-mobile/src/pages/index/index.vue:1
  • main/manager-web/src/components/TtsModel.vue has 633 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — main/manager-web/src/components/TtsModel.vue:1
  • main/manager-web/src/components/VoiceCloneDialog.vue has 628 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — main/manager-web/src/components/VoiceCloneDialog.vue:1
  • main/manager-web/src/views/VoiceCloneManagement.vue has 607 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — main/manager-web/src/views/VoiceCloneManagement.vue:1
  • main/manager-web/src/components/HeaderBar.vue has 606 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — main/manager-web/src/components/HeaderBar.vue:1
  • main/manager-mobile/src/pages/voiceprint/index.vue has 588 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — main/manager-mobile/src/pages/voiceprint/index.vue:1
  • main/manager-mobile/src/pages/device-config/components/ultrasonic-config.vue has 586 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — main/manager-mobile/src/pages/device-config/components/ultrasonic-config.vue:1
  • main/manager-web/src/components/ChatHistoryDialog.vue has 586 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — main/manager-web/src/components/ChatHistoryDialog.vue:1
  • main/manager-web/src/apis/module/agent.js has 568 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — main/manager-web/src/apis/module/agent.js:1
  • main/manager-web/src/views/KnowledgeBaseItem.vue has 568 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — main/manager-web/src/views/KnowledgeBaseItem.vue:1
  • main/manager-web/src/views/FeatureManagement.vue has 567 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — main/manager-web/src/views/FeatureManagement.vue:1
  • main/manager-mobile/src/pages/device/index.vue has 563 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — main/manager-mobile/src/pages/device/index.vue:1
  • main/manager-mobile/src/pages/agent/tools.vue has 561 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — main/manager-mobile/src/pages/agent/tools.vue:1
  • main/manager-web/src/views/DictManagement.vue has 555 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — main/manager-web/src/views/DictManagement.vue:1
  • main/manager-mobile/src/pages/login/user-agreement-zh.vue has 526 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — main/manager-mobile/src/pages/login/user-agreement-zh.vue:1
  • main/manager-mobile/src/pages/login/user-agreement-en.vue has 524 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — main/manager-mobile/src/pages/login/user-agreement-en.vue:1
  • main/manager-web/src/views/DeviceManagement.vue has 521 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — main/manager-web/src/views/DeviceManagement.vue:1
  • main/digital-human/js/core/network/websocket.js has 520 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — main/digital-human/js/core/network/websocket.js:1
  • main/manager-mobile/src/pages/device-config/components/wifi-selector.vue has 502 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — main/manager-mobile/src/pages/device-config/components/wifi-selector.vue:1
  • main/manager-web/src/components/ModelEditDialog.vue has 492 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — main/manager-web/src/components/ModelEditDialog.vue:1
  • main/digital-human/js/core/mcp/tools.js has 488 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — main/digital-human/js/core/mcp/tools.js:1
  • main/manager-web/src/views/ProviderManagement.vue has 474 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — main/manager-web/src/views/ProviderManagement.vue:1
  • main/manager-web/src/views/ReplacementWordManagement.vue has 473 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — main/manager-web/src/views/ReplacementWordManagement.vue:1
  • main/manager-web/src/views/AgentTemplateManagement.vue has 466 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — main/manager-web/src/views/AgentTemplateManagement.vue:1
  • main/manager-mobile/src/pages/settings/index.vue has 459 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — main/manager-mobile/src/pages/settings/index.vue:1

What to do

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

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

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

  • No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×40) — main/digital-human/js/ui/controller.js:1, main/digital-human/js/live2d/live2d.js:1, main/digital-human/js/core/network/websocket.js:1, …

What to do

  • Add tests that import the unreached modules (directly or through their public entry).
R5 · Dependency Freshness8.6 / 10Strong✓ Tool-verified

React / JS · Readiness — How outdated the npm dependencies are (a maturity signal). JS/npm CVEs are scored separately in D30 (JS/npm Dependency Vulnerabilities).

Method: npm dependency staleness from manifest/registry metadata (a maturity signal; JS/npm CVEs are scored separately in D30, which answers dependency vulnerabilities for every ecosystem). Deterministic.

R6 · Tooling10.0 / 10Exemplary✓ Tool-verified

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

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

  • The package in `main/manager-mobile` declares the lint script `lint` (`eslint`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `main/manager-mobile` (or the workspace's task runner). — REDACTED:75
R7 · Dead Code7.2 / 10Strong✓ Tool-verified

React / JS · Code Health — Files unreachable from every application/tooling/test entry point, and exports nothing imports (module-graph reachability, D-386).

Method: Dead code: files unreachable from every application/tooling/test entry point plus exports nothing imports, via module-graph reachability. Deterministic, exhaustive over the import graph.

  • Unreachable from the 28 application, 10 tooling and 9 test entry point(s) detected in this repo. Gate removals on `npm run build` — an undetected custom entry would make these reachable.
  • no import path from any entry point (28 application, 10 tooling, 9 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (main/manager-mobile/src/pages/device-config/index.vue) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×3) — main/manager-mobile/src/pages/device-config/components/ultrasonic-config.vue, main/manager-mobile/src/pages/device-config/components/wifi-selector.vue, main/manager-mobile/src/pages/device-config/components/wifi-config.vue
  • no import path from any entry point (28 application, 10 tooling, 9 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (main/manager-mobile/src/pages/agent/index.vue) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×4) — main/manager-mobile/src/pages/device/index.vue, main/manager-mobile/src/pages/voiceprint/index.vue, main/manager-mobile/src/pages/chat-history/index.vue, …
  • no import path from any entry point (28 application, 10 tooling, 9 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 (×23) — main/manager-mobile/src/utils/uploadFile.ts, main/manager-mobile/src/pages/register/index.vue, main/manager-mobile/src/pages/chat-history/detail.vue, …
  • no import path from any entry point (28 application, 10 tooling, 9 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (main/manager-mobile/src/api/voiceprint/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — main/manager-mobile/src/api/voiceprint/voiceprint.ts
  • no import path from any entry point (28 application, 10 tooling, 9 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (main/manager-mobile/src/api/device/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — main/manager-mobile/src/api/device/device.ts
  • no import path from any entry point (28 application, 10 tooling, 9 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (main/manager-mobile/src/api/chat-history/index.ts, main/manager-mobile/src/pages/chat-history/detail.vue, main/manager-mobile/src/pages/chat-history/index.vue) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — main/manager-mobile/src/api/chat-history/chat-history.ts
  • no import path from any entry point (28 application, 10 tooling, 9 test roots considered), but 4 in-repo import(s) from 4 other file(s) do name it (main/manager-mobile/src/api/chat-history/chat-history.ts, main/manager-mobile/src/api/chat-history/index.ts, main/manager-mobile/src/pages/chat-history/detail.vue and 1 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — main/manager-mobile/src/api/chat-history/types.ts
  • no import path from any entry point (28 application, 10 tooling, 9 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (main/manager-mobile/src/layouts/tabbar.vue) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — main/manager-mobile/src/layouts/fg-tabbar/fg-tabbar.vue
  • no import path from any entry point (28 application, 10 tooling, 9 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (main/manager-mobile/src/api/voiceprint/index.ts, main/manager-mobile/src/api/voiceprint/voiceprint.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — main/manager-mobile/src/api/voiceprint/types.ts
  • no import path from any entry point (28 application, 10 tooling, 9 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (main/manager-mobile/src/api/device/device.ts, main/manager-mobile/src/api/device/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — main/manager-mobile/src/api/device/types.ts
  • no import path from any entry point (28 application, 10 tooling, 9 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (main/manager-mobile/src/layouts/fg-tabbar/fg-tabbar.vue) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — main/manager-mobile/src/layouts/fg-tabbar/tabbar.ts
  • no import path from any entry point (28 application, 10 tooling, 9 test roots considered), but 2 in-repo import(s) from 1 other file(s) do name it (main/manager-mobile/src/pages/device/index.vue) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — main/manager-mobile/src/api/device/index.ts

What to do

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

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

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

  • Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×24) — REDACTED:110, REDACTED:115, REDACTED:116, …
  • Declared in main/manager-web/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. (×5) — main/manager-web/package.json:33, main/manager-web/package.json:34, main/manager-web/package.json:14, …

What to do

  • Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports5.1 / 10Adequate✓ Tool-verified

React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.

Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.

  • main/digital-human/js/core/network/wakeword-bridge.js → main/digital-human/js/ui/controller.js → main/digital-human/js/core/network/wakeword-bridge.js (one verified cycle inside a mutually-dependent group of 3 files) — main/digital-human/js/core/network/wakeword-bridge.js:1
  • main/manager-web/src/apis/api.js → main/manager-web/src/apis/module/addressBook.js → main/manager-web/src/apis/api.js (one verified cycle inside a mutually-dependent group of 16 files) — main/manager-web/src/apis/api.js:14

What to do

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

Other · Security — Only what this repository's own non-C# files could be read for was assessed — and because this repository commits the configuration that serves its own HTTP surface, that configuration could be read in full for the security response headers it sets. Nothing else in this dimension was assessed: the transport, cookie, input-validation and crypto controls are read from a source model that was not loaded for this repository’s language, so their absence here is not a finding about this repository.

Method: Roslyn plus filesystem scan: HSTS/security headers, secure cookies, input validation, middleware order, weak crypto (MD5/SHA1/DES); HTTPS-metadata context-aware. On a repository with no .NET source it reads JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Elixir source itself (test, vendored, generated and minified paths not) for the arms that hold whether or not the code serves HTTP: a weak hash or cipher, key material fixed in the source, a TLS client that accepts any certificate, and (JavaScript/TypeScript, Ruby, Scala, Rust and Elixir) an obsolete TLS version; the server controls are not assessed there, and a Dart, Ruby, Scala, Rust or Elixir repository that serves no HTTP of its own is N/A on them. Deterministic.

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

What to do

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

Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.

Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.

  • The task this creates is not kept anywhere. The event loop holds only a weak reference to its tasks, so a task nobody references can be garbage-collected before it finishes (Python's documentation for `asyncio.create_task`: save a reference to the result); and nothing ever awaits it, so an exception it raises is never handled — it surfaces, if at all, as "Task exception was never retrieved" in a log. Keep the task: `await` it, gather it, start it in an `asyncio.TaskGroup` (`async with asyncio.TaskGroup() as tg: tg.create_task(…)`), or, for genuine fire-and-forget, add it to a set and `task.add_done_callback(tasks.discard)` with a callback that also reads its exception. (×9) — main/xiaozhi-server/core/providers/tools/mcp_endpoint/mcp_endpoint_handler.py:26, main/xiaozhi-server/core/providers/asr/doubao_stream.py:262, main/xiaozhi-server/core/providers/asr/xunfei_stream.py:276, …
  • This `async def` runs on the event loop's thread, and `time.sleep` blocks that thread: for the whole delay no other coroutine, request or callback on the loop makes progress — the Python form of blocking on a task. Use `await asyncio.sleep(…)`, which suspends only this coroutine. Where the blocking work is not a sleep but a synchronous call that cannot be made async, move it off the loop with `await asyncio.to_thread(…)` (or `loop.run_in_executor(…)`). — main/xiaozhi-server/core/providers/asr/fun_local.py:109
  • The function passed to `new Promise(…)` is `async`. The constructor ignores what its executor returns, so anything this executor throws — every throw inside an `async` function, including after an `await` — rejects a Promise nobody holds instead of the one being constructed: the outer Promise never settles, whoever awaits it hangs, and the error is reported nowhere. If the body needs `await`, it does not need `new Promise` at all: make the enclosing function `async` and `return` the value (or `throw`) directly. If it wraps a callback API, keep the executor synchronous — call the API and `resolve`/`reject` from its callback — and do the awaiting outside it. — main/digital-human/js/app.js:267

What to do

  • Task from `asyncio.create_task` is not kept
X12 · Unreachable branch10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.

Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.

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

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

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

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

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

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

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

Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.

Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.

X17 · Uncapped recursion over a caller-supplied document2.7 / 10Weak✓ Tool-verified

Other · Security — Whether a walk that recurses through a JSON/XML tree handed in by its caller bounds how deep it will go — an uncapped walk lets the document's nesting choose the stack depth, and the resulting StackOverflowException cannot be caught.

Method: Roslyn syntax + semantics: methods that take a JSON/XML document node and call themselves with a child of it, reachable from an externally-callable member of the same type that accepts a document, checked for any depth parameter, descent counter or threaded arithmetic anywhere in the walk. On a repository with no .NET source it reads TypeScript off the engine’s own token stream (test, vendored, generated and minified paths and `.d.ts` not) with the same rule: a function or method with a parameter typed as a document value — `unknown`, `any`, `object`, `Record<string, unknown|any>`, a JSON alias (`JsonValue`, `JSONObject`, …) or a DOM node global the file does not rebind — that calls itself (bare, or through `this` for a method, or hands itself to a call over the value as in `value.map(walk)`) with something it took out of that value and never through an ancestor accessor such as `closest()` or `parentElement`, that is exported or reached from an exported function (a public method of the same exported class) taking such a value, and that names no depth, level, nesting, recursion, remaining or budget anywhere and threads no `+`/`-` arithmetic through a self-call. Plain JavaScript is not read: with no annotation nothing tells a parsed document from a tree the code built itself. Deterministic, provable per finding. Advisory.

  • `redactSnapshotDisplayValue` is exported and takes `value: object` from its caller, and it calls itself at line 73 (`redactSnapshotDisplayValue`) with a piece of `value` (and at line 88) — and nowhere in `redactSnapshotDisplayValue` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `redactSnapshotDisplayValue` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — main/manager-mobile/src/pages/agent/components/agentSnapshotUtils.mjs:73
  • `normalizeSnapshotOrderedList` is exported, takes a document from its caller (line 53) and hands it to `normalizeDisplayObject`, which calls itself at line 297 (`normalizeDisplayObject`) with a piece of `value` (and at line 301) — and nowhere in `normalizeDisplayObject` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `normalizeDisplayObject` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — main/manager-mobile/src/pages/agent/components/agentSnapshotUtils.mjs:297

What to do

  • Each finding names the externally-callable member that accepts the document and the self-call that descends, and states that no depth parameter or counter exists anywhere in the walk. Confirm from the two, then thread a depth argument through the walk and reject documents past a fixed maximum, or rewrite it with an explicit stack.
X18 · Disposal-pattern correctness10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.

Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.

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

Other · Code Health — Whether a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.

Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. Deterministic, provable per finding. Advisory.

X2 · Cancellation propagation4.0 / 10Weak✓ Tool-verified

Other · Code Health — Whether async functions that make a cancellable request accept or pass on an AbortSignal (adoption curve).

Method: Roslyn scan: every async method (excluding framework-fixed overrides/Blazor handlers) checked for CancellationToken parameter presence. Deterministic, adoption percentage. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same question: every named async function that itself makes a request an AbortSignal can cancel (global `fetch`, axios and its file-local instances, ky, ofetch) counts, and it is compliant when its parameters or body name a signal or it hands one of its own parameters to the request as options; signatures a framework fixes (JSX event handlers, route and lifecycle exports, request-first handlers, `override`, `'use server'` modules, TanStack `mutationFn`) are exempt unless they take a signal. Deterministic, adoption percentage.

  • Only 0/3 async functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
  • `initCamera` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — main/digital-human/js/app.js:131
  • `sendOTA` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — main/digital-human/js/core/network/ota-connector.js:65
  • `initMcpTools` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — main/digital-human/js/core/mcp/tools.js:24

What to do

  • Thread an AbortSignal through async functions that make requests, so the work stops when its caller gives up.
X21 · Side-effecting pattern guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.

Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.

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

Other · Code Health — Whether the work a diagnostic log line costs is paid only when that line is wanted — C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.

Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` — outside any arrow or function passed as an argument, which the logger calls only when the level is on — with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. Deterministic, provable per finding. Advisory.

X24 · Document value interpolated into markup unescaped3.1 / 10Weak✓ Tool-verified

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

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

  • `tool.name` is text this program did not author, and it is written into the text of an element through markup built here with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — main/digital-human/js/core/mcp/tools.js:74
  • `tool.description` is text this program did not author, and it is written into the text of an element through markup built here with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — main/digital-human/js/core/mcp/tools.js:84
  • `hasMockResponse?'✅ 已配置: '+JSON.stringify(tool.mockResponse):'⚪ 使用默认'` is text this program did not author, and it is written into the text of an element through markup built here with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — main/digital-human/js/core/mcp/tools.js:92
  • `prop.name` is text this program did not author, and it is written into the text of an element through markup built here with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — main/digital-human/js/core/mcp/tools.js:123
  • `getTypeLabel(prop.type)` is text this program did not author, and it is written into the text of an element through markup built here with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — main/digital-human/js/core/mcp/tools.js:127
  • `prop.description||'-'` is text this program did not author, and it is written into the text of an element through markup built here with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — main/digital-human/js/core/mcp/tools.js:131
  • `message` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — main/digital-human/js/core/mcp/tools.js:434
  • `content` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — main/digital-human/js/ui/controller.js:446
  • `toolId` is text this program did not author, and it is written into a script or style context through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. A script or style context needs its own escaping (or a JSON serialiser that escapes `<`); better, pass the value through a data attribute. — main/digital-human/js/ui/controller.js:846
  • `renderMarkdownValue(item.afterValue)` is text this program did not author, and it is written into the text of an element through Vue's `v-html` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. (×3) — main/manager-web/src/components/AgentSnapshotDialog.vue:199, main/manager-web/src/components/AgentSnapshotDialog.vue:290, main/manager-web/src/components/AgentSnapshotDialog.vue:422
  • `renderMarkdownValue(item.beforeValue)` is text this program did not author, and it is written into the text of an element through Vue's `v-html` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. (×2) — main/manager-web/src/components/AgentSnapshotDialog.vue:279, main/manager-web/src/components/AgentSnapshotDialog.vue:411

What to do

  • Each finding names the expression, the attribute it lands in and the line. Confirm the value's origin from the read this analyzer traced, then escape it at the sink or validate it against the shape the attribute accepts before interpolating.
X25 · Inert configuration knob10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.

Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.

X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.

Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.

X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.

Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.

X3 · Exception handling5.4 / 10Adequate✓ Tool-verified

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

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

  • `except Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×11) — main/xiaozhi-server/scripts/capacity_bench.py:157, main/xiaozhi-server/scripts/capacity_bench.py:318, main/xiaozhi-server/scripts/capacity_bench.py:446, …
  • 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. (×26) — main/xiaozhi-server/scripts/capacity_bench.py:246, main/xiaozhi-server/scripts/capacity_bench.py:253, main/xiaozhi-server/scripts/capacity_bench.py:476, …
  • An empty catch block silently discards the error — failures vanish with no log and no rethrow. On a teardown path letting it propagate is not an option (throwing out of `close()` masks the failure already in flight and abandons the rest of the cleanup), so make the swallow deliberate instead: narrow the catch to the exception this release can actually raise, and record it through whatever this codebase already uses to report problems — or, if it truly cannot matter, say why in a comment on the catch. (×3) — main/xiaozhi-server/core/connection.py:2177, main/xiaozhi-server/core/connection.py:2202, main/xiaozhi-server/core/connection.py:2283

What to do

  • Swallowed exception (caught, then discarded)
X4 · Structured logging7.6 / 10Strong✓ Tool-verified

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

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

  • `error` at line 49 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog. — main/xiaozhi-server/core/utils/opus_encoder_utils.py:49
  • `error` at line 114 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog. — main/xiaozhi-server/core/utils/opus_encoder_utils.py:114
  • `warning` at line 128 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.warning("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.warning("order moved", order_id=order_id, status=status)` with structlog. — main/xiaozhi-server/core/utils/opus_encoder_utils.py:128
  • `error` at line 139 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog. — main/xiaozhi-server/core/utils/opus_encoder_utils.py:139

What to do

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

Other · Code Health — Whether strict null checking is enabled and not undermined by heavy `!` assertion — TypeScript's `strictNullChecks` (which `strict` turns on) is what makes `string` exclude `null` and `undefined`, and the postfix `!` is the operator that silences it.

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

  • 0/1 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.

What to do

  • The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`).

WCAG coverage — what static analysis assessed

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

DimensionWCAG 2.2 A/AA criteriaCoverage
AC1 · Text alternatives1.1.1, 1.2.2, 1.2.5Partial signal
AC2 · Forms & labels1.3.1, 3.3.2, 4.1.2Partial signal
AC3 · Page structure1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2Partial signal
AC4 · Keyboard semantics2.1.1, 2.4.3Partial signal
AC5 · ARIA correctness4.1.2Partial signal

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

Reference — by lens

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

LensScoreRatingImpact
Code Health33.0Weak — gated by R1, R3, X5Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture74.1StrongStrongest area.
Maturity72.1Adequate — gated by M2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness33.3Weak — gated by R8, P3, P7Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security58.5Adequate — gated by D28, D29, D36Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Accessibility42.8Weak — gated by AC4Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance60.0AdequateAcceptable, with room to improve.
Unscored — 3 check(s) recorded observations but carry no score

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

  • X10 Duplicated predicate — 35 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X6 Hand-rolled structured-format parsing — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X7 Silent fallback defaults — 7 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 4 control(s) we could not find positive evidence for

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

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

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

  • AC6 Visual & motion safety — Visual & motion safety could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository.
  • AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • AX7 Slice cohesion — not applicable — not a vertical-slice architecture
  • AX8 Test isolation — no test/production split to check
  • AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
  • AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • AXR1 Runtime accessibility — compose up failed (exit 15 — the compose project is invalid) — service "xiaozhi-esp32-server" has neither an image nor a build context specified: invalid compose project; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
  • C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • D1 Cyclomatic Complexity — cyclomatic complexity not measured — .js, .vue exposed no member bodies
  • D11 Test Reliability — Test reliability not measured — JavaScript/TypeScript suite did not run
  • 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.
  • D2 Cognitive Complexity — cognitive complexity not measured — .js, .vue exposed no member bodies
  • 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/REDACTED` 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 measured no build unit over this repository's .js, .lua source. Not scored: this is a gap in the analyzer, not a verdict about this repository.
  • D27 Navigability — D27 reads resolved call sites in the languages it reads only — this repository's production source is .java, .lua, .ts, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
  • D3 God Classes — Most of this repository's production source (.js, .vue) was not read by god-class detection, so class size was not assessed for the languages that are the product — whatever else this pass did read is not this repository's class size. Not scored — this is a gap in the analyzer, not a verdict about this repository.
  • D32 Data Compliance (PII/GDPR) — 2 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
  • D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
  • D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
  • D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
  • D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
  • D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
  • D8 Code Coverage — Coverage not measured — JavaScript/TypeScript suite
  • DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (13 value object(s))
  • ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
  • ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
  • ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
  • GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
  • IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
  • P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
  • PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a REDACTED, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
  • PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
  • SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X27 Collection changed while being enumerated — X27 reached only 46% of this repository's production lines — javascript (45,828 lines), typescript (19,156 lines), lua (12 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
  • X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

Appendix A — Findings (grouped)

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

Critical — 211 finding(s)
D30 · Dependency Vulnerabilities · High CVE · ×77
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • + 52 more in this group — see findings.md.
AC4 · Keyboard semantics · Click handler on a non-interactive <div> · ×27
  • Click handler on a non-interactive <div> main/digital-human/js/core/mcp/tools.js:120 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> main/manager-web/src/components/AddDeviceDialog.vue:22 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> main/manager-web/src/components/AddDeviceDialog.vue:25 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> main/manager-web/src/components/AddWisdomBodyDialog.vue:21 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> main/manager-web/src/components/AddWisdomBodyDialog.vue:24 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> main/manager-web/src/components/AudioPlayer.vue:29 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> main/manager-web/src/components/ChatHistoryDialog.vue:19 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> main/manager-web/src/components/DeviceItem.vue:25 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> main/manager-web/src/components/DeviceItem.vue:28 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> main/manager-web/src/components/DeviceItem.vue:31 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> main/manager-web/src/components/DeviceItem.vue:34 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> main/manager-web/src/components/FunctionDialog.vue:25 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> main/manager-web/src/components/FunctionDialog.vue:50 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> main/manager-web/src/components/HeaderBar.vue:5 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> main/manager-web/src/components/HeaderBar.vue:12 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> main/manager-web/src/components/HeaderBar.vue:29 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> main/manager-web/src/components/HeaderBar.vue:69 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> main/manager-web/src/components/HeaderBar.vue:77 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> main/manager-web/src/components/HeaderBar.vue:86 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> main/manager-web/src/components/TtsModel.vue:87 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> main/manager-web/src/components/ViewPasswordDialog.vue:23 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> main/manager-web/src/components/ViewPasswordDialog.vue:27 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> main/manager-web/src/views/AddressBookManagement.vue:33 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> main/manager-web/src/views/DictManagement.vue:37 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> main/manager-web/src/views/FeatureManagement.vue:37 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • + 2 more in this group — see findings.md.
D30 · Dependency Vulnerabilities · Critical CVE · ×19
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
AC2 · Forms & labels · <input> without a programmatic label · ×12
  • <input> without a programmatic label main/digital-human/js/ui/controller.js:844 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label main/digital-human/js/ui/controller.js:845 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label main/manager-mobile/src/pages/agent/edit.vue:1296 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label main/manager-mobile/src/pages/agent/edit.vue:1308 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label main/manager-mobile/src/pages/agent/tools.vue:421 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label main/manager-mobile/src/pages/agent/tools.vue:507 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label main/manager-mobile/src/pages/index/index.vue:367 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label main/manager-mobile/src/pages/voiceprint/index.vue:491 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label main/manager-web/src/components/AudioPlayer.vue:63 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label main/manager-web/src/views/AddressBookManagement.vue:73 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label main/manager-web/src/views/AddressBookManagement.vue:105 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label main/manager-web/src/views/AddressBookManagement.vue:168 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
AC1 · Text alternatives · <img> without a text alternative · ×7
  • <img> without a text alternative main/manager-mobile/src/components/custom-tabs/index.vue:45 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative main/manager-mobile/src/pages/forgot-password/index.vue:358 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative main/manager-mobile/src/pages/login/index.vue:375 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative main/manager-mobile/src/pages/register/index.vue:419 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative main/manager-web/src/components/ChatHistoryDialog.vue:21 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative main/manager-web/src/components/ChatHistoryDialog.vue:37 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative main/manager-web/src/views/KnowledgeBaseItem.vue:25 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
D28 · Secrets (history) · REDACTED · ×7
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
AC4 · Keyboard semantics · Click handler on a non-interactive <text> · ×5
  • Click handler on a non-interactive <text> main/manager-mobile/src/pages/login/index.vue:388 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <text> main/manager-mobile/src/pages/login/index.vue:394 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <text> main/manager-mobile/src/pages/login/index.vue:401 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <text> main/manager-mobile/src/pages/login/index.vue:407 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <text> main/manager-mobile/src/pages/register/index.vue:459 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
AC2 · Forms & labels · Custom control with no accessible name on <div> · ×4
  • Custom control with no accessible name on <div> main/manager-web/src/components/AudioPlayer.vue:29 — This <div> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.
  • Custom control with no accessible name on <div> main/manager-web/src/components/TtsModel.vue:87 — This <div> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.
  • Custom control with no accessible name on <div> main/manager-web/src/views/KnowledgeBaseManagement.vue:29 — This <div> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.
  • Custom control with no accessible name on <div> main/manager-web/src/views/KnowledgeBaseManagement.vue:82 — This <div> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.
AC2 · Forms & labels · Custom control with no accessible name on <i> · ×4
  • Custom control with no accessible name on <i> main/manager-web/src/components/ChatHistoryDialog.vue:65 — This <i> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.
  • Custom control with no accessible name on <i> main/manager-web/src/views/AddressBookManagement.vue:85 — This <i> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.
  • Custom control with no accessible name on <i> main/manager-web/src/views/AddressBookManagement.vue:115 — This <i> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.
  • Custom control with no accessible name on <i> main/manager-web/src/views/home.vue:33 — This <i> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.
AC2 · Forms & labels · <textarea> without a programmatic label · ×3
  • <textarea> without a programmatic label main/manager-mobile/src/pages/agent/edit.vue:1368 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
  • <textarea> without a programmatic label main/manager-mobile/src/pages/agent/tools.vue:523 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
  • <textarea> without a programmatic label main/manager-mobile/src/pages/voiceprint/index.vue:506 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
AC4 · Keyboard semantics · Click handler on a non-interactive <i> · ×3
  • Click handler on a non-interactive <i> main/manager-web/src/components/ChatHistoryDialog.vue:65 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <i> main/manager-web/src/views/AddressBookManagement.vue:85 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <i> main/manager-web/src/views/AddressBookManagement.vue:115 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
AC4 · Keyboard semantics · Click handler on a non-interactive <span> · ×3
  • Click handler on a non-interactive <span> main/manager-web/src/components/HeaderBar.vue:160 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <span> main/manager-web/src/views/AddressBookManagement.vue:82 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <span> main/manager-web/src/views/AddressBookManagement.vue:114 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
D30 · Dependency Vulnerabilities · High vulnerability · ×3
  • REDACTED
  • REDACTED
  • REDACTED
D31 · IaC & Container Security · High IaC · ×3
  • REDACTED
  • REDACTED
  • REDACTED
AC2 · Forms & labels · <button> with no accessible text · ×2
  • <button> with no accessible text main/manager-web/src/components/AudioPlayer.vue:13 — A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
  • <button> with no accessible text main/manager-web/src/components/AudioPlayer.vue:44 — A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
AC3 · Page structure · <html> without a lang · ×2
  • <html> without a lang main/manager-mobile/index.html:2 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
  • <html> without a lang main/manager-web/public/index.html:2 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
R9 · Circular Imports · Import cycle (2 files) · ×2
  • Import cycle (2 files) main/digital-human/js/core/network/wakeword-bridge.js:1 — main/digital-human/js/core/network/wakeword-bridge.js → main/digital-human/js/ui/controller.js → main/digital-human/js/core/network/wakeword-bridge.js (one verified cycle inside a mutually-dependent group of 3 files)
  • Import cycle (2 files) main/manager-web/src/apis/api.js:14 — main/manager-web/src/apis/api.js → main/manager-web/src/apis/module/addressBook.js → main/manager-web/src/apis/api.js (one verified cycle inside a mutually-dependent group of 16 files)
AC2 · Forms & labels · <label> that labels no control · ×1
  • <label> that labels no control main/digital-human/index.html:298 — This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
AC2 · Forms & labels · Custom control with no accessible name on <img> · ×1
  • Custom control with no accessible name on <img> main/manager-web/src/components/HeaderBar.vue:159 — This <img> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.
AC4 · Keyboard semantics · Hover-only interaction on <div> · ×1
  • Hover-only interaction on <div> main/manager-web/src/components/AudioPlayer.vue:55 — This <div> binds mouse-enter and mouse-leave and nothing else — no click, no key handler, no focus handler, and no tabindex="0", so it cannot even take focus. A keyboard user cannot hover, so whatever the pair reveals or highlights is reachable with a mouse only. Bind the same state to focus/blur as well, and add tabindex="0"="0" so the element can receive that focus.
AC4 · Keyboard semantics · Click handler on a non-interactive <img> · ×1
  • Click handler on a non-interactive <img> main/manager-web/src/components/HeaderBar.vue:159 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
D13 · REDACTED Scanning · Leaked secret · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
Serious — 681 finding(s)
R4 · Test Coverage · No test reaches this file · ×40
  • No test reaches this file main/digital-human/js/ui/controller.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file main/digital-human/js/live2d/live2d.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file main/digital-human/js/core/network/websocket.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file main/digital-human/js/core/mcp/tools.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file main/manager-mobile/src/pages/device-config/components/ultrasonic-config.vue:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file main/digital-human/js/core/audio/recorder.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file main/manager-mobile/src/pages/device/index.vue:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file main/manager-mobile/src/pages/voiceprint/index.vue:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file main/digital-human/js/app.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file main/manager-mobile/src/utils/uploadFile.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file main/manager-mobile/src/pages/register/index.vue:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file main/manager-mobile/src/pages/chat-history/detail.vue:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file main/manager-mobile/src/pages/forgot-password/index.vue:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file main/digital-human/js/core/audio/player.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file main/manager-mobile/src/pages/settings/index.vue:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file main/manager-mobile/src/pages/login/index.vue:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file main/manager-mobile/src/pages/agent/tools.vue:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file main/digital-human/js/core/network/wakeword-bridge.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file main/digital-human/js/core/audio/stream-context.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file main/manager-mobile/src/pages/device-config/components/wifi-selector.vue:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file main/manager-mobile/src/pages/index/index.vue:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file main/manager-mobile/src/pages/chat-history/index.vue:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file main/digital-human/js/core/audio/opus-codec.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file main/manager-web/src/App.vue:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file main/manager-web/src/components/CacheViewer.vue:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • + 15 more in this group — see findings.md.
D30 · Dependency Vulnerabilities · Medium CVE · ×37
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • + 12 more in this group — see findings.md.
X3 · Exception handling · Swallowed exception (empty catch) · ×29
  • Swallowed exception (empty catch) main/xiaozhi-server/scripts/capacity_bench.py:246 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) main/xiaozhi-server/scripts/capacity_bench.py:253 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) main/xiaozhi-server/scripts/capacity_bench.py:476 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) main/xiaozhi-server/scripts/capacity_bench.py:581 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) main/xiaozhi-server/scripts/registry_verify.py:94 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) main/xiaozhi-server/scripts/ws_lifecycle_smoke.py:210 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) main/xiaozhi-server/scripts/ws_lifecycle_smoke.py:227 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) main/xiaozhi-server/scripts/ws_lifecycle_smoke.py:310 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) main/xiaozhi-server/scripts/ws_lifecycle_smoke.py:358 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) main/xiaozhi-server/plugins_func/functions/search_from_ragflow.py:121 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) main/xiaozhi-server/performance_tester/performance_tester_stream_asr.py:192 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) main/xiaozhi-server/models/snakers4_silero-vad/src/silero_vad/__init__.py:4 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) main/xiaozhi-server/core/connection.py:373 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) main/xiaozhi-server/core/connection.py:396 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) main/xiaozhi-server/core/connection.py:1373 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) main/xiaozhi-server/core/connection.py:1958 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) main/xiaozhi-server/core/connection.py:1978 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) main/xiaozhi-server/core/connection.py:2004 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) main/xiaozhi-server/core/connection.py:2118 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) main/xiaozhi-server/core/connection.py:2137 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) main/xiaozhi-server/core/connection.py:2177 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. On a teardown path letting it propagate is not an option (throwing out of `close()` masks the failure already in flight and abandons the rest of the cleanup), so make the swallow deliberate instead: narrow the catch to the exception this release can actually raise, and record it through whatever this codebase already uses to report problems — or, if it truly cannot matter, say why in a comment on the catch.
  • Swallowed exception (empty catch) main/xiaozhi-server/core/connection.py:2202 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. On a teardown path letting it propagate is not an option (throwing out of `close()` masks the failure already in flight and abandons the rest of the cleanup), so make the swallow deliberate instead: narrow the catch to the exception this release can actually raise, and record it through whatever this codebase already uses to report problems — or, if it truly cannot matter, say why in a comment on the catch.
  • Swallowed exception (empty catch) main/xiaozhi-server/core/connection.py:2283 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. On a teardown path letting it propagate is not an option (throwing out of `close()` masks the failure already in flight and abandons the rest of the cleanup), so make the swallow deliberate instead: narrow the catch to the exception this release can actually raise, and record it through whatever this codebase already uses to report problems — or, if it truly cannot matter, say why in a comment on the catch.
  • Swallowed exception (empty catch) main/xiaozhi-server/core/websocket_server.py:207 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) main/xiaozhi-server/core/websocket_server.py:324 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • + 4 more in this group — see findings.md.
P7 · Outbound HTTP resilience · Outbound HTTP without resilience · ×25
  • Outbound HTTP without resilience main/manager-api/src/main/java/xiaozhi/modules/llm/service/impl/OpenAIStyleLLMServiceImpl.java:47 — `new RestTemplate(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
  • Outbound HTTP without resilience main/manager-api/src/main/java/xiaozhi/modules/voiceclone/service/impl/VoiceCloneServiceImpl.java:340 — `HttpClient.newHttpClient(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
  • Outbound HTTP without resilience REDACTED:78 — `requests.get(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
  • Outbound HTTP without resilience REDACTED:62 — `requests.get(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
  • Outbound HTTP without resilience main/xiaozhi-server/core/providers/asr/openai.py:51 — `requests.post(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
  • Outbound HTTP without resilience main/xiaozhi-server/core/providers/asr/tencent.py:188 — `requests.post(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
  • Outbound HTTP without resilience main/xiaozhi-server/core/providers/llm/dify/dify.py:49 — `requests.post(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
  • Outbound HTTP without resilience main/xiaozhi-server/core/providers/llm/fastgpt/fastgpt.py:26 — `requests.post(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
  • Outbound HTTP without resilience main/xiaozhi-server/core/providers/llm/gemini/gemini.py:21 — `requests.get(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
  • Outbound HTTP without resilience main/xiaozhi-server/core/providers/llm/homeassistant/homeassistant.py:42 — `requests.post(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
  • Outbound HTTP without resilience REDACTED:76 — `requests.get(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
  • Outbound HTTP without resilience REDACTED:191 — `requests.post(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
  • Outbound HTTP without resilience REDACTED:196 — `requests.post(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
  • Outbound HTTP without resilience REDACTED:78 — `requests.get(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
  • Outbound HTTP without resilience main/xiaozhi-server/core/providers/tts/cozecn.py:49 — `requests.request(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
  • Outbound HTTP without resilience main/xiaozhi-server/core/providers/tts/custom.py:41 — `requests.post(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
  • Outbound HTTP without resilience main/xiaozhi-server/core/providers/tts/custom.py:43 — `requests.get(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
  • Outbound HTTP without resilience main/xiaozhi-server/core/providers/tts/doubao.py:82 — `requests.post(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
  • Outbound HTTP without resilience main/xiaozhi-server/core/providers/tts/fishspeech.py:163 — `requests.post(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
  • Outbound HTTP without resilience main/xiaozhi-server/core/providers/tts/gpt_sovits_v2.py:93 — `requests.post(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
  • Outbound HTTP without resilience main/xiaozhi-server/core/providers/tts/gpt_sovits_v3.py:54 — `requests.get(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
  • Outbound HTTP without resilience main/xiaozhi-server/core/providers/tts/openai.py:50 — `requests.post(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
  • Outbound HTTP without resilience main/xiaozhi-server/core/providers/tts/siliconflow.py:41 — `requests.request(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
  • Outbound HTTP without resilience main/xiaozhi-server/core/providers/tts/tencent.py:156 — `requests.post(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
  • Outbound HTTP without resilience main/xiaozhi-server/core/utils/util.py:90 — `requests.get(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
D15 · Churn × Complexity Hotspots · Hotspot · ×16
  • Hotspot: main/xiaozhi-server/core/connection.py main/xiaozhi-server/core/connection.py:1389 — main/xiaozhi-server/core/connection.py changed 20 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 86 in ConnectionHandler._chat_body at line 1389. 7 of those changes were fix/bug commits, and the other 13 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-05-23..2026-08-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-05-23 10:00:04 +08:00' --until='2026-08-21 10:00:04 +08:00' --full-history --no-merges -- main/xiaozhi-server/core/connection.py`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: main/manager-api/src/main/java/xiaozhi/modules/agent/service/impl/AgentServiceImpl.java main/manager-api/src/main/java/xiaozhi/modules/agent/service/impl/AgentServiceImpl.java:365 — main/manager-api/src/main/java/xiaozhi/modules/agent/service/impl/AgentServiceImpl.java changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 41 in AgentServiceImpl.updateAgentById at line 365. 5 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-05-23..2026-08-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-05-23 10:00:04 +08:00' --until='2026-08-21 10:00:04 +08:00' --full-history --no-merges -- main/manager-api/src/main/java/xiaozhi/modules/agent/service/impl/AgentServiceImpl.java`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: main/xiaozhi-server/config/config_loader.py main/xiaozhi-server/config/config_loader.py:96 — main/xiaozhi-server/config/config_loader.py changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 33 in config_loader.get_config_from_api_async at line 96. 2 of those changes were fix/bug commits, and the other 7 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-05-23..2026-08-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-05-23 10:00:04 +08:00' --until='2026-08-21 10:00:04 +08:00' --full-history --no-merges -- main/xiaozhi-server/config/config_loader.py`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: main/xiaozhi-server/core/handle/receiveAudioHandle.py main/xiaozhi-server/core/handle/receiveAudioHandle.py:55 — main/xiaozhi-server/core/handle/receiveAudioHandle.py changed 11 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 24 in receiveAudioHandle.startToChat at line 55. 6 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-05-23..2026-08-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-05-23 10:00:04 +08:00' --until='2026-08-21 10:00:04 +08:00' --full-history --no-merges -- main/xiaozhi-server/core/handle/receiveAudioHandle.py`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: main/manager-api/src/main/java/xiaozhi/modules/device/service/impl/DeviceServiceImpl.java main/manager-api/src/main/java/xiaozhi/modules/device/service/impl/DeviceServiceImpl.java:195 — main/manager-api/src/main/java/xiaozhi/modules/device/service/impl/DeviceServiceImpl.java changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 24 in DeviceServiceImpl.checkDeviceActive at line 195. 6 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-05-23..2026-08-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-05-23 10:00:04 +08:00' --until='2026-08-21 10:00:04 +08:00' --full-history --no-merges -- main/manager-api/src/main/java/xiaozhi/modules/device/service/impl/DeviceServiceImpl.java`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: main/xiaozhi-server/core/websocket_server.py main/xiaozhi-server/core/websocket_server.py:245 — main/xiaozhi-server/core/websocket_server.py changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 24 in WebSocketServer.update_config at line 245. 3 of those changes were fix/bug commits, and the other 6 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-05-23..2026-08-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-05-23 10:00:04 +08:00' --until='2026-08-21 10:00:04 +08:00' --full-history --no-merges -- main/xiaozhi-server/core/websocket_server.py`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: main/xiaozhi-server/core/handle/textHandler/listenMessageHandler.py main/xiaozhi-server/core/handle/textHandler/listenMessageHandler.py:34 — main/xiaozhi-server/core/handle/textHandler/listenMessageHandler.py changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 28 in ListenTextMessageHandler.handle at line 34. 2 of those changes were fix/bug commits, and the other 5 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-05-23..2026-08-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-05-23 10:00:04 +08:00' --until='2026-08-21 10:00:04 +08:00' --full-history --no-merges -- main/xiaozhi-server/core/handle/textHandler/listenMessageHandler.py`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: main/xiaozhi-server/core/utils/session_state.py main/xiaozhi-server/core/utils/session_state.py:639 — main/xiaozhi-server/core/utils/session_state.py changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 26 in session_state.speak_broadcast_text at line 639. 5 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-05-23..2026-08-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-05-23 10:00:04 +08:00' --until='2026-08-21 10:00:04 +08:00' --full-history --no-merges -- main/xiaozhi-server/core/utils/session_state.py`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: main/xiaozhi-server/core/providers/asr/base.py main/xiaozhi-server/core/providers/asr/base.py:313 — main/xiaozhi-server/core/providers/asr/base.py changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 29 in ASRProviderBase.speech_to_text_wrapper at line 313. 1 of those changes was a fix/bug commit, and the other 4 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-05-23..2026-08-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-05-23 10:00:04 +08:00' --until='2026-08-21 10:00:04 +08:00' --full-history --no-merges -- main/xiaozhi-server/core/providers/asr/base.py`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: main/xiaozhi-server/core/providers/tts/base.py main/xiaozhi-server/core/providers/tts/base.py:294 — main/xiaozhi-server/core/providers/tts/base.py changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 26 in TTSProviderBase.to_tts at line 294. 2 of those changes were fix/bug commits, and the other 3 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-05-23..2026-08-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-05-23 10:00:04 +08:00' --until='2026-08-21 10:00:04 +08:00' --full-history --no-merges -- main/xiaozhi-server/core/providers/tts/base.py`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: main/manager-web/src/views/roleConfig.vue main/manager-web/src/views/roleConfig.vue:865 — main/manager-web/src/views/roleConfig.vue changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 23 in applyTemplateData at line 865. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-05-23..2026-08-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-05-23 10:00:04 +08:00' --until='2026-08-21 10:00:04 +08:00' --full-history --no-merges -- main/manager-web/src/views/roleConfig.vue`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: main/manager-mobile/src/pages/agent/edit.vue main/manager-mobile/src/pages/agent/edit.vue:724 — main/manager-mobile/src/pages/agent/edit.vue changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 28 in selectRoleTemplate at line 724. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-05-23..2026-08-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-05-23 10:00:04 +08:00' --until='2026-08-21 10:00:04 +08:00' --full-history --no-merges -- main/manager-mobile/src/pages/agent/edit.vue`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: main/xiaozhi-server/core/utils/resilience.py main/xiaozhi-server/core/utils/resilience.py:216 — main/xiaozhi-server/core/utils/resilience.py changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 30 in resilience.get_resilience_settings at line 216. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-05-23..2026-08-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-05-23 10:00:04 +08:00' --until='2026-08-21 10:00:04 +08:00' --full-history --no-merges -- main/xiaozhi-server/core/utils/resilience.py`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: main/xiaozhi-server/core/handle/intentHandler.py main/xiaozhi-server/core/handle/intentHandler.py:95 — main/xiaozhi-server/core/handle/intentHandler.py changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in intentHandler.process_intent_result at line 95. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-05-23..2026-08-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-05-23 10:00:04 +08:00' --until='2026-08-21 10:00:04 +08:00' --full-history --no-merges -- main/xiaozhi-server/core/handle/intentHandler.py`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: main/xiaozhi-server/core/utils/dialogue.py main/xiaozhi-server/core/utils/dialogue.py:94 — main/xiaozhi-server/core/utils/dialogue.py changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in Dialogue.get_llm_dialogue_with_memory at line 94. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-05-23..2026-08-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-05-23 10:00:04 +08:00' --until='2026-08-21 10:00:04 +08:00' --full-history --no-merges -- main/xiaozhi-server/core/utils/dialogue.py`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: main/manager-api/src/main/java/xiaozhi/modules/knowledge/service/impl/KnowledgeBaseServiceImpl.java main/manager-api/src/main/java/xiaozhi/modules/knowledge/service/impl/KnowledgeBaseServiceImpl.java:91 — main/manager-api/src/main/java/xiaozhi/modules/knowledge/service/impl/KnowledgeBaseServiceImpl.java changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in KnowledgeBaseServiceImpl.syncDatasetFromRAG at line 91. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-05-23..2026-08-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-05-23 10:00:04 +08:00' --until='2026-08-21 10:00:04 +08:00' --full-history --no-merges -- main/manager-api/src/main/java/xiaozhi/modules/knowledge/service/impl/KnowledgeBaseServiceImpl.java`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
D29 · Static Analysis (SAST) · REDACTED · ×14
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
X24 · Document value interpolated into markup unescaped · Untrusted text written into markup unescaped · ×14
  • Untrusted text written into markup unescaped main/digital-human/js/core/mcp/tools.js:74 — `tool.name` is text this program did not author, and it is written into the text of an element through markup built here with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped main/digital-human/js/core/mcp/tools.js:84 — `tool.description` is text this program did not author, and it is written into the text of an element through markup built here with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped main/digital-human/js/core/mcp/tools.js:92 — `hasMockResponse?'✅ 已配置: '+JSON.stringify(tool.mockResponse):'⚪ 使用默认'` is text this program did not author, and it is written into the text of an element through markup built here with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped main/digital-human/js/core/mcp/tools.js:123 — `prop.name` is text this program did not author, and it is written into the text of an element through markup built here with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped main/digital-human/js/core/mcp/tools.js:127 — `getTypeLabel(prop.type)` is text this program did not author, and it is written into the text of an element through markup built here with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped main/digital-human/js/core/mcp/tools.js:131 — `prop.description||'-'` is text this program did not author, and it is written into the text of an element through markup built here with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped main/digital-human/js/core/mcp/tools.js:434 — `message` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped main/digital-human/js/ui/controller.js:446 — `content` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped main/digital-human/js/ui/controller.js:846 — `toolId` is text this program did not author, and it is written into a script or style context through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. A script or style context needs its own escaping (or a JSON serialiser that escapes `<`); better, pass the value through a data attribute.
  • Untrusted text written into markup unescaped main/manager-web/src/components/AgentSnapshotDialog.vue:199 — `renderMarkdownValue(item.afterValue)` is text this program did not author, and it is written into the text of an element through Vue's `v-html` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped main/manager-web/src/components/AgentSnapshotDialog.vue:279 — `renderMarkdownValue(item.beforeValue)` is text this program did not author, and it is written into the text of an element through Vue's `v-html` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped main/manager-web/src/components/AgentSnapshotDialog.vue:290 — `renderMarkdownValue(item.afterValue)` is text this program did not author, and it is written into the text of an element through Vue's `v-html` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped main/manager-web/src/components/AgentSnapshotDialog.vue:411 — `renderMarkdownValue(item.beforeValue)` is text this program did not author, and it is written into the text of an element through Vue's `v-html` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped main/manager-web/src/components/AgentSnapshotDialog.vue:422 — `renderMarkdownValue(item.afterValue)` is text this program did not author, and it is written into the text of an element through Vue's `v-html` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
PF3 · Async & latency hygiene · Sync-over-async blocking · ×12
  • Sync-over-async blocking main/xiaozhi-server/core/providers/asr/fun_local.py:71 — `speech_to_text` is async and calls time.sleep — a blocking call inside async code stalls the event loop — every other task on it waits for as long as it runs.
  • Sync-over-async blocking main/xiaozhi-server/core/providers/asr/openai.py:27 — `speech_to_text` is async and calls requests.post — a blocking call inside async code stalls the event loop — every other task on it waits for as long as it runs.
  • Sync-over-async blocking REDACTED:173 — `text_to_speak` is async and calls requests.post — a blocking call inside async code stalls the event loop — every other task on it waits for as long as it runs.
  • Sync-over-async blocking main/xiaozhi-server/core/providers/tts/cozecn.py:33 — `text_to_speak` is async and calls requests.request — a blocking call inside async code stalls the event loop — every other task on it waits for as long as it runs.
  • Sync-over-async blocking main/xiaozhi-server/core/providers/tts/custom.py:33 — `text_to_speak` is async and calls requests.post, requests.get — a blocking call inside async code stalls the event loop — every other task on it waits for as long as it runs.
  • Sync-over-async blocking main/xiaozhi-server/core/providers/tts/doubao.py:56 — `text_to_speak` is async and calls requests.post — a blocking call inside async code stalls the event loop — every other task on it waits for as long as it runs.
  • Sync-over-async blocking main/xiaozhi-server/core/providers/tts/fishspeech.py:137 — `text_to_speak` is async and calls requests.post — a blocking call inside async code stalls the event loop — every other task on it waits for as long as it runs.
  • Sync-over-async blocking main/xiaozhi-server/core/providers/tts/gpt_sovits_v2.py:70 — `text_to_speak` is async and calls requests.post — a blocking call inside async code stalls the event loop — every other task on it waits for as long as it runs.
  • Sync-over-async blocking main/xiaozhi-server/core/providers/tts/gpt_sovits_v3.py:37 — `text_to_speak` is async and calls requests.get — a blocking call inside async code stalls the event loop — every other task on it waits for as long as it runs.
  • Sync-over-async blocking main/xiaozhi-server/core/providers/tts/openai.py:38 — `text_to_speak` is async and calls requests.post — a blocking call inside async code stalls the event loop — every other task on it waits for as long as it runs.
  • Sync-over-async blocking main/xiaozhi-server/core/providers/tts/siliconflow.py:29 — `text_to_speak` is async and calls requests.request — a blocking call inside async code stalls the event loop — every other task on it waits for as long as it runs.
  • Sync-over-async blocking main/xiaozhi-server/core/providers/tts/tencent.py:139 — `text_to_speak` is async and calls requests.post — a blocking call inside async code stalls the event loop — every other task on it waits for as long as it runs.
D31 · IaC & Container Security · Medium IaC · ×11
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
X3 · Exception handling · Swallowed exception (caught, then discarded) · ×11
  • Swallowed exception (caught, then discarded) main/xiaozhi-server/scripts/capacity_bench.py:157 — `except Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) main/xiaozhi-server/scripts/capacity_bench.py:318 — `except Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) main/xiaozhi-server/scripts/capacity_bench.py:446 — `except Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) main/xiaozhi-server/scripts/capacity_bench.py:468 — `except Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) main/xiaozhi-server/scripts/capacity_bench.py:533 — `except Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) main/xiaozhi-server/scripts/capacity_bench.py:573 — `except Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) main/xiaozhi-server/scripts/ws_lifecycle_smoke.py:403 — `except Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) main/xiaozhi-server/core/auth.py:71 — `except Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) main/xiaozhi-server/core/connection.py:219 — `except Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) main/xiaozhi-server/core/utils/bounded_queue.py:61 — `except Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) main/xiaozhi-server/core/utils/current_time.py:54 — `except Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
AC3 · Page structure · Page without a main landmark · ×9
  • Page without a main landmark main/digital-human/index.html:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark main/manager-mobile/index.html:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="app">, so there is no content here to wrap — render the <main> from the component mounted into it.
  • Page without a main landmark main/manager-web/public/generator/index.html:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="app">, so there is no content here to wrap — render the <main> from the component mounted into it.
  • Page without a main landmark main/manager-web/public/index.html:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="app">, so there is no content here to wrap — render the <main> from the component mounted into it.
  • Page without a main landmark main/manager-web/public/offline.html:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark main/manager-web/public/privacy-policy-en.html:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark main/manager-web/public/privacy-policy.html:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark main/manager-web/public/user-agreement-en.html:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark main/manager-web/public/user-agreement.html:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
D35 · Change Coupling · Change coupling · ×9
  • Change coupling: Constant.java ↔ index.vue main/manager-api/src/main/java/xiaozhi/common/constant/Constant.java:1 — `main/manager-api/src/main/java/xiaozhi/common/constant/Constant.java` and `main/manager-mobile/src/pages/settings/index.vue` change together 67% of the time (18 of the 27 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) and are written in DIFFERENT LANGUAGES, so no import can join them and they cannot be co-located into one unit — they compile and ship as separate artifacts. What binds them is a CONTRACT across that boundary — an event or message name, a route, a serialised shape — that each side currently spells out on its own, which is exactly why a change to one drags the other. Declare that contract once where both sides read it (a shared schema, a generated constants file, an interface-definition file) so a change on one side fails the other's build instead of drifting silently; where the surface is too small to be worth that, name the counterpart in a comment on both sides so the next reader finds it. There is nothing here to merge. You can check this without leaving the row: of the 18 shared commits counted here, the most recent 3 are `9da58e25` Bump to 0.9.6; `f77970dd` update:Bump to 0.9.5; `370d148a` Bump to 0.9.4 — run `git show` on any of them.
  • Change coupling: Constant.java ↔ logger.py main/manager-api/src/main/java/xiaozhi/common/constant/Constant.java:1 — `main/manager-api/src/main/java/xiaozhi/common/constant/Constant.java` and `main/xiaozhi-server/config/logger.py` change together 59% of the time (41 of the 70 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) and are written in DIFFERENT LANGUAGES, so no import can join them and they cannot be co-located into one unit — they compile and ship as separate artifacts. What binds them is a CONTRACT across that boundary — an event or message name, a route, a serialised shape — that each side currently spells out on its own, which is exactly why a change to one drags the other. Declare that contract once where both sides read it (a shared schema, a generated constants file, an interface-definition file) so a change on one side fails the other's build instead of drifting silently; where the surface is too small to be worth that, name the counterpart in a comment on both sides so the next reader finds it. There is nothing here to merge. You can check this without leaving the row: of the 41 shared commits counted here, the most recent 3 are `9da58e25` Bump to 0.9.6; `f77970dd` update:Bump to 0.9.5; `370d148a` Bump to 0.9.4 — run `git show` on any of them.
  • Change coupling: intentHandler.py ↔ REDACTED main/xiaozhi-server/core/handle/intentHandler.py:1 — `main/xiaozhi-server/core/handle/intentHandler.py` and `REDACTED` change together 58% of the time (15 of the 26 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 15 shared commits counted here, the most recent 3 are `ed89c052` fix: intent阻塞主线程; `0738c52d` fix:修复LLM意图识别的若干问题; `3b34d687` "fix: 修复MCP工具调用参数类型错误问题,无参调用时提供默认空字典" — run `git show` on any of them.
  • Change coupling: ModelController.java ↔ ModelConfigServiceImpl.java main/manager-api/src/main/java/xiaozhi/modules/model/controller/ModelController.java:1 — `main/manager-api/src/main/java/xiaozhi/modules/model/controller/ModelController.java` and `main/manager-api/src/main/java/xiaozhi/modules/model/service/impl/ModelConfigServiceImpl.java` change together 55% of the time (6 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `be7146fa` 添加新接口,获取llm模型基础模型信息 --LlmModelBasicInfoDTO.java 新的llm模型基础模型信息返回对象 --M…; `e00da5d8` update:智控台可设置允许用户自由注册 (#809); `50897e97` update:完成角色配置功能 (#679) — run `git show` on any of them.
  • Change coupling: app.js ↔ websocket.js main/digital-human/js/app.js:1 — `main/digital-human/js/app.js` and `main/digital-human/js/core/network/websocket.js` change together 53% of the time (8 of the 15 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `7b3db722` update:优化 (at that commit the files were still `main/xiaozhi-server/test/js/app.js` and `main/xiaozhi-server/test/js/core/network/websocket.js`); `e4cfabeb` update: 优化代码 (at that commit the files were still `main/xiaozhi-server/test/js/app.js` and `main/xiaozhi-server/test/js/core/network/websocket.js`); `85a83727` feat: 摄像头验证码绑定检查 && 视觉分析URL动态获取 (at that commit the files were still `main/xiaozhi-server/test/js/app.js` and `main/xiaozhi-server/test/js/core/network/websocket.js`) — run `git show` on any of them.
  • Change coupling: connection.py ↔ mem_local_short.py main/xiaozhi-server/core/connection.py:1 — `main/xiaozhi-server/core/connection.py` and `main/xiaozhi-server/core/providers/memory/mem_local_short/mem_local_short.py` change together 53% of the time (8 of the 15 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `6ae0af27` feat: 统一LLM错误处理并添加系统错误回复配置; `d6697948` fix:使用java端做聊天记录总结; `fb5c35e6` 后台初始化组件,gc全局化避免每次回收触发GIL锁,音频定时发送 — run `git show` on any of them.
  • Change coupling: connection.py ↔ silero.py main/xiaozhi-server/core/connection.py:1 — `main/xiaozhi-server/core/connection.py` and `main/xiaozhi-server/core/providers/vad/silero.py` change together 53% of the time (9 of the 17 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `a6904f6e` refactor: vad独立时间戳,相关残余状态处理; `fd829626` fix:高并发下,共享vad里decoder变量扰动; `4645c50f` update:将垃圾回收放置ws关闭处,避免频繁操作 — run `git show` on any of them.
  • Change coupling: DeviceController.java ↔ DeviceServiceImpl.java main/manager-api/src/main/java/xiaozhi/modules/device/controller/DeviceController.java:1 — `main/manager-api/src/main/java/xiaozhi/modules/device/controller/DeviceController.java` and `main/manager-api/src/main/java/xiaozhi/modules/device/service/impl/DeviceServiceImpl.java` change together 52% of the time (12 of the 23 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 12 shared commits counted here, the most recent 3 are `e87fc766` fix: restore device auto-update switch behavior; `ec5063f0` fix: 设备最后连接时间返回 UTC 时间戳,修复时区显示问题; `de78e87c` 调整逻辑使用java端作为中转发送 — run `git show` on any of them.
  • Change coupling: AgentChatHistoryServiceImpl.java ↔ AgentServiceImpl.java main/manager-api/src/main/java/xiaozhi/modules/agent/service/impl/AgentChatHistoryServiceImpl.java:1 — `main/manager-api/src/main/java/xiaozhi/modules/agent/service/impl/AgentChatHistoryServiceImpl.java` and `main/manager-api/src/main/java/xiaozhi/modules/agent/service/impl/AgentServiceImpl.java` change together 50% of the time (8 of the 16 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `4a2c90ec` refactor(manager-api): 升级常用工具依赖并收敛冗余实现; `d7604654` fix(manager-api): make JSON collections type-safe; `aae2ef21` fix: prevent agent IDOR access — run `git show` on any of them.
R11 · Import Boundaries · Boundary violation [package · ×9
  • Boundary violation [package:third-party-deep-import] main/manager-mobile/src/App.vue:8 — main/manager-mobile/src/App.vue:8 imports abortcontroller-polyfill/dist/abortcontroller-polyfill-only, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] main/manager-web/src/apis/httpRequest.js:1 — main/manager-web/src/apis/httpRequest.js:1 imports flyio/dist/npm/fly, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] main/manager-web/src/i18n/index.js:10 — main/manager-web/src/i18n/index.js:10 imports element-ui/lib/locale/lang/en, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] main/manager-web/src/i18n/index.js:11 — main/manager-web/src/i18n/index.js:11 imports element-ui/lib/locale/lang/zh-CN, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] main/manager-web/src/i18n/index.js:12 — main/manager-web/src/i18n/index.js:12 imports element-ui/lib/locale/lang/zh-TW, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] main/manager-web/src/i18n/index.js:13 — main/manager-web/src/i18n/index.js:13 imports element-ui/lib/locale/lang/de, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] main/manager-web/src/i18n/index.js:14 — main/manager-web/src/i18n/index.js:14 imports element-ui/lib/locale/lang/vi, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] main/manager-web/src/i18n/index.js:15 — main/manager-web/src/i18n/index.js:15 imports element-ui/lib/locale/lang/pt-br, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] main/manager-web/src/main.js:9 — main/manager-web/src/main.js:9 imports element-ui/lib/locale, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
X1 · Async correctness · Task from `asyncio.create_task` is not kept · ×9
  • Task from `asyncio.create_task` is not kept main/xiaozhi-server/core/providers/tools/mcp_endpoint/mcp_endpoint_handler.py:26 — The task this creates is not kept anywhere. The event loop holds only a weak reference to its tasks, so a task nobody references can be garbage-collected before it finishes (Python's documentation for `asyncio.create_task`: save a reference to the result); and nothing ever awaits it, so an exception it raises is never handled — it surfaces, if at all, as "Task exception was never retrieved" in a log. Keep the task: `await` it, gather it, start it in an `asyncio.TaskGroup` (`async with asyncio.TaskGroup() as tg: tg.create_task(…)`), or, for genuine fire-and-forget, add it to a set and `task.add_done_callback(tasks.discard)` with a callback that also reads its exception.
  • Task from `asyncio.create_task` is not kept main/xiaozhi-server/core/providers/asr/doubao_stream.py:262 — The task this creates is not kept anywhere. The event loop holds only a weak reference to its tasks, so a task nobody references can be garbage-collected before it finishes (Python's documentation for `asyncio.create_task`: save a reference to the result); and nothing ever awaits it, so an exception it raises is never handled — it surfaces, if at all, as "Task exception was never retrieved" in a log. Keep the task: `await` it, gather it, start it in an `asyncio.TaskGroup` (`async with asyncio.TaskGroup() as tg: tg.create_task(…)`), or, for genuine fire-and-forget, add it to a set and `task.add_done_callback(tasks.discard)` with a callback that also reads its exception.
  • Task from `asyncio.create_task` is not kept main/xiaozhi-server/core/providers/asr/xunfei_stream.py:276 — The task this creates is not kept anywhere. The event loop holds only a weak reference to its tasks, so a task nobody references can be garbage-collected before it finishes (Python's documentation for `asyncio.create_task`: save a reference to the result); and nothing ever awaits it, so an exception it raises is never handled — it surfaces, if at all, as "Task exception was never retrieved" in a log. Keep the task: `await` it, gather it, start it in an `asyncio.TaskGroup` (`async with asyncio.TaskGroup() as tg: tg.create_task(…)`), or, for genuine fire-and-forget, add it to a set and `task.add_done_callback(tasks.discard)` with a callback that also reads its exception.
  • Task from `asyncio.create_task` is not kept main/xiaozhi-server/core/handle/helloHandle.py:63 — The task this creates is not kept anywhere. The event loop holds only a weak reference to its tasks, so a task nobody references can be garbage-collected before it finishes (Python's documentation for `asyncio.create_task`: save a reference to the result); and nothing ever awaits it, so an exception it raises is never handled — it surfaces, if at all, as "Task exception was never retrieved" in a log. Keep the task: `await` it, gather it, start it in an `asyncio.TaskGroup` (`async with asyncio.TaskGroup() as tg: tg.create_task(…)`), or, for genuine fire-and-forget, add it to a set and `task.add_done_callback(tasks.discard)` with a callback that also reads its exception.
  • Task from `asyncio.create_task` is not kept main/xiaozhi-server/core/handle/helloHandle.py:160 — The task this creates is not kept anywhere. The event loop holds only a weak reference to its tasks, so a task nobody references can be garbage-collected before it finishes (Python's documentation for `asyncio.create_task`: save a reference to the result); and nothing ever awaits it, so an exception it raises is never handled — it surfaces, if at all, as "Task exception was never retrieved" in a log. Keep the task: `await` it, gather it, start it in an `asyncio.TaskGroup` (`async with asyncio.TaskGroup() as tg: tg.create_task(…)`), or, for genuine fire-and-forget, add it to a set and `task.add_done_callback(tasks.discard)` with a callback that also reads its exception.
  • Task from `asyncio.create_task` is not kept main/xiaozhi-server/core/handle/textHandler/iotMessageHandler.py:20 — The task this creates is not kept anywhere. The event loop holds only a weak reference to its tasks, so a task nobody references can be garbage-collected before it finishes (Python's documentation for `asyncio.create_task`: save a reference to the result); and nothing ever awaits it, so an exception it raises is never handled — it surfaces, if at all, as "Task exception was never retrieved" in a log. Keep the task: `await` it, gather it, start it in an `asyncio.TaskGroup` (`async with asyncio.TaskGroup() as tg: tg.create_task(…)`), or, for genuine fire-and-forget, add it to a set and `task.add_done_callback(tasks.discard)` with a callback that also reads its exception.
  • Task from `asyncio.create_task` is not kept main/xiaozhi-server/core/handle/textHandler/iotMessageHandler.py:22 — The task this creates is not kept anywhere. The event loop holds only a weak reference to its tasks, so a task nobody references can be garbage-collected before it finishes (Python's documentation for `asyncio.create_task`: save a reference to the result); and nothing ever awaits it, so an exception it raises is never handled — it surfaces, if at all, as "Task exception was never retrieved" in a log. Keep the task: `await` it, gather it, start it in an `asyncio.TaskGroup` (`async with asyncio.TaskGroup() as tg: tg.create_task(…)`), or, for genuine fire-and-forget, add it to a set and `task.add_done_callback(tasks.discard)` with a callback that also reads its exception.
  • Task from `asyncio.create_task` is not kept main/xiaozhi-server/core/handle/textHandler/listenMessageHandler.py:60 — The task this creates is not kept anywhere. The event loop holds only a weak reference to its tasks, so a task nobody references can be garbage-collected before it finishes (Python's documentation for `asyncio.create_task`: save a reference to the result); and nothing ever awaits it, so an exception it raises is never handled — it surfaces, if at all, as "Task exception was never retrieved" in a log. Keep the task: `await` it, gather it, start it in an `asyncio.TaskGroup` (`async with asyncio.TaskGroup() as tg: tg.create_task(…)`), or, for genuine fire-and-forget, add it to a set and `task.add_done_callback(tasks.discard)` with a callback that also reads its exception.
  • Task from `asyncio.create_task` is not kept main/xiaozhi-server/core/handle/textHandler/mcpMessageHandler.py:20 — The task this creates is not kept anywhere. The event loop holds only a weak reference to its tasks, so a task nobody references can be garbage-collected before it finishes (Python's documentation for `asyncio.create_task`: save a reference to the result); and nothing ever awaits it, so an exception it raises is never handled — it surfaces, if at all, as "Task exception was never retrieved" in a log. Keep the task: `await` it, gather it, start it in an `asyncio.TaskGroup` (`async with asyncio.TaskGroup() as tg: tg.create_task(…)`), or, for genuine fire-and-forget, add it to a set and `task.add_done_callback(tasks.discard)` with a callback that also reads its exception.
D4 · Code Duplication · Duplicated block (7 lines × 2) · ×8
  • Duplicated block (7 lines × 2) main/xiaozhi-server/core/websocket_server.py:83 — main/xiaozhi-server/core/websocket_server.py:83-89 | main/xiaozhi-server/core/websocket_server.py:297-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.
  • Duplicated block (7 lines × 2) main/xiaozhi-server/core/providers/asr/doubao_stream.py:139 — main/xiaozhi-server/core/providers/asr/doubao_stream.py:139-145 | main/xiaozhi-server/core/providers/asr/xunfei_stream.py:162-168 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (7 lines × 2) main/xiaozhi-server/core/providers/asr/fun_local.py:31 — main/xiaozhi-server/core/providers/asr/fun_local.py:31-37 | main/xiaozhi-server/core/providers/asr/sherpa_onnx_local.py:28-34 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (7 lines × 2) main/xiaozhi-server/core/providers/tools/device_mcp/mcp_client.py:16 — main/xiaozhi-server/core/providers/tools/device_mcp/mcp_client.py:16-22 | main/xiaozhi-server/core/providers/tools/device_mcp/mcp_handler.py:23-29 — before extracting anything, compare `main/xiaozhi-server/core/providers/tools/device_mcp/mcp_client.py` and `main/xiaozhi-server/core/providers/tools/device_mcp/mcp_handler.py` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 43 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (7 lines × 2) main/manager-api/src/main/java/xiaozhi/modules/llm/service/impl/OpenAIStyleLLMServiceImpl.java:194 — main/manager-api/src/main/java/xiaozhi/modules/llm/service/impl/OpenAIStyleLLMServiceImpl.java:194-200 | main/manager-api/src/main/java/xiaozhi/modules/llm/service/impl/OpenAIStyleLLMServiceImpl.java:352-358 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `main/manager-api/src/main/java/xiaozhi/modules/llm/service/impl/OpenAIStyleLLMServiceImpl.java:194` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 2) main/manager-api/src/main/java/xiaozhi/modules/security/secret/ServerSecretFilter.java:44 — main/manager-api/src/main/java/xiaozhi/modules/security/oauth2/Oauth2Filter.java:47-53 | main/manager-api/src/main/java/xiaozhi/modules/security/secret/ServerSecretFilter.java:44-50 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (7 lines × 2) main/manager-api/src/main/java/xiaozhi/modules/agent/service/impl/AgentServiceImpl.java:129 — main/manager-api/src/main/java/xiaozhi/modules/agent/service/impl/AgentServiceImpl.java:129-135 | main/manager-api/src/main/java/xiaozhi/modules/agent/service/impl/AgentSnapshotServiceImpl.java:317-323 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (7 lines × 2) main/manager-api/src/main/java/xiaozhi/modules/device/service/impl/OtaServiceImpl.java:24 — main/manager-api/src/main/java/xiaozhi/modules/device/service/impl/OtaServiceImpl.java:24-30 | main/manager-api/src/main/java/xiaozhi/modules/voiceclone/service/impl/VoiceCloneServiceImpl.java:53-59 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Edited copy of a member (10 corresponding lines) · ×6
  • Edited copy of a member (10 corresponding lines) main/xiaozhi-server/plugins_func/functions/hass_get_state.py:34 — main/xiaozhi-server/plugins_func/functions/hass_get_state.py:34-43 | main/xiaozhi-server/plugins_func/functions/hass_set_state.py:57-68 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) main/manager-api/src/main/java/xiaozhi/modules/agent/controller/AgentController.java:272 — main/manager-api/src/main/java/xiaozhi/modules/agent/controller/AgentController.java:272-281 | main/manager-api/src/main/java/xiaozhi/modules/voiceclone/controller/VoiceCloneController.java:136-146 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) main/xiaozhi-server/plugins_func/functions/hass_play_music.py:40 — main/xiaozhi-server/plugins_func/functions/hass_play_music.py:40-49 | main/xiaozhi-server/plugins_func/functions/play_music.py:40-52 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) main/xiaozhi-server/core/utils/circuit_store.py:133 — main/xiaozhi-server/core/utils/circuit_store.py:133-142 | main/xiaozhi-server/core/utils/circuit_store.py:188-197 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) main/manager-api/src/main/java/xiaozhi/modules/knowledge/controller/KnowledgeFilesController.java:65 — main/manager-api/src/main/java/xiaozhi/modules/knowledge/controller/KnowledgeFilesController.java:65-76 | main/manager-api/src/main/java/xiaozhi/modules/knowledge/controller/KnowledgeFilesController.java:85-94 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) main/xiaozhi-server/core/utils/runtime_env.py:136 — main/xiaozhi-server/core/utils/runtime_env.py:136-147 | main/xiaozhi-server/core/utils/runtime_env.py:155-164 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (12 lines × 2) · ×6
  • Duplicated block (12 lines × 2) main/xiaozhi-server/core/utils/resilience.py:899 — main/xiaozhi-server/core/utils/resilience.py:899-910 | main/xiaozhi-server/core/utils/resilience.py:973-984 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (12 lines × 2) main/xiaozhi-server/core/utils/resilience.py:1050 — main/xiaozhi-server/core/utils/resilience.py:1050-1061 | main/xiaozhi-server/core/utils/resilience.py:1194-1205 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `main/xiaozhi-server/core/utils/resilience.py:1050` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12 lines × 2) main/xiaozhi-server/core/utils/util.py:434 — main/xiaozhi-server/core/utils/util.py:434-445 | main/xiaozhi-server/core/utils/util.py:463-474 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (12 lines × 2) main/xiaozhi-server/core/providers/asr/doubao_stream.py:419 — main/xiaozhi-server/core/providers/asr/doubao_stream.py:419-430 | main/xiaozhi-server/core/providers/asr/xunfei_stream.py:325-336 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (12 lines × 2) main/xiaozhi-server/core/providers/tts/alibl_stream.py:309 — main/xiaozhi-server/core/providers/tts/alibl_stream.py:309-321 | REDACTED:404-415 — before extracting anything, compare `main/xiaozhi-server/core/providers/tts/alibl_stream.py` and `REDACTED` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 297 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (12 lines × 2) main/manager-api/src/main/java/xiaozhi/modules/agent/service/impl/AgentSnapshotServiceImpl.java:546 — main/manager-api/src/main/java/xiaozhi/modules/agent/service/impl/AgentSnapshotServiceImpl.java:546-557 | main/manager-api/src/main/java/xiaozhi/modules/agent/service/impl/AgentSnapshotServiceImpl.java:818-829 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `main/manager-api/src/main/java/xiaozhi/modules/agent/service/impl/AgentSnapshotServiceImpl.java:546` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (8 lines × 2) · ×6
  • Duplicated block (8 lines × 2) main/xiaozhi-server/core/handle/reportHandle.py:110 — main/xiaozhi-server/core/handle/reportHandle.py:110-117 | main/xiaozhi-server/core/handle/reportHandle.py:163-170 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (8 lines × 2) main/xiaozhi-server/core/providers/tts/cozecn.py:12 — main/xiaozhi-server/core/providers/tts/cozecn.py:12-19 | main/xiaozhi-server/core/providers/tts/siliconflow.py:12-19 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `main/xiaozhi-server/core/providers/tts/siliconflow.py:20` calls `get`, `_apply_percentage_params` and `main/xiaozhi-server/core/providers/tts/cozecn.py:20` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (8 lines × 2) main/xiaozhi-server/core/utils/resilience.py:1133 — main/xiaozhi-server/core/utils/resilience.py:1133-1140 | main/xiaozhi-server/core/utils/resilience.py:1206-1215 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (8 lines × 2) main/xiaozhi-server/plugins_func/functions/hass_get_state.py:36 — main/xiaozhi-server/plugins_func/functions/hass_get_state.py:36-43 | main/xiaozhi-server/plugins_func/functions/hass_set_state.py:61-68 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (8 lines × 2) main/manager-api/src/main/java/xiaozhi/modules/security/password/BCrypt.java:283 — main/manager-api/src/main/java/xiaozhi/modules/security/password/BCrypt.java:283-290 | main/manager-api/src/main/java/xiaozhi/modules/security/password/BCrypt.java:291-298 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (8 lines × 2) main/manager-api/src/main/java/xiaozhi/modules/security/password/BCrypt.java:435 — main/manager-api/src/main/java/xiaozhi/modules/security/password/BCrypt.java:435-442 | main/manager-api/src/main/java/xiaozhi/modules/security/password/BCrypt.java:466-473 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `main/manager-api/src/main/java/xiaozhi/modules/security/password/BCrypt.java:435` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `main/manager-api/src/main/java/xiaozhi/modules/security/password/BCrypt.java:474` calls `streamtoword` and `main/manager-api/src/main/java/xiaozhi/modules/security/password/BCrypt.java:443` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
R10 · Code Duplication · Duplicated block (22 lines × 2 locations) · ×6
  • Duplicated block (22 lines × 2 locations) main/manager-mobile/src/utils/index.ts:148 — main/manager-mobile/src/utils/index.ts:148 · main/manager-mobile/src/utils/index.ts:181 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (22 lines × 2 locations) main/manager-web/src/apis/module/agent.js:139 — main/manager-web/src/apis/module/agent.js:139 · main/manager-web/src/apis/module/agent.js:167 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
  • Duplicated block (22 lines × 2 locations) main/manager-web/src/apis/module/timbre.js:31 — main/manager-web/src/apis/module/timbre.js:31 · main/manager-web/src/apis/module/timbre.js:74 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (22 lines × 2 locations) main/manager-web/src/components/DictDataDialog.vue:62 — main/manager-web/src/components/DictDataDialog.vue:62 · main/manager-web/src/components/DictTypeDialog.vue:53 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
  • Duplicated block (22 lines × 2 locations) main/manager-web/src/utils/featureManager.js:111 — main/manager-web/src/utils/featureManager.js:111 · main/manager-web/src/utils/featureManager.js:145 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
  • Duplicated block (22 lines × 2 locations) main/manager-web/src/views/roleConfig.vue:763 — main/manager-web/src/views/roleConfig.vue:763 · main/manager-web/src/views/roleConfig.vue:1838 — 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.
D4 · Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) · ×5
  • Members sharing a duplicated core (4 members, 50+ identical tokens) REDACTED:37 — REDACTED:37-87 | REDACTED:39-67 | REDACTED:35-85 | REDACTED:42-86 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) REDACTED:197 — REDACTED:197-279 | main/xiaozhi-server/core/providers/asr/aliyunbl_stream.py:158-246 | main/xiaozhi-server/core/providers/asr/doubao_stream.py:160-258 | main/xiaozhi-server/core/providers/asr/xunfei_stream.py:189-250 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) main/xiaozhi-server/core/providers/tts/alibl_stream.py:194 — main/xiaozhi-server/core/providers/tts/alibl_stream.py:194-229 | REDACTED:298-333 | main/xiaozhi-server/core/providers/tts/huoshan_double_stream.py:370-398 | main/xiaozhi-server/core/providers/tts/xunfei_stream.py:243-271 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) main/xiaozhi-server/core/providers/tts/alibl_stream.py:336 — main/xiaozhi-server/core/providers/tts/alibl_stream.py:336-407 | REDACTED:418-482 | main/xiaozhi-server/core/providers/tts/huoshan_double_stream.py:489-565 | main/xiaozhi-server/core/providers/tts/xunfei_stream.py:345-425 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) main/manager-api/src/main/java/xiaozhi/modules/knowledge/service/impl/KnowledgeFilesServiceImpl.java:320 — main/manager-api/src/main/java/xiaozhi/modules/knowledge/service/impl/KnowledgeFilesServiceImpl.java:320-358 | main/manager-api/src/main/java/xiaozhi/modules/knowledge/service/impl/KnowledgeFilesServiceImpl.java:640-691 | main/manager-api/src/main/java/xiaozhi/modules/knowledge/service/impl/KnowledgeFilesServiceImpl.java:694-719 | main/manager-api/src/main/java/xiaozhi/modules/knowledge/service/impl/KnowledgeFilesServiceImpl.java:722-747 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication · Duplicated block (11 lines × 2) · ×5
  • Duplicated block (11 lines × 2) REDACTED:261 — REDACTED:261-271 | main/xiaozhi-server/core/providers/asr/xunfei_stream.py:227-237 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `main/xiaozhi-server/core/providers/asr/xunfei_stream.py:238` calls `hasattr`, `bind`, `error` and `REDACTED:272` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (11 lines × 2) main/xiaozhi-server/core/providers/tts/index_stream.py:216 — main/xiaozhi-server/core/providers/tts/index_stream.py:216-226 | main/xiaozhi-server/core/providers/tts/minimax_httpstream.py:328-338 — before extracting anything, compare `main/xiaozhi-server/core/providers/tts/index_stream.py` and `main/xiaozhi-server/core/providers/tts/minimax_httpstream.py` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 133 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `main/xiaozhi-server/core/providers/tts/minimax_httpstream.py:328` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (11 lines × 2) main/xiaozhi-server/core/providers/tts/index_stream.py:244 — main/xiaozhi-server/core/providers/tts/index_stream.py:244-254 | main/xiaozhi-server/core/providers/tts/minimax_httpstream.py:370-380 — before extracting anything, compare `main/xiaozhi-server/core/providers/tts/index_stream.py` and `main/xiaozhi-server/core/providers/tts/minimax_httpstream.py` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 133 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (11 lines × 2) main/manager-api/src/main/java/xiaozhi/modules/agent/service/impl/AgentChatSummaryServiceImpl.java:419 — main/manager-api/src/main/java/xiaozhi/modules/agent/service/impl/AgentChatSummaryServiceImpl.java:419-429 | main/manager-api/src/main/java/xiaozhi/modules/agent/service/impl/AgentChatSummaryServiceImpl.java:445-455 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `main/manager-api/src/main/java/xiaozhi/modules/agent/service/impl/AgentChatSummaryServiceImpl.java:419` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 2) main/manager-api/src/main/java/xiaozhi/modules/security/secret/ServerSecretFilter.java:31 — main/manager-api/src/main/java/xiaozhi/modules/security/oauth2/Oauth2Filter.java:34-44 | main/manager-api/src/main/java/xiaozhi/modules/security/secret/ServerSecretFilter.java:31-41 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D15 · Churn × Complexity Hotspots · Repeated repair · ×4
  • Repeated repair: main/manager-api/src/main/java/xiaozhi/modules/device/vo/UserShowDeviceListVO.java main/manager-api/src/main/java/xiaozhi/modules/device/vo/UserShowDeviceListVO.java:12 — main/manager-api/src/main/java/xiaozhi/modules/device/vo/UserShowDeviceListVO.java changed 5 times in last 90 days and 5 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 1 (its worst body is UserShowDeviceListVO.<init> at line 12), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: restore device auto-update switch behavior”; “fix: 修复设备跨时区时间与在线状态”; “fix:用户别名缺失bug”; “fix:修复设备型号不显示的问题”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-05-23..2026-08-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-05-23 10:00:04 +08:00' --until='2026-08-21 10:00:04 +08:00' --full-history --no-merges -- main/manager-api/src/main/java/xiaozhi/modules/device/vo/UserShowDeviceListVO.java`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: main/manager-api/src/main/java/xiaozhi/modules/agent/controller/AgentController.java main/manager-api/src/main/java/xiaozhi/modules/agent/controller/AgentController.java:152 — main/manager-api/src/main/java/xiaozhi/modules/agent/controller/AgentController.java changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 3 (its worst body is AgentController.generateAndSaveChatSummary at line 152), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(manager-api): make JSON collections type-safe”; “fix: prevent agent IDOR access”; “Fix agent snapshot history issues”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-05-23..2026-08-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-05-23 10:00:04 +08:00' --until='2026-08-21 10:00:04 +08:00' --full-history --no-merges -- main/manager-api/src/main/java/xiaozhi/modules/agent/controller/AgentController.java`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: main/manager-api/src/main/java/xiaozhi/modules/agent/service/impl/AgentChatHistoryServiceImpl.java main/manager-api/src/main/java/xiaozhi/modules/agent/service/impl/AgentChatHistoryServiceImpl.java:163 — main/manager-api/src/main/java/xiaozhi/modules/agent/service/impl/AgentChatHistoryServiceImpl.java changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 7 (its worst body is AgentChatHistoryServiceImpl.extractContentFromString at line 163), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(manager-api): make JSON collections type-safe”; “fix: 修复上下文源类型处理器兼容问题”; “fix: prevent agent IDOR access”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-05-23..2026-08-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-05-23 10:00:04 +08:00' --until='2026-08-21 10:00:04 +08:00' --full-history --no-merges -- main/manager-api/src/main/java/xiaozhi/modules/agent/service/impl/AgentChatHistoryServiceImpl.java`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: main/manager-web/src/components/AgentSnapshotDialog.vue main/manager-web/src/components/AgentSnapshotDialog.vue:1923 — main/manager-web/src/components/AgentSnapshotDialog.vue changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 12 (its worst body is normalizeValueForField at line 1923), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: harden agent snapshot restore flow”; “fix: 修复智能体快照基线与查看逻辑”; “Fix agent snapshot history issues”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-05-23..2026-08-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-05-23 10:00:04 +08:00' --until='2026-08-21 10:00:04 +08:00' --full-history --no-merges -- main/manager-web/src/components/AgentSnapshotDialog.vue`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
D29 · Static Analysis (SAST) · REDACTED · ×4
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×4
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D30 · Dependency Vulnerabilities · Medium vulnerability · ×4
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Edited copy of a member (9 corresponding lines) · ×4
  • Edited copy of a member (9 corresponding lines) main/manager-api/src/main/java/xiaozhi/modules/device/controller/DeviceController.java:194 — main/manager-api/src/main/java/xiaozhi/modules/device/controller/DeviceController.java:194-202 | main/manager-api/src/main/java/xiaozhi/modules/device/controller/DeviceController.java:207-215 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) main/manager-api/src/main/java/xiaozhi/modules/agent/service/impl/AgentSnapshotServiceImpl.java:931 — main/manager-api/src/main/java/xiaozhi/modules/agent/service/impl/AgentSnapshotServiceImpl.java:931-939 | main/manager-api/src/main/java/xiaozhi/modules/agent/service/impl/AgentSnapshotServiceImpl.java:1025-1037 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) main/manager-api/src/main/java/xiaozhi/modules/security/secret/ServerSecretFilter.java:92 — main/manager-api/src/main/java/xiaozhi/modules/security/oauth2/Oauth2Filter.java:100-108 | main/manager-api/src/main/java/xiaozhi/modules/security/secret/ServerSecretFilter.java:92-100 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) main/xiaozhi-server/core/utils/dialogue_registry.py:35 — main/xiaozhi-server/core/utils/dialogue_registry.py:35-48 | main/xiaozhi-server/core/utils/util.py:21-29 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (15 lines × 2) · ×4
  • Duplicated block (15 lines × 2) main/xiaozhi-server/core/connection.py:804 — main/xiaozhi-server/core/connection.py:804-818 | main/xiaozhi-server/core/connection.py:822-836 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (15 lines × 2) main/xiaozhi-server/core/providers/tts/index_stream.py:76 — main/xiaozhi-server/core/providers/tts/index_stream.py:76-90 | main/xiaozhi-server/core/providers/tts/minimax_httpstream.py:132-146 — before extracting anything, compare `main/xiaozhi-server/core/providers/tts/index_stream.py` and `main/xiaozhi-server/core/providers/tts/minimax_httpstream.py` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 133 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (15 lines × 2) main/manager-api/src/main/java/xiaozhi/modules/device/service/impl/DeviceServiceImpl.java:763 — main/manager-api/src/main/java/xiaozhi/modules/device/service/impl/DeviceServiceImpl.java:763-777 | main/manager-api/src/main/java/xiaozhi/modules/device/service/impl/DeviceServiceImpl.java:854-868 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (15 lines × 2) main/manager-api/src/main/java/xiaozhi/modules/knowledge/service/impl/KnowledgeFilesServiceImpl.java:322 — main/manager-api/src/main/java/xiaozhi/modules/knowledge/service/impl/KnowledgeFilesServiceImpl.java:322-336 | main/manager-api/src/main/java/xiaozhi/modules/knowledge/service/impl/KnowledgeFilesServiceImpl.java:642-656 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `main/manager-api/src/main/java/xiaozhi/modules/knowledge/service/impl/KnowledgeFilesServiceImpl.java:322` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (13 lines × 2) · ×4
  • Duplicated block (13 lines × 2) main/xiaozhi-server/core/providers/tts/alibl_stream.py:336 — main/xiaozhi-server/core/providers/tts/alibl_stream.py:336-348 | REDACTED:418-430 — before extracting anything, compare `main/xiaozhi-server/core/providers/tts/alibl_stream.py` and `REDACTED` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 297 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (13 lines × 2) main/xiaozhi-server/core/utils/modules_initialize.py:45 — main/xiaozhi-server/core/utils/modules_initialize.py:45-57 | main/xiaozhi-server/core/utils/modules_initialize.py:59-71 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `main/xiaozhi-server/core/utils/modules_initialize.py:45` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13 lines × 2) main/xiaozhi-server/core/utils/session_state.py:618 — main/xiaozhi-server/core/utils/session_state.py:618-630 | main/xiaozhi-server/core/utils/session_state.py:703-715 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (13 lines × 2) main/manager-api/src/main/java/xiaozhi/modules/agent/controller/AgentChatHistoryController.java:107 — main/manager-api/src/main/java/xiaozhi/modules/agent/controller/AgentChatHistoryController.java:107-119 | main/manager-api/src/main/java/xiaozhi/modules/agent/controller/AgentChatHistoryController.java:140-152 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `main/manager-api/src/main/java/xiaozhi/modules/agent/controller/AgentChatHistoryController.java:107` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (9 lines × 2) · ×4
  • Duplicated block (9 lines × 2) main/xiaozhi-server/scripts/capacity_bench.py:528 — main/xiaozhi-server/scripts/capacity_bench.py:528-536 | main/xiaozhi-server/scripts/capacity_bench.py:568-576 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (9 lines × 2) main/manager-api/src/main/java/xiaozhi/modules/voiceclone/service/impl/VoiceCloneServiceImpl.java:77 — main/manager-api/src/main/java/xiaozhi/modules/voiceclone/service/impl/VoiceCloneServiceImpl.java:77-85 | main/manager-api/src/main/java/xiaozhi/modules/voiceclone/service/impl/VoiceCloneServiceImpl.java:283-291 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (9 lines × 2) main/manager-api/src/main/java/xiaozhi/modules/voiceclone/service/impl/VoiceCloneServiceImpl.java:161 — main/manager-api/src/main/java/xiaozhi/modules/voiceclone/service/impl/VoiceCloneServiceImpl.java:161-169 | main/manager-api/src/main/java/xiaozhi/modules/voiceclone/service/impl/VoiceCloneServiceImpl.java:202-210 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `main/manager-api/src/main/java/xiaozhi/modules/voiceclone/service/impl/VoiceCloneServiceImpl.java:161` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 2) main/manager-api/src/main/java/xiaozhi/modules/sys/service/impl/SysDictDataServiceImpl.java:45 — main/manager-api/src/main/java/xiaozhi/modules/sys/service/impl/SysDictDataServiceImpl.java:45-53 | main/manager-api/src/main/java/xiaozhi/modules/sys/service/impl/SysDictTypeServiceImpl.java:45-53 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
R7 · Dead Code · Dead file (~16 LoC) · ×4
  • Dead file (~16 LoC) main/manager-mobile/src/pages/login/privacy-policy-en.vue — no import path from any entry point (28 application, 10 tooling, 9 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
  • Dead file (~16 LoC) main/manager-mobile/src/pages/login/privacy-policy-zh.vue — no import path from any entry point (28 application, 10 tooling, 9 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
  • Dead file (~16 LoC) main/manager-mobile/src/pages/login/user-agreement-en.vue — no import path from any entry point (28 application, 10 tooling, 9 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
  • Dead file (~16 LoC) main/manager-mobile/src/pages/login/user-agreement-zh.vue — no import path from any entry point (28 application, 10 tooling, 9 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
D17 · Explicit Debt · TodoComment · ×3
  • TodoComment main/xiaozhi-server/core/providers/tools/server_mcp/mcp_client.py:196 — # TODO 兼容旧版本 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment main/manager-mobile/src/router/interceptor.ts:10 — // TODO Check — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment main/manager-mobile/src/layouts/fg-tabbar/tabbarList.ts:23 — // TODO:通过这里切换使用tabbar的策略 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
D4 · Code Duplication · Edited copy of a member (20 corresponding lines) · ×3
  • Edited copy of a member (20 corresponding lines) main/xiaozhi-server/core/handle/reportHandle.py:188 — main/xiaozhi-server/core/handle/reportHandle.py:188-214 | main/xiaozhi-server/core/handle/reportHandle.py:259-285 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (20 corresponding lines) main/xiaozhi-server/core/providers/tts/cozecn.py:12 — main/xiaozhi-server/core/providers/tts/cozecn.py:12-31 | main/xiaozhi-server/core/providers/tts/tencent.py:19-40 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (20 corresponding lines) main/xiaozhi-server/core/utils/util.py:426 — main/xiaozhi-server/core/utils/util.py:426-445 | main/xiaozhi-server/core/utils/util.py:449-474 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (22 corresponding lines) · ×3
  • Edited copy of a member (22 corresponding lines) main/manager-api/src/main/java/xiaozhi/modules/security/password/BCrypt.java:432 — main/manager-api/src/main/java/xiaozhi/modules/security/password/BCrypt.java:432-453 | main/manager-api/src/main/java/xiaozhi/modules/security/password/BCrypt.java:463-488 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (22 corresponding lines) main/manager-api/src/main/java/xiaozhi/modules/agent/service/impl/AgentChatSummaryServiceImpl.java:408 — main/manager-api/src/main/java/xiaozhi/modules/agent/service/impl/AgentChatSummaryServiceImpl.java:408-429 | main/manager-api/src/main/java/xiaozhi/modules/agent/service/impl/AgentChatSummaryServiceImpl.java:434-455 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (22 corresponding lines) main/manager-api/src/main/java/xiaozhi/modules/sys/service/impl/SysDictDataServiceImpl.java:167 — main/manager-api/src/main/java/xiaozhi/modules/sys/service/impl/SysDictDataServiceImpl.java:167-188 | main/manager-api/src/main/java/xiaozhi/modules/timbre/service/impl/TimbreServiceImpl.java:69-96 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (18 corresponding lines) · ×3
  • Edited copy of a member (18 corresponding lines) main/manager-api/src/main/java/xiaozhi/modules/sys/service/impl/SysDictDataServiceImpl.java:135 — main/manager-api/src/main/java/xiaozhi/modules/sys/service/impl/SysDictDataServiceImpl.java:135-152 | main/manager-api/src/main/java/xiaozhi/modules/sys/service/impl/SysDictTypeServiceImpl.java:124-141 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (18 corresponding lines) main/manager-api/src/main/java/xiaozhi/modules/llm/service/impl/OpenAIStyleLLMServiceImpl.java:262 — main/manager-api/src/main/java/xiaozhi/modules/llm/service/impl/OpenAIStyleLLMServiceImpl.java:262-279 | main/manager-api/src/main/java/xiaozhi/modules/llm/service/impl/OpenAIStyleLLMServiceImpl.java:282-305 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (18 corresponding lines) main/xiaozhi-server/scripts/capacity_bench.py:213 — main/xiaozhi-server/scripts/capacity_bench.py:213-230 | main/xiaozhi-server/scripts/ws_lifecycle_smoke.py:172-189 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (14 corresponding lines) · ×3
  • Edited copy of a member (14 corresponding lines) main/manager-api/src/main/java/xiaozhi/modules/agent/service/impl/AgentSnapshotServiceImpl.java:405 — main/manager-api/src/main/java/xiaozhi/modules/agent/service/impl/AgentSnapshotServiceImpl.java:405-418 | main/manager-api/src/main/java/xiaozhi/modules/agent/service/impl/AgentSnapshotServiceImpl.java:420-435 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) main/xiaozhi-server/core/utils/cache/manager.py:167 — main/xiaozhi-server/core/utils/cache/manager.py:167-182 | main/xiaozhi-server/core/utils/cache/manager.py:185-198 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) main/xiaozhi-server/core/utils/util.py:233 — main/xiaozhi-server/core/utils/util.py:233-246 | main/xiaozhi-server/core/utils/util.py:330-343 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (11 corresponding lines) · ×3
  • Edited copy of a member (11 corresponding lines) main/manager-api/src/main/java/xiaozhi/modules/agent/service/impl/AgentChatHistoryServiceImpl.java:92 — main/manager-api/src/main/java/xiaozhi/modules/agent/service/impl/AgentChatHistoryServiceImpl.java:92-102 | main/manager-api/src/main/java/xiaozhi/modules/agent/service/impl/AgentChatHistoryServiceImpl.java:193-203 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) main/manager-api/src/main/java/xiaozhi/modules/sys/service/impl/SysDictDataServiceImpl.java:154 — main/manager-api/src/main/java/xiaozhi/modules/sys/service/impl/SysDictDataServiceImpl.java:154-164 | main/manager-api/src/main/java/xiaozhi/modules/sys/service/impl/SysDictTypeServiceImpl.java:143-153 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) main/manager-api/src/main/java/xiaozhi/modules/sys/service/impl/SysDictDataServiceImpl.java:77 — main/manager-api/src/main/java/xiaozhi/modules/sys/service/impl/SysDictDataServiceImpl.java:77-87 | main/manager-api/src/main/java/xiaozhi/modules/sys/service/impl/SysDictDataServiceImpl.java:91-101 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (15–16 lines × 2) · ×3
  • Duplicated block (15–16 lines × 2) main/digital-human/wakeword_runtime/core/detector_assets.py:67 — main/digital-human/wakeword_runtime/core/detector_assets.py:67-82 | main/digital-human/wakeword_runtime/runtime/http_server.py:256-270 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `main/digital-human/wakeword_runtime/core/detector_assets.py:67` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (15–16 lines × 2) main/xiaozhi-server/core/providers/asr/doubao_stream.py:234 — main/xiaozhi-server/core/providers/asr/doubao_stream.py:234-249 | main/xiaozhi-server/core/providers/asr/xunfei_stream.py:231-245 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (15–16 lines × 2) main/xiaozhi-server/core/providers/tools/device_mcp/mcp_handler.py:160 — main/xiaozhi-server/core/providers/tools/device_mcp/mcp_handler.py:160-174 | main/xiaozhi-server/core/providers/tools/mcp_endpoint/mcp_endpoint_handler.py:106-121 — `main/xiaozhi-server/core/providers/tools/device_mcp/mcp_handler.py` and `main/xiaozhi-server/core/providers/tools/mcp_endpoint/mcp_endpoint_handler.py` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 5 separate duplicated blocks between them, totalling at least 158 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `main/xiaozhi-server/core/providers/tools/mcp_endpoint/mcp_endpoint_handler.py:106` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (14 lines × 2) · ×3
  • Duplicated block (14 lines × 2) REDACTED:266 — REDACTED:266-279 | main/xiaozhi-server/core/providers/asr/aliyunbl_stream.py:233-246 — before extracting anything, compare `REDACTED` and `main/xiaozhi-server/core/providers/asr/aliyunbl_stream.py` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 88 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `REDACTED:264` calls `bind`, `error` and `main/xiaozhi-server/core/providers/asr/aliyunbl_stream.py:231` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (14 lines × 2) main/xiaozhi-server/core/providers/tts/huoshan_double_stream.py:370 — main/xiaozhi-server/core/providers/tts/huoshan_double_stream.py:370-385 | main/xiaozhi-server/core/providers/tts/xunfei_stream.py:243-256 — before extracting anything, compare `main/xiaozhi-server/core/providers/tts/huoshan_double_stream.py` and `main/xiaozhi-server/core/providers/tts/xunfei_stream.py` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 111 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (14 lines × 2) main/manager-api/src/main/java/xiaozhi/modules/agent/service/impl/AgentVoicePrintServiceImpl.java:304 — main/manager-api/src/main/java/xiaozhi/modules/agent/service/impl/AgentVoicePrintServiceImpl.java:304-317 | main/manager-api/src/main/java/xiaozhi/modules/agent/service/impl/AgentVoicePrintServiceImpl.java:388-401 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `main/manager-api/src/main/java/xiaozhi/modules/agent/service/impl/AgentVoicePrintServiceImpl.java:304` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `main/manager-api/src/main/java/xiaozhi/modules/agent/service/impl/AgentVoicePrintServiceImpl.java:385` calls `stream`, `collect`, `joining` and `main/manager-api/src/main/java/xiaozhi/modules/agent/service/impl/AgentVoicePrintServiceImpl.java:303` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (11–12 lines × 2) · ×3
  • Duplicated block (11–12 lines × 2) main/xiaozhi-server/core/providers/memory/mem_local_short/mem_local_short.py:152 — main/xiaozhi-server/core/providers/memory/mem_local_short/mem_local_short.py:152-162 | main/xiaozhi-server/core/providers/memory/powermem/powermem.py:170-181 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (11–12 lines × 2) main/xiaozhi-server/core/providers/tools/device_mcp/mcp_handler.py:219 — main/xiaozhi-server/core/providers/tools/device_mcp/mcp_handler.py:219-229 | main/xiaozhi-server/core/providers/tools/mcp_endpoint/mcp_endpoint_handler.py:193-204 — `main/xiaozhi-server/core/providers/tools/device_mcp/mcp_handler.py` and `main/xiaozhi-server/core/providers/tools/mcp_endpoint/mcp_endpoint_handler.py` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 5 separate duplicated blocks between them, totalling at least 158 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `main/xiaozhi-server/core/providers/tools/mcp_endpoint/mcp_endpoint_handler.py:193` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (11–12 lines × 2) main/xiaozhi-server/core/providers/tts/xunfei_stream.py:357 — main/xiaozhi-server/core/providers/tts/xunfei_stream.py:357-368 | main/xiaozhi-server/core/providers/tts/xunfei_stream.py:464-474 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (10 lines × 3) · ×3
  • Duplicated block (10 lines × 3) main/xiaozhi-server/core/providers/tts/alibl_stream.py:324 — main/xiaozhi-server/core/providers/tts/alibl_stream.py:324-333 | REDACTED:503-512 | main/xiaozhi-server/core/providers/tts/huoshan_double_stream.py:730-739 — before extracting anything, compare `main/xiaozhi-server/core/providers/tts/alibl_stream.py` and `REDACTED` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 297 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (10 lines × 3) main/xiaozhi-server/core/providers/tts/custom.py:44 — main/xiaozhi-server/core/providers/tts/custom.py:44-53 | main/xiaozhi-server/core/providers/tts/gpt_sovits_v2.py:94-103 | main/xiaozhi-server/core/providers/tts/gpt_sovits_v3.py:55-64 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (10 lines × 3) REDACTED:314 — REDACTED:314-323 | main/xiaozhi-server/core/providers/asr/aliyunbl_stream.py:296-305 | main/xiaozhi-server/core/providers/asr/xunfei_stream.py:305-314 — before extracting anything, compare `REDACTED` and `main/xiaozhi-server/core/providers/asr/aliyunbl_stream.py` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 88 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (10 lines × 2) · ×3
  • Duplicated block (10 lines × 2) main/xiaozhi-server/core/providers/memory/mem0ai/mem0ai.py:52 — main/xiaozhi-server/core/providers/memory/mem0ai/mem0ai.py:52-61 | main/xiaozhi-server/core/providers/memory/powermem/powermem.py:174-183 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (10 lines × 2) main/xiaozhi-server/performance_tester/performance_tester_stream_asr.py:53 — main/xiaozhi-server/performance_tester/performance_tester_stream_asr.py:53-62 | main/xiaozhi-server/performance_tester/performance_tester_stream_tts.py:562-571 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (10 lines × 2) main/manager-api/src/main/java/xiaozhi/modules/llm/service/impl/OpenAIStyleLLMServiceImpl.java:266 — main/manager-api/src/main/java/xiaozhi/modules/llm/service/impl/OpenAIStyleLLMServiceImpl.java:266-275 | main/manager-api/src/main/java/xiaozhi/modules/llm/service/impl/OpenAIStyleLLMServiceImpl.java:292-301 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `main/manager-api/src/main/java/xiaozhi/modules/llm/service/impl/OpenAIStyleLLMServiceImpl.java:266` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (5 lines × 2) · ×3
  • Duplicated block (5 lines × 2) main/manager-api/src/main/java/xiaozhi/modules/agent/service/impl/AgentServiceImpl.java:464 — main/manager-api/src/main/java/xiaozhi/modules/agent/service/impl/AgentServiceImpl.java:464-468 | main/manager-api/src/main/java/xiaozhi/modules/agent/service/impl/AgentSnapshotServiceImpl.java:609-613 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `main/manager-api/src/main/java/xiaozhi/modules/agent/service/impl/AgentServiceImpl.java:464` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (5 lines × 2) main/manager-api/src/main/java/xiaozhi/modules/device/controller/DeviceController.java:195 — main/manager-api/src/main/java/xiaozhi/modules/device/controller/DeviceController.java:195-199 | main/manager-api/src/main/java/xiaozhi/modules/device/controller/DeviceController.java:208-212 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note first that the copies are not typed on the same thing: the declarations holding them bind `dto` to `DeviceAddressBookAliasDTO` in one and `DeviceAddressBookPermissionDTO` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (5 lines × 2) main/manager-api/src/main/java/xiaozhi/modules/security/password/BCrypt.java:380 — main/manager-api/src/main/java/xiaozhi/modules/security/password/BCrypt.java:380-384 | main/manager-api/src/main/java/xiaozhi/modules/security/password/BCrypt.java:387-391 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
R10 · Code Duplication · Duplicated block with local edits (21 matched lines × 2 locations) · ×3
  • Duplicated block with local edits (21 matched lines × 2 locations) main/manager-mobile/src/pages/chat-history/detail.vue:238 — main/manager-mobile/src/pages/chat-history/detail.vue:238 · main/manager-web/src/components/ChatHistoryDialog.vue:197 — the two spans are one implementation copied and then locally edited — 122 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
  • Duplicated block with local edits (21 matched lines × 2 locations) main/manager-mobile/src/pages/device/index.vue:280 — main/manager-mobile/src/pages/device/index.vue:280 · main/manager-mobile/src/pages/device/index.vue:324 — the two spans are one implementation copied and then locally edited — 120 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.
  • Duplicated block with local edits (21 matched lines × 2 locations) main/manager-web/src/views/DeviceManagement.vue:233 — main/manager-web/src/views/DeviceManagement.vue:233 · main/manager-web/src/views/UserManagement.vue:194 — the two spans are one implementation copied and then locally edited — 79 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block (18 lines × 2 locations) · ×3
  • Duplicated block (18 lines × 2 locations) main/manager-mobile/src/pages/agent/index.vue:22 — main/manager-mobile/src/pages/agent/index.vue:22 · main/manager-mobile/src/pages/chat-history/detail.vue:21 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
  • Duplicated block (18 lines × 2 locations) main/manager-mobile/src/pages/chat-history/index.vue:14 — main/manager-mobile/src/pages/chat-history/index.vue:14 · main/manager-mobile/src/pages/voiceprint/index.vue:18 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
  • Duplicated block (18 lines × 2 locations) main/manager-web/src/apis/module/agent.js:543 — main/manager-web/src/apis/module/agent.js:543 · main/manager-web/src/apis/module/model.js:156 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (17 lines × 2 locations) · ×3
  • Duplicated block (17 lines × 2 locations) main/manager-mobile/src/pages/agent/components/AgentSnapshotPanel.vue:376 — main/manager-mobile/src/pages/agent/components/AgentSnapshotPanel.vue:376 · main/manager-mobile/src/pages/agent/components/AgentSnapshotPanel.vue:437 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
  • Duplicated block (17 lines × 2 locations) main/manager-web/src/components/ContextProviderDialog.vue:130 — main/manager-web/src/components/ContextProviderDialog.vue:130 · main/manager-web/src/components/TtsAdvancedSettings.vue:134 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
  • Duplicated block (17 lines × 2 locations) main/manager-web/src/components/ParamDialog.vue:142 — main/manager-web/src/components/ParamDialog.vue:142 · main/manager-web/src/components/ReplacementWordDialog.vue:228 — 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.
X2 · Cancellation propagation · Async function without AbortSignal · ×3
  • Async function without AbortSignal: initCamera main/digital-human/js/app.js:131 — `initCamera` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
  • Async function without AbortSignal: sendOTA main/digital-human/js/core/network/ota-connector.js:65 — `sendOTA` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
  • Async function without AbortSignal: initMcpTools main/digital-human/js/core/mcp/tools.js:24 — `initMcpTools` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
AC1 · Text alternatives · <canvas> without a text alternative · ×2
  • <canvas> without a text alternative main/digital-human/index.html:82 — A <canvas> with no aria-label/title and no inner fallback content can't be described by assistive tech. Add a name or fallback content.
  • <canvas> without a text alternative main/manager-web/src/components/VoiceCloneDialog.vue:51 — A <canvas> with no aria-label/title and no inner fallback content can't be described by assistive tech. Add a name or fallback content.
AC3 · Page structure · Heading level jumps from h2 to h4 · ×2
  • Heading level jumps from h2 to h4 main/manager-web/src/views/DictManagement.vue:20 — Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
  • Heading level jumps from h2 to h4 main/manager-web/src/views/KnowledgeBaseManagement.vue:170 — Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
D29 · Static Analysis (SAST) · REDACTED · ×2
  • REDACTED
  • REDACTED
D4 · Code Duplication · Edited copy of a member (24 corresponding lines) · ×2
  • Edited copy of a member (24 corresponding lines) main/manager-api/src/main/java/xiaozhi/modules/agent/service/impl/AgentVoicePrintServiceImpl.java:297 — main/manager-api/src/main/java/xiaozhi/modules/agent/service/impl/AgentVoicePrintServiceImpl.java:297-326 | main/manager-api/src/main/java/xiaozhi/modules/agent/service/impl/AgentVoicePrintServiceImpl.java:333-356 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (24 corresponding lines) main/xiaozhi-server/core/utils/p3.py:4 — main/xiaozhi-server/core/utils/p3.py:4-33 | main/xiaozhi-server/core/utils/p3.py:36-59 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (27 corresponding lines) · ×2
  • Edited copy of a member (27 corresponding lines) main/xiaozhi-server/core/providers/tts/alibl_stream.py:232 — main/xiaozhi-server/core/providers/tts/alibl_stream.py:232-281 | main/xiaozhi-server/core/providers/tts/xunfei_stream.py:274-300 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (27 corresponding lines) main/manager-api/src/main/java/xiaozhi/modules/sys/utils/WebSocketClientManager.java:116 — main/manager-api/src/main/java/xiaozhi/modules/sys/utils/WebSocketClientManager.java:116-142 | main/manager-api/src/main/java/xiaozhi/modules/sys/utils/WebSocketClientManager.java:147-173 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (15 corresponding lines) · ×2
  • Edited copy of a member (15 corresponding lines) main/manager-api/src/main/java/xiaozhi/modules/agent/service/impl/AgentChatSummaryServiceImpl.java:251 — main/manager-api/src/main/java/xiaozhi/modules/agent/service/impl/AgentChatSummaryServiceImpl.java:251-265 | main/manager-api/src/main/java/xiaozhi/modules/agent/service/impl/AgentChatSummaryServiceImpl.java:503-520 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) main/manager-api/src/main/java/xiaozhi/modules/knowledge/rag/impl/RAGFlowAdapter.java:452 — main/manager-api/src/main/java/xiaozhi/modules/knowledge/rag/impl/RAGFlowAdapter.java:452-466 | main/manager-api/src/main/java/xiaozhi/modules/knowledge/rag/impl/RAGFlowAdapter.java:469-483 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 17+ corresponding lines) · ×2
  • Edited copies of one member (3 members, 17+ corresponding lines) main/xiaozhi-server/core/providers/tools/device_mcp/mcp_executor.py:69 — main/xiaozhi-server/core/providers/tools/device_mcp/mcp_executor.py:69-85 | main/xiaozhi-server/core/providers/tools/mcp_endpoint/mcp_endpoint_executor.py:68-87 | main/xiaozhi-server/core/providers/tools/server_mcp/mcp_executor.py:56-72 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 17 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 17+ corresponding lines) main/xiaozhi-server/core/utils/circuit_store.py:17 — main/xiaozhi-server/core/utils/circuit_store.py:17-33 | main/xiaozhi-server/core/utils/dialogue_registry.py:52-71 | main/xiaozhi-server/core/utils/resilience.py:19-35 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 17 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (7 corresponding lines) · ×2
  • Edited copy of a member (7 corresponding lines) main/manager-api/src/main/java/xiaozhi/modules/model/service/impl/ModelProviderServiceImpl.java:94 — main/manager-api/src/main/java/xiaozhi/modules/model/service/impl/ModelProviderServiceImpl.java:94-101 | main/manager-api/src/main/java/xiaozhi/modules/model/service/impl/ModelProviderServiceImpl.java:173-179 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) REDACTED:111 — REDACTED:111-117 | main/manager-api/src/main/java/xiaozhi/modules/voiceclone/controller/VoiceResourceController.java:93-99 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (4 corresponding lines) · ×2
  • Edited copy of a member (4 corresponding lines) main/xiaozhi-server/scripts/production_verify.py:36 — main/xiaozhi-server/scripts/production_verify.py:36-39 | main/xiaozhi-server/scripts/registry_verify.py:14-17 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) main/xiaozhi-server/core/providers/asr/tencent.py:219 — main/xiaozhi-server/core/providers/asr/tencent.py:219-223 | main/xiaozhi-server/core/providers/tts/tencent.py:134-137 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (23–25 lines × 2) · ×2
  • Duplicated block (23–25 lines × 2) REDACTED:303 — REDACTED:303-325 | main/xiaozhi-server/core/providers/asr/xunfei_stream.py:292-316 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (23–25 lines × 2) main/manager-api/src/main/java/xiaozhi/modules/llm/service/impl/OpenAIStyleLLMServiceImpl.java:78 — main/manager-api/src/main/java/xiaozhi/modules/llm/service/impl/OpenAIStyleLLMServiceImpl.java:78-102 | main/manager-api/src/main/java/xiaozhi/modules/llm/service/impl/OpenAIStyleLLMServiceImpl.java:175-197 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `main/manager-api/src/main/java/xiaozhi/modules/llm/service/impl/OpenAIStyleLLMServiceImpl.java:78` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `main/manager-api/src/main/java/xiaozhi/modules/llm/service/impl/OpenAIStyleLLMServiceImpl.java:103` calls `getDouble`, `getInt` and `main/manager-api/src/main/java/xiaozhi/modules/llm/service/impl/OpenAIStyleLLMServiceImpl.java:199` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (24 lines × 2) · ×2
  • Duplicated block (24 lines × 2) main/xiaozhi-server/core/providers/llm/openai/openai.py:92 — main/xiaozhi-server/core/providers/llm/openai/openai.py:92-115 | main/xiaozhi-server/core/providers/llm/openai/openai.py:138-161 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (24 lines × 2) main/manager-api/src/main/java/xiaozhi/modules/device/service/impl/DeviceServiceImpl.java:722 — main/manager-api/src/main/java/xiaozhi/modules/device/service/impl/DeviceServiceImpl.java:722-745 | main/manager-api/src/main/java/xiaozhi/modules/device/service/impl/DeviceServiceImpl.java:822-845 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (20 lines × 2) · ×2
  • Duplicated block (20 lines × 2) REDACTED:242 — REDACTED:242-261 | main/xiaozhi-server/core/providers/asr/aliyunbl_stream.py:198-217 — before extracting anything, compare `REDACTED` and `main/xiaozhi-server/core/providers/asr/aliyunbl_stream.py` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 88 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (20 lines × 2) main/xiaozhi-server/core/providers/tts/base.py:265 — main/xiaozhi-server/core/providers/tts/base.py:265-284 | main/xiaozhi-server/core/providers/tts/base.py:363-382 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `main/xiaozhi-server/core/providers/tts/base.py:265` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (18–20 lines × 2) · ×2
  • Duplicated block (18–20 lines × 2) main/xiaozhi-server/core/providers/llm/ollama/ollama.py:29 — main/xiaozhi-server/core/providers/llm/ollama/ollama.py:29-46 | main/xiaozhi-server/core/providers/llm/ollama/ollama.py:96-115 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `main/xiaozhi-server/core/providers/llm/ollama/ollama.py:29` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (18–20 lines × 2) REDACTED:105 — REDACTED:105-122 | REDACTED:110-129 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 81 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (18–19 lines × 2) · ×2
  • Duplicated block (18–19 lines × 2) main/xiaozhi-server/core/connection.py:1282 — main/xiaozhi-server/core/connection.py:1282-1299 | main/xiaozhi-server/core/connection.py:1323-1341 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (18–19 lines × 2) main/xiaozhi-server/core/utils/resilience.py:880 — main/xiaozhi-server/core/utils/resilience.py:880-898 | main/xiaozhi-server/core/utils/resilience.py:950-967 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (18 lines × 2) · ×2
  • Duplicated block (18 lines × 2) main/xiaozhi-server/core/handle/reportHandle.py:196 — main/xiaozhi-server/core/handle/reportHandle.py:196-213 | main/xiaozhi-server/core/handle/reportHandle.py:267-284 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (18 lines × 2) main/xiaozhi-server/core/providers/llm/coze/coze.py:58 — main/xiaozhi-server/core/providers/llm/coze/coze.py:58-75 | main/xiaozhi-server/core/providers/llm/dify/dify.py:90-107 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (17–18 lines × 2) · ×2
  • Duplicated block (17–18 lines × 2) REDACTED:132 — REDACTED:132-148 | main/xiaozhi-server/core/providers/asr/aliyunbl_stream.py:58-75 — before extracting anything, compare `REDACTED` and `main/xiaozhi-server/core/providers/asr/aliyunbl_stream.py` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 88 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (17–18 lines × 2) main/xiaozhi-server/core/utils/audioRateController.py:47 — main/xiaozhi-server/core/utils/audioRateController.py:47-63 | main/xiaozhi-server/core/utils/audioRateController.py:66-83 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (14–15 lines × 3) · ×2
  • Duplicated block (14–15 lines × 3) main/xiaozhi-server/core/utils/circuit_store.py:17 — main/xiaozhi-server/core/utils/circuit_store.py:17-31 | main/xiaozhi-server/core/utils/dialogue_registry.py:52-66 | main/xiaozhi-server/core/utils/resilience.py:20-33 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
  • Duplicated block (14–15 lines × 3) main/xiaozhi-server/core/providers/tts/alibl_stream.py:133 — main/xiaozhi-server/core/providers/tts/alibl_stream.py:133-146 | main/xiaozhi-server/core/providers/tts/huoshan_double_stream.py:310-323 | main/xiaozhi-server/core/providers/tts/xunfei_stream.py:180-194 — before extracting anything, compare `main/xiaozhi-server/core/providers/tts/alibl_stream.py` and `main/xiaozhi-server/core/providers/tts/huoshan_double_stream.py` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 196 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (10–11 lines × 2) · ×2
  • Duplicated block (10–11 lines × 2) main/xiaozhi-server/core/providers/tts/base.py:205 — main/xiaozhi-server/core/providers/tts/base.py:205-215 | main/xiaozhi-server/core/providers/tts/base.py:300-309 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (10–11 lines × 2) main/xiaozhi-server/performance_tester/performance_tester_stream_tts.py:240 — main/xiaozhi-server/performance_tester/performance_tester_stream_tts.py:240-249 | main/xiaozhi-server/performance_tester/performance_tester_stream_tts.py:254-264 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (9 lines × 3) · ×2
  • Duplicated block (9 lines × 3) REDACTED:125 — REDACTED:125-135 | REDACTED:111-119 | REDACTED:141-151 — `REDACTED` and `REDACTED` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 80 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `REDACTED:137` calls `ValueError` and `REDACTED:120` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (9 lines × 3) REDACTED:136 — REDACTED:136-144 | main/xiaozhi-server/core/providers/asr/aliyunbl_stream.py:62-71 | main/xiaozhi-server/core/providers/asr/xunfei_stream.py:107-116 — before extracting anything, compare `REDACTED` and `main/xiaozhi-server/core/providers/asr/aliyunbl_stream.py` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 88 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (5 lines × 3) · ×2
  • Duplicated block (5 lines × 3) main/xiaozhi-server/core/providers/tools/device_mcp/mcp_client.py:77 — main/xiaozhi-server/core/providers/tools/device_mcp/mcp_client.py:77-81 | main/xiaozhi-server/core/providers/tools/device_mcp/mcp_handler.py:84-88 | main/xiaozhi-server/core/providers/tools/mcp_endpoint/mcp_endpoint_client.py:79-83 — before extracting anything, compare `main/xiaozhi-server/core/providers/tools/device_mcp/mcp_client.py` and `main/xiaozhi-server/core/providers/tools/device_mcp/mcp_handler.py` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 43 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (5 lines × 3) main/xiaozhi-server/core/providers/tools/device_mcp/mcp_client.py:84 — main/xiaozhi-server/core/providers/tools/device_mcp/mcp_client.py:84-88 | main/xiaozhi-server/core/providers/tools/device_mcp/mcp_handler.py:91-95 | main/xiaozhi-server/core/providers/tools/mcp_endpoint/mcp_endpoint_client.py:86-90 — before extracting anything, compare `main/xiaozhi-server/core/providers/tools/device_mcp/mcp_client.py` and `main/xiaozhi-server/core/providers/tools/device_mcp/mcp_handler.py` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 43 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (6 lines × 2) · ×2
  • Duplicated block (6 lines × 2) main/manager-api/src/main/java/xiaozhi/modules/config/service/impl/ConfigServiceImpl.java:489 — main/manager-api/src/main/java/xiaozhi/modules/config/service/impl/ConfigServiceImpl.java:489-494 | main/manager-api/src/main/java/xiaozhi/modules/config/service/impl/ConfigServiceImpl.java:506-512 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (6 lines × 2) main/manager-api/src/main/java/xiaozhi/modules/agent/service/impl/AgentServiceImpl.java:301 — main/manager-api/src/main/java/xiaozhi/modules/agent/service/impl/AgentServiceImpl.java:301-306 | main/manager-api/src/main/java/xiaozhi/modules/agent/service/impl/AgentTagServiceImpl.java:192-197 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
R10 · Code Duplication · Duplicated block (24 lines × 2 locations) · ×2
  • Duplicated block (24 lines × 2 locations) main/manager-web/src/apis/module/model.js:122 — main/manager-web/src/apis/module/model.js:122 · main/manager-web/src/apis/module/model.js:193 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
  • Duplicated block (24 lines × 2 locations) main/manager-web/src/components/DictDataDialog.vue:87 — main/manager-web/src/components/DictDataDialog.vue:87 · main/manager-web/src/components/DictTypeDialog.vue:70 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (20 lines × 2 locations) · ×2
  • Duplicated block (20 lines × 2 locations) main/manager-mobile/src/pages/forgot-password/index.vue:106 — main/manager-mobile/src/pages/forgot-password/index.vue:106 · main/manager-mobile/src/pages/register/index.vue:116 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
  • Duplicated block (20 lines × 2 locations) main/manager-web/src/views/roleConfig.vue:1660 — main/manager-web/src/views/roleConfig.vue:1660 · main/manager-web/src/views/roleConfig.vue:1750 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
R10 · Code Duplication · Duplicated block (19 lines × 2 locations) · ×2
  • Duplicated block (19 lines × 2 locations) main/manager-web/src/apis/module/model.js:161 — main/manager-web/src/apis/module/model.js:161 · main/manager-web/src/apis/module/model.js:415 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (19 lines × 2 locations) main/manager-web/src/apis/module/user.js:46 — main/manager-web/src/apis/module/user.js:46 · main/manager-web/src/apis/module/user.js:66 — 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.
R7 · Dead Code · Dead file (~378 LoC) · ×2
  • Dead file (~378 LoC) main/manager-mobile/src/pages/device/index.vue — no import path from any entry point (28 application, 10 tooling, 9 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (main/manager-mobile/src/pages/agent/index.vue) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
  • Dead file (~378 LoC) main/manager-mobile/src/pages/voiceprint/index.vue — no import path from any entry point (28 application, 10 tooling, 9 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (main/manager-mobile/src/pages/agent/index.vue) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~2 LoC) · ×2
  • Dead file (~2 LoC) main/manager-mobile/src/api/chat-history/index.ts — no import path from any entry point (28 application, 10 tooling, 9 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
  • Dead file (~2 LoC) main/manager-mobile/src/api/device/index.ts — no import path from any entry point (28 application, 10 tooling, 9 test roots considered), but 2 in-repo import(s) from 1 other file(s) do name it (main/manager-mobile/src/pages/device/index.vue) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
X17 · Uncapped recursion over a caller-supplied document · Recursive walk over a caller-supplied document has no depth cap · ×2
  • Recursive walk over a caller-supplied document has no depth cap main/manager-mobile/src/pages/agent/components/agentSnapshotUtils.mjs:73 — `redactSnapshotDisplayValue` is exported and takes `value: object` from its caller, and it calls itself at line 73 (`redactSnapshotDisplayValue`) with a piece of `value` (and at line 88) — and nowhere in `redactSnapshotDisplayValue` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `redactSnapshotDisplayValue` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
  • Recursive walk over a caller-supplied document has no depth cap main/manager-mobile/src/pages/agent/components/agentSnapshotUtils.mjs:297 — `normalizeSnapshotOrderedList` is exported, takes a document from its caller (line 53) and hands it to `normalizeDisplayObject`, which calls itself at line 297 (`normalizeDisplayObject`) with a piece of `value` (and at line 301) — and nowhere in `normalizeDisplayObject` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `normalizeDisplayObject` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
AC3 · Page structure · Heading level jumps from h1 to h3 · ×1
  • Heading level jumps from h1 to h3 main/manager-web/src/views/AddressBookManagement.vue:140 — Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D4 · Code Duplication · Near-duplicate member family (3 members, 40 shared lines) · ×1
  • Near-duplicate member family (3 members, 40 shared lines) main/manager-api/src/main/java/xiaozhi/modules/llm/service/impl/OpenAIStyleLLMServiceImpl.java:77 — main/manager-api/src/main/java/xiaozhi/modules/llm/service/impl/OpenAIStyleLLMServiceImpl.java:77-165 | main/manager-api/src/main/java/xiaozhi/modules/llm/service/impl/OpenAIStyleLLMServiceImpl.java:174-259 | main/manager-api/src/main/java/xiaozhi/modules/llm/service/impl/OpenAIStyleLLMServiceImpl.java:333-418 — These 3 members are variants of one another: a block of 40 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 3 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 3 times.
D4 · Code Duplication · Near-duplicate member pair (55 shared lines) · ×1
  • Near-duplicate member pair (55 shared lines) main/xiaozhi-server/core/providers/tools/device_mcp/mcp_handler.py:121 — main/xiaozhi-server/core/providers/tools/device_mcp/mcp_handler.py:121-235 | main/xiaozhi-server/core/providers/tools/mcp_endpoint/mcp_endpoint_handler.py:59-221 — These two members are variants of one another: 55 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication · Edited copy of a member (16 corresponding lines) · ×1
  • Edited copy of a member (16 corresponding lines) main/xiaozhi-server/core/handle/reportHandle.py:87 — main/xiaozhi-server/core/handle/reportHandle.py:87-129 | main/xiaozhi-server/core/handle/reportHandle.py:133-184 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Members sharing a duplicated core (6 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (6 members, 50+ identical tokens) main/xiaozhi-server/core/providers/tts/alibl_stream.py:104 — main/xiaozhi-server/core/providers/tts/alibl_stream.py:104-191 | REDACTED:217-295 | main/xiaozhi-server/core/providers/tts/huoshan_double_stream.py:275-367 | main/xiaozhi-server/core/providers/tts/index_stream.py:40-73 | main/xiaozhi-server/core/providers/tts/minimax_httpstream.py:97-129 | main/xiaozhi-server/core/providers/tts/xunfei_stream.py:153-240 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
D4 · Code Duplication · Edited copy of a member (101 corresponding lines) · ×1
  • Edited copy of a member (101 corresponding lines) main/xiaozhi-server/core/providers/tools/device_mcp/mcp_handler.py:303 — main/xiaozhi-server/core/providers/tools/device_mcp/mcp_handler.py:303-403 | main/xiaozhi-server/core/providers/tools/mcp_endpoint/mcp_endpoint_handler.py:289-392 — These two members are one piece of code written twice and then edited apart: 101 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (84 corresponding lines) · ×1
  • Edited copy of a member (84 corresponding lines) main/manager-api/src/main/java/xiaozhi/modules/device/service/impl/DeviceServiceImpl.java:720 — main/manager-api/src/main/java/xiaozhi/modules/device/service/impl/DeviceServiceImpl.java:720-817 | main/manager-api/src/main/java/xiaozhi/modules/device/service/impl/DeviceServiceImpl.java:820-903 — These two members are one piece of code written twice and then edited apart: 84 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (102 corresponding lines) · ×1
  • Edited copy of a member (102 corresponding lines) REDACTED:157 — REDACTED:157-258 | main/xiaozhi-server/plugins_func/functions/get_news_from_newsnow.py:182-294 — These two members are one piece of code written twice and then edited apart: 102 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (54 corresponding lines) · ×1
  • Edited copy of a member (54 corresponding lines) main/xiaozhi-server/core/utils/resilience.py:875 — main/xiaozhi-server/core/utils/resilience.py:875-928 | main/xiaozhi-server/core/utils/resilience.py:942-1002 — These two members are one piece of code written twice and then edited apart: 54 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (64 corresponding lines) · ×1
  • Edited copy of a member (64 corresponding lines) main/xiaozhi-server/core/providers/llm/ollama/ollama.py:29 — main/xiaozhi-server/core/providers/llm/ollama/ollama.py:29-92 | main/xiaozhi-server/core/providers/llm/ollama/ollama.py:96-171 — These two members are one piece of code written twice and then edited apart: 64 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (66 corresponding lines) · ×1
  • Edited copy of a member (66 corresponding lines) main/xiaozhi-server/performance_tester/performance_tester_asr.py:242 — main/xiaozhi-server/performance_tester/performance_tester_asr.py:242-307 | main/xiaozhi-server/performance_tester/performance_tester_llm.py:368-451 — These two members are one piece of code written twice and then edited apart: 66 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (37 corresponding lines) · ×1
  • Edited copy of a member (37 corresponding lines) REDACTED:96 — REDACTED:96-132 | REDACTED:97-149 — These two members are one piece of code written twice and then edited apart: 37 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (46 corresponding lines) · ×1
  • Edited copy of a member (46 corresponding lines) main/xiaozhi-server/core/providers/tools/device_mcp/mcp_executor.py:21 — main/xiaozhi-server/core/providers/tools/device_mcp/mcp_executor.py:21-66 | main/xiaozhi-server/core/providers/tools/mcp_endpoint/mcp_endpoint_executor.py:18-65 — These two members are one piece of code written twice and then edited apart: 46 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 29+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 29+ corresponding lines) main/manager-api/src/main/java/xiaozhi/modules/sys/controller/SysParamsController.java:177 — main/manager-api/src/main/java/xiaozhi/modules/sys/controller/SysParamsController.java:177-212 | main/manager-api/src/main/java/xiaozhi/modules/sys/controller/SysParamsController.java:214-242 | main/manager-api/src/main/java/xiaozhi/modules/sys/controller/SysParamsController.java:245-276 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 29 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (26 corresponding lines) · ×1
  • Edited copy of a member (26 corresponding lines) main/xiaozhi-server/performance_tester/performance_tester_stream_asr.py:347 — main/xiaozhi-server/performance_tester/performance_tester_stream_asr.py:347-372 | main/xiaozhi-server/performance_tester/performance_tester_stream_tts.py:574-602 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 22+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 22+ corresponding lines) main/manager-api/src/main/java/xiaozhi/modules/agent/service/impl/AgentSnapshotServiceImpl.java:544 — main/manager-api/src/main/java/xiaozhi/modules/agent/service/impl/AgentSnapshotServiceImpl.java:544-565 | main/manager-api/src/main/java/xiaozhi/modules/agent/service/impl/AgentSnapshotServiceImpl.java:816-837 | main/manager-api/src/main/java/xiaozhi/modules/agent/service/impl/AgentSnapshotServiceImpl.java:861-889 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 22 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (21 corresponding lines) · ×1
  • Edited copy of a member (21 corresponding lines) main/manager-api/src/main/java/xiaozhi/modules/device/service/impl/DeviceServiceImpl.java:390 — main/manager-api/src/main/java/xiaozhi/modules/device/service/impl/DeviceServiceImpl.java:390-411 | main/manager-api/src/main/java/xiaozhi/modules/sys/service/impl/SysUserServiceImpl.java:160-180 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 19+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 19+ corresponding lines) main/xiaozhi-server/core/providers/tts/huoshan_double_stream.py:401 — main/xiaozhi-server/core/providers/tts/huoshan_double_stream.py:401-430 | main/xiaozhi-server/core/providers/tts/huoshan_double_stream.py:433-452 | main/xiaozhi-server/core/providers/tts/huoshan_double_stream.py:455-473 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 19 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (25 corresponding lines) · ×1
  • Edited copy of a member (25 corresponding lines) REDACTED:119 — REDACTED:119-143 | REDACTED:135-159 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 18+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 18+ corresponding lines) main/manager-api/src/main/java/xiaozhi/modules/agent/service/impl/AgentChatSummaryServiceImpl.java:210 — main/manager-api/src/main/java/xiaozhi/modules/agent/service/impl/AgentChatSummaryServiceImpl.java:210-228 | main/manager-api/src/main/java/xiaozhi/modules/agent/service/impl/AgentServiceImpl.java:700-717 | main/manager-api/src/main/java/xiaozhi/modules/llm/service/impl/OpenAIStyleLLMServiceImpl.java:310-330 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 18 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 9+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 9+ corresponding lines) main/manager-api/src/main/java/xiaozhi/modules/sys/controller/AdminController.java:55 — main/manager-api/src/main/java/xiaozhi/modules/sys/controller/AdminController.java:55-63 | main/manager-api/src/main/java/xiaozhi/modules/sys/controller/AdminController.java:100-108 | main/manager-api/src/main/java/xiaozhi/modules/timbre/controller/TimbreController.java:52-62 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (7 members, 7+ corresponding lines) · ×1
  • Edited copies of one member (7 members, 7+ corresponding lines) main/xiaozhi-server/core/utils/asr.py:17 — main/xiaozhi-server/core/utils/asr.py:17-24 | main/xiaozhi-server/core/utils/intent.py:11-17 | main/xiaozhi-server/core/utils/llm.py:17-23 | main/xiaozhi-server/core/utils/memory.py:10-18 | main/xiaozhi-server/core/utils/tts.py:35-41 | main/xiaozhi-server/core/utils/vad.py:12-19 | main/xiaozhi-server/core/utils/vllm.py:17-23 — These 7 members are one piece of code written 7 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 7 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 11+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 11+ corresponding lines) main/manager-api/src/main/java/xiaozhi/modules/agent/controller/AgentController.java:226 — main/manager-api/src/main/java/xiaozhi/modules/agent/controller/AgentController.java:226-238 | main/manager-api/src/main/java/xiaozhi/modules/agent/controller/AgentController.java:244-256 | main/manager-api/src/main/java/xiaozhi/modules/agent/controller/AgentMcpAccessPointController.java:56-66 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (12 corresponding lines) · ×1
  • Edited copy of a member (12 corresponding lines) main/manager-api/src/main/java/xiaozhi/modules/security/secret/ServerSecretFilter.java:76 — main/manager-api/src/main/java/xiaozhi/modules/security/oauth2/Oauth2Filter.java:80-95 | main/manager-api/src/main/java/xiaozhi/modules/security/secret/ServerSecretFilter.java:76-87 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 13+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 13+ corresponding lines) main/manager-api/src/main/java/xiaozhi/modules/knowledge/controller/KnowledgeBaseController.java:63 — main/manager-api/src/main/java/xiaozhi/modules/knowledge/controller/KnowledgeBaseController.java:63-75 | main/manager-api/src/main/java/xiaozhi/modules/knowledge/controller/KnowledgeBaseController.java:89-106 | main/manager-api/src/main/java/xiaozhi/modules/knowledge/controller/KnowledgeBaseController.java:112-127 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 4+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 4+ corresponding lines) REDACTED:30 — REDACTED:30-33 | REDACTED:32-35 | REDACTED:28-31 | REDACTED:35-38 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (8 corresponding lines) · ×1
  • Edited copy of a member (8 corresponding lines) main/xiaozhi-server/core/providers/asr/doubao_stream.py:340 — main/xiaozhi-server/core/providers/asr/doubao_stream.py:340-347 | main/xiaozhi-server/core/providers/asr/doubao.py:107-114 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 1+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 1+ corresponding lines) main/xiaozhi-server/core/providers/tts/base.py:127 — main/xiaozhi-server/core/providers/tts/base.py:127-130 | main/xiaozhi-server/core/providers/tts/custom.py:31-31 | main/xiaozhi-server/core/providers/tts/edge.py:40-43 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 1 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (6 corresponding lines) · ×1
  • Edited copy of a member (6 corresponding lines) main/manager-api/src/main/java/xiaozhi/modules/device/service/impl/DeviceServiceImpl.java:305 — main/manager-api/src/main/java/xiaozhi/modules/device/service/impl/DeviceServiceImpl.java:305-310 | main/manager-api/src/main/java/xiaozhi/modules/voiceclone/service/impl/VoiceCloneServiceImpl.java:134-139 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 2+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 2+ corresponding lines) REDACTED:25 — REDACTED:25-26 | REDACTED:27-28 | REDACTED:23-24 | REDACTED:30-31 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 2 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 7+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 7+ corresponding lines) main/manager-api/src/main/java/xiaozhi/modules/knowledge/service/impl/KnowledgeBaseServiceImpl.java:176 — main/manager-api/src/main/java/xiaozhi/modules/knowledge/service/impl/KnowledgeBaseServiceImpl.java:176-182 | main/manager-api/src/main/java/xiaozhi/modules/model/service/impl/ModelConfigServiceImpl.java:298-304 | main/manager-api/src/main/java/xiaozhi/modules/sys/service/impl/SysDictTypeServiceImpl.java:67-74 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Duplicated block (70 lines × 2) · ×1
  • Duplicated block (70 lines × 2) main/xiaozhi-server/core/providers/tools/device_mcp/mcp_handler.py:303 — main/xiaozhi-server/core/providers/tools/device_mcp/mcp_handler.py:303-372 | main/xiaozhi-server/core/providers/tools/mcp_endpoint/mcp_endpoint_handler.py:289-358 — `main/xiaozhi-server/core/providers/tools/device_mcp/mcp_handler.py` and `main/xiaozhi-server/core/providers/tools/mcp_endpoint/mcp_endpoint_handler.py` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 5 separate duplicated blocks between them, totalling at least 158 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (22–37 lines × 4) · ×1
  • Duplicated block (22–37 lines × 4) REDACTED:37 — REDACTED:37-73 | REDACTED:39-60 | REDACTED:35-71 | REDACTED:42-72 — `REDACTED` and `REDACTED` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 80 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:37` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (34–35 lines × 2) · ×1
  • Duplicated block (34–35 lines × 2) main/xiaozhi-server/scripts/ws_lifecycle_smoke.py:300 — main/xiaozhi-server/scripts/ws_lifecycle_smoke.py:300-334 | main/xiaozhi-server/scripts/ws_lifecycle_smoke.py:348-381 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (33–34 lines × 2) · ×1
  • Duplicated block (33–34 lines × 2) main/xiaozhi-server/core/providers/tts/index_stream.py:40 — main/xiaozhi-server/core/providers/tts/index_stream.py:40-73 | main/xiaozhi-server/core/providers/tts/minimax_httpstream.py:97-129 — before extracting anything, compare `main/xiaozhi-server/core/providers/tts/index_stream.py` and `main/xiaozhi-server/core/providers/tts/minimax_httpstream.py` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 133 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (29–33 lines × 2) · ×1
  • Duplicated block (29–33 lines × 2) main/xiaozhi-server/core/providers/tools/device_mcp/mcp_handler.py:177 — main/xiaozhi-server/core/providers/tools/device_mcp/mcp_handler.py:177-205 | main/xiaozhi-server/core/providers/tools/mcp_endpoint/mcp_endpoint_handler.py:127-159 — `main/xiaozhi-server/core/providers/tools/device_mcp/mcp_handler.py` and `main/xiaozhi-server/core/providers/tools/mcp_endpoint/mcp_endpoint_handler.py` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 5 separate duplicated blocks between them, totalling at least 158 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
D4 · Code Duplication · Duplicated block (32–33 lines × 2) · ×1
  • Duplicated block (32–33 lines × 2) main/xiaozhi-server/core/providers/tts/alibl_stream.py:198 — main/xiaozhi-server/core/providers/tts/alibl_stream.py:198-229 | REDACTED:301-333 — before extracting anything, compare `main/xiaozhi-server/core/providers/tts/alibl_stream.py` and `REDACTED` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 297 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (32 lines × 2) · ×1
  • Duplicated block (32 lines × 2) main/xiaozhi-server/core/providers/tts/xunfei_stream.py:28 — main/xiaozhi-server/core/providers/tts/xunfei_stream.py:28-59 | main/xiaozhi-server/performance_tester/performance_tester_stream_tts.py:483-514 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
D4 · Code Duplication · Duplicated block (12–30 lines × 2) · ×1
  • Duplicated block (12–30 lines × 2) main/xiaozhi-server/core/providers/tts/alibl_stream.py:240 — main/xiaozhi-server/core/providers/tts/alibl_stream.py:240-251 | REDACTED:343-372 — before extracting anything, compare `main/xiaozhi-server/core/providers/tts/alibl_stream.py` and `REDACTED` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 297 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `main/xiaozhi-server/core/providers/tts/alibl_stream.py:240` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (28–29 lines × 3) · ×1
  • Duplicated block (28–29 lines × 3) main/xiaozhi-server/core/providers/tts/alibl_stream.py:142 — main/xiaozhi-server/core/providers/tts/alibl_stream.py:142-169 | REDACTED:247-275 | main/xiaozhi-server/core/providers/tts/huoshan_double_stream.py:319-346 — before extracting anything, compare `main/xiaozhi-server/core/providers/tts/alibl_stream.py` and `REDACTED` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 297 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `main/xiaozhi-server/core/providers/tts/alibl_stream.py:142` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (9–28 lines × 2) · ×1
  • Duplicated block (9–28 lines × 2) main/xiaozhi-server/core/providers/tts/alibl_stream.py:273 — main/xiaozhi-server/core/providers/tts/alibl_stream.py:273-281 | REDACTED:351-378 — before extracting anything, compare `main/xiaozhi-server/core/providers/tts/alibl_stream.py` and `REDACTED` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 297 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `main/xiaozhi-server/core/providers/tts/alibl_stream.py:273` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (24–27 lines × 2) · ×1
  • Duplicated block (24–27 lines × 2) main/xiaozhi-server/core/handle/textHandler/serverMessageHandler.py:68 — main/xiaozhi-server/core/handle/textHandler/serverMessageHandler.py:68-91 | main/xiaozhi-server/core/handle/textHandler/serverMessageHandler.py:119-145 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (27 lines × 2) · ×1
  • Duplicated block (27 lines × 2) main/xiaozhi-server/core/providers/tools/device_mcp/mcp_handler.py:377 — main/xiaozhi-server/core/providers/tools/device_mcp/mcp_handler.py:377-403 | main/xiaozhi-server/core/providers/tools/mcp_endpoint/mcp_endpoint_handler.py:366-392 — `main/xiaozhi-server/core/providers/tools/device_mcp/mcp_handler.py` and `main/xiaozhi-server/core/providers/tools/mcp_endpoint/mcp_endpoint_handler.py` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 5 separate duplicated blocks between them, totalling at least 158 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (21–27 lines × 2) · ×1
  • Duplicated block (21–27 lines × 2) main/xiaozhi-server/performance_tester/performance_tester_asr.py:287 — main/xiaozhi-server/performance_tester/performance_tester_asr.py:287-307 | main/xiaozhi-server/performance_tester/performance_tester_llm.py:425-451 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `main/xiaozhi-server/performance_tester/performance_tester_llm.py:425` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (24–26 lines × 2) · ×1
  • Duplicated block (24–26 lines × 2) main/xiaozhi-server/core/providers/tools/device_mcp/mcp_executor.py:43 — main/xiaozhi-server/core/providers/tools/device_mcp/mcp_executor.py:43-66 | main/xiaozhi-server/core/providers/tools/mcp_endpoint/mcp_endpoint_executor.py:40-65 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `main/xiaozhi-server/core/providers/tools/mcp_endpoint/mcp_endpoint_executor.py:40` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (22–26 lines × 2) · ×1
  • Duplicated block (22–26 lines × 2) main/xiaozhi-server/core/providers/tts/cozecn.py:34 — main/xiaozhi-server/core/providers/tts/cozecn.py:34-59 | main/xiaozhi-server/core/providers/tts/siliconflow.py:30-51 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (26 lines × 2) · ×1
  • Duplicated block (26 lines × 2) main/xiaozhi-server/core/providers/tts/index_stream.py:93 — main/xiaozhi-server/core/providers/tts/index_stream.py:93-118 | main/xiaozhi-server/core/providers/tts/minimax_httpstream.py:149-174 — before extracting anything, compare `main/xiaozhi-server/core/providers/tts/index_stream.py` and `main/xiaozhi-server/core/providers/tts/minimax_httpstream.py` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 133 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (23–24 lines × 2) · ×1
  • Duplicated block (23–24 lines × 2) main/xiaozhi-server/core/providers/llm/ollama/ollama.py:63 — main/xiaozhi-server/core/providers/llm/ollama/ollama.py:63-86 | main/xiaozhi-server/core/providers/llm/ollama/ollama.py:142-164 — 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (77–78 lines × 2) · ×1
  • Duplicated block (77–78 lines × 2) main/xiaozhi-server/core/providers/tts/alibl_stream.py:114 — main/xiaozhi-server/core/providers/tts/alibl_stream.py:114-191 | main/xiaozhi-server/core/providers/tts/huoshan_double_stream.py:291-367 — before extracting anything, compare `main/xiaozhi-server/core/providers/tts/alibl_stream.py` and `main/xiaozhi-server/core/providers/tts/huoshan_double_stream.py` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 196 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `main/xiaozhi-server/core/providers/tts/alibl_stream.py:114` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (19–23 lines × 2) · ×1
  • Duplicated block (19–23 lines × 2) REDACTED:183 — REDACTED:183-201 | main/xiaozhi-server/plugins_func/functions/get_news_from_newsnow.py:213-235 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `main/xiaozhi-server/plugins_func/functions/get_news_from_newsnow.py:213` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (19–21 lines × 3) · ×1
  • Duplicated block (19–21 lines × 3) main/xiaozhi-server/core/providers/tts/alibl_stream.py:387 — main/xiaozhi-server/core/providers/tts/alibl_stream.py:387-407 | REDACTED:464-482 | main/xiaozhi-server/core/providers/tts/xunfei_stream.py:405-425 — before extracting anything, compare `main/xiaozhi-server/core/providers/tts/alibl_stream.py` and `REDACTED` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 297 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `main/xiaozhi-server/core/providers/tts/alibl_stream.py:387` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `REDACTED:462` calls `isinstance`, `encode_pcm_to_opus_stream` and `main/xiaozhi-server/core/providers/tts/xunfei_stream.py:403` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (17–21 lines × 3) · ×1
  • Duplicated block (17–21 lines × 3) main/xiaozhi-server/core/providers/tts/alibl_stream.py:539 — main/xiaozhi-server/core/providers/tts/alibl_stream.py:539-559 | REDACTED:631-649 | main/xiaozhi-server/core/providers/tts/xunfei_stream.py:489-505 — before extracting anything, compare `main/xiaozhi-server/core/providers/tts/alibl_stream.py` and `REDACTED` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 297 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (13–20 lines × 2) · ×1
  • Duplicated block (13–20 lines × 2) main/xiaozhi-server/core/utils/p3.py:14 — main/xiaozhi-server/core/utils/p3.py:14-33 | main/xiaozhi-server/core/utils/p3.py:47-59 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (19 lines × 2) · ×1
  • Duplicated block (19 lines × 2) REDACTED:119 — REDACTED:119-137 | REDACTED:135-153 — `REDACTED` and `REDACTED` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 80 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `REDACTED:116` calls `makedirs` and `REDACTED:132` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (17 lines × 2) · ×1
  • Duplicated block (17 lines × 2) main/xiaozhi-server/core/utils/resilience.py:912 — main/xiaozhi-server/core/utils/resilience.py:912-928 | main/xiaozhi-server/core/utils/resilience.py:986-1002 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (14–16 lines × 2) · ×1
  • Duplicated block (14–16 lines × 2) REDACTED:226 — REDACTED:226-239 | main/xiaozhi-server/core/providers/asr/aliyunbl_stream.py:172-187 — before extracting anything, compare `REDACTED` and `main/xiaozhi-server/core/providers/asr/aliyunbl_stream.py` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 88 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (13–16 lines × 2) · ×1
  • Duplicated block (13–16 lines × 2) main/xiaozhi-server/core/providers/tts/index_stream.py:153 — main/xiaozhi-server/core/providers/tts/index_stream.py:153-168 | main/xiaozhi-server/core/providers/tts/minimax_httpstream.py:264-276 — before extracting anything, compare `main/xiaozhi-server/core/providers/tts/index_stream.py` and `main/xiaozhi-server/core/providers/tts/minimax_httpstream.py` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 133 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `main/xiaozhi-server/core/providers/tts/index_stream.py:153` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (15 lines × 3) · ×1
  • Duplicated block (15 lines × 3) main/xiaozhi-server/core/providers/tts/alibl_stream.py:234 — main/xiaozhi-server/core/providers/tts/alibl_stream.py:234-248 | REDACTED:337-351 | main/xiaozhi-server/core/providers/tts/xunfei_stream.py:275-289 — before extracting anything, compare `main/xiaozhi-server/core/providers/tts/alibl_stream.py` and `REDACTED` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 297 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (13–14 lines × 4) · ×1
  • Duplicated block (13–14 lines × 4) main/xiaozhi-server/core/providers/tts/alibl_stream.py:119 — main/xiaozhi-server/core/providers/tts/alibl_stream.py:119-131 | REDACTED:227-240 | main/xiaozhi-server/core/providers/tts/huoshan_double_stream.py:296-308 | main/xiaozhi-server/core/providers/tts/xunfei_stream.py:160-172 — before extracting anything, compare `main/xiaozhi-server/core/providers/tts/alibl_stream.py` and `REDACTED` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 297 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:227` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (12–13 lines × 3) · ×1
  • Duplicated block (12–13 lines × 3) REDACTED:131 — REDACTED:131-143 | REDACTED:147-159 | REDACTED:163-174 — `REDACTED` and `REDACTED` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 80 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
D4 · Code Duplication · Duplicated block (13 lines × 3) · ×1
  • Duplicated block (13 lines × 3) REDACTED:298 — REDACTED:298-310 | main/xiaozhi-server/core/providers/tts/huoshan_double_stream.py:371-386 | main/xiaozhi-server/core/providers/tts/xunfei_stream.py:244-257 — before extracting anything, compare `REDACTED` and `main/xiaozhi-server/core/providers/tts/huoshan_double_stream.py` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 119 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (12 lines × 4) · ×1
  • Duplicated block (12 lines × 4) main/xiaozhi-server/core/providers/tts/alibl_stream.py:151 — main/xiaozhi-server/core/providers/tts/alibl_stream.py:151-162 | REDACTED:257-268 | main/xiaozhi-server/core/providers/tts/huoshan_double_stream.py:328-339 | main/xiaozhi-server/core/providers/tts/xunfei_stream.py:200-211 — before extracting anything, compare `main/xiaozhi-server/core/providers/tts/alibl_stream.py` and `REDACTED` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 297 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (8–12 lines × 2) · ×1
  • Duplicated block (8–12 lines × 2) main/xiaozhi-server/core/providers/asr/doubao_stream.py:125 — main/xiaozhi-server/core/providers/asr/doubao_stream.py:125-136 | main/xiaozhi-server/core/providers/asr/doubao_stream.py:150-157 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (10–11 lines × 4) · ×1
  • Duplicated block (10–11 lines × 4) main/xiaozhi-server/core/providers/tts/alibl_stream.py:181 — main/xiaozhi-server/core/providers/tts/alibl_stream.py:181-190 | REDACTED:286-295 | main/xiaozhi-server/core/providers/tts/huoshan_double_stream.py:357-366 | main/xiaozhi-server/core/providers/tts/xunfei_stream.py:230-240 — before extracting anything, compare `main/xiaozhi-server/core/providers/tts/alibl_stream.py` and `REDACTED` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 297 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `main/xiaozhi-server/core/providers/tts/xunfei_stream.py:230` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `REDACTED:285` calls `result` and `main/xiaozhi-server/core/providers/tts/xunfei_stream.py:230` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (11 lines × 3) · ×1
  • Duplicated block (11 lines × 3) REDACTED:110 — REDACTED:110-120 | REDACTED:116-126 | main/xiaozhi-server/core/providers/tts/edge.py:23-33 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 81 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `main/xiaozhi-server/core/providers/tts/edge.py:20` calls `get` and `REDACTED:107` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (9–11 lines × 2) · ×1
  • Duplicated block (9–11 lines × 2) main/xiaozhi-server/core/providers/tts/index_stream.py:135 — main/xiaozhi-server/core/providers/tts/index_stream.py:135-143 | main/xiaozhi-server/core/providers/tts/minimax_httpstream.py:205-215 — before extracting anything, compare `main/xiaozhi-server/core/providers/tts/index_stream.py` and `main/xiaozhi-server/core/providers/tts/minimax_httpstream.py` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 133 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `main/xiaozhi-server/core/providers/tts/minimax_httpstream.py:205` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (9–10 lines × 2) · ×1
  • Duplicated block (9–10 lines × 2) main/xiaozhi-server/performance_tester/performance_tester_stream_asr.py:354 — main/xiaozhi-server/performance_tester/performance_tester_stream_asr.py:354-362 | main/xiaozhi-server/performance_tester/performance_tester_stream_tts.py:583-592 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `main/xiaozhi-server/performance_tester/performance_tester_stream_asr.py:354` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (7–9 lines × 6) · ×1
  • Duplicated block (7–9 lines × 6) main/xiaozhi-server/core/providers/tts/alibl_stream.py:166 — main/xiaozhi-server/core/providers/tts/alibl_stream.py:166-173 | REDACTED:272-278 | main/xiaozhi-server/core/providers/tts/huoshan_double_stream.py:343-349 | main/xiaozhi-server/core/providers/tts/index_stream.py:57-64 | main/xiaozhi-server/core/providers/tts/minimax_httpstream.py:114-120 | main/xiaozhi-server/core/providers/tts/xunfei_stream.py:216-224 — before extracting anything, compare `main/xiaozhi-server/core/providers/tts/alibl_stream.py` and `REDACTED` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 297 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (8–9 lines × 4) · ×1
  • Duplicated block (8–9 lines × 4) main/xiaozhi-server/core/providers/tts/alibl_stream.py:141 — main/xiaozhi-server/core/providers/tts/alibl_stream.py:141-148 | REDACTED:246-254 | main/xiaozhi-server/core/providers/tts/huoshan_double_stream.py:318-325 | main/xiaozhi-server/core/providers/tts/xunfei_stream.py:188-196 — before extracting anything, compare `main/xiaozhi-server/core/providers/tts/alibl_stream.py` and `REDACTED` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 297 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `main/xiaozhi-server/core/providers/tts/alibl_stream.py:141` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (9 lines × 4) · ×1
  • Duplicated block (9 lines × 4) main/xiaozhi-server/core/providers/tts/alibl_stream.py:362 — main/xiaozhi-server/core/providers/tts/alibl_stream.py:362-370 | REDACTED:446-454 | main/xiaozhi-server/core/providers/tts/huoshan_double_stream.py:527-535 | main/xiaozhi-server/core/providers/tts/xunfei_stream.py:379-387 — before extracting anything, compare `main/xiaozhi-server/core/providers/tts/alibl_stream.py` and `REDACTED` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 297 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (8–9 lines × 2) · ×1
  • Duplicated block (8–9 lines × 2) main/xiaozhi-server/core/api/vision_handler.py:161 — main/xiaozhi-server/core/api/vision_handler.py:161-169 | main/xiaozhi-server/core/api/vision_handler.py:186-193 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `main/xiaozhi-server/core/api/vision_handler.py:161` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (7–8 lines × 3) · ×1
  • Duplicated block (7–8 lines × 3) main/xiaozhi-server/core/providers/tts/huoshan_double_stream.py:424 — main/xiaozhi-server/core/providers/tts/huoshan_double_stream.py:424-430 | main/xiaozhi-server/core/providers/tts/huoshan_double_stream.py:445-452 | main/xiaozhi-server/core/providers/tts/huoshan_double_stream.py:467-473 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
D4 · Code Duplication · Duplicated block (6 lines × 3) · ×1
  • Duplicated block (6 lines × 3) main/xiaozhi-server/core/providers/tts/alibl_stream.py:481 — main/xiaozhi-server/core/providers/tts/alibl_stream.py:481-486 | main/xiaozhi-server/core/providers/tts/alibl_stream.py:532-537 | REDACTED:564-569 — before extracting anything, compare `main/xiaozhi-server/core/providers/tts/alibl_stream.py` and `REDACTED` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 297 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (7–8 lines × 2) · ×1
  • Duplicated block (7–8 lines × 2) main/xiaozhi-server/core/handle/reportHandle.py:119 — main/xiaozhi-server/core/handle/reportHandle.py:119-126 | main/xiaozhi-server/core/handle/reportHandle.py:172-178 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
D4 · Code Duplication · Duplicated block (19 lines × 3) · ×1
  • Duplicated block (19 lines × 3) main/xiaozhi-server/core/providers/tools/device_mcp/mcp_client.py:29 — main/xiaozhi-server/core/providers/tools/device_mcp/mcp_client.py:29-47 | main/xiaozhi-server/core/providers/tools/device_mcp/mcp_handler.py:36-54 | main/xiaozhi-server/core/providers/tools/mcp_endpoint/mcp_endpoint_client.py:31-49 — before extracting anything, compare `main/xiaozhi-server/core/providers/tools/device_mcp/mcp_client.py` and `main/xiaozhi-server/core/providers/tools/device_mcp/mcp_handler.py` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 43 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (7 lines × 3) · ×1
  • Duplicated block (7 lines × 3) main/xiaozhi-server/core/providers/tools/device_mcp/mcp_client.py:58 — main/xiaozhi-server/core/providers/tools/device_mcp/mcp_client.py:58-64 | main/xiaozhi-server/core/providers/tools/device_mcp/mcp_handler.py:65-71 | main/xiaozhi-server/core/providers/tools/mcp_endpoint/mcp_endpoint_client.py:60-66 — before extracting anything, compare `main/xiaozhi-server/core/providers/tools/device_mcp/mcp_client.py` and `main/xiaozhi-server/core/providers/tools/device_mcp/mcp_handler.py` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 43 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (14 lines × 3) · ×1
  • Duplicated block (14 lines × 3) main/xiaozhi-server/core/providers/tts/alibl_stream.py:412 — main/xiaozhi-server/core/providers/tts/alibl_stream.py:412-425 | REDACTED:487-500 | main/xiaozhi-server/core/providers/tts/xunfei_stream.py:510-523 — before extracting anything, compare `main/xiaozhi-server/core/providers/tts/alibl_stream.py` and `REDACTED` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 297 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (22–24 lines × 3) · ×1
  • Duplicated block (22–24 lines × 3) main/manager-api/src/main/java/xiaozhi/modules/llm/service/impl/OpenAIStyleLLMServiceImpl.java:128 — main/manager-api/src/main/java/xiaozhi/modules/llm/service/impl/OpenAIStyleLLMServiceImpl.java:128-151 | main/manager-api/src/main/java/xiaozhi/modules/llm/service/impl/OpenAIStyleLLMServiceImpl.java:222-245 | main/manager-api/src/main/java/xiaozhi/modules/llm/service/impl/OpenAIStyleLLMServiceImpl.java:376-397 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `main/manager-api/src/main/java/xiaozhi/modules/llm/service/impl/OpenAIStyleLLMServiceImpl.java:128` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (23 lines × 2) · ×1
  • Duplicated block (23 lines × 2) main/manager-api/src/main/java/xiaozhi/modules/sys/utils/WebSocketClientManager.java:117 — main/manager-api/src/main/java/xiaozhi/modules/sys/utils/WebSocketClientManager.java:117-139 | main/manager-api/src/main/java/xiaozhi/modules/sys/utils/WebSocketClientManager.java:148-170 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `main/manager-api/src/main/java/xiaozhi/modules/sys/utils/WebSocketClientManager.java:140` calls `close` and `main/manager-api/src/main/java/xiaozhi/modules/sys/utils/WebSocketClientManager.java:172` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (10–13 lines × 3) · ×1
  • Duplicated block (10–13 lines × 3) main/manager-api/src/main/java/xiaozhi/modules/llm/service/impl/OpenAIStyleLLMServiceImpl.java:83 — main/manager-api/src/main/java/xiaozhi/modules/llm/service/impl/OpenAIStyleLLMServiceImpl.java:83-95 | main/manager-api/src/main/java/xiaozhi/modules/llm/service/impl/OpenAIStyleLLMServiceImpl.java:180-190 | main/manager-api/src/main/java/xiaozhi/modules/llm/service/impl/OpenAIStyleLLMServiceImpl.java:339-348 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `main/manager-api/src/main/java/xiaozhi/modules/llm/service/impl/OpenAIStyleLLMServiceImpl.java:83` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (12–13 lines × 2) · ×1
  • Duplicated block (12–13 lines × 2) main/manager-api/src/main/java/xiaozhi/modules/agent/service/impl/AgentChatSummaryServiceImpl.java:213 — main/manager-api/src/main/java/xiaozhi/modules/agent/service/impl/AgentChatSummaryServiceImpl.java:213-224 | main/manager-api/src/main/java/xiaozhi/modules/llm/service/impl/OpenAIStyleLLMServiceImpl.java:314-326 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `main/manager-api/src/main/java/xiaozhi/modules/agent/service/impl/AgentChatSummaryServiceImpl.java:213` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (11 lines × 4) · ×1
  • Duplicated block (11 lines × 4) main/manager-api/src/main/java/xiaozhi/modules/knowledge/service/impl/KnowledgeFilesServiceImpl.java:348 — main/manager-api/src/main/java/xiaozhi/modules/knowledge/service/impl/KnowledgeFilesServiceImpl.java:348-358 | main/manager-api/src/main/java/xiaozhi/modules/knowledge/service/impl/KnowledgeFilesServiceImpl.java:681-691 | main/manager-api/src/main/java/xiaozhi/modules/knowledge/service/impl/KnowledgeFilesServiceImpl.java:709-719 | main/manager-api/src/main/java/xiaozhi/modules/knowledge/service/impl/KnowledgeFilesServiceImpl.java:737-747 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `main/manager-api/src/main/java/xiaozhi/modules/knowledge/service/impl/KnowledgeFilesServiceImpl.java:348` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (8–11 lines × 3) · ×1
  • Duplicated block (8–11 lines × 3) main/manager-api/src/main/java/xiaozhi/modules/llm/service/impl/OpenAIStyleLLMServiceImpl.java:113 — main/manager-api/src/main/java/xiaozhi/modules/llm/service/impl/OpenAIStyleLLMServiceImpl.java:113-123 | main/manager-api/src/main/java/xiaozhi/modules/llm/service/impl/OpenAIStyleLLMServiceImpl.java:210-217 | main/manager-api/src/main/java/xiaozhi/modules/llm/service/impl/OpenAIStyleLLMServiceImpl.java:364-371 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `main/manager-api/src/main/java/xiaozhi/modules/llm/service/impl/OpenAIStyleLLMServiceImpl.java:113` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (8–10 lines × 3) · ×1
  • Duplicated block (8–10 lines × 3) main/manager-api/src/main/java/xiaozhi/modules/agent/service/impl/AgentChatSummaryServiceImpl.java:211 — main/manager-api/src/main/java/xiaozhi/modules/agent/service/impl/AgentChatSummaryServiceImpl.java:211-218 | main/manager-api/src/main/java/xiaozhi/modules/agent/service/impl/AgentServiceImpl.java:701-708 | main/manager-api/src/main/java/xiaozhi/modules/llm/service/impl/OpenAIStyleLLMServiceImpl.java:311-320 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `main/manager-api/src/main/java/xiaozhi/modules/agent/service/impl/AgentChatSummaryServiceImpl.java:211` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (8–10 lines × 2) · ×1
  • Duplicated block (8–10 lines × 2) main/manager-api/src/main/java/xiaozhi/modules/knowledge/service/impl/KnowledgeFilesServiceImpl.java:148 — main/manager-api/src/main/java/xiaozhi/modules/knowledge/service/impl/KnowledgeFilesServiceImpl.java:148-155 | main/manager-api/src/main/java/xiaozhi/modules/knowledge/service/impl/KnowledgeFilesServiceImpl.java:961-970 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `main/manager-api/src/main/java/xiaozhi/modules/knowledge/service/impl/KnowledgeFilesServiceImpl.java:148` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (16 lines × 2) · ×1
  • Duplicated block (16 lines × 2) main/manager-api/src/main/java/xiaozhi/modules/sys/service/impl/SysDictDataServiceImpl.java:137 — main/manager-api/src/main/java/xiaozhi/modules/sys/service/impl/SysDictDataServiceImpl.java:137-152 | main/manager-api/src/main/java/xiaozhi/modules/sys/service/impl/SysDictTypeServiceImpl.java:126-141 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D6 · Cohesion (LCOM4) · Low cohesion · ×1
  • Low cohesion: TTSProviderBase (LCOM4 4) main/xiaozhi-server/core/providers/tts/base.py:39 — TTSProviderBase's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
R1 · Type Safety · Type Safety · ×1
  • Type Safety — 69 typed · 124 plain JS — the untyped files are main/digital-human/js/app.js, main/digital-human/js/config/manager.js, main/digital-human/js/core/audio/opus-codec.js, main/digital-human/js/core/audio/player.js, main/digital-human/js/core/audio/recorder.js, main/digital-human/js/core/audio/stream-context.js (+118 more).
R10 · Code Duplication · Duplication concentrated across 2 sibling directories (16 clone groups) · ×1
  • Duplication concentrated across 2 sibling directories (16 clone groups) main/manager-web/src/components/HeaderBar.vue:233 — 16 duplicated blocks under main/manager-web/src/ have copies in at least two of the sibling directories components, views — 8 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 16 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 16 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 16 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Duplication concentrated across 8 sibling directories (9 clone groups) · ×1
  • Duplication concentrated across 8 sibling directories (9 clone groups) main/manager-mobile/src/pages/forgot-password/index.vue:154 — 9 duplicated blocks under main/manager-mobile/src/pages/ have copies in at least two of the sibling directories agent, chat-history, device, forgot-password, index, login (+2 more sibling(s) not listed) — 8 of them are reported below, and 1 is counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 9 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 9 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 9 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Duplication concentrated across 2 sibling directories (6 clone groups) · ×1
  • Duplication concentrated across 2 sibling directories (6 clone groups) main/manager-mobile/src/pages/agent/components/agentSnapshotUtils.mjs:112 — 6 duplicated blocks under main/ have copies in at least two of the sibling directories manager-mobile, manager-web — 5 of them are reported below, and 1 is counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 6 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 6 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 6 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Duplicated block with local edits (139 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (139 matched lines × 2 locations) main/manager-web/src/views/OtaManagement.vue:130 — main/manager-web/src/views/OtaManagement.vue:130 · main/manager-web/src/views/VoiceResourceManagement.vue:105 — the two spans are one implementation copied and then locally edited — 792 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block with local edits (105 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (105 matched lines × 2 locations) main/manager-web/src/views/register.vue:134 — main/manager-web/src/views/register.vue:134 · main/manager-web/src/views/retrievePassword.vue:111 — the two spans are one implementation copied and then locally edited — 635 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block with local edits (99 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (99 matched lines × 2 locations) main/manager-mobile/src/pages/forgot-password/index.vue:154 — main/manager-mobile/src/pages/forgot-password/index.vue:154 · main/manager-mobile/src/pages/register/index.vue:165 — the two spans are one implementation copied and then locally edited — 480 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block with local edits (64 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (64 matched lines × 2 locations) main/manager-mobile/src/pages/login/index.vue:63 — main/manager-mobile/src/pages/login/index.vue:63 · main/manager-mobile/src/pages/register/index.vue:74 — the two spans are one implementation copied and then locally edited — 362 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block with local edits (60 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (60 matched lines × 2 locations) main/digital-human/js/live2d/live2d.js:158 — main/digital-human/js/live2d/live2d.js:158 · main/digital-human/js/live2d/live2d.js:609 — the two spans are one implementation copied and then locally edited — 530 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block (46 lines × 2 locations) · ×1
  • Duplicated block (46 lines × 2 locations) main/manager-mobile/src/pages/chat-history/detail.vue:127 — main/manager-mobile/src/pages/chat-history/detail.vue:127 · main/manager-mobile/src/pages/chat-history/index.vue:119 — 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.
R10 · Code Duplication · Duplicated block (45 lines × 2 locations) · ×1
  • Duplicated block (45 lines × 2 locations) main/manager-mobile/src/pages/device-config/components/ultrasonic-config.vue:177 — main/manager-mobile/src/pages/device-config/components/ultrasonic-config.vue:177 · main/manager-mobile/src/pages/device-config/components/ultrasonic-config.vue:299 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
R10 · Code Duplication · Duplicated block (41 lines × 2 locations) · ×1
  • Duplicated block (41 lines × 2 locations) main/manager-web/src/components/HeaderBar.vue:233 — main/manager-web/src/components/HeaderBar.vue:233 · main/manager-web/src/views/login.vue:174 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block with local edits (36 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (36 matched lines × 2 locations) main/manager-web/src/apis/module/agent.js:83 — main/manager-web/src/apis/module/agent.js:83 · main/manager-web/src/apis/module/agent.js:533 — the two spans are one implementation copied and then locally edited — 186 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block with local edits (32 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (32 matched lines × 2 locations) main/manager-web/src/components/AgentSnapshotDialog.vue:1289 — main/manager-web/src/components/AgentSnapshotDialog.vue:1289 · main/manager-web/src/components/AgentSnapshotDialog.vue:1382 — the two spans are one implementation copied and then locally edited — 162 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block (30 lines × 2 locations) · ×1
  • Duplicated block (30 lines × 2 locations) main/manager-web/src/components/TtsModel.vue:497 — main/manager-web/src/components/TtsModel.vue:497 · main/manager-web/src/views/VoiceResourceManagement.vue:223 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
R10 · Code Duplication · Duplicated block (29 lines × 2 locations) · ×1
  • Duplicated block (29 lines × 2 locations) main/manager-mobile/src/pages/forgot-password/index.vue:23 — main/manager-mobile/src/pages/forgot-password/index.vue:23 · main/manager-mobile/src/pages/register/index.vue:22 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of MODULE-LEVEL DECLARATIONS — bindings the module declares and exports — rather than statements with a call site. Do not read this as an extract-a-helper row: a call expression cannot stand where a declaration was, and putting one there would delete the names themselves, which are what the rest of the codebase imports. What actually repeats here is the INITIALISER — the same expression shape written once per binding. So give that expression one name (a small helper the initialisers call, or a shared base value they are each derived from) and keep every binding under the name it already has. Where the run is an enumeration — one binding per distinct thing, differing precisely in the thing each one names — the repetition IS the enumeration and collapsing it would delete entries; consider instead whether the set belongs in one exported table the individual names are read out of. Reported because the copies drift apart the first time only one of them is edited.
R10 · Code Duplication · Duplicated block (25 lines × 2 locations) · ×1
  • Duplicated block (25 lines × 2 locations) main/manager-web/src/apis/module/model.js:328 — main/manager-web/src/apis/module/model.js:328 · main/manager-web/src/apis/module/model.js:359 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
R10 · Code Duplication · Duplicated block (23 lines × 2 locations) · ×1
  • Duplicated block (23 lines × 2 locations) main/manager-mobile/src/api/agent/agent.ts:158 — main/manager-mobile/src/api/agent/agent.ts:158 · main/manager-mobile/src/api/voiceprint/voiceprint.ts:9 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
R10 · Code Duplication · Duplicated block with local edits (19 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (19 matched lines × 2 locations) main/manager-mobile/src/pages/agent/components/agentSnapshotUtils.mjs:60 — main/manager-mobile/src/pages/agent/components/agentSnapshotUtils.mjs:60 · main/manager-web/src/components/agentSnapshotDisplayUtils.mjs:5 — the two spans are one implementation copied and then locally edited — 134 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block with local edits (17 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (17 matched lines × 2 locations) main/digital-human/js/core/audio/opus-codec.js:151 — main/digital-human/js/core/audio/opus-codec.js:151 · main/digital-human/js/core/audio/player.js:114 — the two spans are one implementation copied and then locally edited — 79 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.
R2 · Cyclomatic Complexity · Complex function animateMouth (cyclomatic 29, cognitive 46) · ×1
  • Complex function animateMouth (cyclomatic 29, cognitive 46) main/digital-human/js/live2d/live2d.js:418 — animateMouth has cyclomatic complexity 29 and cognitive complexity 46; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function selectRoleTemplate (cyclomatic 28, cognitive 33) · ×1
  • Complex function selectRoleTemplate (cyclomatic 28, cognitive 33) main/manager-mobile/src/pages/agent/edit.vue:724 — selectRoleTemplate has cyclomatic complexity 28 and cognitive complexity 33; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function handleTextMessage (cyclomatic 25, cognitive 40) · ×1
  • Complex function handleTextMessage (cyclomatic 25, cognitive 40) main/digital-human/js/core/network/websocket.js:97 — handleTextMessage has cyclomatic complexity 25 and cognitive complexity 40; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function saveAgent (cyclomatic 23, cognitive 23) · ×1
  • Complex function saveAgent (cyclomatic 23, cognitive 23) main/manager-mobile/src/pages/agent/edit.vue:986 — saveAgent has cyclomatic complexity 23 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.
R2 · Cyclomatic Complexity · Complex function applyTemplateData (cyclomatic 23, cognitive 22) · ×1
  • Complex function applyTemplateData (cyclomatic 23, cognitive 22) main/manager-web/src/views/roleConfig.vue:865 — applyTemplateData has cyclomatic complexity 23 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function redactCapabilityPath (cyclomatic 22, cognitive 28) · ×1
  • Complex function redactCapabilityPath (cyclomatic 22, cognitive 28) main/manager-mobile/src/pages/agent/components/agentSnapshotUtils.mjs:196 — redactCapabilityPath has cyclomatic complexity 22 and cognitive complexity 28; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function confirmRestoreSnapshot (cyclomatic 22, cognitive 22) · ×1
  • Complex function confirmRestoreSnapshot (cyclomatic 22, cognitive 22) main/manager-mobile/src/pages/agent/components/AgentSnapshotPanel.vue:533 — confirmRestoreSnapshot has cyclomatic complexity 22 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function onPickerConfirm (cyclomatic 22, cognitive 15) · ×1
  • Complex function onPickerConfirm (cyclomatic 22, cognitive 15) main/manager-mobile/src/pages/agent/edit.vue:789 — onPickerConfirm has cyclomatic complexity 22 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 21, cognitive 71) · ×1
  • Complex function (anonymous) (cyclomatic 21, cognitive 71) main/manager-web/src/utils/featureManager.js:95 — (anonymous) has cyclomatic complexity 21 and cognitive complexity 71; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function playVoicePreview (cyclomatic 20, cognitive 25) · ×1
  • Complex function playVoicePreview (cyclomatic 20, cognitive 25) main/manager-web/src/views/roleConfig.vue:1578 — playVoicePreview has cyclomatic complexity 20 and cognitive complexity 25; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 20, cognitive 23) · ×1
  • Complex function (anonymous) (cyclomatic 20, cognitive 23) main/digital-human/js/live2d/live2d.js:206 — (anonymous) has cyclomatic complexity 20 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.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 20, cognitive 19) · ×1
  • Complex function (anonymous) (cyclomatic 20, cognitive 19) main/manager-web/src/views/roleConfig.vue:960 — (anonymous) has cyclomatic complexity 20 and cognitive complexity 19; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function formatDisplayValue (cyclomatic 20, cognitive 17) · ×1
  • Complex function formatDisplayValue (cyclomatic 20, cognitive 17) main/manager-mobile/src/pages/agent/components/AgentSnapshotPanel.vue:780 — formatDisplayValue has cyclomatic complexity 20 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 18, cognitive 20) · ×1
  • Complex function (anonymous) (cyclomatic 18, cognitive 20) main/digital-human/js/live2d/live2d.js:662 — (anonymous) has cyclomatic complexity 18 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function handleConnect (cyclomatic 17, cognitive 27) · ×1
  • Complex function handleConnect (cyclomatic 17, cognitive 27) main/digital-human/js/ui/controller.js:679 — handleConnect has cyclomatic complexity 17 and cognitive complexity 27; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function fetchAllLanguag (cyclomatic 17, cognitive 18) · ×1
  • Complex function fetchAllLanguag (cyclomatic 17, cognitive 18) main/manager-mobile/src/pages/agent/edit.vue:622 — fetchAllLanguag has cyclomatic complexity 17 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function buildTtsDraft (cyclomatic 17, cognitive 17) · ×1
  • Complex function buildTtsDraft (cyclomatic 17, cognitive 17) main/manager-web/src/views/roleConfig.vue:1147 — buildTtsDraft has cyclomatic complexity 17 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.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 17, cognitive 15) · ×1
  • Complex function (anonymous) (cyclomatic 17, cognitive 15) main/manager-web/src/views/AgentTemplateManagement.vue:247 — (anonymous) has cyclomatic complexity 17 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function updateDialButton (cyclomatic 16, cognitive 29) · ×1
  • Complex function updateDialButton (cyclomatic 16, cognitive 29) main/digital-human/js/ui/controller.js:325 — updateDialButton has cyclomatic complexity 16 and cognitive complexity 29; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function handleRegister (cyclomatic 16, cognitive 21) · ×1
  • Complex function handleRegister (cyclomatic 16, cognitive 21) main/manager-mobile/src/pages/register/index.vue:193 — handleRegister has cyclomatic complexity 16 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function buildSavedVersionDetail (cyclomatic 15, cognitive 10) · ×1
  • Complex function buildSavedVersionDetail (cyclomatic 15, cognitive 10) main/manager-mobile/src/pages/agent/components/AgentSnapshotPanel.vue:483 — buildSavedVersionDetail has cyclomatic complexity 15 and cognitive complexity 10; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function handleMCPMessage (cyclomatic 14, cognitive 20) · ×1
  • Complex function handleMCPMessage (cyclomatic 14, cognitive 20) main/digital-human/js/core/network/websocket.js:270 — handleMCPMessage has cyclomatic complexity 14 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 14, cognitive 17) · ×1
  • Complex function (anonymous) (cyclomatic 14, cognitive 17) main/digital-human/js/app.js:267 — (anonymous) 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.
R2 · Cyclomatic Complexity · Complex function handleApplyWakeword (cyclomatic 14, cognitive 16) · ×1
  • Complex function handleApplyWakeword (cyclomatic 14, cognitive 16) main/digital-human/js/ui/controller.js:544 — handleApplyWakeword has cyclomatic complexity 14 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function onmessage (cyclomatic 14, cognitive 14) · ×1
  • Complex function onmessage (cyclomatic 14, cognitive 14) main/digital-human/js/core/network/wakeword-bridge.js:42 — onmessage 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.
R2 · Cyclomatic Complexity · Complex function loadSnapshots (cyclomatic 14, cognitive 14) · ×1
  • Complex function loadSnapshots (cyclomatic 14, cognitive 14) main/manager-mobile/src/pages/agent/components/AgentSnapshotPanel.vue:286 — loadSnapshots 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.
R2 · Cyclomatic Complexity · Complex function loadConfig (cyclomatic 14, cognitive 13) · ×1
  • Complex function loadConfig (cyclomatic 14, cognitive 13) main/digital-human/js/config/manager.js:20 — loadConfig has cyclomatic complexity 14 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function handlePointerUp (cyclomatic 13, cognitive 19) · ×1
  • Complex function handlePointerUp (cyclomatic 13, cognitive 19) main/digital-human/js/live2d/live2d.js:303 — handlePointerUp has cyclomatic complexity 13 and cognitive complexity 19; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function handleTTSMessage (cyclomatic 13, cognitive 17) · ×1
  • Complex function handleTTSMessage (cyclomatic 13, cognitive 17) main/digital-human/js/core/network/websocket.js:173 — handleTTSMessage has cyclomatic complexity 13 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.
R2 · Cyclomatic Complexity · Complex function validateContent (cyclomatic 13, cognitive 17) · ×1
  • Complex function validateContent (cyclomatic 13, cognitive 17) main/manager-web/src/components/ReplacementWordDialog.vue:86 — validateContent has cyclomatic complexity 13 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.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 13, cognitive 13) · ×1
  • Complex function (anonymous) (cyclomatic 13, cognitive 13) main/digital-human/js/live2d/live2d.js:178 — (anonymous) 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.
R2 · Cyclomatic Complexity · Complex function previewRestoreSnapshot (cyclomatic 13, cognitive 13) · ×1
  • Complex function previewRestoreSnapshot (cyclomatic 13, cognitive 13) main/manager-mobile/src/pages/agent/components/AgentSnapshotPanel.vue:400 — previewRestoreSnapshot 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.
R2 · Cyclomatic Complexity · Complex function filterVoicesByLanguage (cyclomatic 13, cognitive 13) · ×1
  • Complex function filterVoicesByLanguage (cyclomatic 13, cognitive 13) main/manager-web/src/views/roleConfig.vue:1266 — filterVoicesByLanguage 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.
R2 · Cyclomatic Complexity · Complex function confirm (cyclomatic 13, cognitive 12) · ×1
  • Complex function confirm (cyclomatic 13, cognitive 12) main/manager-web/src/components/AddModelDialog.vue:190 — confirm 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.
R2 · Cyclomatic Complexity · Complex function saveConfig (cyclomatic 13, cognitive 12) · ×1
  • Complex function saveConfig (cyclomatic 13, cognitive 12) main/manager-web/src/views/roleConfig.vue:628 — saveConfig 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.
R2 · Cyclomatic Complexity · Complex function handleModelChange (cyclomatic 12, cognitive 14) · ×1
  • Complex function handleModelChange (cyclomatic 12, cognitive 14) main/manager-web/src/views/roleConfig.vue:1347 — handleModelChange 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.
R2 · Cyclomatic Complexity · Complex function normalizeValueForField (cyclomatic 12, cognitive 13) · ×1
  • Complex function normalizeValueForField (cyclomatic 12, cognitive 13) main/manager-web/src/components/AgentSnapshotDialog.vue:1923 — normalizeValueForField has cyclomatic complexity 12 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.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 12, cognitive 13) · ×1
  • Complex function (anonymous) (cyclomatic 12, cognitive 13) main/manager-web/src/views/KnowledgeBaseManagement.vue:604 — (anonymous) has cyclomatic complexity 12 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.
R2 · Cyclomatic Complexity · Complex function start (cyclomatic 12, cognitive 12) · ×1
  • Complex function start (cyclomatic 12, cognitive 12) main/digital-human/js/core/audio/recorder.js:203 — start 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.
R2 · Cyclomatic Complexity · Complex function stop (cyclomatic 12, cognitive 12) · ×1
  • Complex function stop (cyclomatic 12, cognitive 12) main/digital-human/js/core/audio/recorder.js:282 — stop 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.
R3 · Large Files · main/manager-web/src/components/AgentSnapshotDialog.vue · ×1
  • main/manager-web/src/components/AgentSnapshotDialog.vue: 2542 lines of code main/manager-web/src/components/AgentSnapshotDialog.vue:1 — main/manager-web/src/components/AgentSnapshotDialog.vue has 2542 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · main/manager-web/src/views/roleConfig.vue · ×1
  • main/manager-web/src/views/roleConfig.vue: 2283 lines of code main/manager-web/src/views/roleConfig.vue:1 — main/manager-web/src/views/roleConfig.vue has 2283 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · main/manager-mobile/src/pages/agent/edit.vue · ×1
  • main/manager-mobile/src/pages/agent/edit.vue: 1552 lines of code main/manager-mobile/src/pages/agent/edit.vue:1 — main/manager-mobile/src/pages/agent/edit.vue has 1552 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · main/manager-mobile/src/pages/agent/components/AgentSnapshotPanel.vue · ×1
  • main/manager-mobile/src/pages/agent/components/AgentSnapshotPanel.vue: 1344 lines of code main/manager-mobile/src/pages/agent/components/AgentSnapshotPanel.vue:1 — main/manager-mobile/src/pages/agent/components/AgentSnapshotPanel.vue has 1344 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · main/manager-web/src/views/AddressBookManagement.vue · ×1
  • main/manager-web/src/views/AddressBookManagement.vue: 1188 lines of code main/manager-web/src/views/AddressBookManagement.vue:1 — main/manager-web/src/views/AddressBookManagement.vue has 1188 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · main/manager-web/src/views/KnowledgeBaseManagement.vue · ×1
  • main/manager-web/src/views/KnowledgeBaseManagement.vue: 1148 lines of code main/manager-web/src/views/KnowledgeBaseManagement.vue:1 — main/manager-web/src/views/KnowledgeBaseManagement.vue has 1148 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · main/manager-web/src/views/ParamsManagement.vue · ×1
  • main/manager-web/src/views/ParamsManagement.vue: 986 lines of code main/manager-web/src/views/ParamsManagement.vue:1 — main/manager-web/src/views/ParamsManagement.vue has 986 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · main/manager-web/src/views/ModelConfig.vue · ×1
  • main/manager-web/src/views/ModelConfig.vue: 900 lines of code main/manager-web/src/views/ModelConfig.vue:1 — main/manager-web/src/views/ModelConfig.vue has 900 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · main/manager-mobile/src/pages/login/index.vue · ×1
  • main/manager-mobile/src/pages/login/index.vue: 895 lines of code main/manager-mobile/src/pages/login/index.vue:1 — main/manager-mobile/src/pages/login/index.vue has 895 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · main/manager-web/src/views/home.vue · ×1
  • main/manager-web/src/views/home.vue: 815 lines of code main/manager-web/src/views/home.vue:1 — main/manager-web/src/views/home.vue has 815 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · main/digital-human/js/ui/controller.js · ×1
  • main/digital-human/js/ui/controller.js: 811 lines of code main/digital-human/js/ui/controller.js:1 — main/digital-human/js/ui/controller.js has 811 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · main/manager-mobile/src/pages/register/index.vue · ×1
  • main/manager-mobile/src/pages/register/index.vue: 805 lines of code main/manager-mobile/src/pages/register/index.vue:1 — main/manager-mobile/src/pages/register/index.vue has 805 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · main/manager-web/src/components/FunctionDialog.vue · ×1
  • main/manager-web/src/components/FunctionDialog.vue: 798 lines of code main/manager-web/src/components/FunctionDialog.vue:1 — main/manager-web/src/components/FunctionDialog.vue has 798 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · main/manager-mobile/src/pages/forgot-password/index.vue · ×1
  • main/manager-mobile/src/pages/forgot-password/index.vue: 754 lines of code main/manager-mobile/src/pages/forgot-password/index.vue:1 — main/manager-mobile/src/pages/forgot-password/index.vue has 754 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · main/digital-human/js/live2d/live2d.js · ×1
  • main/digital-human/js/live2d/live2d.js: 705 lines of code main/digital-human/js/live2d/live2d.js:1 — main/digital-human/js/live2d/live2d.js has 705 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · main/manager-mobile/src/pages/index/index.vue · ×1
  • main/manager-mobile/src/pages/index/index.vue: 703 lines of code main/manager-mobile/src/pages/index/index.vue:1 — main/manager-mobile/src/pages/index/index.vue has 703 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · main/manager-web/src/components/TtsModel.vue · ×1
  • main/manager-web/src/components/TtsModel.vue: 633 lines of code main/manager-web/src/components/TtsModel.vue:1 — main/manager-web/src/components/TtsModel.vue has 633 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · main/manager-web/src/components/VoiceCloneDialog.vue · ×1
  • main/manager-web/src/components/VoiceCloneDialog.vue: 628 lines of code main/manager-web/src/components/VoiceCloneDialog.vue:1 — main/manager-web/src/components/VoiceCloneDialog.vue has 628 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · main/manager-web/src/views/VoiceCloneManagement.vue · ×1
  • main/manager-web/src/views/VoiceCloneManagement.vue: 607 lines of code main/manager-web/src/views/VoiceCloneManagement.vue:1 — main/manager-web/src/views/VoiceCloneManagement.vue has 607 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · main/manager-web/src/components/HeaderBar.vue · ×1
  • main/manager-web/src/components/HeaderBar.vue: 606 lines of code main/manager-web/src/components/HeaderBar.vue:1 — main/manager-web/src/components/HeaderBar.vue has 606 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · main/manager-mobile/src/pages/voiceprint/index.vue · ×1
  • main/manager-mobile/src/pages/voiceprint/index.vue: 588 lines of code main/manager-mobile/src/pages/voiceprint/index.vue:1 — main/manager-mobile/src/pages/voiceprint/index.vue has 588 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · main/manager-mobile/src/pages/device-config/components/ultrasonic-config.vue · ×1
  • main/manager-mobile/src/pages/device-config/components/ultrasonic-config.vue: 586 lines of code main/manager-mobile/src/pages/device-config/components/ultrasonic-config.vue:1 — main/manager-mobile/src/pages/device-config/components/ultrasonic-config.vue has 586 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · main/manager-web/src/components/ChatHistoryDialog.vue · ×1
  • main/manager-web/src/components/ChatHistoryDialog.vue: 586 lines of code main/manager-web/src/components/ChatHistoryDialog.vue:1 — main/manager-web/src/components/ChatHistoryDialog.vue has 586 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · main/manager-web/src/apis/module/agent.js · ×1
  • main/manager-web/src/apis/module/agent.js: 568 lines of code main/manager-web/src/apis/module/agent.js:1 — main/manager-web/src/apis/module/agent.js has 568 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · main/manager-web/src/views/KnowledgeBaseItem.vue · ×1
  • main/manager-web/src/views/KnowledgeBaseItem.vue: 568 lines of code main/manager-web/src/views/KnowledgeBaseItem.vue:1 — main/manager-web/src/views/KnowledgeBaseItem.vue has 568 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · main/manager-web/src/views/FeatureManagement.vue · ×1
  • main/manager-web/src/views/FeatureManagement.vue: 567 lines of code main/manager-web/src/views/FeatureManagement.vue:1 — main/manager-web/src/views/FeatureManagement.vue has 567 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · main/manager-mobile/src/pages/device/index.vue · ×1
  • main/manager-mobile/src/pages/device/index.vue: 563 lines of code main/manager-mobile/src/pages/device/index.vue:1 — main/manager-mobile/src/pages/device/index.vue has 563 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · main/manager-mobile/src/pages/agent/tools.vue · ×1
  • main/manager-mobile/src/pages/agent/tools.vue: 561 lines of code main/manager-mobile/src/pages/agent/tools.vue:1 — main/manager-mobile/src/pages/agent/tools.vue has 561 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · main/manager-web/src/views/DictManagement.vue · ×1
  • main/manager-web/src/views/DictManagement.vue: 555 lines of code main/manager-web/src/views/DictManagement.vue:1 — main/manager-web/src/views/DictManagement.vue has 555 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · main/manager-mobile/src/pages/login/user-agreement-zh.vue · ×1
  • main/manager-mobile/src/pages/login/user-agreement-zh.vue: 526 lines of code main/manager-mobile/src/pages/login/user-agreement-zh.vue:1 — main/manager-mobile/src/pages/login/user-agreement-zh.vue has 526 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · main/manager-mobile/src/pages/login/user-agreement-en.vue · ×1
  • main/manager-mobile/src/pages/login/user-agreement-en.vue: 524 lines of code main/manager-mobile/src/pages/login/user-agreement-en.vue:1 — main/manager-mobile/src/pages/login/user-agreement-en.vue has 524 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · main/manager-web/src/views/DeviceManagement.vue · ×1
  • main/manager-web/src/views/DeviceManagement.vue: 521 lines of code main/manager-web/src/views/DeviceManagement.vue:1 — main/manager-web/src/views/DeviceManagement.vue has 521 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · main/digital-human/js/core/network/websocket.js · ×1
  • main/digital-human/js/core/network/websocket.js: 520 lines of code main/digital-human/js/core/network/websocket.js:1 — main/digital-human/js/core/network/websocket.js has 520 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · main/manager-mobile/src/pages/device-config/components/wifi-selector.vue · ×1
  • main/manager-mobile/src/pages/device-config/components/wifi-selector.vue: 502 lines of code main/manager-mobile/src/pages/device-config/components/wifi-selector.vue:1 — main/manager-mobile/src/pages/device-config/components/wifi-selector.vue has 502 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · main/manager-web/src/components/ModelEditDialog.vue · ×1
  • main/manager-web/src/components/ModelEditDialog.vue: 492 lines of code main/manager-web/src/components/ModelEditDialog.vue:1 — main/manager-web/src/components/ModelEditDialog.vue has 492 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · main/digital-human/js/core/mcp/tools.js · ×1
  • main/digital-human/js/core/mcp/tools.js: 488 lines of code main/digital-human/js/core/mcp/tools.js:1 — main/digital-human/js/core/mcp/tools.js has 488 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · main/manager-web/src/views/ProviderManagement.vue · ×1
  • main/manager-web/src/views/ProviderManagement.vue: 474 lines of code main/manager-web/src/views/ProviderManagement.vue:1 — main/manager-web/src/views/ProviderManagement.vue has 474 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · main/manager-web/src/views/ReplacementWordManagement.vue · ×1
  • main/manager-web/src/views/ReplacementWordManagement.vue: 473 lines of code main/manager-web/src/views/ReplacementWordManagement.vue:1 — main/manager-web/src/views/ReplacementWordManagement.vue has 473 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · main/manager-web/src/views/AgentTemplateManagement.vue · ×1
  • main/manager-web/src/views/AgentTemplateManagement.vue: 466 lines of code main/manager-web/src/views/AgentTemplateManagement.vue:1 — main/manager-web/src/views/AgentTemplateManagement.vue has 466 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · main/manager-mobile/src/pages/settings/index.vue · ×1
  • main/manager-mobile/src/pages/settings/index.vue: 459 lines of code main/manager-mobile/src/pages/settings/index.vue:1 — main/manager-mobile/src/pages/settings/index.vue has 459 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R6 · Tooling · This package's lint script runs in no CI job · ×1
  • This package's lint script runs in no CI job REDACTED:75 — The package in `main/manager-mobile` declares the lint script `lint` (`eslint`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `main/manager-mobile` (or the workspace's task runner).
R7 · Dead Code · Dead file (~451 LoC) · ×1
  • Dead file (~451 LoC) main/manager-mobile/src/pages/device-config/components/ultrasonic-config.vue — no import path from any entry point (28 application, 10 tooling, 9 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (main/manager-mobile/src/pages/device-config/index.vue) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~327 LoC) · ×1
  • Dead file (~327 LoC) main/manager-mobile/src/utils/uploadFile.ts — no import path from any entry point (28 application, 10 tooling, 9 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~323 LoC) · ×1
  • Dead file (~323 LoC) main/manager-mobile/src/pages/register/index.vue — no import path from any entry point (28 application, 10 tooling, 9 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~306 LoC) · ×1
  • Dead file (~306 LoC) main/manager-mobile/src/pages/chat-history/detail.vue — no import path from any entry point (28 application, 10 tooling, 9 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~300 LoC) · ×1
  • Dead file (~300 LoC) main/manager-mobile/src/pages/forgot-password/index.vue — no import path from any entry point (28 application, 10 tooling, 9 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~286 LoC) · ×1
  • Dead file (~286 LoC) main/manager-mobile/src/pages/settings/index.vue — no import path from any entry point (28 application, 10 tooling, 9 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~279 LoC) · ×1
  • Dead file (~279 LoC) main/manager-mobile/src/pages/login/index.vue — no import path from any entry point (28 application, 10 tooling, 9 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~278 LoC) · ×1
  • Dead file (~278 LoC) main/manager-mobile/src/pages/agent/tools.vue — no import path from any entry point (28 application, 10 tooling, 9 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~218 LoC) · ×1
  • Dead file (~218 LoC) main/manager-mobile/src/pages/device-config/components/wifi-selector.vue — no import path from any entry point (28 application, 10 tooling, 9 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (main/manager-mobile/src/pages/device-config/index.vue) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~212 LoC) · ×1
  • Dead file (~212 LoC) main/manager-mobile/src/pages/index/index.vue — no import path from any entry point (28 application, 10 tooling, 9 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~188 LoC) · ×1
  • Dead file (~188 LoC) main/manager-mobile/src/pages/chat-history/index.vue — no import path from any entry point (28 application, 10 tooling, 9 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (main/manager-mobile/src/pages/agent/index.vue) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~162 LoC) · ×1
  • Dead file (~162 LoC) main/manager-mobile/src/pages/agent/index.vue — no import path from any entry point (28 application, 10 tooling, 9 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~160 LoC) · ×1
  • Dead file (~160 LoC) main/manager-mobile/src/hooks/useUpload.ts — no import path from any entry point (28 application, 10 tooling, 9 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~115 LoC) · ×1
  • Dead file (~115 LoC) main/manager-web/src/components/AddressBookDialog.vue — no import path from any entry point (28 application, 10 tooling, 9 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~104 LoC) · ×1
  • Dead file (~104 LoC) main/manager-mobile/src/pages/device-config/components/wifi-config.vue — no import path from any entry point (28 application, 10 tooling, 9 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (main/manager-mobile/src/pages/device-config/index.vue) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~97 LoC) · ×1
  • Dead file (~97 LoC) REDACTED — no import path from any entry point (28 application, 10 tooling, 9 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~84 LoC) · ×1
  • Dead file (~84 LoC) main/manager-mobile/src/pages/agent/provider.vue — no import path from any entry point (28 application, 10 tooling, 9 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~76 LoC) · ×1
  • Dead file (~76 LoC) main/manager-mobile/src/pages/device-config/index.vue — no import path from any entry point (28 application, 10 tooling, 9 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~72 LoC) · ×1
  • Dead file (~72 LoC) main/manager-mobile/src/api/voiceprint/voiceprint.ts — no import path from any entry point (28 application, 10 tooling, 9 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (main/manager-mobile/src/api/voiceprint/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~71 LoC) · ×1
  • Dead file (~71 LoC) main/manager-mobile/src/api/device/device.ts — no import path from any entry point (28 application, 10 tooling, 9 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (main/manager-mobile/src/api/device/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~63 LoC) · ×1
  • Dead file (~63 LoC) main/manager-mobile/src/api/chat-history/chat-history.ts — no import path from any entry point (28 application, 10 tooling, 9 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (main/manager-mobile/src/api/chat-history/index.ts, main/manager-mobile/src/pages/chat-history/detail.vue, main/manager-mobile/src/pages/chat-history/index.vue) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~51 LoC) · ×1
  • Dead file (~51 LoC) main/manager-mobile/src/hooks/useRequest.ts — no import path from any entry point (28 application, 10 tooling, 9 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~47 LoC) · ×1
  • Dead file (~47 LoC) main/manager-mobile/src/pages/agent/speedPitch.vue — no import path from any entry point (28 application, 10 tooling, 9 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~39 LoC) · ×1
  • Dead file (~39 LoC) main/manager-mobile/src/api/chat-history/types.ts — no import path from any entry point (28 application, 10 tooling, 9 test roots considered), but 4 in-repo import(s) from 4 other file(s) do name it (main/manager-mobile/src/api/chat-history/chat-history.ts, main/manager-mobile/src/api/chat-history/index.ts, main/manager-mobile/src/pages/chat-history/detail.vue and 1 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~34 LoC) · ×1
  • Dead file (~34 LoC) main/manager-mobile/src/layouts/fg-tabbar/fg-tabbar.vue — no import path from any entry point (28 application, 10 tooling, 9 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (main/manager-mobile/src/layouts/tabbar.vue) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~32 LoC) · ×1
  • Dead file (~32 LoC) main/manager-mobile/src/components/custom-tabs/index.vue — no import path from any entry point (28 application, 10 tooling, 9 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (main/manager-mobile/src/pages/agent/index.vue) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~29 LoC) · ×1
  • Dead file (~29 LoC) main/manager-mobile/src/api/voiceprint/types.ts — no import path from any entry point (28 application, 10 tooling, 9 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (main/manager-mobile/src/api/voiceprint/index.ts, main/manager-mobile/src/api/voiceprint/voiceprint.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~21 LoC) · ×1
  • Dead file (~21 LoC) main/manager-mobile/src/api/device/types.ts — no import path from any entry point (28 application, 10 tooling, 9 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (main/manager-mobile/src/api/device/device.ts, main/manager-mobile/src/api/device/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~11 LoC) · ×1
  • Dead file (~11 LoC) main/manager-mobile/src/layouts/fg-tabbar/tabbar.ts — no import path from any entry point (28 application, 10 tooling, 9 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (main/manager-mobile/src/layouts/fg-tabbar/fg-tabbar.vue) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~9 LoC) · ×1
  • Dead file (~9 LoC) main/manager-mobile/src/layouts/tabbar.vue — no import path from any entry point (28 application, 10 tooling, 9 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~8 LoC) · ×1
  • Dead file (~8 LoC) main/manager-mobile/src/layouts/default.vue — no import path from any entry point (28 application, 10 tooling, 9 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R8 · Dependency Hygiene · Unused dependency '@alova/wormhole' · ×1
  • Unused dependency '@alova/wormhole' REDACTED:110 — Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
R8 · Dependency Hygiene · Unused dependency '@dcloudio/uni-automator' · ×1
  • Unused dependency '@dcloudio/uni-automator' REDACTED:115 — Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
R8 · Dependency Hygiene · Unused dependency '@dcloudio/uni-cli-shared' · ×1
  • Unused dependency '@dcloudio/uni-cli-shared' REDACTED:116 — Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
R8 · Dependency Hygiene · Unused dependency '@dcloudio/uni-components' · ×1
  • Unused dependency '@dcloudio/uni-components' REDACTED:84 — Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
R8 · Dependency Hygiene · Unused dependency '@dcloudio/uni-mp-alipay' · ×1
  • Unused dependency '@dcloudio/uni-mp-alipay' REDACTED:86 — Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
R8 · Dependency Hygiene · Unused dependency '@dcloudio/uni-mp-baidu' · ×1
  • Unused dependency '@dcloudio/uni-mp-baidu' REDACTED:87 — Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
R8 · Dependency Hygiene · Unused dependency '@dcloudio/uni-mp-harmony' · ×1
  • Unused dependency '@dcloudio/uni-mp-harmony' REDACTED:88 — Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
R8 · Dependency Hygiene · Unused dependency '@dcloudio/uni-mp-jd' · ×1
  • Unused dependency '@dcloudio/uni-mp-jd' REDACTED:89 — Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
R8 · Dependency Hygiene · Unused dependency '@dcloudio/uni-mp-kuaishou' · ×1
  • Unused dependency '@dcloudio/uni-mp-kuaishou' REDACTED:90 — Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
R8 · Dependency Hygiene · Unused dependency '@dcloudio/uni-mp-lark' · ×1
  • Unused dependency '@dcloudio/uni-mp-lark' REDACTED:91 — Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
R8 · Dependency Hygiene · Unused dependency '@dcloudio/uni-mp-qq' · ×1
  • Unused dependency '@dcloudio/uni-mp-qq' REDACTED:92 — Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
R8 · Dependency Hygiene · Unused dependency '@dcloudio/uni-mp-toutiao' · ×1
  • Unused dependency '@dcloudio/uni-mp-toutiao' REDACTED:93 — Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
R8 · Dependency Hygiene · Unused dependency '@dcloudio/uni-mp-weixin' · ×1
  • Unused dependency '@dcloudio/uni-mp-weixin' REDACTED:94 — Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
R8 · Dependency Hygiene · Unused dependency '@dcloudio/uni-mp-xhs' · ×1
  • Unused dependency '@dcloudio/uni-mp-xhs' REDACTED:95 — Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
R8 · Dependency Hygiene · Unused dependency '@dcloudio/uni-quickapp-webview' · ×1
  • Unused dependency '@dcloudio/uni-quickapp-webview' REDACTED:96 — Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
R8 · Dependency Hygiene · Unused dependency '@dcloudio/uni-stacktracey' · ×1
  • Unused dependency '@dcloudio/uni-stacktracey' REDACTED:117 — Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
R8 · Dependency Hygiene · Unused dependency '@dcloudio/uni-uts-v1' · ×1
  • Unused dependency '@dcloudio/uni-uts-v1' REDACTED:118 — Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
R8 · Dependency Hygiene · Unused dependency '@esbuild/darwin-arm64' · ×1
  • Unused dependency '@esbuild/darwin-arm64' REDACTED:120 — Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
R8 · Dependency Hygiene · Unused dependency '@esbuild/darwin-x64' · ×1
  • Unused dependency '@esbuild/darwin-x64' REDACTED:121 — Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
R8 · Dependency Hygiene · Unused dependency '@iconify-json/carbon' · ×1
  • Unused dependency '@iconify-json/carbon' REDACTED:122 — Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
R8 · Dependency Hygiene · Unused dependency '@vue/runtime-core' · ×1
  • Unused dependency '@vue/runtime-core' REDACTED:137 — Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
R8 · Dependency Hygiene · Unused dependency '@vue/tsconfig' · ×1
  • Unused dependency '@vue/tsconfig' REDACTED:138 — Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
R8 · Dependency Hygiene · Unused dependency 'js-cookie' · ×1
  • Unused dependency 'js-cookie' REDACTED:101 — Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
R8 · Dependency Hygiene · Unused dependency 'openapi-ts-request' · ×1
  • Unused dependency 'openapi-ts-request' REDACTED:144 — Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
R8 · Dependency Hygiene · Unused dependency '@vue/cli-plugin-router' · ×1
  • Unused dependency '@vue/cli-plugin-router' main/manager-web/package.json:33 — Declared in main/manager-web/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
R8 · Dependency Hygiene · Unused dependency '@vue/cli-plugin-vuex' · ×1
  • Unused dependency '@vue/cli-plugin-vuex' main/manager-web/package.json:34 — Declared in main/manager-web/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
R8 · Dependency Hygiene · Unused dependency 'core-js' · ×1
  • Unused dependency 'core-js' main/manager-web/package.json:14 — Declared in main/manager-web/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
R8 · Dependency Hygiene · Unused dependency 'opus-recorder' · ×1
  • Unused dependency 'opus-recorder' main/manager-web/package.json:21 — Declared in main/manager-web/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
R8 · Dependency Hygiene · Unused dependency 'vue-axios' · ×1
  • Unused dependency 'vue-axios' main/manager-web/package.json:24 — Declared in main/manager-web/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
X1 · Async correctness · Blocking `time.sleep` inside an `async def` · ×1
  • Blocking `time.sleep` inside an `async def` main/xiaozhi-server/core/providers/asr/fun_local.py:109 — This `async def` runs on the event loop's thread, and `time.sleep` blocks that thread: for the whole delay no other coroutine, request or callback on the loop makes progress — the Python form of blocking on a task. Use `await asyncio.sleep(…)`, which suspends only this coroutine. Where the blocking work is not a sleep but a synchronous call that cannot be made async, move it off the loop with `await asyncio.to_thread(…)` (or `loop.run_in_executor(…)`).
X1 · Async correctness · `async` Promise executor · ×1
  • `async` Promise executor main/digital-human/js/app.js:267 — The function passed to `new Promise(…)` is `async`. The constructor ignores what its executor returns, so anything this executor throws — every throw inside an `async` function, including after an `await` — rejects a Promise nobody holds instead of the one being constructed: the outer Promise never settles, whoever awaits it hangs, and the error is reported nowhere. If the body needs `await`, it does not need `new Promise` at all: make the enclosing function `async` and `return` the value (or `throw`) directly. If it wraps a callback API, keep the executor synchronous — call the API and `resolve`/`reject` from its callback — and do the awaiting outside it.
Minor — 102 finding(s)
X10 · Duplicated predicate · Duplicated predicate · ×35
  • Duplicated predicate main/manager-api/src/main/java/xiaozhi/modules/agent/service/impl/AgentServiceImpl.java:583 — `"openai".equals(type) || "ollama".equals(type)` appears character-identically in 2 files — main/manager-api/src/main/java/xiaozhi/modules/agent/service/impl/AgentServiceImpl.java, main/manager-api/src/main/java/xiaozhi/modules/agent/service/impl/AgentSnapshotServiceImpl.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate main/manager-api/src/main/java/xiaozhi/modules/device/controller/OTAController.java:91 — `StringUtils.isBlank(otaUrl) || otaUrl.equals("null")` appears character-identically in 3 files — main/manager-api/src/main/java/xiaozhi/modules/device/controller/OTAController.java, REDACTED, main/manager-api/src/main/java/xiaozhi/modules/device/service/impl/DeviceServiceImpl.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate main/manager-api/src/main/java/xiaozhi/modules/agent/controller/AgentVoicePrintController.java:79 — `StringUtils.isBlank(voiceprintUrl) || "null".equals(voiceprintUrl)` appears character-identically in 2 files — main/manager-api/src/main/java/xiaozhi/modules/agent/controller/AgentVoicePrintController.java, main/manager-api/src/main/java/xiaozhi/modules/config/service/impl/ConfigServiceImpl.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate main/manager-api/src/main/java/xiaozhi/modules/device/controller/OTAController.java:87 — `StringUtils.isBlank(wsUrl) || wsUrl.equals("null")` appears character-identically in 2 files — main/manager-api/src/main/java/xiaozhi/modules/device/controller/OTAController.java, main/manager-api/src/main/java/xiaozhi/modules/device/service/impl/DeviceServiceImpl.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate main/manager-api/src/main/java/xiaozhi/modules/security/oauth2/Oauth2Filter.java:104 — `StringUtils.isNotBlank(authorization) && authorization.startsWith("Bearer ")` appears character-identically in 2 files — main/manager-api/src/main/java/xiaozhi/modules/security/oauth2/Oauth2Filter.java, main/manager-api/src/main/java/xiaozhi/modules/security/secret/ServerSecretFilter.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate main/manager-api/src/main/java/xiaozhi/modules/agent/service/impl/AgentServiceImpl.java:100 — `agent.getMemModelId() != null && agent.getMemModelId().equals(Constant.MEMORY_NO_MEM)` appears character-identically in 2 files — main/manager-api/src/main/java/xiaozhi/modules/agent/service/impl/AgentServiceImpl.java, main/manager-api/src/main/java/xiaozhi/modules/config/service/impl/ConfigServiceImpl.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate main/manager-api/src/main/java/xiaozhi/modules/agent/service/impl/AgentChatSummaryServiceImpl.java:218 — `config.getIsDefault() != null && config.getIsDefault() == 1` appears character-identically in 2 files — main/manager-api/src/main/java/xiaozhi/modules/agent/service/impl/AgentChatSummaryServiceImpl.java, main/manager-api/src/main/java/xiaozhi/modules/agent/service/impl/AgentServiceImpl.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate main/manager-api/src/main/java/xiaozhi/modules/agent/service/impl/AgentChatSummaryServiceImpl.java:213 — `llmConfigs == null || llmConfigs.isEmpty()` appears character-identically in 2 files — main/manager-api/src/main/java/xiaozhi/modules/agent/service/impl/AgentChatSummaryServiceImpl.java, main/manager-api/src/main/java/xiaozhi/modules/agent/service/impl/AgentServiceImpl.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate main/digital-human/js/app.js:192 — `!navigator.mediaDevices || !navigator.mediaDevices.getUserMedia` appears character-identically in 2 files — main/digital-human/js/app.js, main/digital-human/js/core/audio/recorder.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate main/manager-web/src/apis/module/agent.js:14 — `retryCount >= CALLBACK_RETRY_LIMIT || Date.now() - startedAt >= CALLBACK_RETRY_WINDOW_MS` appears character-identically in 3 files — main/manager-web/src/apis/module/agent.js, main/manager-web/src/apis/module/correctWord.js, main/manager-web/src/apis/module/model.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate main/digital-human/js/core/audio/recorder.js:174 — `this.websocket && this.websocket.readyState === WebSocket.OPEN` appears character-identically in 2 files — main/digital-human/js/core/audio/recorder.js, main/digital-human/js/core/network/websocket.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate main/digital-human/js/config/manager.js:99 — `wakewordWsUrlInput && wakewordWsUrlInput.value.trim()` appears character-identically in 2 files — main/digital-human/js/config/manager.js, main/digital-human/js/ui/controller.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate main/xiaozhi-server/performance_tester/performance_tester_asr.py:85 — `"502" in error_msg or "bad gateway" in error_msg` appears character-identically in 2 files — main/xiaozhi-server/performance_tester/performance_tester_asr.py, main/xiaozhi-server/performance_tester/performance_tester_llm.py. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate main/xiaozhi-server/core/providers/asr/doubao_stream.py:108 — `"code" in result and result["code"] != 1000` appears character-identically in 2 files — main/xiaozhi-server/core/providers/asr/doubao_stream.py, main/xiaozhi-server/performance_tester/performance_tester_stream_asr.py. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate REDACTED:135 — `audio_have_voice and not self.is_processing and not self.asr_ws` appears character-identically in 2 files — REDACTED, main/xiaozhi-server/core/providers/asr/aliyunbl_stream.py. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate main/xiaozhi-server/core/providers/asr/doubao_stream.py:74 — `audio_have_voice and self.asr_ws is None and not self.is_processing` appears character-identically in 2 files — main/xiaozhi-server/core/providers/asr/doubao_stream.py, main/xiaozhi-server/core/providers/asr/xunfei_stream.py. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate main/xiaozhi-server/core/providers/asr/doubao_stream.py:123 — `conn.asr_audio and len(conn.asr_audio) > 0` appears character-identically in 2 files — main/xiaozhi-server/core/providers/asr/doubao_stream.py, main/xiaozhi-server/core/providers/asr/xunfei_stream.py. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate main/xiaozhi-server/core/providers/memory/mem0ai/mem0ai.py:53 — `content and content.strip().startswith("{") and content.strip().endswith("}")` appears character-identically in 3 files — main/xiaozhi-server/core/providers/memory/mem0ai/mem0ai.py, main/xiaozhi-server/core/providers/memory/mem_local_short/mem_local_short.py, main/xiaozhi-server/core/providers/memory/powermem/powermem.py. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate main/xiaozhi-server/core/utils/resilience.py:1079 — `getattr(conn, "stop_event", None) and conn.stop_event.is_set()` appears character-identically in 2 files — main/xiaozhi-server/core/utils/resilience.py, main/xiaozhi-server/core/utils/session_state.py. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate main/xiaozhi-server/core/handle/helloHandle.py:120 — `is_play_only_mode(conn) or getattr( conn, "_broadcast_speak_active", False ) or getattr(conn, "_broadcast_soft_barge_in", False)` appears character-identically in 3 files — main/xiaozhi-server/core/handle/helloHandle.py, main/xiaozhi-server/core/handle/intentHandler.py, main/xiaozhi-server/core/handle/textHandler/listenMessageHandler.py. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate main/xiaozhi-server/core/providers/tools/device_mcp/mcp_handler.py:392 — `isinstance(content, list) and len(content) > 0` appears character-identically in 2 files — main/xiaozhi-server/core/providers/tools/device_mcp/mcp_handler.py, main/xiaozhi-server/core/providers/tools/mcp_endpoint/mcp_endpoint_handler.py. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate main/xiaozhi-server/core/providers/tools/device_mcp/mcp_handler.py:393 — `isinstance(content[0], dict) and "text" in content[0]` appears character-identically in 2 files — main/xiaozhi-server/core/providers/tools/device_mcp/mcp_handler.py, main/xiaozhi-server/core/providers/tools/mcp_endpoint/mcp_endpoint_handler.py. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate main/xiaozhi-server/core/handle/intentHandler.py:30 — `isinstance(parsed_data, dict) and "content" in parsed_data` appears character-identically in 2 files — main/xiaozhi-server/core/handle/intentHandler.py, main/xiaozhi-server/core/handle/sendAudioHandle.py. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate main/xiaozhi-server/core/providers/llm/coze/coze.py:58 — `len(dialogue) == 2 and functions is not None and len(functions) > 0` appears character-identically in 2 files — main/xiaozhi-server/core/providers/llm/coze/coze.py, main/xiaozhi-server/core/providers/llm/dify/dify.py. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate main/xiaozhi-server/core/providers/llm/coze/coze.py:66 — `len(dialogue) > 1 and dialogue[-1]["role"] == "tool"` appears character-identically in 2 files — main/xiaozhi-server/core/providers/llm/coze/coze.py, main/xiaozhi-server/core/providers/llm/dify/dify.py. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • + 10 more in this group — see findings.md.
D34 · Knowledge Freshness · Orphaned file · ×14
  • Orphaned file main/manager-api/src/main/java/xiaozhi/modules/agent/service/impl/AgentVoicePrintServiceImpl.java:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file main/manager-api/src/main/java/xiaozhi/modules/knowledge/dto/document/DocumentDTO.java:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file main/xiaozhi-server/performance_tester/performance_tester_asr.py:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file main/manager-api/src/main/java/xiaozhi/modules/knowledge/dto/document/RetrievalDTO.java:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file main/manager-mobile/src/utils/uploadFile.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file main/manager-api/src/main/java/xiaozhi/modules/agent/controller/AgentTemplateController.java:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file main/manager-api/src/main/java/xiaozhi/common/utils/SensitiveDataUtils.java:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file main/manager-api/src/main/java/xiaozhi/modules/knowledge/dto/document/ChunkDTO.java:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file main/manager-api/src/main/java/xiaozhi/modules/sys/controller/AdminController.java:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file main/manager-mobile/src/hooks/useUpload.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file main/manager-api/src/main/java/xiaozhi/modules/agent/controller/AgentVoicePrintController.java:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file main/manager-api/src/main/java/xiaozhi/modules/knowledge/entity/DocumentEntity.java:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file main/manager-mobile/src/api/auth.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file main/manager-mobile/src/layouts/fg-tabbar/tabbarList.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
D30 · Dependency Vulnerabilities · Low CVE · ×8
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D24 · Comment Value · redundant comment · ×4
  • redundant comment main/digital-human/js/core/audio/recorder.js:90 — "Create audio processor" repeats the code it sits on: 3 of its 3 words (create, audio, processor) are already in `async createAudioProcessor()`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment main/digital-human/js/core/audio/recorder.js:162 — "Encode and send Opus data" repeats the code it sits on: 4 of its 4 words (encode, send, opus, data) are already in `encodeAndSendOpus(pcmData = null)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment main/digital-human/js/core/audio/recorder.js:370 — "Check if it is HTTP protocol" repeats the code it sits on: 3 of its 3 words (check, http, protocol) are already in `if (protocol !== 'http:')`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment main/digital-human/js/ui/controller.js:398 — 7 comments in this file only repeat the code they sit on (lines 398, 439, 463, 642, 834, 853, 918), for example "Update record button state". Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
D29 · Static Analysis (SAST) · REDACTED · ×4
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
X4 · Structured logging · Interpolated log message defeats structured logging · ×4
  • Interpolated log message defeats structured logging main/xiaozhi-server/core/utils/opus_encoder_utils.py:49 — `error` at line 49 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog.
  • Interpolated log message defeats structured logging main/xiaozhi-server/core/utils/opus_encoder_utils.py:114 — `error` at line 114 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog.
  • Interpolated log message defeats structured logging main/xiaozhi-server/core/utils/opus_encoder_utils.py:128 — `warning` at line 128 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.warning("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.warning("order moved", order_id=order_id, status=status)` with structlog.
  • Interpolated log message defeats structured logging main/xiaozhi-server/core/utils/opus_encoder_utils.py:139 — `error` at line 139 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.error("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.error("order moved", order_id=order_id, status=status)` with structlog.
X7 · Silent fallback defaults · Pending state with no failure state · ×4
  • Pending state with no failure state main/manager-mobile/src/pages/voiceprint/index.vue:384 — The view draws `{{ t('voiceprint.loading') }}` under `loading && voicePrintList.length === 0`, but `loading` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
  • Pending state with no failure state main/manager-mobile/src/pages/chat-history/index.vue:194 — The view draws `{{ t('chatHistory.loading') }}` under `loading && sessionList.length === 0`, but `loading` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
  • Pending state with no failure state main/manager-mobile/src/pages/chat-history/index.vue:202 — The view draws `0" class="session-container"> {{ session.title || `${t('chatHistory.conversationRecord')} ${session.sessionId.substring(0, 8)}...` }} {{ formatTime(session.createdAt) }} {{ t('chatHistory.totalChats', { count: session.chatCount }) }} {{ t('chatHistory.loading') }} 0" class="no-more"> {{ t('chatHistory.noMoreData') }}` under `sessionList.length > 0`, but `sessionList` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
  • Pending state with no failure state main/manager-mobile/src/pages/chat-history/index.vue:233 — The view draws `{{ t('chatHistory.loading') }}` under `loadingMore`, but `loadingMore` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
X7 · Silent fallback defaults · Silent fallback default in catch · ×3
  • Silent fallback default in catch main/xiaozhi-server/core/utils/current_time.py:54 — `get_current_lunar_date` swallows every exception into `return '农历获取失败'` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
  • Silent fallback default in catch main/xiaozhi-server/core/utils/dialogue_registry.py:47 — `_get_local_ip` swallows every exception into `return '127.0.0.1'` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
  • Silent fallback default in catch main/xiaozhi-server/core/utils/util.py:28 — `get_local_ip` swallows every exception into `return '127.0.0.1'` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
AX6 · Interface segregation · Fat interface · ×2
  • Fat interface: AgentService (16 abstract methods) main/manager-api/src/main/java/xiaozhi/modules/agent/service/AgentService.java:22 — `AgentService` declares 16 abstract methods under just 13 distinct name(s): `adminAgentList`, `checkAgentPermission`, `createAgent`, `deleteAgent`, `deleteAgentById`, `deleteAgentByUserId`, `getAgentById`, `getAgentById`, `getDefaultAgentByMacAddress`, `getDeviceCountByAgentId`, `getUserAgents`, `insert`, `updateAgentById`, `updateAgentById`, `updateAgentById`, `updateAgentMemoryByDeviceMacAddress`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. That is an OVERLOAD SET, not 16 separate responsibilities: a caller binds to 13 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 16 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface.
  • Fat interface: DeviceService (19 abstract methods) main/manager-api/src/main/java/xiaozhi/modules/device/service/DeviceService.java:16 — `DeviceService` declares 19 abstract methods: `callDeviceTool`, `checkDeviceActive`, `deleteByAgentId`, `deleteByUserId`, `deviceActivation`, `geCodeByDeviceId`, `generateWebSocketToken`, `getDeviceByMacAddress`, `getDeviceOnlineData`, `getDeviceTools`, `getLatestLastConnectionTime`, `getUserDeviceList`, `getUserDevices`, `manualAddDevice`, `page`, `searchDevicesByMacAddress`, `selectCountByUserId`, `unbindDevice`, `updateDeviceConnectionInfo`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
D28 · Secrets (history) · REDACTED · ×2
  • REDACTED
  • REDACTED
D30 · Dependency Vulnerabilities · Low vulnerability · ×2
  • REDACTED
  • REDACTED
D16 · Bus Factor · Off-boarding risk · ×1
  • Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 11 significant file(s) lose their only recent owner: main/xiaozhi-server/core/utils/resilience.py, main/xiaozhi-server/core/utils/session_state.py, main/xiaozhi-server/scripts/capacity_bench.py, main/xiaozhi-server/core/utils/dialogue_registry.py, main/xiaozhi-server/scripts/ws_lifecycle_smoke.py, main/xiaozhi-server/core/utils/metrics.py, main/xiaozhi-server/scripts/resilience_verify.py, main/xiaozhi-server/core/utils/runtime_env.py (+3 more). Pair on, review, or document these before any departure.
D16 · Bus Factor · Further sole-owners (lower concentration) · ×1
  • Further sole-owners (lower concentration) — 4 other contributor(s) are each the sole owner of a small amount of code below the off-boarding threshold — folded into the bus-factor score and metrics (18 single-owned of 229 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 229 of the 521 production source files in this repository met that bar). They are anonymized user #2 (3 file(s)), anonymized user #3 (2 file(s)), anonymized user #4 (1 file(s)), anonymized user #5 (1 file(s)) — spread or document their files in the same way, at lower priority than the named off-boarding risks above. The files folded here: main/xiaozhi-server/core/utils/voiceprint_provider.py, main/digital-human/wakeword_runtime/config/config_loader.py, main/digital-human/wakeword_runtime/core/microphone.py, main/xiaozhi-server/performance_tester/performance_tester_stream_tts.py, main/xiaozhi-server/performance_tester/performance_tester_stream_asr.py, main/manager-api/src/main/java/xiaozhi/modules/knowledge/rag/RAGFlowClient.java, main/manager-mobile/src/http/request/alova.ts.
D20 · ADR Quality · No ADRs found · ×1
  • No ADRs found REDACTED:274 — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`. ADRs are expected here because `REDACTED` makes this repository a deployable product (line 274).
D21 · Naming Consistency · `currentDtoClass` spells `Dto` where 106 names in the project spell it `DTO` · ×1
  • `currentDtoClass` spells `Dto` where 106 names in the project spell it `DTO` main/manager-api/src/main/java/xiaozhi/common/service/impl/CrudServiceImpl.java:28 — 106 of 107 names in project xiaozhi-esp32-api spell the token `DTO` (106 of 107; unit: names in project xiaozhi-esp32-api containing `DTO`). Peers: xiaozhi.common.page.TokenDTO (main/manager-api/src/main/java/xiaozhi/common/page/TokenDTO.java:15); xiaozhi.modules.agent.dto.AgentChatHistoryDTO (main/manager-api/src/main/java/xiaozhi/modules/agent/dto/AgentChatHistoryDTO.java:13); xiaozhi.modules.agent.dto.AgentChatHistoryReportDTO (main/manager-api/src/main/java/xiaozhi/modules/agent/dto/AgentChatHistoryReportDTO.java:16); xiaozhi.modules.agent.dto.AgentChatSessionDTO (main/manager-api/src/main/java/xiaozhi/modules/agent/dto/AgentChatSessionDTO.java:11); xiaozhi.modules.agent.dto.AgentChatSummaryDTO (main/manager-api/src/main/java/xiaozhi/modules/agent/dto/AgentChatSummaryDTO.java:11). Rename to `currentDTOClass`. [rule N6]
D28 · Secrets (history) · Rotate the exposed credentials · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D31 · IaC & Container Security · Low IaC · ×1
  • REDACTED
D34 · Knowledge Freshness · Orphaned files with no living knowledge · ×1
  • Orphaned files with no living knowledge — 14 of 229 analysed file(s) have no living knowledge left — their last meaningful change has decayed away, so if one breaks, no one currently understands it (counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 229 of the 521 production source files in this repository met that bar). None is large enough to earn a read-through of its own, so this row stands in for the per-file rows rather than raising one each — most significant first: main/manager-api/src/main/java/xiaozhi/modules/agent/service/impl/AgentVoicePrintServiceImpl.java, main/manager-api/src/main/java/xiaozhi/modules/knowledge/dto/document/DocumentDTO.java, main/xiaozhi-server/performance_tester/performance_tester_asr.py, main/manager-api/src/main/java/xiaozhi/modules/knowledge/dto/document/RetrievalDTO.java, main/manager-mobile/src/utils/uploadFile.ts, main/manager-api/src/main/java/xiaozhi/modules/agent/controller/AgentTemplateController.java, main/manager-api/src/main/java/xiaozhi/common/utils/SensitiveDataUtils.java, main/manager-api/src/main/java/xiaozhi/modules/knowledge/dto/document/ChunkDTO.java (and 6 more). Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
M2 · Architecture documentation · No ADRs · ×1
  • No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
P2 · Observability · Logging is not universal · ×1
  • Logging is not universal — Only 3/4 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `.`.
P3 · Security & performance tooling · No SAST · ×1
  • No SAST REDACTED:9 — No static application security testing detected. For this repository's stack, add bandit, `semgrep --config=p/python`, or CodeQL's python pack as a CI step. What was searched, so you can tell an absence from a miss: the 3 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
P3 · Security & performance tooling · No dependency-update automation · ×1
  • No dependency-update automation REDACTED:78 — `REDACTED` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`.
S1 · Web-Security Posture · No security response headers detected · ×1
  • No security response headers detected docs/docker/nginx.conf:25 — None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. This is reported because `nginx.conf` is committed to this repository and declares the server that serves it, so the configuration that would carry these headers is in this repository and was read in full. (−2.0 on this card.)
X2 · Cancellation propagation · Not all async functions that make a request accept an AbortSignal · ×1
  • Not all async functions that make a request accept an AbortSignal — Only 0/3 async functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
X5 · Nullable reference types · Strict null checking is not enabled everywhere the repository type-checks · ×1
  • Strict null checking is not enabled everywhere the repository type-checks — 0/1 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.
X6 · Hand-rolled structured-format parsing · Hand-rolled JSON/XML parsing via regex · ×1
  • Hand-rolled JSON/XML parsing via regex main/manager-api/src/main/java/xiaozhi/modules/agent/service/impl/AgentChatSummaryServiceImpl.java:319 — A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This JVM code already uses a real parser in the same package; use it here too.
Minor — 166 finding(s)
D12 · Dependency Hygiene · Outdated (compile) · ×2
  • Outdated (compile): com.alibaba:druid-spring-boot-3-starter — com.alibaba:druid-spring-boot-3-starter 1.2.20 → 1.2.28 available.
  • Outdated (compile): com.baomidou:mybatis-plus-spring-boot-native-image — com.baomidou:mybatis-plus-spring-boot-native-image 3.5.17 → 3.5.18.1 available.
D12 · Dependency Hygiene · Outdated (compile -- module org.apache.shiro.core [auto]) · ×1
  • Outdated (compile -- module org.apache.shiro.core [auto]): org.apache.shiro:shiro-core — org.apache.shiro:shiro-core 2.0.2 → 3.0.2 available.
D12 · Dependency Hygiene · Outdated (compile -- module org.apache.shiro.lang [auto]) · ×1
  • Outdated (compile -- module org.apache.shiro.lang [auto]): org.apache.shiro:shiro-lang — org.apache.shiro:shiro-lang 2.0.2 → 3.0.2 available.
D12 · Dependency Hygiene · Outdated (compile -- module org.apache.shiro.cache [auto]) · ×1
  • Outdated (compile -- module org.apache.shiro.cache [auto]): org.apache.shiro:shiro-cache — org.apache.shiro:shiro-cache 2.0.2 → 3.0.2 available.
D12 · Dependency Hygiene · Outdated (compile -- module org.apache.shiro.crypto.hash [auto]) · ×1
  • Outdated (compile -- module org.apache.shiro.crypto.hash [auto]): org.apache.shiro:shiro-crypto-hash — org.apache.shiro:shiro-crypto-hash 2.0.2 → 3.0.2 available.
D12 · Dependency Hygiene · Outdated (compile -- module org.apache.shiro.crypto.core [auto]) · ×1
  • Outdated (compile -- module org.apache.shiro.crypto.core [auto]): org.apache.shiro:shiro-crypto-core — org.apache.shiro:shiro-crypto-core 2.0.2 → 3.0.2 available.
D12 · Dependency Hygiene · Outdated (runtime -- module org.apache.shiro.hashes.argon2 [auto]) · ×1
  • Outdated (runtime -- module org.apache.shiro.hashes.argon2 [auto]): org.apache.shiro.crypto:shiro-hashes-argon2 — org.apache.shiro.crypto:shiro-hashes-argon2 2.0.2 → 3.0.2 available.
D12 · Dependency Hygiene · Outdated (runtime -- module org.apache.shiro.hashes.bcrypt [auto]) · ×1
  • Outdated (runtime -- module org.apache.shiro.hashes.bcrypt [auto]): org.apache.shiro.crypto:shiro-hashes-bcrypt — org.apache.shiro.crypto:shiro-hashes-bcrypt 2.0.2 → 3.0.2 available.
D12 · Dependency Hygiene · Outdated (compile -- module org.apache.shiro.crypto.cipher [auto]) · ×1
  • Outdated (compile -- module org.apache.shiro.crypto.cipher [auto]): org.apache.shiro:shiro-crypto-cipher — org.apache.shiro:shiro-crypto-cipher 2.0.2 → 3.0.2 available.
D12 · Dependency Hygiene · Outdated (compile -- module org.apache.shiro.config.core [auto]) · ×1
  • Outdated (compile -- module org.apache.shiro.config.core [auto]): org.apache.shiro:shiro-config-core — org.apache.shiro:shiro-config-core 2.0.2 → 3.0.2 available.
D12 · Dependency Hygiene · Outdated (compile -- module org.apache.shiro.config.ogdl [auto]) · ×1
  • Outdated (compile -- module org.apache.shiro.config.ogdl [auto]): org.apache.shiro:shiro-config-ogdl — org.apache.shiro:shiro-config-ogdl 2.0.2 → 3.0.2 available.
D12 · Dependency Hygiene · Outdated (compile -- module commons.beanutils (auto)) · ×1
  • Outdated (compile -- module commons.beanutils (auto)): commons-beanutils:commons-beanutils — commons-beanutils:commons-beanutils 1.9.4 → 1.11.0 available.
D12 · Dependency Hygiene · Outdated (compile -- module commons.collections (auto)) · ×1
  • Outdated (compile -- module commons.collections (auto)): commons-collections:commons-collections — commons-collections:commons-collections 3.2.2 → 20040616 available.
D12 · Dependency Hygiene · Outdated (compile -- module org.apache.shiro.event [auto]) · ×1
  • Outdated (compile -- module org.apache.shiro.event [auto]): org.apache.shiro:shiro-event — org.apache.shiro:shiro-event 2.0.2 → 3.0.2 available.
D12 · Dependency Hygiene · Outdated (compile -- module org.apache.shiro.spring [auto]) · ×1
  • Outdated (compile -- module org.apache.shiro.spring [auto]): org.apache.shiro:shiro-spring — org.apache.shiro:shiro-spring 2.0.2 → 3.0.2 available.
D12 · Dependency Hygiene · Outdated (compile -- module org.apache.shiro.web [auto]) · ×1
  • Outdated (compile -- module org.apache.shiro.web [auto]): org.apache.shiro:shiro-web — org.apache.shiro:shiro-web 2.0.2 → 3.0.2 available.
D12 · Dependency Hygiene · Outdated (compile -- module owasp.encoder) · ×1
  • Outdated (compile -- module owasp.encoder): org.owasp.encoder:encoder — org.owasp.encoder:encoder 1.3.1 → 1.6.0 available.
D12 · Dependency Hygiene · Outdated (compile -- module spring.boot.starter.websocket [auto]) · ×1
  • Outdated (compile -- module spring.boot.starter.websocket [auto]): org.springframework.boot:spring-boot-starter-websocket — org.springframework.boot:spring-boot-starter-websocket 3.4.3 → 4.1.2 available.
D12 · Dependency Hygiene · Outdated (compile -- module spring.messaging [auto]) · ×1
  • Outdated (compile -- module spring.messaging [auto]): org.springframework:spring-messaging — org.springframework:spring-messaging 6.2.3 → 7.0.10 available.
D12 · Dependency Hygiene · Outdated (compile -- module spring.websocket [auto]) · ×1
  • Outdated (compile -- module spring.websocket [auto]): org.springframework:spring-websocket — org.springframework:spring-websocket 6.2.3 → 7.0.10 available.
D12 · Dependency Hygiene · Outdated (compile -- module com.google.common) · ×1
  • Outdated (compile -- module com.google.common): com.google.guava:guava — com.google.guava:guava 33.6.0-jre → 33.8.0-android available.
D12 · Dependency Hygiene · Outdated (compile -- module org.jspecify) · ×1
  • Outdated (compile -- module org.jspecify): org.jspecify:jspecify — org.jspecify:jspecify 1.0.0 → 1.0.1 available.
D12 · Dependency Hygiene · Outdated (compile -- module com.google.errorprone.annotations) · ×1
  • Outdated (compile -- module com.google.errorprone.annotations): com.google.errorprone:error_prone_annotations — com.google.errorprone:error_prone_annotations 2.47.0 → 2.52.0 available.
D12 · Dependency Hygiene · Outdated (test -- module org.junit.jupiter.api) · ×1
  • Outdated (test -- module org.junit.jupiter.api): org.junit.jupiter:junit-jupiter-api — org.junit.jupiter:junit-jupiter-api 5.10.1 → 6.1.3 available.
D12 · Dependency Hygiene · Outdated (test -- module org.junit.jupiter.engine) · ×1
  • Outdated (test -- module org.junit.jupiter.engine): org.junit.jupiter:junit-jupiter-engine — org.junit.jupiter:junit-jupiter-engine 5.10.1 → 6.1.3 available.
D12 · Dependency Hygiene · Outdated (test -- module org.junit.jupiter.params) · ×1
  • Outdated (test -- module org.junit.jupiter.params): org.junit.jupiter:junit-jupiter-params — org.junit.jupiter:junit-jupiter-params 5.10.1 → 6.1.3 available.
D12 · Dependency Hygiene · Outdated (test -- module org.junit.platform.launcher) · ×1
  • Outdated (test -- module org.junit.platform.launcher): org.junit.platform:junit-platform-launcher — org.junit.platform:junit-platform-launcher 1.10.1 → 6.1.3 available.
D12 · Dependency Hygiene · Outdated (test -- module org.junit.platform.commons) · ×1
  • Outdated (test -- module org.junit.platform.commons): org.junit.platform:junit-platform-commons — org.junit.platform:junit-platform-commons 1.10.1 → 6.1.3 available.
D12 · Dependency Hygiene · Outdated (test -- module org.junit.platform.engine) · ×1
  • Outdated (test -- module org.junit.platform.engine): org.junit.platform:junit-platform-engine — org.junit.platform:junit-platform-engine 1.10.1 → 6.1.3 available.
D12 · Dependency Hygiene · Outdated (test -- module spring.boot.starter.test [auto]) · ×1
  • Outdated (test -- module spring.boot.starter.test [auto]): org.springframework.boot:spring-boot-starter-test — org.springframework.boot:spring-boot-starter-test 3.4.3 → 4.1.2 available.
D12 · Dependency Hygiene · Outdated (compile -- module spring.boot.starter [auto]) · ×1
  • Outdated (compile -- module spring.boot.starter [auto]): org.springframework.boot:spring-boot-starter — org.springframework.boot:spring-boot-starter 3.4.3 → 4.1.2 available.
D12 · Dependency Hygiene · Outdated (compile -- module spring.boot [auto]) · ×1
  • Outdated (compile -- module spring.boot [auto]): org.springframework.boot:spring-boot — org.springframework.boot:spring-boot 3.4.3 → 4.1.2 available.
D12 · Dependency Hygiene · Outdated (compile -- module spring.boot.starter.logging [auto]) · ×1
  • Outdated (compile -- module spring.boot.starter.logging [auto]): org.springframework.boot:spring-boot-starter-logging — org.springframework.boot:spring-boot-starter-logging 3.4.3 → 4.1.2 available.
D12 · Dependency Hygiene · Outdated (compile -- module ch.qos.logback.classic) · ×1
  • Outdated (compile -- module ch.qos.logback.classic): ch.qos.logback:logback-classic — ch.qos.logback:logback-classic 1.5.16 → 1.6.7 available.
D12 · Dependency Hygiene · Outdated (compile -- module ch.qos.logback.core) · ×1
  • Outdated (compile -- module ch.qos.logback.core): ch.qos.logback:logback-core — ch.qos.logback:logback-core 1.5.16 → 1.6.7 available.
D12 · Dependency Hygiene · Outdated (compile -- module org.apache.logging.log4j.to.slf4j) · ×1
  • Outdated (compile -- module org.apache.logging.log4j.to.slf4j): org.apache.logging.log4j:log4j-to-slf4j — org.apache.logging.log4j:log4j-to-slf4j 2.24.3 → 2.26.1 available.
D12 · Dependency Hygiene · Outdated (compile -- module org.apache.logging.log4j) · ×1
  • Outdated (compile -- module org.apache.logging.log4j): org.apache.logging.log4j:log4j-api — org.apache.logging.log4j:log4j-api 2.24.3 → 2.26.1 available.
D12 · Dependency Hygiene · Outdated (compile -- module jul.to.slf4j) · ×1
  • Outdated (compile -- module jul.to.slf4j): org.slf4j:jul-to-slf4j — org.slf4j:jul-to-slf4j 2.0.16 → 2.0.20 available.
D12 · Dependency Hygiene · Outdated (compile -- module jakarta.annotation) · ×1
  • Outdated (compile -- module jakarta.annotation): jakarta.annotation:jakarta.annotation-api — jakarta.annotation:jakarta.annotation-api 2.1.1 → 3.0.0 available.
D12 · Dependency Hygiene · Outdated (test -- module spring.boot.test [auto]) · ×1
  • Outdated (test -- module spring.boot.test [auto]): org.springframework.boot:spring-boot-test — org.springframework.boot:spring-boot-test 3.4.3 → 4.1.2 available.
D12 · Dependency Hygiene · Outdated (test -- module spring.boot.test.autoconfigure [auto]) · ×1
  • Outdated (test -- module spring.boot.test.autoconfigure [auto]): org.springframework.boot:spring-boot-test-autoconfigure — org.springframework.boot:spring-boot-test-autoconfigure 3.4.3 → 4.1.2 available.
D12 · Dependency Hygiene · Outdated (test -- module json.path [auto]) · ×1
  • Outdated (test -- module json.path [auto]): com.jayway.jsonpath:json-path — com.jayway.jsonpath:json-path 2.9.0 → 3.0.0 available.
D12 · Dependency Hygiene · Outdated (compile -- module jakarta.xml.bind) · ×1
  • Outdated (compile -- module jakarta.xml.bind): jakarta.xml.bind:jakarta.xml.bind-api — jakarta.xml.bind:jakarta.xml.bind-api 4.0.2 → 4.0.5 available.
D12 · Dependency Hygiene · Outdated (compile -- module jakarta.activation) · ×1
  • Outdated (compile -- module jakarta.activation): jakarta.activation:jakarta.activation-api — jakarta.activation:jakarta.activation-api 2.1.3 → 2.1.4 available.
D12 · Dependency Hygiene · Outdated (test -- module json.smart (auto)) · ×1
  • Outdated (test -- module json.smart (auto)): net.minidev:json-smart — net.minidev:json-smart 2.5.2 → 2.6.1 available.
D12 · Dependency Hygiene · Outdated (test -- module accessors.smart (auto)) · ×1
  • Outdated (test -- module accessors.smart (auto)): net.minidev:accessors-smart — net.minidev:accessors-smart 2.5.2 → 2.6.1 available.
D12 · Dependency Hygiene · Outdated (test -- module org.objectweb.asm) · ×1
  • Outdated (test -- module org.objectweb.asm): org.ow2.asm:asm — org.ow2.asm:asm 9.7.1 → 9.11.1 available.
D12 · Dependency Hygiene · Outdated (test -- module org.assertj.core) · ×1
  • Outdated (test -- module org.assertj.core): org.assertj:assertj-core — org.assertj:assertj-core 3.26.3 → 3.27.7 available.
D12 · Dependency Hygiene · Outdated (test -- module net.bytebuddy) · ×1
  • Outdated (test -- module net.bytebuddy): net.bytebuddy:byte-buddy — net.bytebuddy:byte-buddy 1.15.11 → 1.18.17 available.
D12 · Dependency Hygiene · Outdated (test -- module awaitility (auto)) · ×1
  • Outdated (test -- module awaitility (auto)): org.awaitility:awaitility — org.awaitility:awaitility 4.2.2 → 4.3.0 available.
D12 · Dependency Hygiene · Outdated (test -- module org.hamcrest [auto]) · ×1
  • Outdated (test -- module org.hamcrest [auto]): org.hamcrest:hamcrest — org.hamcrest:hamcrest 2.2 → 3.0 available.
D12 · Dependency Hygiene · Outdated (test -- module org.junit.jupiter) · ×1
  • Outdated (test -- module org.junit.jupiter): org.junit.jupiter:junit-jupiter — org.junit.jupiter:junit-jupiter 5.11.4 → 6.1.3 available.
D12 · Dependency Hygiene · Outdated (test -- module org.mockito [auto]) · ×1
  • Outdated (test -- module org.mockito [auto]): org.mockito:mockito-core — org.mockito:mockito-core 5.14.2 → 5.24.0 available.
D12 · Dependency Hygiene · Outdated (test -- module net.bytebuddy.agent) · ×1
  • Outdated (test -- module net.bytebuddy.agent): net.bytebuddy:byte-buddy-agent — net.bytebuddy:byte-buddy-agent 1.15.11 → 1.18.17 available.
D12 · Dependency Hygiene · Outdated (test -- module org.objenesis [auto]) · ×1
  • Outdated (test -- module org.objenesis [auto]): org.objenesis:objenesis — org.objenesis:objenesis 3.3 → 3.6 available.
D12 · Dependency Hygiene · Outdated (test -- module org.mockito.junit.jupiter [auto]) · ×1
  • Outdated (test -- module org.mockito.junit.jupiter [auto]): org.mockito:mockito-junit-jupiter — org.mockito:mockito-junit-jupiter 5.14.2 → 5.24.0 available.
D12 · Dependency Hygiene · Outdated (compile -- module spring.core [auto]) · ×1
  • Outdated (compile -- module spring.core [auto]): org.springframework:spring-core — org.springframework:spring-core 6.2.3 → 7.0.10 available.
D12 · Dependency Hygiene · Outdated (compile -- module spring.jcl [auto]) · ×1
  • Outdated (compile -- module spring.jcl [auto]): org.springframework:spring-jcl — org.springframework:spring-jcl 6.2.3 → 6.2.19 available.
D12 · Dependency Hygiene · Outdated (test -- module spring.test [auto]) · ×1
  • Outdated (test -- module spring.test [auto]): org.springframework:spring-test — org.springframework:spring-test 6.2.3 → 7.0.10 available.
D12 · Dependency Hygiene · Outdated (test -- module org.xmlunit [auto]) · ×1
  • Outdated (test -- module org.xmlunit [auto]): org.xmlunit:xmlunit-core — org.xmlunit:xmlunit-core 2.10.0 → 2.14.0 available.
D12 · Dependency Hygiene · Outdated (provided -- module jakarta.servlet) · ×1
  • Outdated (provided -- module jakarta.servlet): jakarta.servlet:jakarta.servlet-api — jakarta.servlet:jakarta.servlet-api 6.0.0 → 6.1.0 available.
D12 · Dependency Hygiene · Outdated (compile -- module spring.boot.starter.web [auto]) · ×1
  • Outdated (compile -- module spring.boot.starter.web [auto]): org.springframework.boot:spring-boot-starter-web — org.springframework.boot:spring-boot-starter-web 3.4.3 → 4.1.2 available.
D12 · Dependency Hygiene · Outdated (compile -- module spring.boot.starter.json [auto]) · ×1
  • Outdated (compile -- module spring.boot.starter.json [auto]): org.springframework.boot:spring-boot-starter-json — org.springframework.boot:spring-boot-starter-json 3.4.3 → 4.1.2 available.
D12 · Dependency Hygiene · Outdated (compile -- module com.fasterxml.jackson.datatype.jdk8) · ×1
  • Outdated (compile -- module com.fasterxml.jackson.datatype.jdk8): com.fasterxml.jackson.datatype:jackson-datatype-jdk8 — com.fasterxml.jackson.datatype:jackson-datatype-jdk8 2.18.2 → 2.23.0 available.
D12 · Dependency Hygiene · Outdated (compile -- module com.fasterxml.jackson.module.paramnames) · ×1
  • Outdated (compile -- module com.fasterxml.jackson.module.paramnames): com.fasterxml.jackson.module:jackson-module-parameter-names — com.fasterxml.jackson.module:jackson-module-parameter-names 2.18.2 → 2.23.0 available.
D12 · Dependency Hygiene · Outdated (compile -- module spring.boot.starter.tomcat [auto]) · ×1
  • Outdated (compile -- module spring.boot.starter.tomcat [auto]): org.springframework.boot:spring-boot-starter-tomcat — org.springframework.boot:spring-boot-starter-tomcat 3.4.3 → 4.1.2 available.
D12 · Dependency Hygiene · Outdated (compile -- module org.apache.tomcat.embed.core) · ×1
  • Outdated (compile -- module org.apache.tomcat.embed.core): org.apache.tomcat.embed:tomcat-embed-core — org.apache.tomcat.embed:tomcat-embed-core 10.1.36 → 11.0.29 available.
D12 · Dependency Hygiene · Outdated (compile -- module org.apache.tomcat.embed.websocket) · ×1
  • Outdated (compile -- module org.apache.tomcat.embed.websocket): org.apache.tomcat.embed:tomcat-embed-websocket — org.apache.tomcat.embed:tomcat-embed-websocket 10.1.36 → 11.0.29 available.
D12 · Dependency Hygiene · Outdated (compile -- module spring.web [auto]) · ×1
  • Outdated (compile -- module spring.web [auto]): org.springframework:spring-web — org.springframework:spring-web 6.2.3 → 7.0.10 available.
D12 · Dependency Hygiene · Outdated (compile -- module micrometer.observation [auto]) · ×1
  • Outdated (compile -- module micrometer.observation [auto]): io.micrometer:micrometer-observation — io.micrometer:micrometer-observation 1.14.4 → 1.17.2 available.
D12 · Dependency Hygiene · Outdated (compile -- module micrometer.commons [auto]) · ×1
  • Outdated (compile -- module micrometer.commons [auto]): io.micrometer:micrometer-commons — io.micrometer:micrometer-commons 1.14.4 → 1.17.2 available.
D12 · Dependency Hygiene · Outdated (compile -- module spring.webmvc [auto]) · ×1
  • Outdated (compile -- module spring.webmvc [auto]): org.springframework:spring-webmvc — org.springframework:spring-webmvc 6.2.3 → 7.0.10 available.
D12 · Dependency Hygiene · Outdated (compile -- module spring.expression [auto]) · ×1
  • Outdated (compile -- module spring.expression [auto]): org.springframework:spring-expression — org.springframework:spring-expression 6.2.3 → 7.0.10 available.
D12 · Dependency Hygiene · Outdated (compile -- module spring.boot.starter.aop [auto]) · ×1
  • Outdated (compile -- module spring.boot.starter.aop [auto]): org.springframework.boot:spring-boot-starter-aop — org.springframework.boot:spring-boot-starter-aop 3.4.3 → 3.5.16 available.
D12 · Dependency Hygiene · Outdated (compile -- module spring.aop [auto]) · ×1
  • Outdated (compile -- module spring.aop [auto]): org.springframework:spring-aop — org.springframework:spring-aop 6.2.3 → 7.0.10 available.
D12 · Dependency Hygiene · Outdated (compile -- module org.aspectj.weaver [auto]) · ×1
  • Outdated (compile -- module org.aspectj.weaver [auto]): org.aspectj:aspectjweaver — org.aspectj:aspectjweaver 1.9.22.1 → 1.9.27 available.
D12 · Dependency Hygiene · Outdated (compile -- module spring.context.support [auto]) · ×1
  • Outdated (compile -- module spring.context.support [auto]): org.springframework:spring-context-support — org.springframework:spring-context-support 6.2.3 → 7.0.10 available.
D12 · Dependency Hygiene · Outdated (compile -- module spring.beans [auto]) · ×1
  • Outdated (compile -- module spring.beans [auto]): org.springframework:spring-beans — org.springframework:spring-beans 6.2.3 → 7.0.10 available.
D12 · Dependency Hygiene · Outdated (compile -- module spring.context [auto]) · ×1
  • Outdated (compile -- module spring.context [auto]): org.springframework:spring-context — org.springframework:spring-context 6.2.3 → 7.0.10 available.
D12 · Dependency Hygiene · Outdated (compile -- module spring.boot.starter.data.redis [auto]) · ×1
  • Outdated (compile -- module spring.boot.starter.data.redis [auto]): org.springframework.boot:spring-boot-starter-data-redis — org.springframework.boot:spring-boot-starter-data-redis 3.4.3 → 4.1.2 available.
D12 · Dependency Hygiene · Outdated (compile -- module lettuce.core [auto]) · ×1
  • Outdated (compile -- module lettuce.core [auto]): io.lettuce:lettuce-core — io.lettuce:lettuce-core 6.4.2.RELEASE → 7.9.0.RELEASE available.
D12 · Dependency Hygiene · Outdated (compile -- module io.netty.common [auto]) · ×1
  • Outdated (compile -- module io.netty.common [auto]): io.netty:netty-common — io.netty:netty-common 4.1.118.Final → 4.2.20.Final available.
D12 · Dependency Hygiene · Outdated (compile -- module io.netty.handler [auto]) · ×1
  • Outdated (compile -- module io.netty.handler [auto]): io.netty:netty-handler — io.netty:netty-handler 4.1.118.Final → 4.2.20.Final available.
D12 · Dependency Hygiene · Outdated (compile -- module io.netty.resolver [auto]) · ×1
  • Outdated (compile -- module io.netty.resolver [auto]): io.netty:netty-resolver — io.netty:netty-resolver 4.1.118.Final → 4.2.20.Final available.
D12 · Dependency Hygiene · Outdated (compile -- module io.netty.buffer [auto]) · ×1
  • Outdated (compile -- module io.netty.buffer [auto]): io.netty:netty-buffer — io.netty:netty-buffer 4.1.118.Final → 4.2.20.Final available.
D12 · Dependency Hygiene · Outdated (compile -- module io.netty.transport.unix.common [auto]) · ×1
  • Outdated (compile -- module io.netty.transport.unix.common [auto]): io.netty:netty-transport-native-unix-common — io.netty:netty-transport-native-unix-common 4.1.118.Final → 4.2.20.Final available.
D12 · Dependency Hygiene · Outdated (compile -- module io.netty.codec [auto]) · ×1
  • Outdated (compile -- module io.netty.codec [auto]): io.netty:netty-codec — io.netty:netty-codec 4.1.118.Final → 4.2.20.Final available.
D12 · Dependency Hygiene · Outdated (compile -- module io.netty.transport [auto]) · ×1
  • Outdated (compile -- module io.netty.transport [auto]): io.netty:netty-transport — io.netty:netty-transport 4.1.118.Final → 4.2.20.Final available.
D12 · Dependency Hygiene · Outdated (compile -- module reactor.core [auto]) · ×1
  • Outdated (compile -- module reactor.core [auto]): io.projectreactor:reactor-core — io.projectreactor:reactor-core 3.7.3 → 3.8.8 available.
D12 · Dependency Hygiene · Outdated (compile -- module spring.data.redis [auto]) · ×1
  • Outdated (compile -- module spring.data.redis [auto]): org.springframework.data:spring-data-redis — org.springframework.data:spring-data-redis 3.4.3 → 4.1.2 available.
D12 · Dependency Hygiene · Outdated (compile -- module spring.data.keyvalue [auto]) · ×1
  • Outdated (compile -- module spring.data.keyvalue [auto]): org.springframework.data:spring-data-keyvalue — org.springframework.data:spring-data-keyvalue 3.4.3 → 4.1.2 available.
D12 · Dependency Hygiene · Outdated (compile -- module spring.data.commons [auto]) · ×1
  • Outdated (compile -- module spring.data.commons [auto]): org.springframework.data:spring-data-commons — org.springframework.data:spring-data-commons 3.4.3 → 4.1.2 available.
D12 · Dependency Hygiene · Outdated (compile -- module spring.tx [auto]) · ×1
  • Outdated (compile -- module spring.tx [auto]): org.springframework:spring-tx — org.springframework:spring-tx 6.2.3 → 7.0.10 available.
D12 · Dependency Hygiene · Outdated (compile -- module spring.oxm [auto]) · ×1
  • Outdated (compile -- module spring.oxm [auto]): org.springframework:spring-oxm — org.springframework:spring-oxm 6.2.3 → 7.0.10 available.
D12 · Dependency Hygiene · Outdated (compile -- module spring.boot.starter.validation [auto]) · ×1
  • Outdated (compile -- module spring.boot.starter.validation [auto]): org.springframework.boot:spring-boot-starter-validation — org.springframework.boot:spring-boot-starter-validation 3.4.3 → 4.1.2 available.
D12 · Dependency Hygiene · Outdated (compile -- module org.apache.tomcat.embed.el) · ×1
  • Outdated (compile -- module org.apache.tomcat.embed.el): org.apache.tomcat.embed:tomcat-embed-el — org.apache.tomcat.embed:tomcat-embed-el 10.1.36 → 11.0.29 available.
D12 · Dependency Hygiene · Outdated (compile -- module org.hibernate.validator [auto]) · ×1
  • Outdated (compile -- module org.hibernate.validator [auto]): org.hibernate.validator:hibernate-validator — org.hibernate.validator:hibernate-validator 8.0.2.Final → 9.1.6.Final available.
D12 · Dependency Hygiene · Outdated (compile -- module jakarta.validation) · ×1
  • Outdated (compile -- module jakarta.validation): jakarta.validation:jakarta.validation-api — jakarta.validation:jakarta.validation-api 3.0.2 → 3.1.1 available.
D12 · Dependency Hygiene · Outdated (compile -- module org.jboss.logging) · ×1
  • Outdated (compile -- module org.jboss.logging): org.jboss.logging:jboss-logging — org.jboss.logging:jboss-logging 3.6.1.Final → 3.6.3.Final available.
D12 · Dependency Hygiene · Outdated (compile -- module com.fasterxml.classmate) · ×1
  • Outdated (compile -- module com.fasterxml.classmate): com.fasterxml:classmate — com.fasterxml:classmate 1.7.0 → 1.8.0 available.
D12 · Dependency Hygiene · Outdated (compile (optional) -- module spring.boot.configuration.processor [auto]) · ×1
  • Outdated (compile (optional) -- module spring.boot.configuration.processor [auto]): org.springframework.boot:spring-boot-configuration-processor — org.springframework.boot:spring-boot-configuration-processor 3.4.3 → 4.1.2 available.
D12 · Dependency Hygiene · Outdated (compile -- module mysql.connector.j (auto)) · ×1
  • Outdated (compile -- module mysql.connector.j (auto)): com.mysql:mysql-connector-j — com.mysql:mysql-connector-j 9.1.0 → 26.10.0 available.
D12 · Dependency Hygiene · Outdated (compile -- module druid (auto)) · ×1
  • Outdated (compile -- module druid (auto)): com.alibaba:druid — com.alibaba:druid 1.2.20 → 1.2.28 available.
D12 · Dependency Hygiene · Outdated (compile -- module org.slf4j) · ×1
  • Outdated (compile -- module org.slf4j): org.slf4j:slf4j-api — org.slf4j:slf4j-api 2.0.16 → 2.0.20 available.
D12 · Dependency Hygiene · Outdated (compile -- module spring.boot.autoconfigure [auto]) · ×1
  • Outdated (compile -- module spring.boot.autoconfigure [auto]): org.springframework.boot:spring-boot-autoconfigure — org.springframework.boot:spring-boot-autoconfigure 3.4.3 → 4.1.2 available.
D12 · Dependency Hygiene · Outdated (compile -- module liquibase.core [auto]) · ×1
  • Outdated (compile -- module liquibase.core [auto]): org.liquibase:liquibase-core — org.liquibase:liquibase-core 4.20.0 → 5.0.4 available.
D12 · Dependency Hygiene · Outdated (compile -- module org.yaml.snakeyaml) · ×1
  • Outdated (compile -- module org.yaml.snakeyaml): org.yaml:snakeyaml — org.yaml:snakeyaml 2.3 → 2.7 available.
D12 · Dependency Hygiene · Outdated (compile -- module com.opencsv [auto]) · ×1
  • Outdated (compile -- module com.opencsv [auto]): com.opencsv:opencsv — com.opencsv:opencsv 5.7.1 → 5.12.0 available.
D12 · Dependency Hygiene · Outdated (compile -- module org.apache.commons.text [auto]) · ×1
  • Outdated (compile -- module org.apache.commons.text [auto]): org.apache.commons:commons-text — org.apache.commons:commons-text 1.10.0 → 1.15.0 available.
D12 · Dependency Hygiene · Outdated (compile -- module org.apache.commons.collections4 [auto]) · ×1
  • Outdated (compile -- module org.apache.commons.collections4 [auto]): org.apache.commons:commons-collections4 — org.apache.commons:commons-collections4 4.4 → 4.6.0 available.
D12 · Dependency Hygiene · Outdated (compile -- module mybatis.plus.spring.boot3.starter (auto)) · ×1
  • Outdated (compile -- module mybatis.plus.spring.boot3.starter (auto)): com.baomidou:mybatis-plus-spring-boot3-starter — com.baomidou:mybatis-plus-spring-boot3-starter 3.5.17 → 3.5.18.1 available.
D12 · Dependency Hygiene · Outdated (compile -- module mybatis.plus (auto)) · ×1
  • Outdated (compile -- module mybatis.plus (auto)): com.baomidou:mybatis-plus — com.baomidou:mybatis-plus 3.5.17 → 3.5.18.1 available.
D12 · Dependency Hygiene · Outdated (compile -- module mybatis.plus.core (auto)) · ×1
  • Outdated (compile -- module mybatis.plus.core (auto)): com.baomidou:mybatis-plus-core — com.baomidou:mybatis-plus-core 3.5.17 → 3.5.18.1 available.
D12 · Dependency Hygiene · Outdated (compile -- module mybatis.plus.annotation (auto)) · ×1
  • Outdated (compile -- module mybatis.plus.annotation (auto)): com.baomidou:mybatis-plus-annotation — com.baomidou:mybatis-plus-annotation 3.5.17 → 3.5.18.1 available.
D12 · Dependency Hygiene · Outdated (compile -- module mybatis.plus.spring (auto)) · ×1
  • Outdated (compile -- module mybatis.plus.spring (auto)): com.baomidou:mybatis-plus-spring — com.baomidou:mybatis-plus-spring 3.5.17 → 3.5.18.1 available.
D12 · Dependency Hygiene · Outdated (compile -- module org.mybatis [auto]) · ×1
  • Outdated (compile -- module org.mybatis [auto]): org.mybatis:mybatis — org.mybatis:mybatis 3.5.19 → 3.6.0 available.
D12 · Dependency Hygiene · Outdated (compile -- module org.mybatis.spring [auto]) · ×1
  • Outdated (compile -- module org.mybatis.spring [auto]): org.mybatis:mybatis-spring — org.mybatis:mybatis-spring 3.0.5 → 4.1.0 available.
D12 · Dependency Hygiene · Outdated (compile -- module mybatis.plus.spring.boot.autoconfigure (auto)) · ×1
  • Outdated (compile -- module mybatis.plus.spring.boot.autoconfigure (auto)): com.baomidou:mybatis-plus-spring-boot-autoconfigure — com.baomidou:mybatis-plus-spring-boot-autoconfigure 3.5.17 → 3.5.18.1 available.
D12 · Dependency Hygiene · Outdated (compile -- module spring.boot.starter.jdbc [auto]) · ×1
  • Outdated (compile -- module spring.boot.starter.jdbc [auto]): org.springframework.boot:spring-boot-starter-jdbc — org.springframework.boot:spring-boot-starter-jdbc 3.4.3 → 4.1.2 available.
D12 · Dependency Hygiene · Outdated (compile -- module com.zaxxer.hikari) · ×1
  • Outdated (compile -- module com.zaxxer.hikari): com.zaxxer:HikariCP — com.zaxxer:HikariCP 5.1.0 → 7.1.0 available.
D12 · Dependency Hygiene · Outdated (compile -- module spring.jdbc [auto]) · ×1
  • Outdated (compile -- module spring.jdbc [auto]): org.springframework:spring-jdbc — org.springframework:spring-jdbc 6.2.3 → 7.0.10 available.
D12 · Dependency Hygiene · Outdated (compile -- module mybatis.plus.jsqlparser (auto)) · ×1
  • Outdated (compile -- module mybatis.plus.jsqlparser (auto)): com.baomidou:mybatis-plus-jsqlparser-4.9 — com.baomidou:mybatis-plus-jsqlparser-4.9 3.5.17 → 3.5.18.1 available.
D12 · Dependency Hygiene · Outdated (compile -- module net.sf.jsqlparser [auto]) · ×1
  • Outdated (compile -- module net.sf.jsqlparser [auto]): com.github.jsqlparser:jsqlparser — com.github.jsqlparser:jsqlparser 4.9 → 5.4 available.
D12 · Dependency Hygiene · Outdated (compile -- module mybatis.plus.jsqlparser.common (auto)) · ×1
  • Outdated (compile -- module mybatis.plus.jsqlparser.common (auto)): com.baomidou:mybatis-plus-jsqlparser-common — com.baomidou:mybatis-plus-jsqlparser-common 3.5.17 → 3.5.18.1 available.
D12 · Dependency Hygiene · Outdated (compile -- module mybatis.plus.extension (auto)) · ×1
  • Outdated (compile -- module mybatis.plus.extension (auto)): com.baomidou:mybatis-plus-extension — com.baomidou:mybatis-plus-extension 3.5.17 → 3.5.18.1 available.
D12 · Dependency Hygiene · Outdated (compile -- module cn.hutool [auto]) · ×1
  • Outdated (compile -- module cn.hutool [auto]): cn.hutool:hutool-all — cn.hutool:hutool-all 5.8.46 → 5.8.48 available.
D12 · Dependency Hygiene · Outdated (compile -- module org.jsoup) · ×1
  • Outdated (compile -- module org.jsoup): org.jsoup:jsoup — org.jsoup:jsoup 1.22.2 → 1.24.1 available.
D12 · Dependency Hygiene · Outdated (compile -- module org.bouncycastle.provider) · ×1
  • Outdated (compile -- module org.bouncycastle.provider): org.bouncycastle:bcprov-jdk18on — org.bouncycastle:bcprov-jdk18on 1.78 → 1.87 available.
D12 · Dependency Hygiene · Outdated (compile -- module org.springdoc.openapi.ui [auto]) · ×1
  • Outdated (compile -- module org.springdoc.openapi.ui [auto]): org.springdoc:springdoc-openapi-starter-webmvc-ui — org.springdoc:springdoc-openapi-starter-webmvc-ui 2.8.8 → 3.2.0 available.
D12 · Dependency Hygiene · Outdated (compile -- module org.springdoc.openapi.webmvc.core [auto]) · ×1
  • Outdated (compile -- module org.springdoc.openapi.webmvc.core [auto]): org.springdoc:springdoc-openapi-starter-webmvc-api — org.springdoc:springdoc-openapi-starter-webmvc-api 2.8.8 → 3.2.0 available.
D12 · Dependency Hygiene · Outdated (compile -- module org.springdoc.openapi.common [auto]) · ×1
  • Outdated (compile -- module org.springdoc.openapi.common [auto]): org.springdoc:springdoc-openapi-starter-common — org.springdoc:springdoc-openapi-starter-common 2.8.8 → 3.2.0 available.
D12 · Dependency Hygiene · Outdated (compile -- module io.swagger.v3.core [auto]) · ×1
  • Outdated (compile -- module io.swagger.v3.core [auto]): io.swagger.core.v3:swagger-core-jakarta — io.swagger.core.v3:swagger-core-jakarta 2.2.30 → 2.2.55 available.
D12 · Dependency Hygiene · Outdated (compile -- module io.swagger.v3.oas.annotations [auto]) · ×1
  • Outdated (compile -- module io.swagger.v3.oas.annotations [auto]): io.swagger.core.v3:swagger-annotations-jakarta — io.swagger.core.v3:swagger-annotations-jakarta 2.2.30 → 2.2.55 available.
D12 · Dependency Hygiene · Outdated (compile -- module io.swagger.v3.oas.models [auto]) · ×1
  • Outdated (compile -- module io.swagger.v3.oas.models [auto]): io.swagger.core.v3:swagger-models-jakarta — io.swagger.core.v3:swagger-models-jakarta 2.2.30 → 2.2.55 available.
D12 · Dependency Hygiene · Outdated (compile -- module com.fasterxml.jackson.dataformat.yaml) · ×1
  • Outdated (compile -- module com.fasterxml.jackson.dataformat.yaml): com.fasterxml.jackson.dataformat:jackson-dataformat-yaml — com.fasterxml.jackson.dataformat:jackson-dataformat-yaml 2.18.2 → 2.23.0 available.
D12 · Dependency Hygiene · Outdated (compile -- module swagger.ui (auto)) · ×1
  • Outdated (compile -- module swagger.ui (auto)): org.webjars:swagger-ui — org.webjars:swagger-ui 5.21.0 → 5.35.0 available.
D12 · Dependency Hygiene · Outdated (compile -- module webjars.locator.lite (auto)) · ×1
  • Outdated (compile -- module webjars.locator.lite (auto)): org.webjars:webjars-locator-lite — org.webjars:webjars-locator-lite 1.0.1 → 1.1.5 available.
D12 · Dependency Hygiene · Outdated (compile -- module org.apache.commons.lang3) · ×1
  • Outdated (compile -- module org.apache.commons.lang3): org.apache.commons:commons-lang3 — org.apache.commons:commons-lang3 3.20.0 → 3.22.0 available.
D12 · Dependency Hygiene · Outdated (compile (optional) -- module lombok) · ×1
  • Outdated (compile (optional) -- module lombok): org.projectlombok:lombok — org.projectlombok:lombok 1.18.36 → 1.18.48 available.
D12 · Dependency Hygiene · Outdated (compile -- module com.fasterxml.jackson.datatype.jsr310) · ×1
  • Outdated (compile -- module com.fasterxml.jackson.datatype.jsr310): com.fasterxml.jackson.datatype:jackson-datatype-jsr310 — com.fasterxml.jackson.datatype:jackson-datatype-jsr310 2.18.2 → 2.23.0 available.
D12 · Dependency Hygiene · Outdated (compile -- module com.fasterxml.jackson.annotation) · ×1
  • Outdated (compile -- module com.fasterxml.jackson.annotation): com.fasterxml.jackson.core:jackson-annotations — com.fasterxml.jackson.core:jackson-annotations 2.18.2 → 2.23 available.
D12 · Dependency Hygiene · Outdated (compile -- module com.fasterxml.jackson.core) · ×1
  • Outdated (compile -- module com.fasterxml.jackson.core): com.fasterxml.jackson.core:jackson-core — com.fasterxml.jackson.core:jackson-core 2.18.2 → 2.23.0 available.
D12 · Dependency Hygiene · Outdated (compile -- module com.fasterxml.jackson.databind) · ×1
  • Outdated (compile -- module com.fasterxml.jackson.databind): com.fasterxml.jackson.core:jackson-databind — com.fasterxml.jackson.core:jackson-databind 2.18.2 → 2.23.0 available.
D12 · Dependency Hygiene · Outdated (compile -- module dysmsapi20170525 (auto)) · ×1
  • Outdated (compile -- module dysmsapi20170525 (auto)): com.aliyun:dysmsapi20170525 — com.aliyun:dysmsapi20170525 4.1.0 → 4.6.0 available.
D12 · Dependency Hygiene · Outdated (compile -- module tea.util (auto)) · ×1
  • Outdated (compile -- module tea.util (auto)): com.aliyun:tea-util — com.aliyun:tea-util 0.2.23 → 0.2.28 available.
D12 · Dependency Hygiene · Outdated (compile -- module com.google.gson) · ×1
  • Outdated (compile -- module com.google.gson): com.google.code.gson:gson — com.google.code.gson:gson 2.11.0 → 2.15.0 available.
D12 · Dependency Hygiene · Outdated (compile -- module endpoint.util (auto)) · ×1
  • Outdated (compile -- module endpoint.util (auto)): com.aliyun:endpoint-util — com.aliyun:endpoint-util 0.0.7 → 0.0.8 available.
D12 · Dependency Hygiene · Outdated (compile -- module tea (auto)) · ×1
  • Outdated (compile -- module tea (auto)): com.aliyun:tea — com.aliyun:tea 1.3.1 → 1.4.3 available.
D12 · Dependency Hygiene · Outdated (compile -- module okhttp3 [auto]) · ×1
  • Outdated (compile -- module okhttp3 [auto]): com.squareup.okhttp3:okhttp — com.squareup.okhttp3:okhttp 3.12.13 → 5.5.1 available.
D12 · Dependency Hygiene · Outdated (compile -- module tea.openapi (auto)) · ×1
  • Outdated (compile -- module tea.openapi (auto)): com.aliyun:tea-openapi — com.aliyun:tea-openapi 0.3.8 → 0.3.20 available.
D12 · Dependency Hygiene · Outdated (compile -- module credentials.java (auto)) · ×1
  • Outdated (compile -- module credentials.java (auto)): com.aliyun:credentials-java — com.aliyun:credentials-java 1.0.1 → 1.0.8 available.
D12 · Dependency Hygiene · Outdated (compile -- module alibabacloud.gateway.spi (auto)) · ×1
  • Outdated (compile -- module alibabacloud.gateway.spi (auto)): com.aliyun:alibabacloud-gateway-spi — com.aliyun:alibabacloud-gateway-spi 0.0.2 → 0.0.3 available.
D12 · Dependency Hygiene · Outdated (compile -- module tea.xml (auto)) · ×1
  • Outdated (compile -- module tea.xml (auto)): com.aliyun:tea-xml — com.aliyun:tea-xml 0.1.6 → 0.1.7 available.
D12 · Dependency Hygiene · Outdated (compile -- module dom4j (auto)) · ×1
  • Outdated (compile -- module dom4j (auto)): org.dom4j:dom4j — org.dom4j:dom4j 2.0.3 → 2.2.0 available.
D12 · Dependency Hygiene · Outdated (compile -- module org.jacoco.agent.rt [auto]) · ×1
  • Outdated (compile -- module org.jacoco.agent.rt [auto]): org.jacoco:org.jacoco.agent — org.jacoco:org.jacoco.agent 0.8.4 → 0.8.16 available.
D12 · Dependency Hygiene · Outdated (compile -- module openapiutil (auto)) · ×1
  • Outdated (compile -- module openapiutil (auto)): com.aliyun:openapiutil — com.aliyun:openapiutil 0.2.2 → 0.2.5 available.
D12 · Dependency Hygiene · Outdated (compile -- module org.apache.commons.codec) · ×1
  • Outdated (compile -- module org.apache.commons.codec): commons-codec:commons-codec — commons-codec:commons-codec 1.17.2 → 1.23.0 available.
D12 · Dependency Hygiene · Outdated (compile -- module okio (auto)) · ×1
  • Outdated (compile -- module okio (auto)): com.squareup.okio:okio — com.squareup.okio:okio 3.4.0 → 3.18.2 available.
D12 · Dependency Hygiene · Outdated (compile -- module okio [auto]) · ×1
  • Outdated (compile -- module okio [auto]): com.squareup.okio:okio-jvm — com.squareup.okio:okio-jvm 3.4.0 → 3.18.2 available.
D12 · Dependency Hygiene · Outdated (compile -- module kotlin.stdlib.jdk8) · ×1
  • Outdated (compile -- module kotlin.stdlib.jdk8): org.jetbrains.kotlin:kotlin-stdlib-jdk8 — org.jetbrains.kotlin:kotlin-stdlib-jdk8 1.9.25 → 2.4.21 available.
D12 · Dependency Hygiene · Outdated (compile -- module kotlin.stdlib) · ×1
  • Outdated (compile -- module kotlin.stdlib): org.jetbrains.kotlin:kotlin-stdlib — org.jetbrains.kotlin:kotlin-stdlib 1.9.25 → 2.4.21 available.
D12 · Dependency Hygiene · Outdated (compile -- module annotations (auto)) · ×1
  • Outdated (compile -- module annotations (auto)): org.jetbrains:annotations — org.jetbrains:annotations 13.0 → 26.1.0 available.
D12 · Dependency Hygiene · Outdated (compile -- module kotlin.stdlib.jdk7) · ×1
  • Outdated (compile -- module kotlin.stdlib.jdk7): org.jetbrains.kotlin:kotlin-stdlib-jdk7 — org.jetbrains.kotlin:kotlin-stdlib-jdk7 1.9.25 → 2.4.21 available.
D12 · Dependency Hygiene · Outdated (compile -- module kotlin.stdlib.common (auto)) · ×1
  • Outdated (compile -- module kotlin.stdlib.common (auto)): org.jetbrains.kotlin:kotlin-stdlib-common — org.jetbrains.kotlin:kotlin-stdlib-common 1.9.25 → 2.4.21 available.
D24 · Comment Value · doc comments repeat the names · ×1
  • doc comments repeat the names main/manager-web/src/utils/index.js:22 — 0 of 11 documented parameters and 0 of 0 summaries in `xiaozhi` only repeat the member or parameter name (e.g. "" for `data`). 11 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.

Appendix B — Reproduction & audit trail

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

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=0 --max-count=200" --report-format json --report-path /tmp/watchdog-gitleaks-ea9c94fd9bce4ff4a1a4e90984d589ec/history.json --exit-code 0 --source .0artifacts/raw/gitleaks-history.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=200 --max-count=800" --report-format json --report-path /tmp/watchdog-gitleaks-ea9c94fd9bce4ff4a1a4e90984d589ec/history-1.json --exit-code 0 --source .13artifacts/raw/gitleaks-history-1.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=1000 --max-count=2787" --report-format json --report-path /tmp/watchdog-gitleaks-ea9c94fd9bce4ff4a1a4e90984d589ec/history-2.json --exit-code 0 --source .16artifacts/raw/gitleaks-history-2.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-ea9c94fd9bce4ff4a1a4e90984d589ec/tree.json --exit-code 0 --source .9artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)semgrep—semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt .55artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** .150artifacts/raw/trivy-fs.json
D31 · IaC & Container Securitytrivy—trivy config --format json --quiet .15artifacts/raw/trivy-config.json
D32 · Data Compliance (PII/GDPR)semgrep—semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 2 file(s) — `main/digital-human/js/utils/libopus.js`, `main/manager-web/public/generator/assets/index-Guo1hQ-y.js` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.0—
D37 · Vulnerability-disclosure Policydisclosure—disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.0—
D40 · Network Egress Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.0—
D41 · Kernel & Syscall Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.0—
D42 · Runtime Threat Enforcementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.0—
D43 · Malicious Dependenciestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** .0artifacts/raw/trivy-fs.json

Run 01a1e856-b0e6-75c3-a87f-8d2858abaef5 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Downloadable artifacts

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

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