Public report of dcloudio/uni-app, published 15 November 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 15 November 2026, 05:29 UTC · Survey ID cd_09a00e0b944b4a6ea5eb5090493fd13d
dcloudio/uni-app
Measured 15 November 2026, 05:28 UTC, at code version caff0e8
Bus factor is not measured: No living knowledge left to concentrate.
Knowledge freshness is not measured: Freshness signal contradicted by repo activity.
CAI scoreAt risk
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A medium codebase: 52,091 lines of product code in 137 projects, tests not counted · Estimated rebuild effort: about 0.3 person-years · Weakest lens: Event-Driven, 10
Findings by how serious they are
149 critical617 serious252 minor
24 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Canine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
15 November 2026, 05:28 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 ▸
55of 55 dimensions measured by tools.
1005of 1018 findings point to an exact file and line, so you can open each one in the code. The other 13 concern the repository as a whole, such as missing documentation.
55dimensions across 9 lenses, read from 52,091 lines of product code in 137 projects.
dcloudio/uni-app is rated At risk because critical security findings are open, most of them in the packages it uses. It scores 19 out of 100, which the At risk rating leaves unchanged.
Event-Driven, at 10, is the weakest lens and counts most in the score. The best first step is stopping the event handlers from waiting on other services, worth about 8 points. Making the events unchangeable comes next, worth about 6 points. Raising Event-Driven to 70 would lift the score to about 27.
114 known security holes in the packages the code depends on can be used by attackers. Two passwords or keys are open to anyone who can read the repository. Updating the vulnerable packages and replacing each exposed password or key would close both risks. Making recorded events unchangeable would take care of the eight recorded events that can be changed afterwards.
The product code is 52,091 lines, about €44,000 to rebuild.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
If Event-Driven rose from 10 to 70, the lowest score rated Strong, the score would rise from 19 to about 27.
Code composition: what the lines of code are
Product code 100%Tests 0%
Rebuild cost: about €44,000 · Estimate
Cost to rebuild
€15,000 to €74,000, for 246 to 779 hours of work, about 0.3 person-years for one engineer
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.7 at a score of 19. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Medium: 52,091 lines of product code
What it is not
Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.
How the estimate is made: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Replace the synchronous wait with `async`/`await` so the handler never blocks on a peer/resource.
Raises the score by about 6 points · Medium effort · Immutable events
3
Resolve the 2 Leaked secret finding(s) in Secret Scanning — start with REDACTED, REDACTED.
Raises the score by about 1 point · Low effort · Secret Scanning
Diagnosis: what the measurements show together
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
Where the investment is most exposed · Value at risk
This code would cost about €44,000 to build again, about 0.3 person-years of work. Its weakest lens is Event-Driven, at 10 (Critical). Event-Driven is about whether the parts of the system can rely on the messages they send each other. Because the weakest lens counts most in the score, work on Event-Driven also moves the score most.
Based on: the rebuild estimate · the Event-Driven grade · how much each lens counts
What to do: Start with the Event-Driven actions in Top priorities.
If you do one thing first · First action
Replace the synchronous wait with `async`/`await` so the handler never blocks on a peer/resource. Of all the actions in this report, it raises the score most for the work it takes: about 8 points for medium effort. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 6.6 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 4% to 8% on every change. The history of the code shows how much it changes: about 354,260 lines over the last 90 days, which is about 1,436,721 lines a year. At that pace, the extra work comes to an estimated 129.3 to 775.9 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of our own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Code Duplication · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.
Architecture — module dependency graph
Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.
Architecture: which parts of the code depend on which
The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.
59 modules, with 13 dependencies between them. 3 loops run through 6 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 19 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.
uts.sdk.modules.DCloudUniGetBackgroundAudioManager uses uts.sdk.modules.uniGetBackgroundAudioManager, so a change to uts.sdk.modules.uniGetBackgroundAudioManager can break uts.sdk.modules.DCloudUniGetBackgroundAudioManager, while a change to uts.sdk.modules.DCloudUniGetBackgroundAudioManager can't break uts.sdk.modules.uniGetBackgroundAudioManager.
Position
Below the diagonal: uts.sdk.modules.DCloudUniGetBackgroundAudioManager uses a module listed above it, which is the healthy direction.
29→38 uts.sdk.modules.DcloudUniGetBackgroundLocation.UniSystemLocationService uses uts.sdk.modules.DcloudUniGetBackgroundLocationpart of a loop✕
Connections
1 pair of types, where a type in uts.sdk.modules.DcloudUniGetBackgroundLocation.UniSystemLocationService uses a type in uts.sdk.modules.DcloudUniGetBackgroundLocation.
uts.sdk.modules.DcloudUniGetBackgroundLocation.UniSystemLocationService uses uts.sdk.modules.DcloudUniGetBackgroundLocation, so a change to uts.sdk.modules.DcloudUniGetBackgroundLocation can break uts.sdk.modules.DcloudUniGetBackgroundLocation.UniSystemLocationService, while a change to uts.sdk.modules.DcloudUniGetBackgroundLocation.UniSystemLocationService can't break uts.sdk.modules.DcloudUniGetBackgroundLocation.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
30→39 uts.sdk.modules.uniCamera.CameraManager uses uts.sdk.modules.uniCamerapart of a loop✕
Connections
1 pair of types, where a type in uts.sdk.modules.uniCamera.CameraManager uses a type in uts.sdk.modules.uniCamera.
uts.sdk.modules.uniCamera.CameraManager uses uts.sdk.modules.uniCamera, so a change to uts.sdk.modules.uniCamera can break uts.sdk.modules.uniCamera.CameraManager, while a change to uts.sdk.modules.uniCamera.CameraManager can't break uts.sdk.modules.uniCamera.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
1 pair of types, where a type in uts.sdk.modules.uniCreateInnerAudioContext.AudioFocusHelper uses a type in uts.sdk.modules.uniCreateInnerAudioContext.
uts.sdk.modules.uniCreateInnerAudioContext.AudioFocusHelper uses uts.sdk.modules.uniCreateInnerAudioContext, so a change to uts.sdk.modules.uniCreateInnerAudioContext can break uts.sdk.modules.uniCreateInnerAudioContext.AudioFocusHelper, while a change to uts.sdk.modules.uniCreateInnerAudioContext.AudioFocusHelper can't break uts.sdk.modules.uniCreateInnerAudioContext.
Position
Below the diagonal: uts.sdk.modules.uniCreateInnerAudioContext.AudioFocusHelper uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in uts.sdk.modules.uniGetBackgroundAudioManager.BackgroundAudioPlayer uses a type in uts.sdk.modules.uniGetBackgroundAudioManager.
uts.sdk.modules.uniGetBackgroundAudioManager.BackgroundAudioPlayer uses uts.sdk.modules.uniGetBackgroundAudioManager, so a change to uts.sdk.modules.uniGetBackgroundAudioManager can break uts.sdk.modules.uniGetBackgroundAudioManager.BackgroundAudioPlayer, while a change to uts.sdk.modules.uniGetBackgroundAudioManager.BackgroundAudioPlayer can't break uts.sdk.modules.uniGetBackgroundAudioManager.
Position
Below the diagonal: uts.sdk.modules.uniGetBackgroundAudioManager.BackgroundAudioPlayer uses a module listed above it, which is the healthy direction.
33→40 uts.sdk.modules.uniMapAmap.marker uses uts.sdk.modules.uniMapAmappart of a loop✕
Connections
1 pair of types, where a type in uts.sdk.modules.uniMapAmap.marker uses a type in uts.sdk.modules.uniMapAmap.
uts.sdk.modules.uniMapAmap.marker uses uts.sdk.modules.uniMapAmap, so a change to uts.sdk.modules.uniMapAmap can break uts.sdk.modules.uniMapAmap.marker, while a change to uts.sdk.modules.uniMapAmap.marker can't break uts.sdk.modules.uniMapAmap.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
uts.sdk.modules.uniRecorder uses uts.sdk.modules.uniRecorder.AudioRecorder, so a change to uts.sdk.modules.uniRecorder.AudioRecorder can break uts.sdk.modules.uniRecorder, while a change to uts.sdk.modules.uniRecorder can't break uts.sdk.modules.uniRecorder.AudioRecorder.
Position
Below the diagonal: uts.sdk.modules.uniRecorder uses a module listed above it, which is the healthy direction.
uts.sdk.modules.uniRecorder.AudioRecorder.RecordingFormat uses uts.sdk.modules.uniRecorder.AudioRecorder, so a change to uts.sdk.modules.uniRecorder.AudioRecorder can break uts.sdk.modules.uniRecorder.AudioRecorder.RecordingFormat, while a change to uts.sdk.modules.uniRecorder.AudioRecorder.RecordingFormat can't break uts.sdk.modules.uniRecorder.AudioRecorder.
Position
Below the diagonal: uts.sdk.modules.uniRecorder.AudioRecorder.RecordingFormat uses a module listed above it, which is the healthy direction.
uts.sdk.modules.uniWebView uses uts.sdk.modules.uniWebView.WebViewFileChooseDialog, so a change to uts.sdk.modules.uniWebView.WebViewFileChooseDialog can break uts.sdk.modules.uniWebView, while a change to uts.sdk.modules.uniWebView can't break uts.sdk.modules.uniWebView.WebViewFileChooseDialog.
Position
Below the diagonal: uts.sdk.modules.uniWebView uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in uts.sdk.modules.DCloudUniGetBackgroundAudioManager.AudioService uses a type in uts.sdk.modules.DCloudUniGetBackgroundAudioManager.
uts.sdk.modules.DCloudUniGetBackgroundAudioManager.AudioService uses uts.sdk.modules.DCloudUniGetBackgroundAudioManager, so a change to uts.sdk.modules.DCloudUniGetBackgroundAudioManager can break uts.sdk.modules.DCloudUniGetBackgroundAudioManager.AudioService, while a change to uts.sdk.modules.DCloudUniGetBackgroundAudioManager.AudioService can't break uts.sdk.modules.DCloudUniGetBackgroundAudioManager.
Position
Below the diagonal: uts.sdk.modules.DCloudUniGetBackgroundAudioManager.AudioService uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in uts.sdk.modules.DcloudUniGetBackgroundLocation uses a type in uts.sdk.modules.DcloudUniGetBackgroundLocation.UniSystemLocationService.
uts.sdk.modules.DcloudUniGetBackgroundLocation uses uts.sdk.modules.DcloudUniGetBackgroundLocation.UniSystemLocationService, so a change to uts.sdk.modules.DcloudUniGetBackgroundLocation.UniSystemLocationService can break uts.sdk.modules.DcloudUniGetBackgroundLocation, while a change to uts.sdk.modules.DcloudUniGetBackgroundLocation can't break uts.sdk.modules.DcloudUniGetBackgroundLocation.UniSystemLocationService.
Position
Below the diagonal: uts.sdk.modules.DcloudUniGetBackgroundLocation uses a module listed above it, which is the healthy direction.
uts.sdk.modules.uniCamera uses uts.sdk.modules.uniCamera.CameraManager, so a change to uts.sdk.modules.uniCamera.CameraManager can break uts.sdk.modules.uniCamera, while a change to uts.sdk.modules.uniCamera can't break uts.sdk.modules.uniCamera.CameraManager.
Position
Below the diagonal: uts.sdk.modules.uniCamera uses a module listed above it, which is the healthy direction.
uts.sdk.modules.uniMapAmap uses uts.sdk.modules.uniMapAmap.marker, so a change to uts.sdk.modules.uniMapAmap.marker can break uts.sdk.modules.uniMapAmap, while a change to uts.sdk.modules.uniMapAmap can't break uts.sdk.modules.uniMapAmap.marker.
Position
Below the diagonal: uts.sdk.modules.uniMapAmap uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 36% · Weak · gated by R1, R10 ·
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A03:2025 — Software Supply Chain Failures
177
High / Critical
A05:2025 — Injection
8
Medium
A07:2025 — Authentication Failures
2
High / Critical
Roadmap
Top priorities: Replace the synchronous wait with `async`/`await` so the handler never blocks on a peer/resource; Resolve the 8 finding(s) in Immutable events; Resolve the 2 Leaked secret finding(s) in Secret Scanning — start with REDACTED, REDACTED.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Replace the synchronous wait with `async`/`await` so the handler never blocks on a peer/resource.
Resolve the 3 Assertions commented out finding(s) in Test Quality — start with mixin-datacom.test.js, create-inner-audio-context.test.js, clipboard.test.js.
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.
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
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 — 149
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 — 617
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 — 252
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 24
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 55 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
Every figure here is one of two kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10.
What we checked — 55 dimensions across the health lenses
Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.
How to trust any code-health report — three questions
Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 1005 of 1018 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D4 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. The 102 duplicated block group(s) on this row were found in the languages this pass could tokenize, and they do NOT cover all of this repository's production source: .cpp (18,985 lines, 27% of production source) went unread, because no language model this pass could load exposed a clone-unit token stream for those file kinds. Duplication in that source is UNMEASURED — its absence from the count above is a gap in this analyzer's language coverage, not a finding that the code is free of duplication.
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 src/code-review/ 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 1,318 test(s) behind this row are the ones the JavaScript/TypeScript census could read, and this repository also carries at least 1 test source file(s) (.swift) 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 examples/hello-uvue/code-review/ failed in the analyzer sandbox ((node:658) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 socket listeners added to [ClientRequest]. MaxListeners is 10. Use emitte…), 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 jest suite in examples/hello-uvue/code-review/ was NOT MEASURED: the dependency install for examples/hello-uvue/code-review/ failed in the analyzer sandbox ((node:658) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 socket listeners added to [ClientRequest]. MaxListeners is 10. Use emitte…), 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.
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 jest suite in src/code-review/ was NOT MEASURED: the dependency install for src/code-review/ 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.
D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. All 75 significant source file(s) were last meaningfully changed so long ago that no living knowledge remains — nothing since has been substantial enough to re-establish ownership (a broad, mechanical sweep that touches many files shallowly does not count, and neither does no activity at all). There is no concentration to measure, so the bus factor is not scored. This is not a clean bill: nobody currently holds working knowledge of this code (see D34 Knowledge Freshness). Counted over 75 of the 98 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's 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 — 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. 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's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
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 — 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. Project size and spread are measured over build units whose source a code model reads. This repository's .cpp source is a material share of its production lines and was read by none, so the score is a verdict about the units that were read. Not a finding that the unread source is cohesive — it is unmeasured.
D27 Navigability — 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. Tracing effort is measured over resolved call sites, and all 489 sampled here came from .swift files. This repository's .cpp source is a material share of its production lines and contributed none, so the score above is a verdict about the part that was read. Not a finding that the unread half navigates well — it is unmeasured.
D28 Secrets (history) — 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. `gitleaks` TIMED OUT after 297.4s against a 297.4s budget, so we killed its process tree. The budget is ours; the work may simply be larger than it allows. Nothing about this repository is asserted by the absence of a result; the budget is ours to raise, and raising it is our backlog item, not an action for this repository's owner.
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. `src/uni_modules/uni-event/utssdk/app-ios/native.swift`, `src/uni_modules/uni-upgrade-center-app/utils/check-update.ts` 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.
D34 Knowledge Freshness — 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. File-level freshness contradicts repo activity: 538 commits in the last 90 days, yet 75 of 75 significant files carry no living knowledge. Those two readings cannot both be true, so the per-file recency signal is treated as unreliable here and freshness is not scored for this run.
D44 Platform End-of-Life — 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 dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a Dockerfile) is simply not read here yet.
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 DevServer (start). the dev server (`npm run start`) exited before it served a page. Likely cause (the repository): package.json has no "start" script, so `npm run start` could not start the app. Last output: "npm error Missing script: "start" / npm error / npm error Did you mean one of these? / npm error npm star # Mark your favorite packages / npm error npm stars # View packages marked as favorites / npm error / npm error To see a list of scripts, run: / npm error npm run / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
C4 Data Retention — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
C5 Data-Subject Rights — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and this repository's Java, Kotlin, Swift, Vue components, c, cpp is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and this repository's Kotlin, Swift, Vue components, c, cpp 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.
P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
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. 43 further occurrence(s) are not listed individually; the score already reflects all 83.
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. 9 further occurrence(s) are not listed individually; the score already reflects all 49.
S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security 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 web-security controls.
X1 Async correctness — 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.
X12 Unreachable branch — 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.
X16 Unfloored truncation loop — 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.
X18 Disposal-pattern correctness — 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.
X2 Cancellation propagation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check'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.
X21 Side-effecting pattern guard — 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.
X26 Unsynchronised callback handoff — 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 — 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.
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. 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.
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.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
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.
AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
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.
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.
What it measures: How tangled the control flow is — methods with many branches are hard to test and change.
Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.
35 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was service.createOrder at 56. A further 2 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being UniFileSystemManagerError.errorCode at 27 — they are counted neither in the figure above nor in this dimension's score.
+ 24 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 4 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with service.createOrder (cyclomatic 56), AudioRecorder.startRecording (cyclomatic 42), CameraManager._setupOutputMode (cyclomatic 31). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 4 together lifts Cyclomatic Complexity from 6.6 to about 7.3/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
+ 69 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 2 bodies over 60 down to 60 or less in Cognitive Complexity — start with service.createOrder (cognitive 84), Scanner._processScanBarCode (cognitive 71). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cognitive Complexity from 5.3 to about 5.8/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes8.2 / 10Strong✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 14 FileTooLong finding(s) in God Classes — start with UniFileSystemManager.swift, CameraManager.swift, InnerWebView.swift. — One of this dimension's main actionable groups (14 warning-level).
Resolve the 14 TooManyMethods finding(s) in God Classes — start with CameraManager.swift, BackgroundAudioPlayer.kt, InnerWebView.swift. — One of this dimension's main actionable groups (14 warning-level).
Resolve the 9 ClassTooLong finding(s) in God Classes — start with CameraManager.swift, pay.js, amap.js. — One of this dimension's main actionable groups (9 warning-level).
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How much of the production code is copy-pasted: the share of production lines inside a reported copy (every copy of a duplicated block or of an edited member, each line once), 10 at none and 0 at a quarter of the lines.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), scored on the share of production lines inside a reported copy (each line once; 10 at none, 0 at a quarter). Deterministic.
102 duplicated block group(s) detected. 9.7 % of the production lines (5,071 of 52,091) are in a reported copy. A further 102 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 96 of the 204 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population. Measured on part of this repository only: .cpp (27% of production source) was not exposed to the token comparison, so duplication there is unmeasured and is not in this count.
+ 85 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 12 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with ColorEffectValue.swift (3), DCAlertView.Blocks.swift (2), ShapeLayerModel.swift (2). — One of this dimension's main actionable groups (12 warning-level).
Resolve the 9 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with UniAudioPlayer.swift (2), DCAlertControllerUtil.swift, UniStoreKit.swift. — One of this dimension's main actionable groups (9 warning-level).
Resolve the 9 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with UniAudioPlayer.swift (3), UniInputView.swift, MCToast+Loading.swift. — One of this dimension's main actionable groups (9 warning-level).
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
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.
137 production modules (npm+uni_modules), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations, and main-sequence distance (abstractness) is not computed for these modules yet.
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.
Resolve the 22 Low cohesion finding(s) in Cohesion (LCOM4) — start with Interpolatable.swift (3), InnerWebView.swift, CoreAnimationLayer.swift. — One of this dimension's main actionable groups (22 warning-level).
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D10 · Test Quality9.9 / 10Adequategated by 3 critical findings✓ Tool-verified
What it measures: Whether the tests truly assert behaviour rather than just running the code.
Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.
96 skipped (95 with a documented reason), 8 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 1318 tests. Measured on the JavaScript/TypeScript suite only — at least 1 test source file(s) (.swift) went unread, so its test quality is unmeasured and is not in these counts.
Resolve the 3 Assertions commented out finding(s) in Test Quality — start with mixin-datacom.test.js, create-inner-audio-context.test.js, clipboard.test.js. — One of this dimension's main actionable groups (3 issue-level).
Resolve the 5 No assertions finding(s) in Test Quality — start with editor.test.js (2), web-view.test.js, swiper.test.js. — One of this dimension's main actionable groups (5 warning-level).
Resolve the 1 Skipped test finding(s) in Test Quality — start with wrap-picker-view.test.js. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d10_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
5 outdated direct production npm dependency(ies) of 5 graded, 0 pinning defect(s), across 6 package.json (5 of them the product) and 3 committed lockfile(s). Development dependencies are deliberately not graded for currency: that grade is about what SHIPS. 0 direct dependency(ies) — production, development or optional — are marked DEPRECATED by their publisher (the registry's per-version mark, or the lockfile's copy of it when the registry could not be asked); deprecated transitive packages are listed but not charged. Whether any is UNMAINTAINED is not graded — the registry publishes no maintenance status, and release age does not stand in for one. Whether any is UNUSED is not graded either: that is a source question, and the frontend dependency lens (R8) answers it in this same run. Known CVEs in this dependency graph are D30's question, read from the manifest there.
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.
Resolve the 2 Leaked secret finding(s) in Secret Scanning — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
Detailed fixes: d13_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
0 of 41 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 41 package(s) this repository's committed lockfile installs for a consumer — its 5 production, optional and peer dependency(ies), across 5 product package.json manifest(s), and everything those install in turn. Its 2 `devDependencies` declaration(s), and every package only they reach, are excluded: a consumer installs none of them. ★ Each licence is the one the registry publishes for the package's CURRENT release rather than for the pinned version, which is the same caveat the Hex and RubyGems arms carry. This repository publishes itself under Apache-2.0 / ISC / MIT, which is its own choice and is not judged here.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
7 deducted task-comment markers across 52091 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
Resolve the 7 TodoComment finding(s) in Explicit Debt — start with UniAudioRecorderManager.swift, native.swift, Interpolatable.swift. — One of this dimension's main actionable groups (7 warning-level).
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.
0 of 1 documentation facets pass in full; short on: F2 example. 715 document(s) read across 18 unit(s).
Documentation: no build, run or usage examplesrc/readme.md:1
What to do
Resolve the 1 Documentation finding(s) in Documentation Quality — start with readme.md. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d19_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
Resolve the 7 redundant comment finding(s) in Comment Value — start with get-current-pages.test.js (2), set-page-style-disable-pull-down-refresh.test.js, get-file-system-manager.test.js. — One of this dimension's main actionable groups (7 recommendation-level).
Detailed fixes: d24_recommendation.md · top locations in Appendix A, every location in findings.md.
0 of 49 build units (npm) flagged as possibly oversized/incoherent. This repository's .cpp source was read by no build unit, so this covers part of the tree, not all of it.
What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.
Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.
Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.
0 % of calls cross a namespace and 3 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated. Measured over the .swift source only — this repository's .cpp was not sampled for call sites, so this score covers part of the tree, not all of it.
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).
8 finding(s): 0 critical, 0 high, 8 medium, 0 low. semgrep hit a parse error in 8 file(s) — `src/pages/template/long-rich-text/long-rich-text.uvue`, `src/uni_modules/uni-animation-view/utssdk/app-ios/Frameworks/Lottie.xcframework/ios-arm64/Lottie.framework/Headers/Lottie-Swift.h`, `src/uni_modules/uni-animation-view/utssdk/app-ios/Frameworks/Lottie.xcframework/ios-arm64_x86_64-simulator/Lottie.framework/Headers/Lottie-Swift.h`, `src/uni_modules/uni-pay-x/uniCloud/cloudfunctions/common/uni-pay/index.js`, `src/uni_modules/uni-pay-x/uniCloud/cloudfunctions/uni-pay-co/libs/certutil.js`, … (+3 more) — so no absence of findings in them is evidence of anything, and nothing in them was analysed. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
REDACTED
REDACTED
REDACTED
What to do
Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4). — One of this dimension's main actionable groups (4 warning-level).
Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
+ 1 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 89 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (73), REDACTED (16). — One of this dimension's main actionable groups (89 issue-level).
Resolve the 23 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (21), REDACTED (2). — One of this dimension's main actionable groups (23 issue-level).
Resolve the 1 Critical vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Reported apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
No dependency in any ecosystem this repository declares is published as malicious.
✓ On the Gold path — maintain.
Detailed fixes: d43_recommendation.md.
Do you agree with this assessment?
Frontend & cross-cutting dimensions
R = React/JS · M = Maturity · P = Readiness.
AC1 · Text alternatives1.0 / 10Critical✓ Tool-verified
Other · Accessibility — Whether non-text content carries a text alternative — img/area/input[type=image] have alt, a meaningful svg has a title or aria-label, video has a captions track, and object/embed/canvas have a name or fallback content. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: every img/area/input[type=image] checked for alt, svg[role=img] for a title/aria-label, video for a captions <track>. Components skipped, spreads suppressed. Deterministic, hard fact per element.
Coverage: Population: image/media elements — img, area, input[type=image], svg, video, object, embed, canvas — across the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and dynamic-attribute elements are skipped. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is NOT read by any producer, so it contributes no element to this population; where such a frontend is present the card discloses it as an analyzer gap rather than scoring around it.
Video with no captions <track> offers no captions. Add a <track kind="captions"> pointing at a WebVTT file for this video (or confirm captions are provided another way). (×2) — src/hybrid/html/local.html:47, src/hybrid/html/local.html:49
An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative. (×3) — src/uni_modules/uni-upgrade-center-app/pages/upgrade-popup.vue:6, src/uni_modules/uni-upgrade-center-app/pages/upgrade-popup.vue:69, src/wxcomponents/vant/icon/index.vue:4
What to do
Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
Do you agree with this assessment?
AC2 · Forms & labels5.2 / 10Adequate✓ Tool-verified
Other · Accessibility — Whether form controls have a programmatic label (an associated label, aria-label or aria-labelledby), buttons have text, links have an accessible name, a click handler on a plain element names the control it declares, fieldsets have a non-empty legend, known UI-library field components carry a label prop, and a placeholder isn't used as the only label. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: inputs/selects/textareas checked for an associated label[for]/wrapping label/aria-label/aria-labelledby (per document), buttons for accessible text, fieldsets for a legend; placeholder-only labelling flagged. Deterministic, hard fact per control.
Coverage: Population: form controls, buttons, links, fieldsets and known UI-library field components in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and spread/dynamic-attribute elements are skipped, so a control whose label arrives through a spread or a runtime expression is deliberately not judged. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×2) — src/hybrid/html/local.html:59, src/hybrid/html/local.html:61
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. (×4) — src/hybrid/html/local.html:63, src/hybrid/html/local.html:65, src/hybrid/html/local.html:67, …
What to do
Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
Do you agree with this assessment?
AC3 · Page structure3.2 / 10Weak✓ Tool-verified
Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.
Coverage: Population: the PARSED MARKUP documents (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx). The page-level checks — lang, title, single main landmark — fire ONCE PER FULL DOCUMENT (an <html> root) and never on a partial or component fragment, so a repo of fragments is assessed only on the per-element checks (heading order, table headers, iframe titles, meta-refresh, zoom). Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). (×3) — src/hybrid/html/local.html:2, src/hybrid/html/privacy.html:2, src/hybrid/html/simple.html:2
No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. (×3) — src/hybrid/html/local.html:2, src/hybrid/html/privacy.html:2, src/hybrid/html/simple.html:2
An iframe with no title (or an empty one) is announced only as "frame". Add a non-empty title describing its content, or an aria-label. — src/hybrid/html/local.html:74
user-scalable=no/0 or a maximum-scale below 2 stops low-vision users zooming to 200%. Remove the zoom restriction from the viewport meta. — src/hybrid/html/privacy.html:6
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. — src/index.html:2
An empty <title> gives no page name in the tab, history or screen-reader page list. Put descriptive text in the <title>. — src/uni_modules/uni-editor/static/editor.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="editor">, so there is no content here to wrap — render the <main> from the component mounted into it. — src/uni_modules/uni-editor/static/editor.html:2
What to do
Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
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. (×3) — src/components/u-link/u-link.vue:3, src/uni_modules/uni-icons/components/uni-icons/uni-icons.vue:3, src/uni_modules/uni-icons/components/uni-icons/uni-icons.vue:6
What to do
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
Other · Accessibility — Whether ARIA is used correctly — valid non-abstract roles, the ARIA state a role requires, valid (non-misspelled) aria-* attribute names, in-enum values for token-typed aria-* attributes, and no aria-hidden on (or wrapping) a focusable element. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: role values checked against the WAI-ARIA role set (abstract/invalid flagged), required ARIA state for a role, and aria-hidden on a focusable element. Deterministic, role/attribute level.
Coverage: Population: elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) that carry a role or an aria-* attribute; roles and token values are checked against the ARIA enums exhaustively within that set. An expression-valued (dynamic) role or aria-* value is skipped rather than guessed, and markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
Other · Accessibility — Whether focus outlines aren't removed without a replacement, motion respects prefers-reduced-motion, and literal CSS colour pairs meet contrast — PARTIAL: inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS literals are read (hex/rgb/hsl/named), never computed/runtime/external-CDN colour. Static markup readiness, not a WCAG conformance claim.
Method: Static markup/CSS scan: inline outline:none/0, literal inline colour/background contrast against the 4.5:1 AA floor, and <style>-block animation without a prefers-reduced-motion guard. Deterministic but PARTIAL — only inline styles and in-repo CSS literals are visible.
Coverage: Population: styled elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx), plus in-repo <style> blocks, in-repo .css files and CSS-in-JS literals. Colour contrast is computed from LITERAL colour pairs only (hex/rgb/hsl/named, including var() tokens and Tailwind neutral utilities) — computed, runtime-themed and external-CDN colour is never resolved, so this is a partial read of contrast by construction. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
`.btn` sets color: #ffffff on background-color: #007aff — 4.0:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — src/hybrid/html/local.html:9
`.van-info` sets color: #fff on background-color: #ee0a24 — 4.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — src/wxcomponents/vant/info/index.vue:19
`.content-body-version` sets color: #fff on background-color: #50aefd — 2.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — src/uni_modules/uni-upgrade-center-app/pages/upgrade-popup.vue:610
`.ql-container .ql-image-overlay .ql-image-size` sets color: #888 on background-color: #fff — 3.5:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — src/uni_modules/uni-editor/static/editor.css:60
`.ql-container` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/uni_modules/uni-editor/static/editor.css:15
`.ql-editor` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/uni_modules/uni-editor/static/editor.css:136
`.van-loading__spinner` moves (`animation: van-rotate .8s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — src/wxcomponents/vant/loading/index.vue:50
`.van-loading__spinner` moves (`animation: van-rotate var(--loading-spinner-animation-duration,.8s) linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — src/wxcomponents/vant/loading/index.vue:50
`.down_arrow` moves (`transition-property: transform`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. (×2) — src/components/uni-collapse-item/uni-collapse-item.vue:122, examples/hello-uvue/components/uni-collapse-item/uni-collapse-item.vue:93
`.uni-collapse-item__content-box` moves (`transition-property: transform, opacity`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — src/components/uni-collapse-item/uni-collapse-item.vue:159
What to do
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
Do you agree with this assessment?
AX8 · Test isolation5.0 / 10Adequate✓ Tool-verified
Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.
Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.
`Hello uni-app x` (production) references the test project `test-image-path`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
`Hello uni-app x` (production) references the test project `test-invoke-network-api`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
What to do
Remove every production → test project reference: extract any shared test helper into a production support library (which the tests reference), or invert the dependency so the test project depends on production — not the reverse.
Other · Architecture — Whether read (query) handlers stay side-effect-free — a query that writes persistent state or raises events breaks CQS and makes reads unsafe to retry, cache, or route to a read replica.
Method: Roslyn scan: CQRS handlers classified query-vs-command by interface (IQueryHandler/ICommandHandler/IRequestHandler<TQuery,TResult>) and name convention (*Query/Get*/Find* vs *Command); each query handler's body checked for persistent-state writes (SaveChanges/repository Add-Update) or event publishes by resolved invocation. Deterministic, type-level, exhaustive over the detected handlers.
Coverage: Population: CQRS handlers identified by IQueryHandler/ICommandHandler/IRequestHandler interface + *Query/Get*/Find*/*Command NAME convention; query purity then checked exhaustively within that set — a query handler using neither convention is invisible, and mutation is a resolved persistence/publish CALL, not full dataflow.
Other · Event-Driven — Whether event/message handlers avoid synchronous blocking waits — a blocking wait inside a handler stalls throughput and risks deadlock.
Method: Roslyn semantic scan (event-driven gated): event-handler bodies scanned for HTTP/gRPC invocations by resolved symbol type, not substring. Deterministic, semantic-resolved.
`DRMManager.handleContentKeyRequest` is an event/message handler that blocks on a synchronous wait (a semaphore/queue `.wait`/`.sync`) — it stalls the handler on a peer or resource and serialises throughput, and can deadlock under load. Await the work asynchronously (`async`/`await`) instead of blocking the handler. — src/uni_modules/uni-video/utssdk/app-ios/VideoPlayer/Managers/DRMManager.swift:58
What to do
Replace the synchronous wait with `async`/`await` so the handler never blocks on a peer/resource.
Other · Event Sourcing — Whether domain events stay immutable (a `struct` with `let` fields) rather than carrying mutable state.
Method: Roslyn scan (event-sourcing gated): persisted events checked for public setters; immutability verified per property/field. Deterministic, hard fact.
`InnerWebViewLoadingEvent` conforms to a domain-event contract but carries mutable state (a `class` event, or a `struct` event with a mutable `var`). Events are immutable facts — model them as a `struct` with `let` fields so a recorded event can never be rewritten. — src/uni_modules/uni-web-view/utssdk/app-ios/InnerWebView.swift:53
`InnerWebViewLoadedEvent` conforms to a domain-event contract but carries mutable state (a `class` event, or a `struct` event with a mutable `var`). Events are immutable facts — model them as a `struct` with `let` fields so a recorded event can never be rewritten. — src/uni_modules/uni-web-view/utssdk/app-ios/InnerWebView.swift:83
`InnerWebViewLoadEvent` conforms to a domain-event contract but carries mutable state (a `class` event, or a `struct` event with a mutable `var`). Events are immutable facts — model them as a `struct` with `let` fields so a recorded event can never be rewritten. — src/uni_modules/uni-web-view/utssdk/app-ios/InnerWebView.swift:120
`InnerWebViewMessageEvent` conforms to a domain-event contract but carries mutable state (a `class` event, or a `struct` event with a mutable `var`). Events are immutable facts — model them as a `struct` with `let` fields so a recorded event can never be rewritten. — src/uni_modules/uni-web-view/utssdk/app-ios/InnerWebView.swift:156
`InnerWebViewServiceMessageEvent` conforms to a domain-event contract but carries mutable state (a `class` event, or a `struct` event with a mutable `var`). Events are immutable facts — model them as a `struct` with `let` fields so a recorded event can never be rewritten. — src/uni_modules/uni-web-view/utssdk/app-ios/InnerWebView.swift:183
`InnerWebViewDownloadEvent` conforms to a domain-event contract but carries mutable state (a `class` event, or a `struct` event with a mutable `var`). Events are immutable facts — model them as a `struct` with `let` fields so a recorded event can never be rewritten. — src/uni_modules/uni-web-view/utssdk/app-ios/InnerWebView.swift:214
`InnerWebViewErrorEvent` conforms to a domain-event contract but carries mutable state (a `class` event, or a `struct` event with a mutable `var`). Events are immutable facts — model them as a `struct` with `let` fields so a recorded event can never be rewritten. — src/uni_modules/uni-web-view/utssdk/app-ios/InnerWebView.swift:260
`InnerWebViewContentHeightChangeEvent` conforms to a domain-event contract but carries mutable state (a `class` event, or a `struct` event with a mutable `var`). Events are immutable facts — model them as a `struct` with `let` fields so a recorded event can never be rewritten. — src/uni_modules/uni-web-view/utssdk/app-ios/InnerWebView.swift:366
Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
The root README is 119 words, against a bar of 120. Of the three newcomer-critical sections this check looks for by heading, in the README and in the repository documents it links, it found no a testing section, no an architecture or project-map section. Sections are matched on HEADING text only, so material written under a heading this check does not recognise — or with no heading at all — is not seen and this row may understate what the document covers. — README.md:1
What to do
Expand the README with getting-started, architecture overview and a project map.
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.
Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.
Do you agree with this assessment?
P1 · CI/CD gates5.0 / 10Adequate✓ Tool-verified
Readiness · Readiness — Whether an automated pipeline builds and tests every change.
Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.
A CI pipeline exists but no test-runner invocation (your stack's test command, or a test job) was found — changes may merge without the suite running.
A CI pipeline exists but no build step was matched — changes may merge without the build ever running. A build step may be invoked directly as a command, or declared as a task that a runner named in the pipeline resolves.
What to do
Run the test suite in CI via an explicit runner step (`npm test` for the toolchain this pipeline already uses) and gate merges on it.
Add an explicit build step to your CI pipeline — your stack's own build command, or, if the pipeline delegates to a task runner, a build task that runner executes in CI — so every change is built before merge.
Do you agree with this assessment?
P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged
Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.
Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language's code model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.
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 CodeQL's Swift pack (Swift/Xcode) (or `semgrep --config=auto`, which runs on any language) — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
`examples/hello-uts/package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — examples/hello-uts/package.json:14
What to do
Run what this repository's stack ships: CodeQL's Swift pack (Swift/Xcode) — or `semgrep --config=auto`, which runs on any language — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · 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.
`readdirSync` in `parseDescribes` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — examples/hello-uts/jest.global.js:35
`readFileSync` in `callback to forEach` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — examples/hello-uts/jest.global.js:37
`fs.readFileSync` in `verifyReceipt` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — src/uni_modules/uni-pay-x/uniCloud/cloudfunctions/uni-pay-co/service/pay.js:912
What to do
TypeScript/JavaScript: use the promise APIs (fs/promises, a promisified child_process.execFile, the async zlib/crypto functions) and await them instead of the *Sync variants.
Do you agree with this assessment?
R1 · Type Safety0.1 / 10Critical✓ Tool-verified
React / JS · Code Health — How much of the frontend is typed TypeScript vs untyped JavaScript.
Method: Frontend file inventory: the share of typed TypeScript vs untyped JavaScript across the source tree. Deterministic, exhaustive over frontend files.
4 typed · 325 plain JS — the untyped files are src/code-review/__tests__/index.test.js, src/code-review/__tests__/setup.js, REDACTED, src/components/api-set-tabbar/api-set-tabbar.vue, src/components/u-link/u-link.vue, src/components/uni-collapse-item/uni-collapse-item.vue (+319 more).
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.
src/uni_modules/uni-payment-alipay/utssdk/app-ios/Frameworks/AlipaySDK.xcframework/ios-arm64/AlipaySDK.framework/ and src/uni_modules/uni-payment-alipay/utssdk/app-ios/Frameworks/AlipaySDK.xcframework/ios-arm64_x86_64-simulator/AlipaySDK.framework/ are near-verbatim copies of each other: 8 files are byte-identical under the same relative paths (~450 lines; the trees hold 8 and 9 files). That is one structural fact, not 8 local ones: every edit made to one tree and not the other drifts silently, which is the failure whole-tree forks guarantee. Pick one tree as the single source and produce the other from it (generated, copied at build or release time, or re-exported) — or, if the copy is a stale snapshot nothing produces any more, delete it. Check first whether the copy is a deliberately published deliverable (a template consumers copy verbatim, a released sample frozen at a version); where it is, keep it produced from the source tree rather than edited in place. — src/uni_modules/uni-payment-alipay/utssdk/app-ios/Frameworks/AlipaySDK.xcframework/ios-arm64/AlipaySDK.framework/Headers/AlipaySDK.h:1
src/uni_modules/uni-icons/components/uni-icons/uniicons_file.ts:17 · src/uni_modules/uni-icons/components/uni-icons/uniicons_file_vue.js:2 — these 2 files are line-for-line copies of one another — 323 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — src/uni_modules/uni-icons/components/uni-icons/uniicons_file.ts:17
src/uni_modules/uni-canvas-dom2/utssdk/app-harmony/canvas.color.js:2 · src/uni_modules/uni-canvas/customElements/uni-canvas/uni-canvas.js:2 — these 2 files are line-for-line copies of one another — 156 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — src/uni_modules/uni-canvas-dom2/utssdk/app-harmony/canvas.color.js:2
src/wxcomponents/vant/button/index.js:4 · src/wxcomponents/vant/button/index.vue:27 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — src/wxcomponents/vant/button/index.js:4
src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/amap.js:554 · src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/amap.js:609 · src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/amap.js:664 — all 3 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. — src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/amap.js:554
src/jest-setup.js:45 · src/jest-setup.js:90 — the two spans are one implementation copied and then locally edited — 170 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. — src/jest-setup.js:45
src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/qqmap.js:550 · src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/qqmap.js:604 · src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/qqmap.js:657 — all 3 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. — src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/qqmap.js:550
src/wxcomponents/vant/icon/index.js:3 · src/wxcomponents/vant/icon/index.vue:15 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — src/wxcomponents/vant/icon/index.js:3
src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/amap.js:60 · src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/qqmap.js:16 — 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. — src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/amap.js:60
src/uni_modules/uni-animation-view/utssdk/app-android/index.vue:36 · src/uni_modules/uni-animation-view/utssdk/app-ios/index.vue:25 — 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. — src/uni_modules/uni-animation-view/utssdk/app-android/index.vue:36
src/wxcomponents/vant/loading/index.js:3 · src/wxcomponents/vant/loading/index.vue:17 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — src/wxcomponents/vant/loading/index.js:3
src/uni_modules/uni-pay-x/uniCloud/cloudfunctions/uni-pay-co/libs/wxpay.js:44 · src/uni_modules/uni-pay-x/uniCloud/cloudfunctions/uni-pay-co/libs/wxpay.js:78 — 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. — src/uni_modules/uni-pay-x/uniCloud/cloudfunctions/uni-pay-co/libs/wxpay.js:44
src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/amap.js:345 · src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/qqmap.js:310 — 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. — src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/amap.js:345
src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/qqmap.js:600 · src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/qqmap.js:653 · src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/qqmap.js:706 — all 3 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/qqmap.js:600
src/uni_modules/uni-editor/static/editor.js:1110 · src/uni_modules/uni-editor/static/editor.js:1137 — 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. — src/uni_modules/uni-editor/static/editor.js:1110
src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/amap.js:225 · src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/qqmap.js:164 — 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. — src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/amap.js:225
src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/amap.js:272 · src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/qqmap.js:200 — 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. — src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/amap.js:272
src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/amap.js:190 · src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/qqmap.js:129 — 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. — src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/amap.js:190
src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/qqmap.js:270 · src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/qqmap.js:352 — 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. — src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/qqmap.js:270
src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/amap.js:649 · src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/amap.js:704 — all 2 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/amap.js:649
src/uni_modules/uni-editor/static/editor.js:744 · src/uni_modules/uni-editor/static/editor.js:767 · src/uni_modules/uni-editor/static/editor.js:790 · src/uni_modules/uni-editor/static/editor.js:813 · +4 more site(s) not listed — all 8 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. — src/uni_modules/uni-editor/static/editor.js:744
src/uni_modules/uni-editor/static/editor.js:908 · src/uni_modules/uni-editor/static/editor.js:930 · src/uni_modules/uni-editor/static/editor.js:952 · src/uni_modules/uni-editor/static/editor.js:974 · +3 more site(s) not listed — all 7 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. — src/uni_modules/uni-editor/static/editor.js:908
src/uni_modules/uni-map-common/uniCloud/cloudfunctions/uni-map-co/index.obj.js:202 · src/uni_modules/uni-map-common/uniCloud/cloudfunctions/uni-map-co/index.obj.js:252 — 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. — src/uni_modules/uni-map-common/uniCloud/cloudfunctions/uni-map-co/index.obj.js:202
src/uni_modules/uni-editor/static/editor.js:861 · src/uni_modules/uni-editor/static/editor.js:1022 — 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. — src/uni_modules/uni-editor/static/editor.js:861
src/uni_modules/uni-map-common/uniCloud/cloudfunctions/uni-map-co/index.obj.js:106 · src/uni_modules/uni-map-common/uniCloud/cloudfunctions/uni-map-co/index.obj.js:129 · src/uni_modules/uni-map-common/uniCloud/cloudfunctions/uni-map-co/index.obj.js:149 · src/uni_modules/uni-map-common/uniCloud/cloudfunctions/uni-map-co/index.obj.js:170 — all 4 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. — src/uni_modules/uni-map-common/uniCloud/cloudfunctions/uni-map-co/index.obj.js:106
src/components/api-set-tabbar/api-set-tabbar.vue:74 · src/components/api-set-tabbar/api-set-tabbar.vue:104 — 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. — src/components/api-set-tabbar/api-set-tabbar.vue:74
src/uni_modules/uni-editor/static/editor.js:438 · src/uni_modules/uni-editor/static/editor.js:457 — 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. — src/uni_modules/uni-editor/static/editor.js:438
src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/amap.js:320 · src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/qqmap.js:261 — 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. — src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/amap.js:320
src/uni_modules/uni-pay-x/uniCloud/cloudfunctions/uni-pay-co/dao/uniIdUsers.js:3 · src/uni_modules/uni-pay-x/uniCloud/cloudfunctions/uni-pay-co/dao/uniPayOrders.js:3 — 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. — src/uni_modules/uni-pay-x/uniCloud/cloudfunctions/uni-pay-co/dao/uniIdUsers.js:3
src/uni_modules/uni-pay-x/uniCloud/cloudfunctions/uni-pay-co/index.obj.js:128 · src/uni_modules/uni-pay-x/uniCloud/cloudfunctions/uni-pay-co/index.obj.js:282 — 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. — src/uni_modules/uni-pay-x/uniCloud/cloudfunctions/uni-pay-co/index.obj.js:128
src/uni_modules/uni-pay-x/uniCloud/cloudfunctions/uni-pay-co/service/pay.js:676 · src/uni_modules/uni-pay-x/uniCloud/cloudfunctions/uni-pay-co/service/pay.js:742 — 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. — src/uni_modules/uni-pay-x/uniCloud/cloudfunctions/uni-pay-co/service/pay.js:676
src/uni_modules/uni-editor/static/quill/formats.js:223 · src/uni_modules/uni-editor/static/quill/formats.js:243 — 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. — src/uni_modules/uni-editor/static/quill/formats.js:223
src/uni_modules/uni-pay-x/uniCloud/cloudfunctions/uni-pay-co/service/pay.js:574 · src/uni_modules/uni-pay-x/uniCloud/cloudfunctions/uni-pay-co/service/pay.js:685 · src/uni_modules/uni-pay-x/uniCloud/cloudfunctions/uni-pay-co/service/pay.js:754 — all 3 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. — src/uni_modules/uni-pay-x/uniCloud/cloudfunctions/uni-pay-co/service/pay.js:574
src/uni_modules/uni-config-center/uniCloud/cloudfunctions/common/uni-config-center/uni-pay/config.js:16 · src/uni_modules/uni-config-center/uniCloud/cloudfunctions/common/uni-config-center/uni-pay/config.js:28 · src/uni_modules/uni-config-center/uniCloud/cloudfunctions/common/uni-config-center/uni-pay/config.js:40 · src/uni_modules/uni-config-center/uniCloud/cloudfunctions/common/uni-config-center/uni-pay/config.js:52 · +1 more site(s) not listed — all 5 copies are in the same file, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — src/uni_modules/uni-config-center/uniCloud/cloudfunctions/common/uni-config-center/uni-pay/config.js:16
src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/amap.js:133 · src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/qqmap.js:105 — 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. — src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/amap.js:133
src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/amap.js:518 · src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/qqmap.js:581 · src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/qqmap.js:635 · src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/qqmap.js:688 — the 4 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. — src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/amap.js:518
src/uni_modules/uni-map-common/uniCloud/cloudfunctions/uni-map-co/index.obj.js:301 · src/uni_modules/uni-map-common/uniCloud/cloudfunctions/uni-map-co/index.obj.js:377 — 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. — src/uni_modules/uni-map-common/uniCloud/cloudfunctions/uni-map-co/index.obj.js:301
src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/amap.js:502 · src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/amap.js:757 — all 2 copies are in the same file, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/amap.js:502
src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/qqmap.js:517 · src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/qqmap.js:586 · src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/qqmap.js:693 — all 3 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. — src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/qqmap.js:517
src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/amap.js:846 · src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/amap.js:854 — all 2 copies are in the same file, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/amap.js:846
What to do
Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
React / JS · 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.
createOrder has cyclomatic complexity 56 and cognitive complexity 84; 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. — src/uni_modules/uni-pay-x/uniCloud/cloudfunctions/uni-pay-co/service/pay.js:174
format has cyclomatic complexity 23 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. — src/uni_modules/uni-editor/static/editor.js:330
_getSign 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. — src/uni_modules/uni-pay-x/uniCloud/cloudfunctions/uni-pay-co/libs/alipay.js:63
verifyReceiptFromAppleiap has cyclomatic complexity 20 and cognitive complexity 29; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/uni_modules/uni-pay-x/uniCloud/cloudfunctions/uni-pay-co/service/pay.js:874
getOrder has cyclomatic complexity 19 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. — src/uni_modules/uni-pay-x/uniCloud/cloudfunctions/uni-pay-co/service/pay.js:463
(anonymous) has cyclomatic complexity 18 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/pages/API/request/request.test.js:20
refund has cyclomatic complexity 16 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. — src/uni_modules/uni-pay-x/uniCloud/cloudfunctions/uni-pay-co/service/pay.js:565
(anonymous) has cyclomatic complexity 15 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. — src/pages/API/action-sheet/action-sheet.test.js:34
processReview has cyclomatic complexity 13 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. — REDACTED:301
parseHTML has cyclomatic complexity 13 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. — src/uni_modules/uni-editor/static/editor.js:33
(anonymous) 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. — src/pages/API/dialog-page/dialog-page.test.js:15
(anonymous) 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. — src/pages/component/video/video.test.js:13
getProviderPayType has cyclomatic complexity 12 and cognitive complexity 9; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/uni_modules/uni-pay-x/uniCloud/cloudfunctions/uni-pay-co/libs/common.js:106
paymentNotify has cyclomatic complexity 11 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. — src/uni_modules/uni-pay-x/uniCloud/cloudfunctions/uni-pay-co/service/pay.js:39
location2address has cyclomatic complexity 11 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/qqmap.js:59
timeFormat has cyclomatic complexity 11 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/uni_modules/uni-pay-x/uniCloud/cloudfunctions/uni-pay-co/libs/common.js:8
(anonymous) has cyclomatic complexity 11 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/uni_modules/uni-upgrade-center-app/utils/call-check-version.ts:34
Do you agree with this assessment?
R3 · Large Files6.0 / 10Adequate✓ 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.
src/uni_modules/uni-pay-x/uniCloud/cloudfunctions/uni-pay-co/service/pay.js has 1223 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/uni_modules/uni-pay-x/uniCloud/cloudfunctions/uni-pay-co/service/pay.js:1
src/uni_modules/uni-editor/static/editor.js has 1044 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/uni_modules/uni-editor/static/editor.js:1
src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/amap.js has 913 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/amap.js:1
src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/qqmap.js has 791 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/qqmap.js:1
src/wxcomponents/vant/icon/index.vue has 775 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/wxcomponents/vant/icon/index.vue:1
src/uni_modules/uni-upgrade-center-app/pages/upgrade-popup.vue has 620 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/uni_modules/uni-upgrade-center-app/pages/upgrade-popup.vue:1
src/uni_modules/uni-map-common/uniCloud/cloudfunctions/uni-map-co/index.obj.js has 497 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/uni_modules/uni-map-common/uniCloud/cloudfunctions/uni-map-co/index.obj.js:1
src/uni_modules/uni-editor/static/quill/formats.js has 408 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/uni_modules/uni-editor/static/quill/formats.js:1
What to do
Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
Do you agree with this assessment?
R4 · Test Coverage0.1 / 10Critical✓ Tool-verified
React / JS · Readiness — Static test reachability (D-386): the share of production files reachable from any test via the import graph — measured without running anything.
Method: Static test reachability: the share of production files reachable from any test via the import graph — measured without running anything. Deterministic.
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) — src/uni_modules/uni-pay-x/uniCloud/cloudfunctions/uni-pay-co/service/pay.js:1, src/uni_modules/uni-editor/static/editor.js:1, src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/amap.js:1, …
What to do
Add tests that import the unreached modules (directly or through their public entry).
React / JS · Readiness — How outdated the npm dependencies are (a maturity signal). JS/npm CVEs are scored separately in D30 (JS/npm Dependency Vulnerabilities).
Method: npm dependency staleness from manifest/registry metadata (a maturity signal; JS/npm CVEs are scored separately in D30, which answers dependency vulnerabilities for every ecosystem). Deterministic.
Do you agree with this assessment?
R6 · Tooling3.4 / 10Weak✓ Tool-verified
React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each package.json script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.
Method: package.json scanned for test/lint/typecheck script wiring. Deterministic presence check.
test ✓ · lint ✗ · typecheck ✗ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
What to do
Add eslint and `tsc --noEmit` as package.json scripts and run them in CI.
Do you agree with this assessment?
R7 · Dead Code8.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.
2 file(s) (~62 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package.
1 file(s) (~133 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. — src/uni_modules/CalendarPicker
1 file(s) (~0 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. — src/uni_modules/test-image-path
2 file(s) (~438 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. — src/uni_modules/uni-animation-view
1 file(s) (~162 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. (×2) — src/uni_modules/uni-canvas, src/uni_modules/uni-canvas-dom2
2 file(s) (~131 LoC) were excluded from dead-code analysis. This package DOES declare main/module/exports — but every declared target is missing from the scanned tree, which is what a build-output entry (dist/, lib/, out/) looks like before the package is built. Point a declared target at the source entry, or build the package before scanning, so reachability can follow it. — src/uni_modules/uni-config-center/uniCloud/cloudfunctions/common/uni-config-center
5 file(s) (~67 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. — src/uni_modules/uni-getbatteryinfo
3 file(s) (~1401 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. — src/uni_modules/uni-icons
1 file(s) (~76 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. — src/uni_modules/uni-installApk
1 file(s) (~121 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. — src/uni_modules/uni-map-amap
1 file(s) (~71 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. — src/uni_modules/uni-memorywarning
1 file(s) (~73 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. — src/uni_modules/uni-nav-bar
1 file(s) (~143 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. — src/uni_modules/uni-refresh-box
5 file(s) (~1106 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. — src/uni_modules/uni-upgrade-center-app
2 file(s) (~423 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. — src/uni_modules/uni-wifi
2 file(s) (~397 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. — src/uni_modules/uts-button
Unreachable from the 42 application, 21 tooling and 232 test entry point(s) detected in this repo. Nothing this repository declares compiles or type-checks these files, so a wrong deletion here would raise no compile error — gate removals on `yarn test`, which loads the modules, and note that it only covers what it exercises. An undetected custom entry would make these reachable.
no import path from any entry point (42 application, 21 tooling, 232 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make (×14) — src/components/api-set-tabbar/api-set-tabbar.vue, src/jest-setup.js, src/wxcomponents/vant/mixins/transition.js, …
no import path from any entry point (42 application, 21 tooling, 232 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/wxcomponents/vant/button/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 (×2) — src/wxcomponents/vant/icon/index.vue, src/wxcomponents/vant/loading/index.vue
no import path from any entry point (42 application, 21 tooling, 232 test roots considered), but 8 in-repo import(s) from 8 other file(s) do name it (src/wxcomponents/vant/button/index.js, src/wxcomponents/vant/button/index.vue, src/wxcomponents/vant/icon/index.js and 5 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/wxcomponents/vant/common/component.js
no import path from any entry point (42 application, 21 tooling, 232 test roots considered), but 5 in-repo import(s) from 5 other file(s) do name it (src/wxcomponents/vant/icon/index.js, src/wxcomponents/vant/icon/index.vue, src/wxcomponents/vant/loading/index.js and 2 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 — src/wxcomponents/vant/common/utils.js
no import path from any entry point (42 application, 21 tooling, 232 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (src/wxcomponents/vant/button/index.js, src/wxcomponents/vant/button/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 (×2) — src/wxcomponents/vant/mixins/open-type.js, src/wxcomponents/vant/mixins/button.js
no import path from any entry point (42 application, 21 tooling, 232 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/wxcomponents/vant/common/component.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×2) — src/wxcomponents/vant/mixins/basic.js, src/wxcomponents/vant/mixins/observer/index.js
What to do
Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
React / JS · Readiness — npm dependency truthfulness (D-386): unused dependencies, imports not declared anywhere, and type-/test-only packages shipped as production deps.
Method: npm dependency truthfulness: unused dependencies, imports declared nowhere, and type-/test-only packages shipped as production deps — from the manifest + import graph. Deterministic.
Imported but not declared in any reachable package.json — installs work only by hoisting accident. — src/testSequencer.js:1
What to do
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.
Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.
Other · Code Health — Whether a value handed from a callback to the body that waits on it crosses on something built to be crossed — a `Queue<T>`/`List<T>`/`Dictionary<K,V>` written inside an event handler and read back outside it is mutated by two flows at once, and the semaphore or completion source beside it orders how MANY items exist while leaving the collection's own head, tail and backing array unprotected.
Method: Roslyn syntax: method, accessor, local-function and lambda bodies that declare BOTH a non-thread-safe generic collection (`Queue`/`Stack`/`List`/`Dictionary`/`HashSet`/`Sorted*`/`LinkedList`) and a synchronisation primitive (`SemaphoreSlim`/`TaskCompletionSource`/`ManualResetEvent(Slim)`/`AutoResetEvent`/`CountdownEvent`) as locals, then read for a `+=`-registered lambda that raises that primitive while the body outside every lambda waits on it — and, in that scope, a mutating call on the collection inside the lambda paired with a mention of it outside. Any `lock` in the scope abstains it. On a repository with no .NET source the same handoff is read in Java off the engine’s own token stream (test source sets, vendored and demonstration paths not): an `ArrayList`/`LinkedList`/`ArrayDeque`/`PriorityQueue`/`Hash*`/`LinkedHash*`/`Tree*` local and a `CountDownLatch`/`Semaphore`/`CompletableFuture` local, a lambda or anonymous class that raises the primitive and mutates the collection, and a wait outside it; any `synchronized` or `lock()` abstains the body. Because each of those primitives orders what the callback wrote before raising it, only a touch that provably overlaps the callback is convicted: one after the registration and before the next wait, or one in a loop registered-before, waiting on every pass and not declaring the collection. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
`.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it. (×2) — src/wxcomponents/vant/mixins/transition.js:70, src/wxcomponents/vant/mixins/transition.js:100
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. (×11) — src/uni_modules/uni-virtualPayment/utssdk/app-ios/UniStoreKit.swift:90, src/uni_modules/uni-virtualPayment/utssdk/app-ios/UniStoreKit.swift:239, src/uni_modules/uni-video/utssdk/app-ios/VideoPlayer/Managers/VolumeHandler.swift:87, …
`catch (e: Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×3) — src/uni_modules/uni-recorder/utssdk/app-android/AudioRecorder.kt:699, src/uni_modules/uni-barcode-scanning/utssdk/app-android/Scanner.kt:168, src/uni_modules/uni-barcode-scanning/utssdk/app-android/Scanner.kt:177
`catch (_: Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — src/uni_modules/uni-getBackgroundAudioManager/utssdk/app-android/BackgroundAudioPlayer.kt:332
`catch (Throwable)` 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. — src/uni_modules/uni-chooseMedia/utssdk/app-android/SystemPickerActivity.java:58
`catch` 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. (×8) — src/uni_modules/uni-camera/utssdk/app-ios/CameraImpl.swift:284, src/uni_modules/uni-camera/utssdk/app-ios/CameraImpl.swift:287, src/uni_modules/uni-camera/utssdk/app-ios/CameraImpl.swift:336, …
Other · Code Health — Whether Kotlin's null safety is not undermined by not-null assertions — `String` cannot hold null and `String?` must be checked before use in every Kotlin module, and each `!!` is a run-time `NullPointerException` the author has told the compiler cannot happen.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
~7.6 `!!` not-null assertions per 1k Kotlin product lines — 54 across the 7086 line(s) of the 24 Kotlin file(s) read (generated, test and sample code not counted). Densest: src/uni_modules/uni-createInnerAudioContext/utssdk/app-android/AudioPlayer.kt (12), src/uni_modules/uni-camera/utssdk/app-android/CameraImpl.kt (11), src/uni_modules/uni-getBackgroundAudioManager/utssdk/app-android/AudioService.kt (8). Each one tells the compiler to trust the author about null and becomes a `NullPointerException` the first time the author is wrong. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
What to do
Replace `!!` rather than adding to it: each is a run-time null check the compiler could not prove. Narrow the value with a null check, an early return or `?: return`, use `?.` / `?:` where absence is legitimate, `requireNotNull(x) { "why" }` / `checkNotNull` where a missing value is a contract breach worth a message, make the property non-nullable and set it in the constructor (or `by lazy`) instead of `lateinit` plus `!!`, or change the API so the null cannot arrive.
Do you agree with this assessment?
WCAG coverage — what static analysis assessed
Statically assessed 15 of 55 WCAG 2.2 Level A/AA success criteria (27%; ≈30% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 40 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 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.
SC1 Supply-chain hygiene — 4 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X10 Duplicated predicate — 16 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 3 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 5 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 68 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.
AX1 Captive dependencies — Not applicable: this repository's JavaScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's Java imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's Kotlin imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's Swift imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's TypeScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Java code is a Spring, JSR-330 or CDI singleton bean. No class in this Kotlin code is a Spring, JSR-330 or CDI singleton bean. No Swift request handler (a Vapor, Hummingbird, Kitura, Swifter or Perfect route handler, as a method or a registered closure) is declared, so no state is shared between request threads. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX6 Interface segregation — no public interfaces
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — the dev server (`npm run start`) exited before it served a page. Likely cause (the repository): package.json has no "start" script, so `npm run start` could not start the app. Last output: "npm error Missing script: "start" / npm error / npm error Did you mean one of these? / npm error npm star # Mark your favorite packages / npm error npm stars # View packages marked as favorites / npm error / npm error To see a list of scripts, run: / npm error npm run / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered. This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
D11 Test Reliability — Test reliability not measured — JavaScript/TypeScript suite did not run
D16 Bus Factor — dormant codebase — no living knowledge left to concentrate
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
D21 Naming Consistency — Naming consistency does not read html yet; not measured.
D22 Internal API Consistency — API consistency is measured on C# only; the exposed JavaScript surface was not measured.
D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D25 ADR Conformance — no ADRs to check
D28 Secrets (history) — gitleaks killed before it finished — this repository's git history not scanned
D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
D32 Data Compliance (PII/GDPR) — 2 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D34 Knowledge Freshness — knowledge concentrated in recent work — freshness signal contradicted by repo activity
D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
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 (2 value object(s))
ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and this analysis resolves a call's owner only where the receiver's type is written down in the source. Reported as guidance rather than measured
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Fold determinism — not applicable — the code was read and holds no event-replay fold, so there is nothing for this check to judge
GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
P2 Observability — This repository's JVM, Swift, JavaScript/TypeScript source (28 module(s), 184 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM, JavaScript/TypeScript, Swift source, so there is no service whose uptime a failing dependency could take down
P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a package.json, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
S1 Web-Security Posture — Not assessed: these web-security 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 web-security 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.
X1 Async correctness — X1 reached only 29% of this repository's production lines — swift (44,017 lines), c (16,020 lines), cpp (2,965 lines), java (298 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X12 Unreachable branch — X12 reached only 29% of this repository's production lines — swift (44,017 lines), c (16,020 lines), cpp (2,965 lines), java (298 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X16 Unfloored truncation loop — X16 reached only 29% of this repository's production lines — swift (44,017 lines), c (16,020 lines), cpp (2,965 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X18 Disposal-pattern correctness — X18 reached only 29% of this repository's production lines — swift (44,017 lines), c (16,020 lines), cpp (2,965 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X2 Cancellation propagation — X2 reached only 29% of this repository's production lines — swift (44,017 lines), c (16,020 lines), cpp (2,965 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
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
X21 Side-effecting pattern guard — X21 reached only 29% of this repository's production lines — swift (44,017 lines), c (16,020 lines), cpp (2,965 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X27 Collection changed while being enumerated — X27 reached only 8% of this repository's production lines — swift (44,017 lines), javascript (17,895 lines), c (16,020 lines), cpp (2,965 lines), typescript (1,120 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X29 Per-element action decided by a fixed element — X29 reached only 29% of this repository's production lines — swift (44,017 lines), c (16,020 lines), cpp (2,965 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.
X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Kotlin was read, and it logs through none that an assembled message defeats: Android's `Log` and Timber, java.util.logging and log4j-api-kotlin take one finished message (as log4net does in C#), or it makes no call through a named logger at all. Calls made through SLF4J, log4j 2 or kotlin-logging (`LoggerFactory.getLogger`, `KotlinLogging.logger {}`) would be judged.
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
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.
Mutable domain event: InnerWebViewLoadingEvent src/uni_modules/uni-web-view/utssdk/app-ios/InnerWebView.swift:53— `InnerWebViewLoadingEvent` conforms to a domain-event contract but carries mutable state (a `class` event, or a `struct` event with a mutable `var`). Events are immutable facts — model them as a `struct` with `let` fields so a recorded event can never be rewritten.
Mutable domain event: InnerWebViewLoadedEvent src/uni_modules/uni-web-view/utssdk/app-ios/InnerWebView.swift:83— `InnerWebViewLoadedEvent` conforms to a domain-event contract but carries mutable state (a `class` event, or a `struct` event with a mutable `var`). Events are immutable facts — model them as a `struct` with `let` fields so a recorded event can never be rewritten.
Mutable domain event: InnerWebViewLoadEvent src/uni_modules/uni-web-view/utssdk/app-ios/InnerWebView.swift:120— `InnerWebViewLoadEvent` conforms to a domain-event contract but carries mutable state (a `class` event, or a `struct` event with a mutable `var`). Events are immutable facts — model them as a `struct` with `let` fields so a recorded event can never be rewritten.
Mutable domain event: InnerWebViewMessageEvent src/uni_modules/uni-web-view/utssdk/app-ios/InnerWebView.swift:156— `InnerWebViewMessageEvent` conforms to a domain-event contract but carries mutable state (a `class` event, or a `struct` event with a mutable `var`). Events are immutable facts — model them as a `struct` with `let` fields so a recorded event can never be rewritten.
Mutable domain event: InnerWebViewServiceMessageEvent src/uni_modules/uni-web-view/utssdk/app-ios/InnerWebView.swift:183— `InnerWebViewServiceMessageEvent` conforms to a domain-event contract but carries mutable state (a `class` event, or a `struct` event with a mutable `var`). Events are immutable facts — model them as a `struct` with `let` fields so a recorded event can never be rewritten.
Mutable domain event: InnerWebViewDownloadEvent src/uni_modules/uni-web-view/utssdk/app-ios/InnerWebView.swift:214— `InnerWebViewDownloadEvent` conforms to a domain-event contract but carries mutable state (a `class` event, or a `struct` event with a mutable `var`). Events are immutable facts — model them as a `struct` with `let` fields so a recorded event can never be rewritten.
Mutable domain event: InnerWebViewErrorEvent src/uni_modules/uni-web-view/utssdk/app-ios/InnerWebView.swift:260— `InnerWebViewErrorEvent` conforms to a domain-event contract but carries mutable state (a `class` event, or a `struct` event with a mutable `var`). Events are immutable facts — model them as a `struct` with `let` fields so a recorded event can never be rewritten.
Mutable domain event: InnerWebViewContentHeightChangeEvent src/uni_modules/uni-web-view/utssdk/app-ios/InnerWebView.swift:366— `InnerWebViewContentHeightChangeEvent` conforms to a domain-event contract but carries mutable state (a `class` event, or a `struct` event with a mutable `var`). Events are immutable facts — model them as a `struct` with `let` fields so a recorded event can never be rewritten.
AC2 · Forms & labels· <input> without a programmatic label · ×5
<input> without a programmatic label src/hybrid/html/local.html:59— 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 src/hybrid/html/local.html:61— 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 src/hybrid/html/local.html:63— 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 src/hybrid/html/local.html:65— 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 src/hybrid/html/local.html:67— 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.
AC1 · Text alternatives· <img> without a text alternative · ×3
<img> without a text alternative src/uni_modules/uni-upgrade-center-app/pages/upgrade-popup.vue:6— 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 src/uni_modules/uni-upgrade-center-app/pages/upgrade-popup.vue:69— 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 src/wxcomponents/vant/icon/index.vue:4— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<html> without a lang src/hybrid/html/local.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 src/hybrid/html/privacy.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 src/hybrid/html/simple.html:2— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
AC4 · Keyboard semantics· Click handler on a non-interactive <text> · ×3
Click handler on a non-interactive <text> src/components/u-link/u-link.vue:3— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
Click handler on a non-interactive <text> src/uni_modules/uni-icons/components/uni-icons/uni-icons.vue:3— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
Click handler on a non-interactive <text> src/uni_modules/uni-icons/components/uni-icons/uni-icons.vue:6— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
Assertions commented out: mixinDatacomGet src/pages/component/unicloud-db/unicloud-db/mixin-datacom/mixin-datacom.test.js:19— The test body contains commented-out assertion calls and no live one — it runs, verifies nothing, and still passes. Restore the assertions or delete the test; a green test that checks nothing is worse than an absent one.
Assertions commented out: onEnded src/pages/API/create-inner-audio-context/create-inner-audio-context.test.js:88— The test body contains commented-out assertion calls and no live one — it runs, verifies nothing, and still passes. Restore the assertions or delete the test; a green test that checks nothing is worse than an absent one.
Assertions commented out: setClipboardData src/pages/API/clipboard/clipboard.test.js:23— The test body contains commented-out assertion calls and no live one — it runs, verifies nothing, and still passes. Restore the assertions or delete the test; a green test that checks nothing is worse than an absent one.
AX8 · Test isolation· Production project references a test project · ×2
Production project references a test project: Hello uni-app x → test-image-path — `Hello uni-app x` (production) references the test project `test-image-path`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
Production project references a test project: Hello uni-app x → test-invoke-network-api — `Hello uni-app x` (production) references the test project `test-invoke-network-api`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
AC2 · Forms & labels· <textarea> without a programmatic label · ×1
<textarea> without a programmatic label src/hybrid/html/local.html:70— 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.
AC3 · Page structure· <iframe> without a title · ×1
<iframe> without a title src/hybrid/html/local.html:74— An iframe with no title (or an empty one) is announced only as "frame". Add a non-empty title describing its content, or an aria-label.
Viewport restricts zoom src/hybrid/html/privacy.html:6— user-scalable=no/0 or a maximum-scale below 2 stops low-vision users zooming to 200%. Remove the zoom restriction from the viewport meta.
AC3 · Page structure· Document <title> is empty · ×1
Document <title> is empty src/uni_modules/uni-editor/static/editor.html:2— An empty <title> gives no page name in the tab, history or screen-reader page list. Put descriptive text in the <title>.
Blocking wait inside a handler: DRMManager.handleContentKeyRequest src/uni_modules/uni-video/utssdk/app-ios/VideoPlayer/Managers/DRMManager.swift:58— `DRMManager.handleContentKeyRequest` is an event/message handler that blocks on a synchronous wait (a semaphore/queue `.wait`/`.sync`) — it stalls the handler on a peer or resource and serialises throughput, and can deadlock under load. Await the work asynchronously (`async`/`await`) instead of blocking the handler.
Unlisted import '@jest/test-sequencer' src/testSequencer.js:1— Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Serious — 617 finding(s)
D30 · Dependency Vulnerabilities· Medium CVE · ×44
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
+ 19 more in this group — see findings.md.
R4 · Test Coverage· No test reaches this file · ×40
No test reaches this file src/uni_modules/uni-pay-x/uniCloud/cloudfunctions/uni-pay-co/service/pay.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 src/uni_modules/uni-editor/static/editor.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 src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/amap.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 src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/qqmap.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 src/uni_modules/uni-map-common/uniCloud/cloudfunctions/uni-map-co/index.obj.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 src/uni_modules/uni-upgrade-center-app/pages/upgrade-popup.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 src/uni_modules/uni-editor/static/quill/formats.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 src/uni_modules/uni-pay-x/uniCloud/cloudfunctions/uni-pay-co/index.obj.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 src/uni_modules/uni-pay-x/uniCloud/cloudfunctions/uni-pay-co/libs/common.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 src/uni_modules/uni-animation-view/utssdk/app-ios/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 src/uni_modules/uni-upgrade-center-app/utils/check-update.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 src/components/api-set-tabbar/api-set-tabbar.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 src/uni_modules/uts-button/utssdk/app-ios/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 src/uni_modules/uni-animation-view/utssdk/app-android/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 src/jest-setup.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 src/uni_modules/uts-button/utssdk/app-android/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 src/uni_modules/uni-upgrade-center-app/utils/check-update-nvue.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 src/uni_modules/uni-pay-x/uniCloud/cloudfunctions/uni-pay-co/libs/alipay.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 src/uni_modules/uni-pay-x/uniCloud/cloudfunctions/uni-pay-co/libs/crypto.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 src/uni_modules/uni-canvas-dom2/utssdk/app-harmony/canvas.color.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 src/uni_modules/uni-canvas/customElements/uni-canvas/uni-canvas.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 src/uni_modules/uni-refresh-box/components/uni-refresh-box/uni-refresh-box.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 src/uni_modules/CalendarPicker/components/CalendarPicker/CalendarPicker.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 src/uni_modules/uni-map-amap/components/map/amap-map.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 src/uni_modules/uni-upgrade-center-app/utils/call-check-version.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.
Low cohesion: InnerWebView (LCOM4 20) src/uni_modules/uni-web-view/utssdk/app-ios/InnerWebView.swift:438— InnerWebView's methods fall into 20 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 20 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.
Low cohesion: CALayer (LCOM4 9) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/CoreAnimation/CoreAnimationLayer.swift:552— CALayer's methods fall into 9 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 9 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.
Low cohesion: CameraManager (LCOM4 8) src/uni_modules/uni-camera/utssdk/app-ios/CameraManager.swift:85— CameraManager's methods fall into 8 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 8 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.
Low cohesion: CacheManager (LCOM4 8) src/uni_modules/uni-video/utssdk/app-ios/VideoPlayer/Managers/CacheManager.swift:12— CacheManager's methods fall into 8 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 8 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.
Low cohesion: DCActionSheetController (LCOM4 7) src/uni_modules/uni-prompt/utssdk/app-ios/UniAlert/DCActionSheetController.swift:12— DCActionSheetController's methods fall into 7 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 7 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.
Low cohesion: PIPManager (LCOM4 7) src/uni_modules/uni-video/utssdk/app-ios/VideoPlayer/Managers/PIPManager.swift:13— PIPManager's methods fall into 7 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 7 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.
Low cohesion: LottieAnimationViewBase (LCOM4 7) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/macOS/LottieAnimationViewBase.macOS.swift:30— LottieAnimationViewBase's methods fall into 7 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 7 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.
Low cohesion: CGFloat (LCOM4 7) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/Keyframes/Interpolatable.swift:112— CGFloat's methods fall into 7 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 7 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.
Low cohesion: String (LCOM4 6) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/DotLottie/DotLottieFile.swift:129— String's methods fall into 6 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 6 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.
Low cohesion: CGSize (LCOM4 6) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/Keyframes/Interpolatable.swift:138— CGSize's methods fall into 6 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 6 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.
Low cohesion: DCAlertViewController (LCOM4 5) src/uni_modules/uni-prompt/utssdk/app-ios/UniAlert/DCAlertViewController.swift:26— DCAlertViewController's methods fall into 5 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 5 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.
Low cohesion: DCBottomMenuController (LCOM4 5) src/uni_modules/uni-prompt/utssdk/app-ios/UniAlert/DCBottomMenuController.swift:39— DCBottomMenuController's methods fall into 5 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 5 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.
Low cohesion: LottieAnimationViewBase (LCOM4 5) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/iOS/LottieAnimationViewBase.swift:14— LottieAnimationViewBase's methods fall into 5 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 5 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.
Low cohesion: CGPoint (LCOM4 5) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/Keyframes/Interpolatable.swift:148— CGPoint's methods fall into 5 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 5 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.
Low cohesion: UniInputView (LCOM4 4) src/uni_modules/uni-form/utssdk/app-ios/UniInputView.swift:10— UniInputView'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.
Low cohesion: UniTextareaView (LCOM4 4) src/uni_modules/uni-form/utssdk/app-ios/UniTextareaView.swift:10— UniTextareaView'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.
Low cohesion: UniBackgroundAudioManager (LCOM4 4) src/uni_modules/uni-getBackgroundAudioManager/utssdk/app-ios/UniBackgroundAudioManager.swift:54— UniBackgroundAudioManager'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.
Low cohesion: UniBaseWebView (LCOM4 4) src/uni_modules/uni-web-view/utssdk/app-ios/UniBaseWebView.swift:12— UniBaseWebView'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.
Low cohesion: DCAlertControllerContentView (LCOM4 4) src/uni_modules/uni-prompt/utssdk/app-ios/UniAlert/DCloudAlertControllerComponents.swift:107— DCAlertControllerContentView'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.
Low cohesion: LottieAnimationLayer (LCOM4 4) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/Animation/LottieAnimationLayer.swift:12— LottieAnimationLayer'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.
Low cohesion: LottieLogger (LCOM4 4) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/Logging/LottieLogger.swift:8— LottieLogger'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.
Low cohesion: MainThreadAnimationLayer (LCOM4 4) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/MainThread/LayerContainers/MainThreadAnimationLayer.swift:16— MainThreadAnimationLayer'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.
FileTooLong: app-ios/UniFileSystemManager.swift src/uni_modules/uni-fileSystemManager/utssdk/app-ios/UniFileSystemManager.swift— FileTooLong — 1403 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 903 over it, 2.81× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: app-ios/CameraManager.swift src/uni_modules/uni-camera/utssdk/app-ios/CameraManager.swift— FileTooLong — 1083 significant lines (blank, comment-only and punctuation-only lines excluded), about 92% of them inside a single declaration: CameraManager (85-1866). The bar is 500 significant lines; this is 583 over it, 2.17× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: app-ios/InnerWebView.swift src/uni_modules/uni-web-view/utssdk/app-ios/InnerWebView.swift— FileTooLong — 1023 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 523 over it, 2.05× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: service/pay.js src/uni_modules/uni-pay-x/uniCloud/cloudfunctions/uni-pay-co/service/pay.js— FileTooLong — 866 significant lines (blank, comment-only and punctuation-only lines excluded), about 99% of them inside a single declaration: service (24-1273). The bar is 500 significant lines; this is 366 over it, 1.73× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: html/privacy.html src/hybrid/html/privacy.html— FileTooLong — 746 significant lines (blank, comment-only and punctuation-only lines excluded), about 99% of them inside a single declaration: QRCode (24-859). The bar is 500 significant lines; this is 246 over it, 1.49× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: service/amap.js src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/amap.js— FileTooLong — 746 significant lines (blank, comment-only and punctuation-only lines excluded), about 94% of them inside a single declaration: Service (47-978). The bar is 500 significant lines; this is 246 over it, 1.49× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: app-ios/UniBackgroundAudioManager.swift src/uni_modules/uni-getBackgroundAudioManager/utssdk/app-ios/UniBackgroundAudioManager.swift— FileTooLong — 736 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 236 over it, 1.47× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: static/editor.js src/uni_modules/uni-editor/static/editor.js— FileTooLong — 658 significant lines (blank, comment-only and punctuation-only lines excluded; the length bar is tripled for a single-responsibility module of 4 or fewer top-level units). The bar is 500 significant lines; this is 158 over it, 1.32× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: app-android/CameraImpl.kt src/uni_modules/uni-camera/utssdk/app-android/CameraImpl.kt— FileTooLong — 654 significant lines (blank, comment-only and punctuation-only lines excluded), about 92% of them inside a single declaration: CameraImpl (61-1037). The bar is 500 significant lines; this is 154 over it, 1.31× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: Managers/UniVideoPlayerManager.swift src/uni_modules/uni-video/utssdk/app-ios/VideoPlayer/Managers/UniVideoPlayerManager.swift— FileTooLong — 650 significant lines (blank, comment-only and punctuation-only lines excluded), about 97% of them inside a single declaration: UniVideoPlayerManager (46-1289). The bar is 500 significant lines; this is 150 over it, 1.30× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: app-android/NativeWebViewImpl.kt src/uni_modules/uni-web-view/utssdk/app-android/NativeWebViewImpl.kt— FileTooLong — 643 significant lines (blank, comment-only and punctuation-only lines excluded), about 75% of them inside a single declaration: NativeWebViewImpl (63-792). The bar is 500 significant lines; this is 143 over it, 1.29× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: app-ios/UniNetWorkManager.swift src/uni_modules/uni-getNetworkType/utssdk/app-ios/UniNetWorkManager.swift— FileTooLong — 637 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 137 over it, 1.27× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: service/qqmap.js src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/qqmap.js— FileTooLong — 635 significant lines (blank, comment-only and punctuation-only lines excluded), about 100% of them inside a single declaration: Service (3-855). The bar is 500 significant lines; this is 135 over it, 1.27× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: app-ios/UniAudioPlayer.swift src/uni_modules/uni-createInnerAudioContext/utssdk/app-ios/UniAudioPlayer.swift— FileTooLong — 629 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 129 over it, 1.26× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
TooManyMethods: CameraManager src/uni_modules/uni-camera/utssdk/app-ios/CameraManager.swift:85— TooManyMethods — 78 methods. The bar is 30 methods; this is 48 over it, 2.60× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: BackgroundAudioPlayer src/uni_modules/uni-getBackgroundAudioManager/utssdk/app-android/BackgroundAudioPlayer.kt:75— TooManyMethods — 76 methods. The bar is 30 methods; this is 46 over it, 2.53× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: InnerWebView src/uni_modules/uni-web-view/utssdk/app-ios/InnerWebView.swift:438— TooManyMethods — 74 methods. The bar is 30 methods; this is 44 over it, 2.47× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: AudioPlayer src/uni_modules/uni-createInnerAudioContext/utssdk/app-android/AudioPlayer.kt:82— TooManyMethods — 71 methods. The bar is 30 methods; this is 41 over it, 2.37× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: UniBackgroundAudioManager src/uni_modules/uni-getBackgroundAudioManager/utssdk/app-ios/UniBackgroundAudioManager.swift:54— TooManyMethods — 67 methods. The bar is 30 methods; this is 37 over it, 2.23× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: VideoImpl src/uni_modules/uni-video/utssdk/app-android/VideoImpl.kt:36— TooManyMethods — 59 methods. The bar is 30 methods; this is 29 over it, 1.97× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: UniAudioPlayer src/uni_modules/uni-createInnerAudioContext/utssdk/app-ios/UniAudioPlayer.swift:53— TooManyMethods — 52 methods. The bar is 30 methods; this is 22 over it, 1.73× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: UniVideoPlayerManager src/uni_modules/uni-video/utssdk/app-ios/VideoPlayer/Managers/UniVideoPlayerManager.swift:44— TooManyMethods — 52 methods. The bar is 30 methods; this is 22 over it, 1.73× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: CameraImpl src/uni_modules/uni-camera/utssdk/app-android/CameraImpl.kt:61— TooManyMethods — 50 methods. The bar is 30 methods; this is 20 over it, 1.67× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: UniFileSystemManager src/uni_modules/uni-fileSystemManager/utssdk/app-ios/UniFileSystemManager.swift:129— TooManyMethods — 49 methods. The bar is 30 methods; this is 19 over it, 1.63× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: UniNetWorkManager src/uni_modules/uni-getNetworkType/utssdk/app-ios/UniNetWorkManager.swift:219— TooManyMethods — 43 methods. The bar is 30 methods; this is 13 over it, 1.43× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: UniAudioRecorderManager src/uni_modules/uni-recorder/utssdk/app-ios/UniAudioRecorderManager.swift:65— TooManyMethods — 43 methods. The bar is 30 methods; this is 13 over it, 1.43× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: UniVideoPlayerView src/uni_modules/uni-video/utssdk/app-ios/VideoPlayer/UniVideoPlayerView.swift:15— TooManyMethods — 33 methods. The bar is 30 methods; this is 3 over it, 1.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: NativeWebViewImpl src/uni_modules/uni-web-view/utssdk/app-android/NativeWebViewImpl.kt:63— TooManyMethods — 31 methods. The bar is 30 methods; this is 1 over it, 1.03× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Swallowed exception (empty catch) src/wxcomponents/vant/mixins/transition.js:70— `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) src/wxcomponents/vant/mixins/transition.js:100— `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) src/uni_modules/uni-virtualPayment/utssdk/app-ios/UniStoreKit.swift:90— 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) src/uni_modules/uni-virtualPayment/utssdk/app-ios/UniStoreKit.swift:239— 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) src/uni_modules/uni-video/utssdk/app-ios/VideoPlayer/Managers/VolumeHandler.swift:87— 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) src/uni_modules/uni-recorder/utssdk/app-ios/UniAudioRecorderManager.swift:383— 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) src/uni_modules/uni-pay-x/uniCloud/cloudfunctions/uni-pay-co/service/pay.js:823— 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) src/uni_modules/uni-pay-x/uniCloud/cloudfunctions/uni-pay-co/service/pay.js:948— 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) src/uni_modules/uni-pay-x/uniCloud/cloudfunctions/uni-pay-co/libs/crypto.js:119— 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) src/uni_modules/uni-pay-x/uniCloud/cloudfunctions/uni-pay-co/libs/crypto.js:166— 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) src/uni_modules/uni-pay-x/uniCloud/cloudfunctions/uni-pay-co/lang/index.js:20— 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) src/uni_modules/uni-chooseMedia/utssdk/app-android/SystemPickerActivity.java:176— 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) src/uni_modules/uni-chooseMedia/utssdk/app-android/SystemPickerActivity.java:233— 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 (caught, then discarded) src/uni_modules/uni-recorder/utssdk/app-android/AudioRecorder.kt:699— `catch (e: Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) src/uni_modules/uni-getBackgroundAudioManager/utssdk/app-android/BackgroundAudioPlayer.kt:332— `catch (_: Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) src/uni_modules/uni-chooseMedia/utssdk/app-android/SystemPickerActivity.java:58— `catch (Throwable)` 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) src/uni_modules/uni-camera/utssdk/app-ios/CameraImpl.swift:284— `catch` 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) src/uni_modules/uni-camera/utssdk/app-ios/CameraImpl.swift:287— `catch` 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) src/uni_modules/uni-camera/utssdk/app-ios/CameraImpl.swift:336— `catch` 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) src/uni_modules/uni-camera/utssdk/app-ios/CameraImpl.swift:351— `catch` 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) src/uni_modules/uni-camera/utssdk/app-ios/CameraManager.swift:1038— `catch` 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) src/uni_modules/uni-camera/utssdk/app-ios/CameraManager.swift:1072— `catch` 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) src/uni_modules/uni-camera/utssdk/app-ios/CameraManager.swift:1764— `catch` 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) src/uni_modules/uni-camera/utssdk/app-ios/CameraManager.swift:1781— `catch` 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) src/uni_modules/uni-barcode-scanning/utssdk/app-android/Scanner.kt:168— `catch (e: Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) src/uni_modules/uni-barcode-scanning/utssdk/app-android/Scanner.kt:177— `catch (e: Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Duplicated block (5 lines × 2) src/uni_modules/uni-prompt/utssdk/app-ios/UniAlert/DCAlertView.Blocks.swift:41— src/uni_modules/uni-prompt/utssdk/app-ios/UniAlert/DCAlertView.Blocks.swift:41-45 | src/uni_modules/uni-prompt/utssdk/app-ios/UniAlert/DCAlertView.Blocks.swift:56-60 — 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 `src/uni_modules/uni-prompt/utssdk/app-ios/UniAlert/DCAlertView.Blocks.swift:41` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (5 lines × 2) src/uni_modules/uni-prompt/utssdk/app-ios/UniAlert/DCAlertView.Blocks.swift:77— src/uni_modules/uni-prompt/utssdk/app-ios/UniAlert/DCAlertView.Blocks.swift:77-81 | src/uni_modules/uni-prompt/utssdk/app-ios/UniAlert/DCAlertView.Blocks.swift:93-97 — 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 `src/uni_modules/uni-prompt/utssdk/app-ios/UniAlert/DCAlertView.Blocks.swift:77` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (5 lines × 2) src/uni_modules/uni-web-view/utssdk/app-android/NativeWebViewImpl.kt:842— src/uni_modules/uni-web-view/utssdk/app-android/NativeWebViewImpl.kt:842-846 | src/uni_modules/uni-web-view/utssdk/app-android/NativeWebViewImpl.kt:848-852 — 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 `src/uni_modules/uni-web-view/utssdk/app-android/NativeWebViewImpl.kt:842` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (5 lines × 2) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/LayerEffects/EffectValues/ColorEffectValue.swift:25— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/LayerEffects/EffectValues/ColorEffectValue.swift:25-29 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/LayerEffects/EffectValues/Vector1DEffectValue.swift:25-29 — 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 (5 lines × 2) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/Layers/ShapeLayerModel.swift:19— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/Layers/ShapeLayerModel.swift:19-23 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/ShapeItems/Group.swift:19-23 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (5 lines × 2) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/Layers/ShapeLayerModel.swift:30— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/Layers/ShapeLayerModel.swift:30-34 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/ShapeItems/Group.swift:35-39 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (5 lines × 2) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/iOS/BundleImageProvider.swift:26— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/iOS/BundleImageProvider.swift:26-30 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/macOS/BundleImageProvider.macOS.swift:25-29 — `examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/iOS/BundleImageProvider.swift` and `examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/macOS/BundleImageProvider.macOS.swift` 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 2 separate duplicated blocks between them, totalling at least 35 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.
Duplicated block (5 lines × 2) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/LayerEffects/EffectValues/ColorEffectValue.swift:8— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/LayerEffects/EffectValues/ColorEffectValue.swift:8-12 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/LayerEffects/EffectValues/Vector1DEffectValue.swift:8-12 — 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 (5 lines × 2) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/LayerEffects/EffectValues/ColorEffectValue.swift:14— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/LayerEffects/EffectValues/ColorEffectValue.swift:14-18 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/LayerEffects/EffectValues/Vector1DEffectValue.swift:14-18 — 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 (5 lines × 2) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/MainThread/LayerContainers/Utility/LayerTransformNode.swift:18— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/MainThread/LayerContainers/Utility/LayerTransformNode.swift:18-22 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/MainThread/NodeRenderSystem/Nodes/RenderContainers/GroupNode.swift:20-24 — 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `transform` to `Transform` in one and `ShapeTransform?` 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) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/MainThread/NodeRenderSystem/Nodes/PathNodes/RectNode.swift:150— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/MainThread/NodeRenderSystem/Nodes/PathNodes/RectNode.swift:150-154 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/MainThread/NodeRenderSystem/Nodes/PathNodes/RectNode.swift:210-214 — 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 `examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/MainThread/NodeRenderSystem/Nodes/PathNodes/RectNode.swift:150` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/Animation/LottieAnimationView.swift:860— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/Animation/LottieAnimationView.swift:860-864 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/Animation/LottieAnimationView.swift:879-883 — 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.
ClassTooLong: CameraManager src/uni_modules/uni-camera/utssdk/app-ios/CameraManager.swift:85— ClassTooLong — 997 significant lines (blank, comment-only and punctuation-only lines excluded), 78 methods. The bar is 400 significant lines; this is 597 over it, 2.49× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: service src/uni_modules/uni-pay-x/uniCloud/cloudfunctions/uni-pay-co/service/pay.js:24— ClassTooLong — 855 significant lines (blank, comment-only and punctuation-only lines excluded), 17 methods. The bar is 400 significant lines; this is 455 over it, 2.14× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: Service src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/amap.js:47— ClassTooLong — 704 significant lines (blank, comment-only and punctuation-only lines excluded), 21 methods. The bar is 400 significant lines; this is 304 over it, 1.76× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: UniVideoPlayerManager src/uni_modules/uni-video/utssdk/app-ios/VideoPlayer/Managers/UniVideoPlayerManager.swift:44— ClassTooLong — 633 significant lines (blank, comment-only and punctuation-only lines excluded), 52 methods. The bar is 400 significant lines; this is 233 over it, 1.58× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: Service src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/qqmap.js:3— ClassTooLong — 633 significant lines (blank, comment-only and punctuation-only lines excluded), 19 methods. The bar is 400 significant lines; this is 233 over it, 1.58× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: CameraImpl src/uni_modules/uni-camera/utssdk/app-android/CameraImpl.kt:61— ClassTooLong — 599 significant lines (blank, comment-only and punctuation-only lines excluded), 50 methods. The bar is 400 significant lines; this is 199 over it, 1.50× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: NativeWebViewImpl src/uni_modules/uni-web-view/utssdk/app-android/NativeWebViewImpl.kt:63— ClassTooLong — 480 significant lines (blank, comment-only and punctuation-only lines excluded), 31 methods. The bar is 400 significant lines; this is 80 over it, 1.20× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: InnerWebView src/uni_modules/uni-web-view/utssdk/app-ios/InnerWebView.swift:438— ClassTooLong — 459 significant lines (blank, comment-only and punctuation-only lines excluded), 74 methods. The bar is 400 significant lines; this is 59 over it, 1.15× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: AudioRecorder src/uni_modules/uni-recorder/utssdk/app-android/AudioRecorder.kt:21— ClassTooLong — 448 significant lines (blank, comment-only and punctuation-only lines excluded), 25 methods. The bar is 400 significant lines; this is 48 over it, 1.12× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Duplicated block (11 lines × 2) src/uni_modules/uni-createInnerAudioContext/utssdk/app-ios/UniAudioPlayer.swift:673— src/uni_modules/uni-createInnerAudioContext/utssdk/app-ios/UniAudioPlayer.swift:673-683 | src/uni_modules/uni-getBackgroundAudioManager/utssdk/app-ios/UniBackgroundAudioManager.swift:671-681 — before extracting anything, compare `src/uni_modules/uni-createInnerAudioContext/utssdk/app-ios/UniAudioPlayer.swift` and `src/uni_modules/uni-getBackgroundAudioManager/utssdk/app-ios/UniBackgroundAudioManager.swift` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 285 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. Note first that the copies are not typed on the same thing: the declarations holding them bind `event` to `UniAudioEvent` in one and `UniBackgroundAudioEvent` 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 (11 lines × 2) src/uni_modules/uni-prompt/utssdk/app-ios/UniAlert/DCAlertControllerUtil.swift:71— src/uni_modules/uni-prompt/utssdk/app-ios/UniAlert/DCAlertControllerUtil.swift:71-81 | src/uni_modules/uni-prompt/utssdk/app-ios/UniToast/MCToast+Loading.swift:324-334 — 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 `src/uni_modules/uni-prompt/utssdk/app-ios/UniAlert/DCAlertControllerUtil.swift:71` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (11 lines × 2) src/uni_modules/uni-virtualPayment/utssdk/app-ios/UniStoreKit.swift:146— src/uni_modules/uni-virtualPayment/utssdk/app-ios/UniStoreKit.swift:146-156 | src/uni_modules/uni-virtualPayment/utssdk/app-ios/UniStoreKit.swift:162-172 — 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 `src/uni_modules/uni-virtualPayment/utssdk/app-ios/UniStoreKit.swift:146` 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) src/uni_modules/uni-createInnerAudioContext/utssdk/app-ios/UniAudioPlayer.swift:630— src/uni_modules/uni-createInnerAudioContext/utssdk/app-ios/UniAudioPlayer.swift:630-640 | src/uni_modules/uni-getBackgroundAudioManager/utssdk/app-ios/UniBackgroundAudioManager.swift:630-640 — before extracting anything, compare `src/uni_modules/uni-createInnerAudioContext/utssdk/app-ios/UniAudioPlayer.swift` and `src/uni_modules/uni-getBackgroundAudioManager/utssdk/app-ios/UniBackgroundAudioManager.swift` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 285 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 2) src/uni_modules/uni-createInnerAudioContext/utssdk/app-android/AudioPlayer.kt:491— src/uni_modules/uni-createInnerAudioContext/utssdk/app-android/AudioPlayer.kt:491-501 | src/uni_modules/uni-getBackgroundAudioManager/utssdk/app-android/BackgroundAudioPlayer.kt:482-492 — before extracting anything, compare `src/uni_modules/uni-createInnerAudioContext/utssdk/app-android/AudioPlayer.kt` and `src/uni_modules/uni-getBackgroundAudioManager/utssdk/app-android/BackgroundAudioPlayer.kt` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 63 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 2) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/Extensions/KeyedDecodingContainerExtensions.swift:34— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/Extensions/KeyedDecodingContainerExtensions.swift:34-44 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/Extensions/KeyedDecodingContainerExtensions.swift:60-70 — 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 `examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/Extensions/KeyedDecodingContainerExtensions.swift:34` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (11 lines × 2) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/Objects/Transform.swift:145— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/Objects/Transform.swift:145-155 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/ShapeItems/ShapeTransform.swift:94-104 — 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 `examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/Objects/Transform.swift:145` 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 (11 lines × 2) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/Controls/LottieButton.swift:101— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/Controls/LottieButton.swift:101-111 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/Controls/LottieSwitch.swift:123-133 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (11 lines × 2) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/DynamicProperties/ValueProviders/PointValueProvider.swift:50— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/DynamicProperties/ValueProviders/PointValueProvider.swift:50-60 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/DynamicProperties/ValueProviders/SizeValueProvider.swift:50-60 — 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) src/uni_modules/uni-form/utssdk/app-ios/UniInputView.swift:55— src/uni_modules/uni-form/utssdk/app-ios/UniInputView.swift:55-61 | src/uni_modules/uni-form/utssdk/app-ios/UniTextareaView.swift:62-68 — before extracting anything, compare `src/uni_modules/uni-form/utssdk/app-ios/UniInputView.swift` and `src/uni_modules/uni-form/utssdk/app-ios/UniTextareaView.swift` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 54 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 `src/uni_modules/uni-form/utssdk/app-ios/UniInputView.swift:55` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 2) src/uni_modules/uni-prompt/utssdk/app-ios/UniToast/MCToast+Loading.swift:35— src/uni_modules/uni-prompt/utssdk/app-ios/UniToast/MCToast+Loading.swift:35-41 | src/uni_modules/uni-prompt/utssdk/app-ios/UniToast/MCToast+Loading.swift:90-96 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/uni_modules/uni-prompt/utssdk/app-ios/UniToast/MCToast+Loading.swift:35` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (7 lines × 2) src/uni_modules/uni-virtualPayment/utssdk/app-ios/PurchaseService.swift:15— src/uni_modules/uni-virtualPayment/utssdk/app-ios/PurchaseService.swift:15-21 | src/uni_modules/uni-virtualPayment/utssdk/app-ios/PurchaseService.swift:60-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.
Duplicated block (7 lines × 2) src/uni_modules/uni-createInnerAudioContext/utssdk/app-ios/UniAudioPlayer.swift:115— src/uni_modules/uni-createInnerAudioContext/utssdk/app-ios/UniAudioPlayer.swift:115-121 | src/uni_modules/uni-getBackgroundAudioManager/utssdk/app-ios/UniBackgroundAudioManager.swift:116-122 — before extracting anything, compare `src/uni_modules/uni-createInnerAudioContext/utssdk/app-ios/UniAudioPlayer.swift` and `src/uni_modules/uni-getBackgroundAudioManager/utssdk/app-ios/UniBackgroundAudioManager.swift` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 285 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 2) src/uni_modules/uni-createInnerAudioContext/utssdk/app-ios/UniAudioPlayer.swift:155— src/uni_modules/uni-createInnerAudioContext/utssdk/app-ios/UniAudioPlayer.swift:155-161 | src/uni_modules/uni-getBackgroundAudioManager/utssdk/app-ios/UniBackgroundAudioManager.swift:164-170 — before extracting anything, compare `src/uni_modules/uni-createInnerAudioContext/utssdk/app-ios/UniAudioPlayer.swift` and `src/uni_modules/uni-getBackgroundAudioManager/utssdk/app-ios/UniBackgroundAudioManager.swift` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 285 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 2) src/uni_modules/uni-createInnerAudioContext/utssdk/app-ios/UniAudioPlayer.swift:166— src/uni_modules/uni-createInnerAudioContext/utssdk/app-ios/UniAudioPlayer.swift:166-172 | src/uni_modules/uni-getBackgroundAudioManager/utssdk/app-ios/UniBackgroundAudioManager.swift:175-181 — before extracting anything, compare `src/uni_modules/uni-createInnerAudioContext/utssdk/app-ios/UniAudioPlayer.swift` and `src/uni_modules/uni-getBackgroundAudioManager/utssdk/app-ios/UniBackgroundAudioManager.swift` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 285 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 2) src/uni_modules/uni-createInnerAudioContext/utssdk/app-android/AudioFocusHelper.kt:54— src/uni_modules/uni-createInnerAudioContext/utssdk/app-android/AudioFocusHelper.kt:54-65 | src/uni_modules/uni-getBackgroundAudioManager/utssdk/app-android/AudioFocusHelper.kt: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. Read the line range as the matched WINDOW rather than a finished unit: at `src/uni_modules/uni-createInnerAudioContext/utssdk/app-android/AudioFocusHelper.kt:54` 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) src/uni_modules/uni-createInnerAudioContext/utssdk/app-android/AudioPlayer.kt:353— src/uni_modules/uni-createInnerAudioContext/utssdk/app-android/AudioPlayer.kt:353-359 | src/uni_modules/uni-getBackgroundAudioManager/utssdk/app-android/BackgroundAudioPlayer.kt:366-372 — before extracting anything, compare `src/uni_modules/uni-createInnerAudioContext/utssdk/app-android/AudioPlayer.kt` and `src/uni_modules/uni-getBackgroundAudioManager/utssdk/app-android/BackgroundAudioPlayer.kt` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 63 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 2) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/MainThread/NodeRenderSystem/Nodes/RenderNodes/GradientFillNode.swift:18— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/MainThread/NodeRenderSystem/Nodes/RenderNodes/GradientFillNode.swift:18-24 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/MainThread/NodeRenderSystem/Nodes/RenderNodes/GradientStrokeNode.swift:18-24 — 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.
D4 · Code Duplication· Edited copy of a member (13 corresponding lines) · ×8
Edited copy of a member (13 corresponding lines) src/uni_modules/uni-prompt/utssdk/app-ios/UniAlert/DCAlertControllerUtil.swift:69— src/uni_modules/uni-prompt/utssdk/app-ios/UniAlert/DCAlertControllerUtil.swift:69-81 | src/uni_modules/uni-prompt/utssdk/app-ios/UniToast/MCToast+Loading.swift:322-334 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) src/uni_modules/uni-camera/utssdk/app-ios/CameraImpl.swift:327— src/uni_modules/uni-camera/utssdk/app-ios/CameraImpl.swift:327-339 | src/uni_modules/uni-camera/utssdk/app-ios/CameraImpl.swift:341-354 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) src/uni_modules/uni-prompt/utssdk/app-ios/UniAlert/DCAlertView.Blocks.swift:40— src/uni_modules/uni-prompt/utssdk/app-ios/UniAlert/DCAlertView.Blocks.swift:40-52 | src/uni_modules/uni-prompt/utssdk/app-ios/UniAlert/DCAlertView.Blocks.swift:75-88 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) src/uni_modules/uni-virtualPayment/utssdk/app-ios/UniStoreKit+Closure.swift:137— src/uni_modules/uni-virtualPayment/utssdk/app-ios/UniStoreKit+Closure.swift:137-149 | src/uni_modules/uni-virtualPayment/utssdk/app-ios/UniStoreKit+Closure.swift:151-166 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) src/uni_modules/uni-barcode-scanning/utssdk/app-android/Scanner.kt:383— src/uni_modules/uni-barcode-scanning/utssdk/app-android/Scanner.kt:383-395 | src/uni_modules/uni-camera/utssdk/app-android/CameraImpl.kt:929-941 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/Extensions/KeyedDecodingContainerExtensions.swift:32— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/Extensions/KeyedDecodingContainerExtensions.swift:32-44 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/Extensions/KeyedDecodingContainerExtensions.swift:52-70 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/LayerStyles/DropShadowStyle.swift:18— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/LayerStyles/DropShadowStyle.swift:18-30 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/ShapeItems/Trim.swift:30-43 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/ShapeItems/Repeater.swift:137— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/ShapeItems/Repeater.swift:137-151 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/ShapeItems/ShapeTransform.swift:165-177 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
TodoComment src/uni_modules/uni-recorder/utssdk/app-ios/UniAudioRecorderManager.swift:305— // 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 src/uni_modules/uni-dialogPage/utssdk/app-ios/native.swift:87— //Todo.. parentPage应为UniPage但定义为UniPage会导致jsexport导出失败原因未知暂时定义为Any — 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 examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/Keyframes/Interpolatable.swift:221— // TODO Support third dimension spatial interpolation — 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 examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/Text/TextAnimator.swift:167— // case textSelector = "s" 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 examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/ShapeItems/GradientStroke.swift:44— // TODO Decode Color Objects instead of array. — 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 examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/MainThread/NodeRenderSystem/Nodes/Text/TextAnimatorNode.swift:227— // TODO Fix This — 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 examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/CoreAnimation/Animations/VisibilityAnimation.swift:32— /// - TODO: We could remove this codepath in favor of always using the simpler codepath above, — 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.
Duplicated block (10 lines × 2) src/uni_modules/uni-fileSystemManager/utssdk/app-ios/UniFileSystemManager.swift:1792— src/uni_modules/uni-fileSystemManager/utssdk/app-ios/UniFileSystemManager.swift:1792-1801 | src/uni_modules/uni-fileSystemManager/utssdk/app-ios/UniFileSystemManager.swift:1972-1981 — 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 `src/uni_modules/uni-fileSystemManager/utssdk/app-ios/UniFileSystemManager.swift:1792` 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 (10 lines × 2) src/uni_modules/uni-video/utssdk/app-ios/VideoPlayer/Managers/DRMManager.swift:35— src/uni_modules/uni-video/utssdk/app-ios/VideoPlayer/Managers/DRMManager.swift:35-44 | src/uni_modules/uni-video/utssdk/app-ios/VideoPlayer/Managers/DRMManager.swift:98-107 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) src/uni_modules/uni-form/utssdk/app-ios/UniInputView.swift:105— src/uni_modules/uni-form/utssdk/app-ios/UniInputView.swift:105-114 | src/uni_modules/uni-form/utssdk/app-ios/UniTextareaView.swift:151-160 — before extracting anything, compare `src/uni_modules/uni-form/utssdk/app-ios/UniInputView.swift` and `src/uni_modules/uni-form/utssdk/app-ios/UniTextareaView.swift` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 54 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 × 2) src/uni_modules/uni-createInnerAudioContext/utssdk/app-ios/UniAudioPlayer.swift:472— src/uni_modules/uni-createInnerAudioContext/utssdk/app-ios/UniAudioPlayer.swift:472-481 | src/uni_modules/uni-getBackgroundAudioManager/utssdk/app-ios/UniBackgroundAudioManager.swift:536-545 — before extracting anything, compare `src/uni_modules/uni-createInnerAudioContext/utssdk/app-ios/UniAudioPlayer.swift` and `src/uni_modules/uni-getBackgroundAudioManager/utssdk/app-ios/UniBackgroundAudioManager.swift` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 285 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 2) src/uni_modules/uni-createInnerAudioContext/utssdk/app-android/AudioPlayer.kt:103— src/uni_modules/uni-createInnerAudioContext/utssdk/app-android/AudioPlayer.kt:103-112 | src/uni_modules/uni-getBackgroundAudioManager/utssdk/app-android/BackgroundAudioPlayer.kt:108-117 — before extracting anything, compare `src/uni_modules/uni-createInnerAudioContext/utssdk/app-android/AudioPlayer.kt` and `src/uni_modules/uni-getBackgroundAudioManager/utssdk/app-android/BackgroundAudioPlayer.kt` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 63 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/uni_modules/uni-createInnerAudioContext/utssdk/app-android/AudioPlayer.kt:114` calls `play` and `src/uni_modules/uni-getBackgroundAudioManager/utssdk/app-android/BackgroundAudioPlayer.kt:118` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (10 lines × 2) src/uni_modules/uni-createInnerAudioContext/utssdk/app-android/AudioPlayer.kt:63— src/uni_modules/uni-createInnerAudioContext/utssdk/app-android/AudioPlayer.kt:63-72 | src/uni_modules/uni-getBackgroundAudioManager/utssdk/app-android/BackgroundAudioPlayer.kt:63-72 — before extracting anything, compare `src/uni_modules/uni-createInnerAudioContext/utssdk/app-android/AudioPlayer.kt` and `src/uni_modules/uni-getBackgroundAudioManager/utssdk/app-android/BackgroundAudioPlayer.kt` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 63 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/uni_modules/uni-createInnerAudioContext/utssdk/app-android/AudioPlayer.kt:63` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (10 lines × 2) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/CoreAnimation/Extensions/Keyframes+combined.swift:133— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/CoreAnimation/Extensions/Keyframes+combined.swift:133-142 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/CoreAnimation/Extensions/Keyframes+combined.swift:173-182 — 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 `examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/CoreAnimation/Extensions/Keyframes+combined.swift:133` 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.
MethodTooLong: service.createOrder src/uni_modules/uni-pay-x/uniCloud/cloudfunctions/uni-pay-co/service/pay.js:174— MethodTooLong — createOrder runs 210 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 110 over it, 2.10× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: service.verifyReceiptFromAppleiap src/uni_modules/uni-pay-x/uniCloud/cloudfunctions/uni-pay-co/service/pay.js:874— MethodTooLong — verifyReceiptFromAppleiap runs 189 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 89 over it, 1.89× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: NativeWebViewImpl.initWebView src/uni_modules/uni-web-view/utssdk/app-android/NativeWebViewImpl.kt:296— MethodTooLong — initWebView runs 161 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 61 over it, 1.61× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Service.transitRoute src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/amap.js:735— MethodTooLong — transitRoute runs 141 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 41 over it, 1.41× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: AudioRecorder.startRecording src/uni_modules/uni-recorder/utssdk/app-android/AudioRecorder.kt:140— MethodTooLong — startRecording runs 124 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 24 over it, 1.24× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: UniFileSystemManager.write src/uni_modules/uni-fileSystemManager/utssdk/app-ios/UniFileSystemManager.swift:1788— MethodTooLong — write runs 108 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 8 over it, 1.08× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
D4 · Code Duplication· Edited copy of a member (14 corresponding lines) · ×6
Edited copy of a member (14 corresponding lines) src/uni_modules/uni-map-amap/utssdk/app-android/marker/AmapMarker.kt:34— src/uni_modules/uni-map-amap/utssdk/app-android/marker/AmapMarker.kt:34-51 | src/uni_modules/uni-map-amap/utssdk/app-android/marker/AmapMarker.kt:53-66 — 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) src/uni_modules/uni-createInnerAudioContext/utssdk/app-android/AudioPlayer.kt:59— src/uni_modules/uni-createInnerAudioContext/utssdk/app-android/AudioPlayer.kt:59-72 | src/uni_modules/uni-getBackgroundAudioManager/utssdk/app-android/BackgroundAudioPlayer.kt:59-72 — 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) src/uni_modules/uni-camera/utssdk/app-ios/CameraManager.swift:718— src/uni_modules/uni-camera/utssdk/app-ios/CameraManager.swift:718-731 | src/uni_modules/uni-camera/utssdk/app-ios/CameraManager.swift:1098-1116 — 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) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/ShapeItems/GradientFill.swift:22— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/ShapeItems/GradientFill.swift:22-35 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/ShapeItems/GradientStroke.swift:32-50 — 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) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/ShapeItems/GradientFill.swift:103— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/ShapeItems/GradientFill.swift:103-116 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/ShapeItems/GradientStroke.swift:196-213 — 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) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/CoreAnimation/CoreAnimationLayer.swift:41— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/CoreAnimation/CoreAnimationLayer.swift:41-56 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/Animation/LottieAnimationLayer.swift:81-94 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (7 corresponding lines) · ×6
Edited copy of a member (7 corresponding lines) src/uni_modules/uni-prompt/utssdk/app-ios/UniToast/MCToast+StatusBar.swift:19— src/uni_modules/uni-prompt/utssdk/app-ios/UniToast/MCToast+StatusBar.swift:19-25 | src/uni_modules/uni-prompt/utssdk/app-ios/UniToast/MCToast+StatusBar.swift:38-48 — 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) src/uni_modules/uni-virtualPayment/utssdk/app-ios/UniPurchase.swift:64— src/uni_modules/uni-virtualPayment/utssdk/app-ios/UniPurchase.swift:64-70 | src/uni_modules/uni-virtualPayment/utssdk/app-ios/UniPurchase.swift:72-83 — 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) src/uni_modules/uni-createInnerAudioContext/utssdk/app-ios/UniAudioPlayer.swift:664— src/uni_modules/uni-createInnerAudioContext/utssdk/app-ios/UniAudioPlayer.swift:664-670 | src/uni_modules/uni-getBackgroundAudioManager/utssdk/app-ios/UniBackgroundAudioManager.swift:662-668 — 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) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/ShapeItems/Ellipse.swift:22— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/ShapeItems/Ellipse.swift:22-28 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/ShapeItems/Rectangle.swift:12-19 — 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) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/ShapeItems/Ellipse.swift:57— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/ShapeItems/Ellipse.swift:57-63 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/ShapeItems/Rectangle.swift:53-60 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/Animation/LottieAnimationLayer.swift:392— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/Animation/LottieAnimationLayer.swift:392-398 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/Animation/LottieAnimationView.swift:350-356 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (12 lines × 2) src/uni_modules/uni-dialogPage/utssdk/app-ios/native.swift:35— src/uni_modules/uni-dialogPage/utssdk/app-ios/native.swift:35-46 | src/uni_modules/uni-dialogPage/utssdk/app-ios/native.swift:105-116 — 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 (12 lines × 2) src/uni_modules/uni-media/utssdk/app-ios/utils/UniChooseFileManager.swift:115— src/uni_modules/uni-media/utssdk/app-ios/utils/UniChooseFileManager.swift:115-126 | src/uni_modules/uni-media/utssdk/app-ios/utils/UniChooseFileManager.swift:129-140 — 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 `src/uni_modules/uni-media/utssdk/app-ios/utils/UniChooseFileManager.swift:115` 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 (12 lines × 2) src/uni_modules/uni-prompt/utssdk/app-ios/UniAlert/DCAlertView.Blocks.swift:62— src/uni_modules/uni-prompt/utssdk/app-ios/UniAlert/DCAlertView.Blocks.swift:62-73 | src/uni_modules/uni-prompt/utssdk/app-ios/UniAlert/DCAlertView.Blocks.swift:99-110 — 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 `src/uni_modules/uni-prompt/utssdk/app-ios/UniAlert/DCAlertView.Blocks.swift:62` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (12 lines × 2) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/MainThread/NodeRenderSystem/Nodes/ModifierNodes/TrimPathNode.swift:149— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/MainThread/NodeRenderSystem/Nodes/ModifierNodes/TrimPathNode.swift:149-160 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/MainThread/NodeRenderSystem/Nodes/ModifierNodes/TrimPathNode.swift:179-191 — 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 `examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/MainThread/NodeRenderSystem/Nodes/ModifierNodes/TrimPathNode.swift:149` 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 (12 lines × 2) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/Animation/LottieAnimationLayer.swift:894— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/Animation/LottieAnimationLayer.swift:894-905 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/Animation/LottieAnimationLayer.swift:915-926 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (12 lines × 2) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/Controls/LottieButton.swift:56— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/Controls/LottieButton.swift:56-67 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/Controls/LottieSwitch.swift:59-70 — 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.
AC3 · Page structure· Page without a main landmark · ×5
Page without a main landmark src/hybrid/html/local.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 src/hybrid/html/privacy.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 src/hybrid/html/simple.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 src/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 src/uni_modules/uni-editor/static/editor.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="editor">, so there is no content here to wrap — render the <main> from the component mounted into it.
AC6 · Visual & motion safety· Animation without a prefers-reduced-motion guard · ×5
Animation without a prefers-reduced-motion guard src/wxcomponents/vant/loading/index.vue:50— `.van-loading__spinner` moves (`animation: van-rotate .8s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard src/wxcomponents/vant/loading/index.vue:50— `.van-loading__spinner` moves (`animation: van-rotate var(--loading-spinner-animation-duration,.8s) linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard src/components/uni-collapse-item/uni-collapse-item.vue:122— `.down_arrow` moves (`transition-property: transform`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard src/components/uni-collapse-item/uni-collapse-item.vue:159— `.uni-collapse-item__content-box` moves (`transition-property: transform, opacity`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard examples/hello-uvue/components/uni-collapse-item/uni-collapse-item.vue:93— `.down_arrow` moves (`transition-property: transform`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
No assertions: test attr webview-styles src/pages/component/web-view/web-view.test.js:34— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: Trigger Event src/pages/component/swiper/swiper.test.js:89— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: check_list_item_multiplex src/pages/component/list-view/list-view-multiplex.test.js:20— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: editor-toolbar src/pages/component/editor/editor.test.js:44— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: insertImage src/pages/component/editor/editor.test.js:85— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
D4 · Code Duplication· Edited copy of a member (9 corresponding lines) · ×5
Edited copy of a member (9 corresponding lines) src/uni_modules/uni-form/utssdk/app-ios/UniInputView.swift:53— src/uni_modules/uni-form/utssdk/app-ios/UniInputView.swift:53-61 | src/uni_modules/uni-form/utssdk/app-ios/UniTextareaView.swift:60-68 — 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) src/uni_modules/uni-createInnerAudioContext/utssdk/app-ios/UniAudioPlayer.swift:778— src/uni_modules/uni-createInnerAudioContext/utssdk/app-ios/UniAudioPlayer.swift:778-786 | src/uni_modules/uni-getBackgroundAudioManager/utssdk/app-ios/UniBackgroundAudioManager.swift:801-810 — 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) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/LayerStyles/DropShadowStyle.swift:51— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/LayerStyles/DropShadowStyle.swift:51-59 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/ShapeItems/Stroke.swift:111-121 — 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) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Utility/Primitives/BezierPath.swift:54— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Utility/Primitives/BezierPath.swift:54-62 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Utility/Primitives/BezierPath.swift:64-72 — 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) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/CoreAnimation/Layers/ShapeItemLayer.swift:41— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/CoreAnimation/Layers/ShapeItemLayer.swift:41-49 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/CoreAnimation/Layers/ShapeLayer.swift:66-75 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (10 corresponding lines) · ×5
Edited copy of a member (10 corresponding lines) src/uni_modules/uni-createInnerAudioContext/utssdk/app-android/AudioPlayer.kt:383— src/uni_modules/uni-createInnerAudioContext/utssdk/app-android/AudioPlayer.kt:383-392 | src/uni_modules/uni-createInnerAudioContext/utssdk/app-android/AudioPlayer.kt:394-403 — 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) src/uni_modules/uni-createInnerAudioContext/utssdk/app-android/AudioFocusHelper.kt:81— src/uni_modules/uni-createInnerAudioContext/utssdk/app-android/AudioFocusHelper.kt:81-94 | src/uni_modules/uni-getBackgroundAudioManager/utssdk/app-android/AudioFocusHelper.kt:75-84 — 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) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/Extensions/Bundle.swift:7— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/Extensions/Bundle.swift:7-17 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/Extensions/Bundle.swift:19-28 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Utility/Extensions/MathKit.swift:219— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Utility/Extensions/MathKit.swift:219-228 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Utility/Extensions/MathKit.swift:231-241 — 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) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/CoreAnimation/Layers/ShapeLayer.swift:320— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/CoreAnimation/Layers/ShapeLayer.swift:320-329 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/CoreAnimation/Layers/ShapeLayer.swift:332-341 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (8 lines × 2) src/uni_modules/uni-prompt/utssdk/app-ios/UniToast/MCToast+Loading.swift:51— src/uni_modules/uni-prompt/utssdk/app-ios/UniToast/MCToast+Loading.swift:51-58 | src/uni_modules/uni-prompt/utssdk/app-ios/UniToast/MCToast+Loading.swift:106-113 — 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 `src/uni_modules/uni-prompt/utssdk/app-ios/UniToast/MCToast+Loading.swift:51` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (8 lines × 2) src/uni_modules/uni-form/utssdk/app-ios/UniInputView.swift:44— src/uni_modules/uni-form/utssdk/app-ios/UniInputView.swift:44-51 | src/uni_modules/uni-form/utssdk/app-ios/UniTextareaView.swift:51-58 — before extracting anything, compare `src/uni_modules/uni-form/utssdk/app-ios/UniInputView.swift` and `src/uni_modules/uni-form/utssdk/app-ios/UniTextareaView.swift` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 54 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 (8 lines × 2) src/uni_modules/uni-createInnerAudioContext/utssdk/app-android/AudioPlayer.kt:517— src/uni_modules/uni-createInnerAudioContext/utssdk/app-android/AudioPlayer.kt:517-524 | src/uni_modules/uni-getBackgroundAudioManager/utssdk/app-android/BackgroundAudioPlayer.kt:523-530 — before extracting anything, compare `src/uni_modules/uni-createInnerAudioContext/utssdk/app-android/AudioPlayer.kt` and `src/uni_modules/uni-getBackgroundAudioManager/utssdk/app-android/BackgroundAudioPlayer.kt` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 63 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/uni_modules/uni-createInnerAudioContext/utssdk/app-android/AudioPlayer.kt:517` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/CoreAnimation/Extensions/Keyframes+combined.swift:117— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/CoreAnimation/Extensions/Keyframes+combined.swift:117-124 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/CoreAnimation/Extensions/Keyframes+combined.swift:154-161 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/CoreAnimation/Layers/BaseCompositionLayer.swift:29— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/CoreAnimation/Layers/BaseCompositionLayer.swift:29-36 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/CoreAnimation/Layers/TextLayer.swift:28-35 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (6 lines × 2) src/uni_modules/uni-video/utssdk/app-ios/VideoPlayer/UniVideoPlayerInstance.swift:307— src/uni_modules/uni-video/utssdk/app-ios/VideoPlayer/UniVideoPlayerInstance.swift:307-312 | src/uni_modules/uni-video/utssdk/app-ios/VideoPlayer/UniVideoPlayerView.swift:379-384 — 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 (6 lines × 2) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/MainThread/NodeRenderSystem/Nodes/PathNodes/PolygonNode.swift:17— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/MainThread/NodeRenderSystem/Nodes/PathNodes/PolygonNode.swift:17-22 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/MainThread/NodeRenderSystem/Nodes/PathNodes/StarNode.swift:17-22 — 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 `examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/MainThread/NodeRenderSystem/Nodes/PathNodes/PolygonNode.swift:17` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Utility/Primitives/BezierPathRoundExtension.swift:113— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Utility/Primitives/BezierPathRoundExtension.swift:113-118 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Utility/Primitives/BezierPathRoundExtension.swift:131-136 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/MainThread/NodeRenderSystem/Nodes/ModifierNodes/RoundedCornersNode.swift:39— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/MainThread/NodeRenderSystem/Nodes/ModifierNodes/RoundedCornersNode.swift:39-44 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/MainThread/NodeRenderSystem/Nodes/ModifierNodes/TrimPathNode.swift:49-54 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (6 lines × 2) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/ShapeItems/GradientFill.swift:24— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/ShapeItems/GradientFill.swift:24-29 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/ShapeItems/GradientStroke.swift:34-39 — before extracting anything, compare `examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/ShapeItems/GradientFill.swift` and `examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/ShapeItems/GradientStroke.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 36 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 locations) src/components/api-set-tabbar/api-set-tabbar.vue:74— src/components/api-set-tabbar/api-set-tabbar.vue:74 · src/components/api-set-tabbar/api-set-tabbar.vue:104 — 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 (13 lines × 2 locations) src/uni_modules/uni-editor/static/editor.js:438— src/uni_modules/uni-editor/static/editor.js:438 · src/uni_modules/uni-editor/static/editor.js:457 — 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 (13 lines × 2 locations) src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/amap.js:320— src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/amap.js:320 · src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/qqmap.js:261 — 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 (13 lines × 2 locations) src/uni_modules/uni-pay-x/uniCloud/cloudfunctions/uni-pay-co/index.obj.js:128— src/uni_modules/uni-pay-x/uniCloud/cloudfunctions/uni-pay-co/index.obj.js:128 · src/uni_modules/uni-pay-x/uniCloud/cloudfunctions/uni-pay-co/index.obj.js:282 — 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 (13 lines × 2 locations) src/uni_modules/uni-pay-x/uniCloud/cloudfunctions/uni-pay-co/service/pay.js:676— src/uni_modules/uni-pay-x/uniCloud/cloudfunctions/uni-pay-co/service/pay.js:676 · src/uni_modules/uni-pay-x/uniCloud/cloudfunctions/uni-pay-co/service/pay.js:742 — 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· Edited copy of a member (16 corresponding lines) · ×4
Edited copy of a member (16 corresponding lines) src/uni_modules/uni-web-view/utssdk/app-ios/Snapshot.swift:275— src/uni_modules/uni-web-view/utssdk/app-ios/Snapshot.swift:275-290 | src/uni_modules/uni-web-view/utssdk/app-ios/Snapshot.swift:292-307 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (16 corresponding lines) src/uni_modules/uni-fileSystemManager/utssdk/app-ios/UniFileSystemManager.swift:308— src/uni_modules/uni-fileSystemManager/utssdk/app-ios/UniFileSystemManager.swift:308-323 | src/uni_modules/uni-fileSystemManager/utssdk/app-ios/UniFileSystemManager.swift:353-368 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (16 corresponding lines) src/uni_modules/uni-camera/utssdk/app-ios/CameraManager.swift:1748— src/uni_modules/uni-camera/utssdk/app-ios/CameraManager.swift:1748-1769 | src/uni_modules/uni-camera/utssdk/app-ios/CameraManager.swift:1771-1786 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (16 corresponding lines) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/DotLottie/DotLottieFileHelpers.swift:144— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/DotLottie/DotLottieFileHelpers.swift:144-163 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/DotLottie/DotLottieFileHelpers.swift:186-201 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (8 corresponding lines) · ×4
Edited copy of a member (8 corresponding lines) src/uni_modules/uni-createInnerAudioContext/utssdk/app-ios/UniAudioPlayer.swift:654— src/uni_modules/uni-createInnerAudioContext/utssdk/app-ios/UniAudioPlayer.swift:654-662 | src/uni_modules/uni-getBackgroundAudioManager/utssdk/app-ios/UniBackgroundAudioManager.swift:653-660 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) src/uni_modules/uni-createInnerAudioContext/utssdk/app-ios/UniAudioPlayer.swift:484— src/uni_modules/uni-createInnerAudioContext/utssdk/app-ios/UniAudioPlayer.swift:484-491 | src/uni_modules/uni-getBackgroundAudioManager/utssdk/app-ios/UniBackgroundAudioManager.swift:548-555 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) src/uni_modules/uni-video/utssdk/app-ios/VideoPlayer/UniVideoPlayerInstance.swift:297— src/uni_modules/uni-video/utssdk/app-ios/VideoPlayer/UniVideoPlayerInstance.swift:297-304 | src/uni_modules/uni-video/utssdk/app-ios/VideoPlayer/UniVideoPlayerView.swift:368-376 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) src/uni_modules/uni-createInnerAudioContext/utssdk/app-ios/UniAudioPlayer.swift:344— src/uni_modules/uni-createInnerAudioContext/utssdk/app-ios/UniAudioPlayer.swift:344-351 | src/uni_modules/uni-getBackgroundAudioManager/utssdk/app-ios/UniBackgroundAudioManager.swift:401-409 — 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.
SC1 · Supply-chain hygiene· JavaScript dependencies are not locked · ×4
JavaScript dependencies are not locked src/uni_modules/uni-id-common/uniCloud/cloudfunctions/common/uni-id-common/package.json:13— src/uni_modules/uni-id-common/uniCloud/cloudfunctions/common/uni-id-common/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / REDACTED / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
JavaScript dependencies are not locked src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/package.json:12— src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / REDACTED / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
JavaScript dependencies are not locked src/uni_modules/uni-map-common/uniCloud/cloudfunctions/uni-map-co/package.json:3— src/uni_modules/uni-map-common/uniCloud/cloudfunctions/uni-map-co/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / REDACTED / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
JavaScript dependencies are not locked src/uni_modules/uni-pay-x/uniCloud/cloudfunctions/uni-pay-co/package.json:3— src/uni_modules/uni-pay-x/uniCloud/cloudfunctions/uni-pay-co/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / REDACTED / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
D4 · Code Duplication· Edited copy of a member (29 corresponding lines) · ×3
Edited copy of a member (29 corresponding lines) src/uni_modules/uni-dialogPage/utssdk/app-ios/native.swift:149— src/uni_modules/uni-dialogPage/utssdk/app-ios/native.swift:149-177 | src/uni_modules/uni-dialogPage/utssdk/app-ios/native.swift:179-207 — These two members are one piece of code written twice and then edited apart: 29 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 (29 corresponding lines) src/uni_modules/uni-camera/utssdk/app-android/CameraImpl.kt:475— src/uni_modules/uni-camera/utssdk/app-android/CameraImpl.kt:475-505 | src/uni_modules/uni-camera/utssdk/app-android/CameraImpl.kt:883-911 — These two members are one piece of code written twice and then edited apart: 29 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 (29 corresponding lines) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/CoreAnimation/Layers/ShapeItemLayer.swift:151— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/CoreAnimation/Layers/ShapeItemLayer.swift:151-185 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/CoreAnimation/Layers/ShapeItemLayer.swift:187-215 — These two members are one piece of code written twice and then edited apart: 29 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) src/uni_modules/uni-createInnerAudioContext/utssdk/app-android/AudioFocusHelper.kt:52— src/uni_modules/uni-createInnerAudioContext/utssdk/app-android/AudioFocusHelper.kt:52-78 | src/uni_modules/uni-getBackgroundAudioManager/utssdk/app-android/AudioFocusHelper.kt:51-72 — 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) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/Animation/LottieAnimationView.swift:99— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/Animation/LottieAnimationView.swift:99-120 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/Animation/LottieAnimationView.swift:123-144 — 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) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/CoreAnimation/Layers/MaskCompositionLayer.swift:13— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/CoreAnimation/Layers/MaskCompositionLayer.swift:13-34 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/MainThread/LayerContainers/CompLayers/MaskContainerLayer.swift:37-58 — 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 (12 corresponding lines) · ×3
Edited copy of a member (12 corresponding lines) src/uni_modules/uni-createInnerAudioContext/utssdk/app-android/AudioPlayer.kt:102— src/uni_modules/uni-createInnerAudioContext/utssdk/app-android/AudioPlayer.kt:102-116 | src/uni_modules/uni-getBackgroundAudioManager/utssdk/app-android/BackgroundAudioPlayer.kt:107-118 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/Animation/LottieView.swift:404— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/Animation/LottieView.swift:404-415 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/Animation/LottieView.swift:424-435 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/Animation/LottieAnimationView.swift:156— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/Animation/LottieAnimationView.swift:156-167 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/Animation/LottieAnimationView.swift:169-180 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (15 corresponding lines) · ×3
Edited copy of a member (15 corresponding lines) src/uni_modules/uni-barcode-scanning/utssdk/app-android/Scanner.kt:367— src/uni_modules/uni-barcode-scanning/utssdk/app-android/Scanner.kt:367-381 | src/uni_modules/uni-camera/utssdk/app-android/CameraImpl.kt:605-619 — 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) src/uni_modules/uni-camera/utssdk/app-android/CameraImpl.kt:803— src/uni_modules/uni-camera/utssdk/app-android/CameraImpl.kt:803-819 | src/uni_modules/uni-camera/utssdk/app-android/CameraImpl.kt:845-859 — 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) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/ShapeItems/Ellipse.swift:30— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/ShapeItems/Ellipse.swift:30-44 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/ShapeItems/Rectangle.swift:21-37 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (5 corresponding lines) · ×3
Edited copy of a member (5 corresponding lines) src/uni_modules/uni-prompt/utssdk/app-ios/UniAlert/DCActionSheetController.swift:131— src/uni_modules/uni-prompt/utssdk/app-ios/UniAlert/DCActionSheetController.swift:131-135 | src/uni_modules/uni-prompt/utssdk/app-ios/UniAlert/DCAlertViewController.swift:231-235 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (5 corresponding lines) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/Layers/ShapeLayerModel.swift:13— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/Layers/ShapeLayerModel.swift:13-17 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/ShapeItems/Group.swift:13-17 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (5 corresponding lines) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/Text/Font.swift:14— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/Text/Font.swift:14-19 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/Objects/Marker.swift:13-17 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (4 corresponding lines) · ×3
Edited copy of a member (4 corresponding lines) src/uni_modules/uni-createInnerAudioContext/utssdk/app-ios/UniAudioPlayer.swift:891— src/uni_modules/uni-createInnerAudioContext/utssdk/app-ios/UniAudioPlayer.swift:891-894 | src/uni_modules/uni-getBackgroundAudioManager/utssdk/app-ios/UniBackgroundAudioManager.swift:1090-1093 — 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) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/ShapeItems/ShapeItem.swift:88— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/ShapeItems/ShapeItem.swift:88-92 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/LayerStyles/LayerStyle.swift:43-46 — 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) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/iOS/FilepathImageProvider.swift:22— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/iOS/FilepathImageProvider.swift:22-25 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/macOS/FilepathImageProvider.macOS.swift:21-24 — 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.
Duplicated block (13 lines × 2) src/uni_modules/uni-form/utssdk/app-ios/UniInputView.swift:91— src/uni_modules/uni-form/utssdk/app-ios/UniInputView.swift:91-103 | src/uni_modules/uni-form/utssdk/app-ios/UniTextareaView.swift:137-149 — before extracting anything, compare `src/uni_modules/uni-form/utssdk/app-ios/UniInputView.swift` and `src/uni_modules/uni-form/utssdk/app-ios/UniTextareaView.swift` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 54 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) src/uni_modules/uni-barcode-scanning/utssdk/app-android/Scanner.kt:369— src/uni_modules/uni-barcode-scanning/utssdk/app-android/Scanner.kt:369-381 | src/uni_modules/uni-camera/utssdk/app-android/CameraImpl.kt:607-619 — 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 `src/uni_modules/uni-barcode-scanning/utssdk/app-android/Scanner.kt:369` 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 (13 lines × 2) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Utility/Primitives/BezierPath.swift:340— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Utility/Primitives/BezierPath.swift:340-352 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Utility/Primitives/BezierPath.swift:445-458 — 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 `examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Utility/Primitives/BezierPath.swift:340` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication· Edited copies of one member (3 members, 7+ corresponding lines) · ×3
Edited copies of one member (3 members, 7+ corresponding lines) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/Assets/ImageAsset.swift:23— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/Assets/ImageAsset.swift:23-30 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/Layers/PreCompLayerModel.swift:13-20 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/Layers/SolidLayerModel.swift:13-19 — 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.
Edited copies of one member (3 members, 7+ corresponding lines) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/Assets/ImageAsset.swift:53— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/Assets/ImageAsset.swift:53-60 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/Layers/PreCompLayerModel.swift:48-55 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/Layers/SolidLayerModel.swift:39-45 — 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.
Edited copies of one member (3 members, 7+ corresponding lines) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/Animation/LottieView.swift:148— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/Animation/LottieView.swift:148-154 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/Controls/LottieButton.swift:47-53 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/Controls/LottieSwitch.swift:50-56 — 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· Edited copy of a member (11 corresponding lines) · ×3
Edited copy of a member (11 corresponding lines) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/MainThread/NodeRenderSystem/Nodes/PathNodes/EllipseNode.swift:17— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/MainThread/NodeRenderSystem/Nodes/PathNodes/EllipseNode.swift:17-27 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/MainThread/NodeRenderSystem/Nodes/PathNodes/RectNode.swift:17-31 — 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) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/MainThread/NodeRenderSystem/Nodes/PathNodes/PolygonNode.swift:90— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/MainThread/NodeRenderSystem/Nodes/PathNodes/PolygonNode.swift:90-100 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/MainThread/NodeRenderSystem/Nodes/PathNodes/StarNode.swift:101-113 — 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) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/MainThread/LayerContainers/MainThreadAnimationLayer.swift:243— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/MainThread/LayerContainers/MainThreadAnimationLayer.swift:243-253 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/MainThread/LayerContainers/MainThreadAnimationLayer.swift:255-265 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (6 corresponding lines) · ×3
Edited copy of a member (6 corresponding lines) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/LayerEffects/LayerEffect.swift:38— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/LayerEffects/LayerEffect.swift:38-43 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/ShapeItems/ShapeItem.swift:81-86 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/Assets/ImageAsset.swift:32— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/Assets/ImageAsset.swift:32-38 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/Layers/SolidLayerModel.swift:21-26 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Utility/Primitives/ColorExtension.swift:56— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Utility/Primitives/ColorExtension.swift:56-62 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Utility/Primitives/VectorsExtensions.swift:201-206 — 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.
Sync-over-async blocking examples/hello-uts/jest.global.js:35— `readdirSync` in `parseDescribes` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking examples/hello-uts/jest.global.js:37— `readFileSync` in `callback to forEach` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking src/uni_modules/uni-pay-x/uniCloud/cloudfunctions/uni-pay-co/service/pay.js:912— `fs.readFileSync` in `verifyReceipt` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Duplicated block (21 lines × 2 locations) src/uni_modules/uni-editor/static/editor.js:1110— src/uni_modules/uni-editor/static/editor.js:1110 · src/uni_modules/uni-editor/static/editor.js:1137 — 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 (21 lines × 2 locations) src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/amap.js:225— src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/amap.js:225 · src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/qqmap.js:164 — 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 (21 lines × 2 locations) src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/amap.js:272— src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/amap.js:272 · src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/qqmap.js:200 — 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.
AC1 · Text alternatives· <video> without a captions track · ×2
<video> without a captions track src/hybrid/html/local.html:47— Video with no captions <track> offers no captions. Add a <track kind="captions"> pointing at a WebVTT file for this video (or confirm captions are provided another way).
<video> without a captions track src/hybrid/html/local.html:49— Video with no captions <track> offers no captions. Add a <track kind="captions"> pointing at a WebVTT file for this video (or confirm captions are provided another way).
AC6 · Visual & motion safety· Focus outline removed in CSS without a · ×2
Focus outline removed in CSS without a :focus replacement src/uni_modules/uni-editor/static/editor.css:15— `.ql-container` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement src/uni_modules/uni-editor/static/editor.css:136— `.ql-editor` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
D4 · Code Duplication· Edited copy of a member (18 corresponding lines) · ×2
Edited copy of a member (18 corresponding lines) src/uni_modules/uni-createInnerAudioContext/utssdk/app-ios/UniAudioPlayer.swift:788— src/uni_modules/uni-createInnerAudioContext/utssdk/app-ios/UniAudioPlayer.swift:788-805 | src/uni_modules/uni-getBackgroundAudioManager/utssdk/app-ios/UniBackgroundAudioManager.swift:812-834 — 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) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/Controls/AnimatedSwitch.swift:26— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/Controls/AnimatedSwitch.swift:26-45 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/Controls/AnimatedSwitch.swift:47-64 — 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 copies of one member (3 members, 31+ corresponding lines) · ×2
Edited copies of one member (3 members, 31+ corresponding lines) src/uni_modules/uni-fileSystemManager/utssdk/app-ios/UniFileTools.swift:33— src/uni_modules/uni-fileSystemManager/utssdk/app-ios/UniFileTools.swift:33-63 | src/uni_modules/uni-fileSystemManager/utssdk/app-ios/UniFileTools.swift:65-95 | src/uni_modules/uni-fileSystemManager/utssdk/app-ios/UniFileTools.swift:97-127 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 31 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 31+ corresponding lines) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/CoreAnimation/Extensions/Keyframes+combined.swift:81— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/CoreAnimation/Extensions/Keyframes+combined.swift:81-111 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/CoreAnimation/Extensions/Keyframes+combined.swift:116-148 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/CoreAnimation/Extensions/Keyframes+combined.swift:153-190 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 31 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (31 corresponding lines) · ×2
Edited copy of a member (31 corresponding lines) src/uni_modules/uni-createInnerAudioContext/utssdk/app-android/AudioPlayer.kt:515— src/uni_modules/uni-createInnerAudioContext/utssdk/app-android/AudioPlayer.kt:515-545 | src/uni_modules/uni-getBackgroundAudioManager/utssdk/app-android/BackgroundAudioPlayer.kt:520-551 — These two members are one piece of code written twice and then edited apart: 31 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 (31 corresponding lines) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/Animation/LottieAnimationHelpers.swift:41— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/Animation/LottieAnimationHelpers.swift:41-71 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/Animation/LottieAnimationHelpers.swift:111-144 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (17 corresponding lines) · ×2
Edited copy of a member (17 corresponding lines) src/uni_modules/uni-createInnerAudioContext/utssdk/app-ios/UniAudioPlayer.swift:815— src/uni_modules/uni-createInnerAudioContext/utssdk/app-ios/UniAudioPlayer.swift:815-831 | src/uni_modules/uni-getBackgroundAudioManager/utssdk/app-ios/UniBackgroundAudioManager.swift:837-855 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (17 corresponding lines) src/uni_modules/uni-createInnerAudioContext/utssdk/app-ios/UniAudioPlayer.swift:873— src/uni_modules/uni-createInnerAudioContext/utssdk/app-ios/UniAudioPlayer.swift:873-889 | src/uni_modules/uni-getBackgroundAudioManager/utssdk/app-ios/UniBackgroundAudioManager.swift:1072-1088 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (27 corresponding lines) · ×2
Edited copy of a member (27 corresponding lines) src/uni_modules/uni-fileSystemManager/utssdk/app-ios/UniFileSystemManager.swift:897— src/uni_modules/uni-fileSystemManager/utssdk/app-ios/UniFileSystemManager.swift:897-924 | src/uni_modules/uni-fileSystemManager/utssdk/app-ios/UniFileSystemManager.swift:1116-1142 — 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) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/Animation/LottieAnimationLayer.swift:132— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/Animation/LottieAnimationLayer.swift:132-159 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/Animation/LottieAnimationLayer.swift:167-193 — 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 (19 corresponding lines) · ×2
Edited copy of a member (19 corresponding lines) src/uni_modules/uni-createInnerAudioContext/utssdk/app-android/AudioPlayer.kt:547— src/uni_modules/uni-createInnerAudioContext/utssdk/app-android/AudioPlayer.kt:547-565 | src/uni_modules/uni-getBackgroundAudioManager/utssdk/app-android/BackgroundAudioPlayer.kt:494-518 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (19 corresponding lines) src/uni_modules/uni-fileSystemManager/utssdk/app-ios/UniFileSystemManager.swift:284— src/uni_modules/uni-fileSystemManager/utssdk/app-ios/UniFileSystemManager.swift:284-303 | src/uni_modules/uni-fileSystemManager/utssdk/app-ios/UniFileSystemManager.swift:328-346 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (24 lines × 2) src/uni_modules/uni-createInnerAudioContext/utssdk/app-ios/UniAudioPlayer.swift:896— src/uni_modules/uni-createInnerAudioContext/utssdk/app-ios/UniAudioPlayer.swift:896-919 | src/uni_modules/uni-getBackgroundAudioManager/utssdk/app-ios/UniBackgroundAudioManager.swift:1095-1118 — before extracting anything, compare `src/uni_modules/uni-createInnerAudioContext/utssdk/app-ios/UniAudioPlayer.swift` and `src/uni_modules/uni-getBackgroundAudioManager/utssdk/app-ios/UniBackgroundAudioManager.swift` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 285 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (24 lines × 2) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/MainThread/NodeRenderSystem/Nodes/OutputNodes/Renderables/GradientFillRenderer.swift:45— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/MainThread/NodeRenderSystem/Nodes/OutputNodes/Renderables/GradientFillRenderer.swift:45-68 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/MainThread/NodeRenderSystem/Nodes/OutputNodes/Renderables/LegacyGradientFillRenderer.swift:64-87 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/MainThread/NodeRenderSystem/Nodes/OutputNodes/Renderables/LegacyGradientFillRenderer.swift:89` calls `setAlpha`, `clip` and `examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/MainThread/NodeRenderSystem/Nodes/OutputNodes/Renderables/GradientFillRenderer.swift:71` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (20 lines × 2) src/uni_modules/uni-createInnerAudioContext/utssdk/app-ios/UniAudioPlayer.swift:921— src/uni_modules/uni-createInnerAudioContext/utssdk/app-ios/UniAudioPlayer.swift:921-940 | src/uni_modules/uni-getBackgroundAudioManager/utssdk/app-ios/UniBackgroundAudioManager.swift:1120-1139 — before extracting anything, compare `src/uni_modules/uni-createInnerAudioContext/utssdk/app-ios/UniAudioPlayer.swift` and `src/uni_modules/uni-getBackgroundAudioManager/utssdk/app-ios/UniBackgroundAudioManager.swift` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 285 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (20 lines × 2) src/uni_modules/uni-camera/utssdk/app-android/CameraImpl.kt:424— src/uni_modules/uni-camera/utssdk/app-android/CameraImpl.kt:424-443 | src/uni_modules/uni-camera/utssdk/app-android/CameraImpl.kt:887-906 — 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 `src/uni_modules/uni-camera/utssdk/app-android/CameraImpl.kt:424` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (16–17 lines × 2) src/uni_modules/uni-fileSystemManager/utssdk/app-ios/UniFileSystemManager.swift:701— src/uni_modules/uni-fileSystemManager/utssdk/app-ios/UniFileSystemManager.swift:701-717 | src/uni_modules/uni-fileSystemManager/utssdk/app-ios/UniFileSystemManager.swift:1990-2005 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (16–17 lines × 2) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/MainThread/NodeRenderSystem/Nodes/ModifierNodes/TrimPathNode.swift:117— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/MainThread/NodeRenderSystem/Nodes/ModifierNodes/TrimPathNode.swift:117-132 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Utility/Primitives/CompoundBezierPath.swift:77-93 — 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 (13–14 lines × 2) src/uni_modules/uni-fileSystemManager/utssdk/app-ios/UniFileSystemManager.swift:1150— src/uni_modules/uni-fileSystemManager/utssdk/app-ios/UniFileSystemManager.swift:1150-1162 | src/uni_modules/uni-fileSystemManager/utssdk/app-ios/UniFileSystemManager.swift:1565-1578 — 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 `src/uni_modules/uni-fileSystemManager/utssdk/app-ios/UniFileSystemManager.swift:1150` 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 (13–14 lines × 2) src/uni_modules/uni-prompt/utssdk/app-ios/UniAlert/DCAlertViewController.swift:405— src/uni_modules/uni-prompt/utssdk/app-ios/UniAlert/DCAlertViewController.swift:405-418 | src/uni_modules/uni-prompt/utssdk/app-ios/UniAlert/DCBottomMenuController.swift:299-311 — 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 `src/uni_modules/uni-prompt/utssdk/app-ios/UniAlert/DCAlertViewController.swift:405` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11–12 lines × 2) src/uni_modules/uni-fileSystemManager/utssdk/app-ios/UniFileSystemManager.swift:899— src/uni_modules/uni-fileSystemManager/utssdk/app-ios/UniFileSystemManager.swift:899-910 | src/uni_modules/uni-fileSystemManager/utssdk/app-ios/UniFileSystemManager.swift:1658-1668 — 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 `src/uni_modules/uni-fileSystemManager/utssdk/app-ios/UniFileSystemManager.swift:899` 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) src/uni_modules/uni-prompt/utssdk/app-ios/UniAlert/DCBottomMenuController.swift:296— src/uni_modules/uni-prompt/utssdk/app-ios/UniAlert/DCBottomMenuController.swift:296-306 | src/uni_modules/uni-prompt/utssdk/app-ios/UniAlert/DCBottomMenuController.swift:316-327 — 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 `src/uni_modules/uni-prompt/utssdk/app-ios/UniAlert/DCBottomMenuController.swift:316` 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 (9 lines × 2) src/uni_modules/uni-web-view/utssdk/app-ios/Snapshot.swift:142— src/uni_modules/uni-web-view/utssdk/app-ios/Snapshot.swift:142-150 | src/uni_modules/uni-web-view/utssdk/app-ios/Snapshot.swift:157-165 — 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) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/ShapeItems/GradientFill.swift:103— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/ShapeItems/GradientFill.swift:103-111 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/ShapeItems/GradientStroke.swift:196-204 — before extracting anything, compare `examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/ShapeItems/GradientFill.swift` and `examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/ShapeItems/GradientStroke.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 36 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 `examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/ShapeItems/GradientFill.swift:103` 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, `examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/ShapeItems/GradientFill.swift:112` calls `encodeIfPresent`, `nestedContainer` and `examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/ShapeItems/GradientStroke.swift:205` 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· Edited copy of a member (23 corresponding lines) · ×2
Edited copy of a member (23 corresponding lines) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/CoreAnimation/Layers/ShapeItemLayer.swift:217— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/CoreAnimation/Layers/ShapeItemLayer.swift:217-247 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/CoreAnimation/Layers/ShapeItemLayer.swift:274-296 — These two members are one piece of code written twice and then edited apart: 23 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 (23 corresponding lines) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/CoreAnimation/Animations/StarAnimation.swift:30— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/CoreAnimation/Animations/StarAnimation.swift:30-54 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/CoreAnimation/Animations/StarAnimation.swift:56-78 — These two members are one piece of code written twice and then edited apart: 23 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 (21 corresponding lines) · ×2
Edited copy of a member (21 corresponding lines) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/CoreAnimation/Extensions/Keyframes+combined.swift:30— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/CoreAnimation/Extensions/Keyframes+combined.swift:30-50 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/CoreAnimation/Extensions/Keyframes+combined.swift:55-76 — 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.
Edited copy of a member (21 corresponding lines) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/Animation/LottieAnimationLayer.swift:17— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/Animation/LottieAnimationLayer.swift:17-37 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/Animation/LottieAnimationLayer.swift:40-63 — 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.
Duplicated block (19 lines × 2) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/ShapeItems/GradientStroke.swift:74— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/ShapeItems/GradientStroke.swift:74-92 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/ShapeItems/Stroke.swift:29-47 — 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 (19 lines × 2) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/Animation/LottieAnimationView.swift:102— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/Animation/LottieAnimationView.swift:102-120 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/Animation/LottieAnimationView.swift:126-144 — 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 `examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/Animation/LottieAnimationView.swift:102` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (9 lines × 3) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/CoreAnimation/Extensions/Keyframes+combined.swift:97— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/CoreAnimation/Extensions/Keyframes+combined.swift:97-105 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/CoreAnimation/Extensions/Keyframes+combined.swift:133-141 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/CoreAnimation/Extensions/Keyframes+combined.swift:173-181 — 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 `examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/CoreAnimation/Extensions/Keyframes+combined.swift:97` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 3) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/Animation/LottieAnimationViewInitializers.swift:121— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/Animation/LottieAnimationViewInitializers.swift:121-129 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/Animation/LottieAnimationViewInitializers.swift:175-183 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/Animation/LottieAnimationViewInitializers.swift:202-210 — 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 `examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/Animation/LottieAnimationViewInitializers.swift:121` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 3) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/LayerStyles/DropShadowStyle.swift:51— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/LayerStyles/DropShadowStyle.swift:51-55 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/ShapeItems/Fill.swift:57-61 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/ShapeItems/Stroke.swift:111-115 — 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 `examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/LayerStyles/DropShadowStyle.swift:51` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/LayerStyles/DropShadowStyle.swift:57` calls `encode` and `examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/ShapeItems/Fill.swift:63` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (5 lines × 3) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/ShapeItems/Ellipse.swift:57— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/ShapeItems/Ellipse.swift:57-61 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/ShapeItems/Rectangle.swift:53-57 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/ShapeItems/Star.swift:102-106 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/ShapeItems/Ellipse.swift:57` 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, `examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/ShapeItems/Rectangle.swift:59` calls `encode` and `examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/ShapeItems/Ellipse.swift:63` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (20 lines × 2 locations) src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/amap.js:190— src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/amap.js:190 · src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/qqmap.js:129 — 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) src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/qqmap.js:270— src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/qqmap.js:270 · src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/qqmap.js:352 — 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 lines × 2 locations) src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/amap.js:133— src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/amap.js:133 · src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/qqmap.js:105 — 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 (10 lines × 2 locations) src/uni_modules/uni-map-common/uniCloud/cloudfunctions/uni-map-co/index.obj.js:301— src/uni_modules/uni-map-common/uniCloud/cloudfunctions/uni-map-co/index.obj.js:301 · src/uni_modules/uni-map-common/uniCloud/cloudfunctions/uni-map-co/index.obj.js:377 — 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.
Dead file (~48 LoC) src/env.js— no import path from any entry point (42 application, 21 tooling, 232 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 (~48 LoC) src/wxcomponents/vant/common/component.js— no import path from any entry point (42 application, 21 tooling, 232 test roots considered), but 8 in-repo import(s) from 8 other file(s) do name it (src/wxcomponents/vant/button/index.js, src/wxcomponents/vant/button/index.vue, src/wxcomponents/vant/icon/index.js and 5 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~32 LoC) src/wxcomponents/vant/common/utils.js— no import path from any entry point (42 application, 21 tooling, 232 test roots considered), but 5 in-repo import(s) from 5 other file(s) do name it (src/wxcomponents/vant/icon/index.js, src/wxcomponents/vant/icon/index.vue, src/wxcomponents/vant/loading/index.js and 2 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~32 LoC) src/wxcomponents/vant/loading/index.js— no import path from any entry point (42 application, 21 tooling, 232 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
Low contrast colour pair in CSS (4.0:1) src/hybrid/html/local.html:9— `.btn` sets color: #ffffff on background-color: #007aff — 4.0:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (4.4:1) src/wxcomponents/vant/info/index.vue:19— `.van-info` sets color: #fff on background-color: #ee0a24 — 4.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (2.4:1) src/uni_modules/uni-upgrade-center-app/pages/upgrade-popup.vue:610— `.content-body-version` sets color: #fff on background-color: #50aefd — 2.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (3.5:1) src/uni_modules/uni-editor/static/editor.css:60— `.ql-container .ql-image-overlay .ql-image-size` sets color: #888 on background-color: #fff — 3.5:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
service.createOrder (cyclomatic 56) src/uni_modules/uni-pay-x/uniCloud/cloudfunctions/uni-pay-co/service/pay.js:174— service.createOrder has cyclomatic complexity 56 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AudioRecorder.startRecording (cyclomatic 42) src/uni_modules/uni-recorder/utssdk/app-android/AudioRecorder.kt:140— AudioRecorder.startRecording has cyclomatic complexity 42 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CameraManager._setupOutputMode (cyclomatic 31) src/uni_modules/uni-camera/utssdk/app-ios/CameraManager.swift:1481— CameraManager._setupOutputMode has cyclomatic complexity 31 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
NativeWebViewImpl.initWebView (cyclomatic 31) src/uni_modules/uni-web-view/utssdk/app-android/NativeWebViewImpl.kt:296— NativeWebViewImpl.initWebView has cyclomatic complexity 31 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
UniFileSystemManager.write (cyclomatic 29) src/uni_modules/uni-fileSystemManager/utssdk/app-ios/UniFileSystemManager.swift:1788— UniFileSystemManager.write has cyclomatic complexity 29 (threshold 15). Most of this is not in the body itself: 10 of the 29 points are its own statements and the rest belongs to 5 function items inside it that branch (safeWrite, safeWrite::normalizedWriteRange, safeWrite::seekAndFillGapIfNeeded, …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
service.verifyReceiptFromAppleiap (cyclomatic 28) src/uni_modules/uni-pay-x/uniCloud/cloudfunctions/uni-pay-co/service/pay.js:874— service.verifyReceiptFromAppleiap has cyclomatic complexity 28 (threshold 15). Of this number, 20 points are the body's own statements and 8 belong to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
DCAlertContentView.sizeToFits (cyclomatic 27) src/uni_modules/uni-prompt/utssdk/app-ios/UniAlert/DCAlertContentView.swift:105— DCAlertContentView.sizeToFits has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Scanner._processScanBarCode (cyclomatic 24) src/uni_modules/uni-barcode-scanning/utssdk/app-ios/Scanner.swift:141— Scanner._processScanBarCode has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
NetworkQualityInfo.qualityLevel (cyclomatic 24) src/uni_modules/uni-getNetworkType/utssdk/app-ios/UniNetWorkManager.swift:149— NetworkQualityInfo.qualityLevel has cyclomatic complexity 24 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
UniAudioPlayer.updatePlayerItem (cyclomatic 23) src/uni_modules/uni-createInnerAudioContext/utssdk/app-ios/UniAudioPlayer.swift:556— UniAudioPlayer.updatePlayerItem has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
UniBackgroundAudioManager.updatePlayerItem (cyclomatic 23) src/uni_modules/uni-getBackgroundAudioManager/utssdk/app-ios/UniBackgroundAudioManager.swift:558— UniBackgroundAudioManager.updatePlayerItem has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
UniNetWorkManager.calculateQualityChange (cyclomatic 23) src/uni_modules/uni-getNetworkType/utssdk/app-ios/UniNetWorkManager.swift:979— UniNetWorkManager.calculateQualityChange has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
UniEditor.format (cyclomatic 23) src/uni_modules/uni-editor/static/editor.js:330— UniEditor.format has cyclomatic complexity 23 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
_getSign (cyclomatic 23) src/uni_modules/uni-pay-x/uniCloud/cloudfunctions/uni-pay-co/libs/alipay.js:63— _getSign has cyclomatic complexity 23 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
DCBottomMenuControllerAnimator.animateTransition (cyclomatic 21) src/uni_modules/uni-prompt/utssdk/app-ios/UniAlert/DCBottomMenuController.swift:260— DCBottomMenuControllerAnimator.animateTransition has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
UniInternalWebView.dispatchTouchEvent (cyclomatic 21) src/uni_modules/uni-web-view/utssdk/app-android/NativeWebViewImpl.kt:823— UniInternalWebView.dispatchTouchEvent has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
UniAudioRecorderManager.isValidEncodeBitRate (cyclomatic 20) src/uni_modules/uni-recorder/utssdk/app-ios/UniAudioRecorderManager.swift:390— UniAudioRecorderManager.isValidEncodeBitRate has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
UniVideoPlayerView.videoPlayer (cyclomatic 20) src/uni_modules/uni-video/utssdk/app-ios/VideoPlayer/UniVideoPlayerView.swift:668— UniVideoPlayerView.videoPlayer has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
formats.list (cyclomatic 20) src/uni_modules/uni-editor/static/quill/formats.js:95— formats.list has cyclomatic complexity 20 (threshold 15). Of this number, 17 points are the body's own statements and 3 belong to one function item inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
UniFileSystemManager.readFile (cyclomatic 19) src/uni_modules/uni-fileSystemManager/utssdk/app-ios/UniFileSystemManager.swift:668— UniFileSystemManager.readFile has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 8 of the 19 points are its own statements and the rest belongs to 2 function items inside it that branch (safeRead, safeRead::safeUTF8String). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest. This is NOT this file's highest cyclomatic complexity: UniFileSystemManagerError.errorCode (cyclomatic 27) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
UniFileSystemManager.writeFile (cyclomatic 19) src/uni_modules/uni-fileSystemManager/utssdk/app-ios/UniFileSystemManager.swift:790— UniFileSystemManager.writeFile has cyclomatic complexity 19 (threshold 15). Of this number, 13 points are the body's own statements and 6 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This is NOT this file's highest cyclomatic complexity: UniFileSystemManagerError.errorCode (cyclomatic 27) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
UniShareWithSystem.sendWithSystem (cyclomatic 19) src/uni_modules/uni-shareWithSystem/utssdk/app-android/UniShareWithSystem.kt:16— UniShareWithSystem.sendWithSystem has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
service.getOrder (cyclomatic 19) src/uni_modules/uni-pay-x/uniCloud/cloudfunctions/uni-pay-co/service/pay.js:463— service.getOrder has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
M3U8ResourceLoaderDelegate.handleTSRequest (cyclomatic 18) src/uni_modules/uni-video/utssdk/app-ios/VideoPlayer/Protocols/M3U8ResourceLoaderDelegate.swift:152— M3U8ResourceLoaderDelegate.handleTSRequest has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Scanner._processScanBarCode (cyclomatic 18) src/uni_modules/uni-barcode-scanning/utssdk/app-android/Scanner.kt:184— Scanner._processScanBarCode has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
DCAlertViewControllerAnimator.animateTransition (cyclomatic 17) src/uni_modules/uni-prompt/utssdk/app-ios/UniAlert/DCAlertViewController.swift:363— DCAlertViewControllerAnimator.animateTransition has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
UniVideoPlayerManager.setupObservers (cyclomatic 17) src/uni_modules/uni-video/utssdk/app-ios/VideoPlayer/Managers/UniVideoPlayerManager.swift:799— UniVideoPlayerManager.setupObservers has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
UniFileSystemManager.openFile (cyclomatic 16) src/uni_modules/uni-fileSystemManager/utssdk/app-ios/UniFileSystemManager.swift:137— UniFileSystemManager.openFile has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This is NOT this file's highest cyclomatic complexity: UniFileSystemManagerError.errorCode (cyclomatic 27) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
service.refund (cyclomatic 16) src/uni_modules/uni-pay-x/uniCloud/cloudfunctions/uni-pay-co/service/pay.js:565— service.refund has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
service.createOrder (cognitive 84) src/uni_modules/uni-pay-x/uniCloud/cloudfunctions/uni-pay-co/service/pay.js:174— service.createOrder has cognitive complexity 84 (threshold 15). Drivers by points: if/else 40 (66 pts), boolean chains 15, ternaries 1 (2 pts), error handling 1 (nesting depth added 27). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Scanner._processScanBarCode (cognitive 71) src/uni_modules/uni-barcode-scanning/utssdk/app-ios/Scanner.swift:141— Scanner._processScanBarCode has cognitive complexity 71 (threshold 15). Drivers by points: if/else 16 (54 pts), loops 2 (8 pts), boolean chains 7, error handling 1 (2 pts) (nesting depth added 45). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
AudioRecorder.startRecording (cognitive 55) src/uni_modules/uni-recorder/utssdk/app-android/AudioRecorder.kt:140— AudioRecorder.startRecording has cognitive complexity 55 (threshold 15). Drivers by points: if/else 22 (36 pts), boolean chains 9, match/switch 2 (5 pts), error handling 4, loops 1 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CameraManager._setupOutputMode (cognitive 54) src/uni_modules/uni-camera/utssdk/app-ios/CameraManager.swift:1481— CameraManager._setupOutputMode has cognitive complexity 54 (threshold 15). Drivers by points: if/else 15 (39 pts), boolean chains 7, loops 3 (4 pts), match/switch 2 (4 pts) (nesting depth added 27). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DCAlertContentView.sizeToFits (cognitive 46) src/uni_modules/uni-prompt/utssdk/app-ios/UniAlert/DCAlertContentView.swift:105— DCAlertContentView.sizeToFits has cognitive complexity 46 (threshold 15). Drivers by points: if/else 22 (38 pts), boolean chains 5, ternaries 2, loops 1 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
UniNetWorkManager.calculateQualityChange (cognitive 44) src/uni_modules/uni-getNetworkType/utssdk/app-ios/UniNetWorkManager.swift:979— UniNetWorkManager.calculateQualityChange has cognitive complexity 44 (threshold 15). Drivers by points: if/else 16 (25 pts), ternaries 4 (16 pts), boolean chains 3 (nesting depth added 21). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
verifyReceiptFromAppleiap (cognitive 38) src/uni_modules/uni-pay-x/uniCloud/cloudfunctions/uni-pay-co/service/pay.js:874— verifyReceiptFromAppleiap has cognitive complexity 38 (threshold 15). Drivers by points: if/else 16 (23 pts), ternaries 4 (6 pts), boolean chains 5, error handling 2 (3 pts), loops 1 (nesting depth added 10). Of this number, 29 points are the body's own statements and 9 belong to 2 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
UniFileSystemManager.write (cognitive 37) src/uni_modules/uni-fileSystemManager/utssdk/app-ios/UniFileSystemManager.swift:1788— UniFileSystemManager.write has cognitive complexity 37 (threshold 15). Drivers by points: if/else 23 (27 pts), boolean chains 4, loops 2 (3 pts), ternaries 2 (3 pts) (nesting depth added 6). Most of this is not in the body itself: 10 of the 37 points are its own statements and the rest belongs to 5 function items inside it that branch (safeWrite, safeWrite::normalizedWriteRange, safeWrite::seekAndFillGapIfNeeded, …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
UniAudioPlayer.updatePlayerItem (cognitive 36) src/uni_modules/uni-createInnerAudioContext/utssdk/app-ios/UniAudioPlayer.swift:556— UniAudioPlayer.updatePlayerItem has cognitive complexity 36 (threshold 15). Drivers by points: if/else 18 (28 pts), boolean chains 8 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
UniBackgroundAudioManager.updatePlayerItem (cognitive 36) src/uni_modules/uni-getBackgroundAudioManager/utssdk/app-ios/UniBackgroundAudioManager.swift:558— UniBackgroundAudioManager.updatePlayerItem has cognitive complexity 36 (threshold 15). Drivers by points: if/else 18 (28 pts), boolean chains 8 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
NativeWebViewImpl.initWebView (cognitive 36) src/uni_modules/uni-web-view/utssdk/app-android/NativeWebViewImpl.kt:296— NativeWebViewImpl.initWebView has cognitive complexity 36 (threshold 15). Drivers by points: if/else 24 (27 pts), boolean chains 6, match/switch 2 (3 pts) (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
DCBottomMenuControllerAnimator.animateTransition (cognitive 33) src/uni_modules/uni-prompt/utssdk/app-ios/UniAlert/DCBottomMenuController.swift:260— DCBottomMenuControllerAnimator.animateTransition has cognitive complexity 33 (threshold 15). Drivers by points: if/else 16 (24 pts), boolean chains 5, loops 2 (4 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
NativeWebViewImpl.handleOnActivityResult (cognitive 33) src/uni_modules/uni-web-view/utssdk/app-android/NativeWebViewImpl.kt:606— NativeWebViewImpl.handleOnActivityResult has cognitive complexity 33 (threshold 15). Drivers by points: if/else 15 (28 pts), loops 1 (5 pts) (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity· format (cognitive 33) · ×1
format (cognitive 33) src/uni_modules/uni-editor/static/editor.js:330— format has cognitive complexity 33 (threshold 15). Drivers by points: if/else 10 (13 pts), ternaries 5 (12 pts), boolean chains 8 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
UniFileSystemManager.readZipEntry::readZip (cognitive 31) src/uni_modules/uni-fileSystemManager/utssdk/app-ios/UniFileSystemManager.swift:2136— UniFileSystemManager.readZipEntry::readZip has cognitive complexity 31 (threshold 15). Drivers by points: if/else 13 (25 pts), loops 1 (4 pts), boolean chains 2 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
UniFileSystemManager.writeFile (cognitive 29) src/uni_modules/uni-fileSystemManager/utssdk/app-ios/UniFileSystemManager.swift:790— UniFileSystemManager.writeFile has cognitive complexity 29 (threshold 15). Drivers by points: if/else 17 (24 pts), boolean chains 3, loops 1, match/switch 1 (nesting depth added 7). Of this number, 20 points are the body's own statements and 9 belong to 2 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DCAlertViewControllerAnimator.animateTransition (cognitive 28) src/uni_modules/uni-prompt/utssdk/app-ios/UniAlert/DCAlertViewController.swift:363— DCAlertViewControllerAnimator.animateTransition has cognitive complexity 28 (threshold 15). Drivers by points: if/else 15 (22 pts), loops 2 (4 pts), boolean chains 2 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
NetworkQualityInfo.qualityLevel (cognitive 27) src/uni_modules/uni-getNetworkType/utssdk/app-ios/UniNetWorkManager.swift:149— NetworkQualityInfo.qualityLevel has cognitive complexity 27 (threshold 15). Drivers by points: if/else 14 (18 pts), boolean chains 8, match/switch 1 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
Scanner._processScanBarCode (cognitive 27) src/uni_modules/uni-barcode-scanning/utssdk/app-android/Scanner.kt:184— Scanner._processScanBarCode has cognitive complexity 27 (threshold 15). Drivers by points: if/else 11 (19 pts), boolean chains 5, error handling 2, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
NativeWebViewImpl.showFileChooser (cognitive 27) src/uni_modules/uni-web-view/utssdk/app-android/NativeWebViewImpl.kt:545— NativeWebViewImpl.showFileChooser has cognitive complexity 27 (threshold 15). Drivers by points: if/else 12 (23 pts), error handling 1 (3 pts), boolean chains 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
service.getOrder (cognitive 27) src/uni_modules/uni-pay-x/uniCloud/cloudfunctions/uni-pay-co/service/pay.js:463— service.getOrder has cognitive complexity 27 (threshold 15). Drivers by points: if/else 16 (19 pts), boolean chains 5, loops 1 (3 pts) (nesting depth added 5). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
UniBackgroundAudioManager.innerPlay (cognitive 25) src/uni_modules/uni-getBackgroundAudioManager/utssdk/app-ios/UniBackgroundAudioManager.swift:464— UniBackgroundAudioManager.innerPlay has cognitive complexity 25 (threshold 15). Drivers by points: if/else 10 (20 pts), boolean chains 5 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
M3U8ResourceLoaderDelegate.handleTSRequest (cognitive 25) src/uni_modules/uni-video/utssdk/app-ios/VideoPlayer/Protocols/M3U8ResourceLoaderDelegate.swift:152— M3U8ResourceLoaderDelegate.handleTSRequest has cognitive complexity 25 (threshold 15). Drivers by points: if/else 15 (19 pts), boolean chains 3, ternaries 1 (3 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AudioRecorder.stopRecording (cognitive 25) src/uni_modules/uni-recorder/utssdk/app-android/AudioRecorder.kt:477— AudioRecorder.stopRecording has cognitive complexity 25 (threshold 15). Drivers by points: error handling 6 (11 pts), if/else 5 (10 pts), loops 1 (2 pts), boolean chains 1, match/switch 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity· list (cognitive 25) · ×1
list (cognitive 25) src/uni_modules/uni-editor/static/quill/formats.js:95— list has cognitive complexity 25 (threshold 15). Drivers by points: if/else 13 (14 pts), ternaries 3 (6 pts), boolean chains 5 (nesting depth added 4). None of this is in the body itself: all 25 points belong to 9 function items inside it that branch (formats, optimize, insertBefore, …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
CameraManager._orientationChanged (cognitive 24) src/uni_modules/uni-camera/utssdk/app-ios/CameraManager.swift:1134— CameraManager._orientationChanged has cognitive complexity 24 (threshold 15). Drivers by points: if/else 6 (19 pts), boolean chains 2, match/switch 1 (2 pts), loops 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
UniInternalWebView.dispatchTouchEvent (cognitive 24) src/uni_modules/uni-web-view/utssdk/app-android/NativeWebViewImpl.kt:823— UniInternalWebView.dispatchTouchEvent has cognitive complexity 24 (threshold 15). Drivers by points: boolean chains 11, if/else 4 (10 pts), match/switch 2 (3 pts) (nesting depth added 7). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
CameraManager._setupInputs (cognitive 23) src/uni_modules/uni-camera/utssdk/app-ios/CameraManager.swift:1702— CameraManager._setupInputs has cognitive complexity 23 (threshold 15). Drivers by points: if/else 5 (14 pts), boolean chains 5, loops 1 (2 pts), match/switch 1 (2 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
UniFileSystemManager.removeDirectory (cognitive 23) src/uni_modules/uni-fileSystemManager/utssdk/app-ios/UniFileSystemManager.swift:1020— UniFileSystemManager.removeDirectory has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (17 pts), error handling 1 (3 pts), boolean chains 2, match/switch 1 (nesting depth added 11). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
CameraImpl.startRecord (cognitive 23) src/uni_modules/uni-camera/utssdk/app-android/CameraImpl.kt:724— CameraImpl.startRecord has cognitive complexity 23 (threshold 15). Drivers by points: if/else 12 (22 pts), match/switch 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
UniShareWithSystem.sendWithSystem (cognitive 23) src/uni_modules/uni-shareWithSystem/utssdk/app-android/UniShareWithSystem.kt:16— UniShareWithSystem.sendWithSystem has cognitive complexity 23 (threshold 15). Drivers by points: if/else 13 (21 pts), error handling 1, match/switch 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
service.refund (cognitive 23) src/uni_modules/uni-pay-x/uniCloud/cloudfunctions/uni-pay-co/service/pay.js:565— service.refund has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 4, error handling 2 (3 pts), ternaries 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
check-update.default (cognitive 22) src/uni_modules/uni-upgrade-center-app/utils/check-update.ts:10— check-update.default has cognitive complexity 22 (threshold 15). Drivers by points: if/else 13 (20 pts), ternaries 2 (nesting depth added 7). None of this is in the body itself: all 22 points belong to 7 function items inside it that branch (a function literal at line 16, updateUseModal, a function literal at line 132, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
_getSign (cognitive 22) src/uni_modules/uni-pay-x/uniCloud/cloudfunctions/uni-pay-co/libs/alipay.js:63— _getSign has cognitive complexity 22 (threshold 15). Drivers by points: boolean chains 12, if/else 9, ternaries 1. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
CameraManager.addLayerPreviewToView (cognitive 21) src/uni_modules/uni-camera/utssdk/app-ios/CameraManager.swift:416— CameraManager.addLayerPreviewToView has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (21 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CameraManager._setupVideoConnection (cognitive 21) src/uni_modules/uni-camera/utssdk/app-ios/CameraManager.swift:1098— CameraManager._setupVideoConnection has cognitive complexity 21 (threshold 15). Drivers by points: if/else 4 (15 pts), loops 2 (5 pts), boolean chains 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
UniAudioPlayer.innerPlay (cognitive 21) src/uni_modules/uni-createInnerAudioContext/utssdk/app-ios/UniAudioPlayer.swift:408— UniAudioPlayer.innerPlay has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (16 pts), boolean chains 5 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
UniFileSystemManager.getStat::get (cognitive 21) src/uni_modules/uni-fileSystemManager/utssdk/app-ios/UniFileSystemManager.swift:1371— UniFileSystemManager.getStat::get has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (13 pts), loops 1 (3 pts), ternaries 1 (3 pts), boolean chains 2 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
UniNetWorkManager.analyzeNetworkError (cognitive 21) src/uni_modules/uni-getNetworkType/utssdk/app-ios/UniNetWorkManager.swift:817— UniNetWorkManager.analyzeNetworkError has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (16 pts), boolean chains 3, match/switch 1 (2 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
UniVideoPlayerManager.setupObservers (cognitive 21) src/uni_modules/uni-video/utssdk/app-ios/VideoPlayer/Managers/UniVideoPlayerManager.swift:799— UniVideoPlayerManager.setupObservers has cognitive complexity 21 (threshold 15). Drivers by points: if/else 13 (18 pts), boolean chains 3 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AudioRecorder.encodeAac (cognitive 21) src/uni_modules/uni-recorder/utssdk/app-android/AudioRecorder.kt:353— AudioRecorder.encodeAac has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (16 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
index.processReview (cognitive 21) REDACTED:301— index.processReview has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (16 pts), boolean chains 2, loops 1 (2 pts), error handling 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CameraManager._getVideoDataOutput (cognitive 20) src/uni_modules/uni-camera/utssdk/app-ios/CameraManager.swift:1305— CameraManager._getVideoDataOutput has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (14 pts), loops 2 (5 pts), boolean chains 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
UniAudioPlayer.observeValue (cognitive 20) src/uni_modules/uni-createInnerAudioContext/utssdk/app-ios/UniAudioPlayer.swift:688— UniAudioPlayer.observeValue has cognitive complexity 20 (threshold 15). Drivers by points: if/else 12 (20 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
UniFileSystemManager.unzip (cognitive 20) src/uni_modules/uni-fileSystemManager/utssdk/app-ios/UniFileSystemManager.swift:1564— UniFileSystemManager.unzip has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (14 pts), match/switch 3 (4 pts), error handling 2 (nesting depth added 7). Of this number, 15 points are the body's own statements and 5 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
UniBackgroundAudioManager.observeValue (cognitive 20) src/uni_modules/uni-getBackgroundAudioManager/utssdk/app-ios/UniBackgroundAudioManager.swift:686— UniBackgroundAudioManager.observeValue has cognitive complexity 20 (threshold 15). Drivers by points: if/else 12 (20 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
InnerWebView.updateUrl (cognitive 20) src/uni_modules/uni-web-view/utssdk/app-ios/InnerWebView.swift:870— InnerWebView.updateUrl has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 8 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
UniShareWithSystem.checkPath (cognitive 20) src/uni_modules/uni-shareWithSystem/utssdk/app-android/UniShareWithSystem.kt:113— UniShareWithSystem.checkPath has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (16 pts), error handling 1 (3 pts), loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
editor.parseHTML (cognitive 20) src/uni_modules/uni-editor/static/editor.js:33— editor.parseHTML has cognitive complexity 20 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 2 (5 pts), boolean chains 4 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
call-check-version.default (cognitive 20) src/uni_modules/uni-upgrade-center-app/utils/call-check-version.ts:32— call-check-version.default has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11 (16 pts), boolean chains 2, error handling 1 (2 pts) (nesting depth added 6). None of this is in the body itself: all 20 points belong to 4 function literals inside it that branch (lines 34, 79, 40, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
UniFileSystemManager.copyFile (cognitive 19) src/uni_modules/uni-fileSystemManager/utssdk/app-ios/UniFileSystemManager.swift:1220— UniFileSystemManager.copyFile has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (16 pts), match/switch 2, error handling 1 (nesting depth added 6). Of this number, 18 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
UniAudioRecorderManager.isValidEncodeBitRate (cognitive 19) src/uni_modules/uni-recorder/utssdk/app-ios/UniAudioRecorderManager.swift:390— UniAudioRecorderManager.isValidEncodeBitRate has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10, boolean chains 9. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
UniChooseFileManager.documentPicker (cognitive 19) src/uni_modules/uni-media/utssdk/app-ios/utils/UniChooseFileManager.swift:92— UniChooseFileManager.documentPicker has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (14 pts), error handling 1 (4 pts), loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CameraManager.capturePictureDataWithCompletion (cognitive 18) src/uni_modules/uni-camera/utssdk/app-ios/CameraManager.swift:582— CameraManager.capturePictureDataWithCompletion has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 3 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CameraManager._focusStart (cognitive 18) src/uni_modules/uni-camera/utssdk/app-ios/CameraManager.swift:852— CameraManager._focusStart has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (13 pts), boolean chains 2, error handling 1 (2 pts), match/switch 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
UniFileSystemManager.appendFile (cognitive 18) src/uni_modules/uni-fileSystemManager/utssdk/app-ios/UniFileSystemManager.swift:1425— UniFileSystemManager.appendFile has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11 (14 pts), boolean chains 2, loops 1, match/switch 1 (nesting depth added 3). Of this number, 9 points are the body's own statements and 9 belong to 2 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
UniFileDecompressTool.unzip (cognitive 18) src/uni_modules/uni-fileSystemManager/utssdk/app-ios/UniFileTools.swift:147— UniFileDecompressTool.unzip has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (9 pts), error handling 2 (4 pts), loops 1 (2 pts), match/switch 1 (2 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
UniNetWorkManager.updateCellularNetworkType (cognitive 18) src/uni_modules/uni-getNetworkType/utssdk/app-ios/UniNetWorkManager.swift:608— UniNetWorkManager.updateCellularNetworkType has cognitive complexity 18 (threshold 15). Drivers by points: if/else 12 (16 pts), boolean chains 2 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Event.parseLine (cognitive 18) src/uni_modules/uni-sse/utssdk/app-ios/EventSource/Event.swift:84— Event.parseLine has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (12 pts), loops 2 (4 pts), boolean chains 2 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
service.paymentNotify (cognitive 18) src/uni_modules/uni-pay-x/uniCloud/cloudfunctions/uni-pay-co/service/pay.js:39— service.paymentNotify has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (14 pts), error handling 1 (3 pts), boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CameraImpl.startRecord (cognitive 17) src/uni_modules/uni-camera/utssdk/app-ios/CameraImpl.swift:165— CameraImpl.startRecord has cognitive complexity 17 (threshold 15). Drivers by points: if/else 14 (17 pts) (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
UniAudioPlayer.configureAudioSession (cognitive 17) src/uni_modules/uni-createInnerAudioContext/utssdk/app-ios/UniAudioPlayer.swift:494— UniAudioPlayer.configureAudioSession has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (15 pts), boolean chains 1, error handling 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
UniFileSystemManager.open (cognitive 17) src/uni_modules/uni-fileSystemManager/utssdk/app-ios/UniFileSystemManager.swift:1688— UniFileSystemManager.open has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 9, if/else 5 (7 pts), match/switch 1 (nesting depth added 2). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
InnerWebView.userContentController (cognitive 17) src/uni_modules/uni-web-view/utssdk/app-ios/InnerWebView.swift:1430— InnerWebView.userContentController has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (11 pts), boolean chains 4, match/switch 1 (2 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
utils.compare (cognitive 17) src/uni_modules/uni-upgrade-center-app/utils/utils.ts:14— utils.compare has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (7 pts), ternaries 2 (6 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CameraManager.applyVideoMirror (cognitive 16) src/uni_modules/uni-camera/utssdk/app-ios/CameraManager.swift:718— CameraManager.applyVideoMirror has cognitive complexity 16 (threshold 15). Drivers by points: if/else 3 (10 pts), loops 2 (5 pts), boolean chains 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
UniFileSystemManager.readFile::safeRead (cognitive 16) src/uni_modules/uni-fileSystemManager/utssdk/app-ios/UniFileSystemManager.swift:697— UniFileSystemManager.readFile::safeRead has cognitive complexity 16 (threshold 15). Drivers by points: if/else 11 (14 pts), loops 1 (2 pts) (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
UniVideoPlayerView.videoPlayer (cognitive 16) src/uni_modules/uni-video/utssdk/app-ios/VideoPlayer/UniVideoPlayerView.swift:668— UniVideoPlayerView.videoPlayer has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (11 pts), boolean chains 4, match/switch 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CameraImpl.ensureAnalyzerRegistered (cognitive 16) src/uni_modules/uni-camera/utssdk/app-android/CameraImpl.kt:538— CameraImpl.ensureAnalyzerRegistered has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (10 pts), boolean chains 3, error handling 1 (3 pts) (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
NativeWebViewImpl.setTheme (cognitive 16) src/uni_modules/uni-web-view/utssdk/app-android/NativeWebViewImpl.kt:755— NativeWebViewImpl.setTheme has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (11 pts), match/switch 2 (4 pts), boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SystemPickerActivity.getFileName (cognitive 16) src/uni_modules/uni-chooseMedia/utssdk/app-android/SystemPickerActivity.java:165— SystemPickerActivity.getFileName has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 2, error handling 1 (2 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SystemPickerActivity.onCreate (cognitive 16) src/uni_modules/uni-chooseMedia/utssdk/app-android/SystemPickerActivity.java:43— SystemPickerActivity.onCreate has cognitive complexity 16 (threshold 15). Drivers by points: if/else 11 (12 pts), boolean chains 2, error handling 1, match/switch 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Service.location2address (cognitive 16) src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/qqmap.js:59— Service.location2address has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
service.initUniPayInstance (cognitive 16) src/uni_modules/uni-pay-x/uniCloud/cloudfunctions/uni-pay-co/service/pay.js:1164— service.initUniPayInstance has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (12 pts), error handling 1 (3 pts), boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (4 members, 50+ identical tokens) src/uni_modules/uni-fileSystemManager/utssdk/app-ios/UniFileSystemManager.swift:373— src/uni_modules/uni-fileSystemManager/utssdk/app-ios/UniFileSystemManager.swift:373-389 | src/uni_modules/uni-fileSystemManager/utssdk/app-ios/UniFileSystemManager.swift:394-408 | src/uni_modules/uni-fileSystemManager/utssdk/app-ios/UniFileSystemManager.swift:415-431 | src/uni_modules/uni-fileSystemManager/utssdk/app-ios/UniFileSystemManager.swift:439-460 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication· Edited copy of a member (87 corresponding lines) · ×1
Edited copy of a member (87 corresponding lines) src/uni_modules/uni-fileSystemManager/utssdk/app-ios/UniFileSystemManager.swift:790— src/uni_modules/uni-fileSystemManager/utssdk/app-ios/UniFileSystemManager.swift:790-891 | src/uni_modules/uni-fileSystemManager/utssdk/app-ios/UniFileSystemManager.swift:1425-1511 — These two members are one piece of code written twice and then edited apart: 87 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 (79 corresponding lines) · ×1
Edited copy of a member (79 corresponding lines) src/uni_modules/uni-prompt/utssdk/app-ios/UniAlert/DCAlertViewController.swift:363— src/uni_modules/uni-prompt/utssdk/app-ios/UniAlert/DCAlertViewController.swift:363-450 | src/uni_modules/uni-prompt/utssdk/app-ios/UniAlert/DCBottomMenuController.swift:260-338 — These two members are one piece of code written twice and then edited apart: 79 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (33 corresponding lines) · ×1
Edited copy of a member (33 corresponding lines) src/uni_modules/uni-virtualPayment/utssdk/app-ios/PurchaseService.swift:25— src/uni_modules/uni-virtualPayment/utssdk/app-ios/PurchaseService.swift:25-57 | src/uni_modules/uni-virtualPayment/utssdk/app-ios/PurchaseService.swift:70-103 — These two members are one piece of code written twice and then edited apart: 33 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (65 corresponding lines) · ×1
Edited copy of a member (65 corresponding lines) src/uni_modules/uni-fileSystemManager/utssdk/app-ios/UniFileSystemManager.swift:1149— src/uni_modules/uni-fileSystemManager/utssdk/app-ios/UniFileSystemManager.swift:1149-1213 | src/uni_modules/uni-fileSystemManager/utssdk/app-ios/UniFileSystemManager.swift:1220-1291 — These two members are one piece of code written twice and then edited apart: 65 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 (32 corresponding lines) · ×1
Edited copy of a member (32 corresponding lines) src/uni_modules/uni-createInnerAudioContext/utssdk/app-ios/UniAudioPlayer.swift:688— src/uni_modules/uni-createInnerAudioContext/utssdk/app-ios/UniAudioPlayer.swift:688-719 | src/uni_modules/uni-getBackgroundAudioManager/utssdk/app-ios/UniBackgroundAudioManager.swift:686-717 — These two members are one piece of code written twice and then edited apart: 32 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 (25 corresponding lines) · ×1
Edited copy of a member (25 corresponding lines) src/uni_modules/uni-createInnerAudioContext/utssdk/app-android/AudioPlayer.kt:118— src/uni_modules/uni-createInnerAudioContext/utssdk/app-android/AudioPlayer.kt:118-142 | src/uni_modules/uni-getBackgroundAudioManager/utssdk/app-android/BackgroundAudioPlayer.kt:120-146 — 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 copy of a member (34 corresponding lines) · ×1
Edited copy of a member (34 corresponding lines) src/uni_modules/uni-createInnerAudioContext/utssdk/app-ios/UniAudioPlayer.swift:408— src/uni_modules/uni-createInnerAudioContext/utssdk/app-ios/UniAudioPlayer.swift:408-441 | src/uni_modules/uni-getBackgroundAudioManager/utssdk/app-ios/UniBackgroundAudioManager.swift:464-502 — These two members are one piece of code written twice and then edited apart: 34 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (28 corresponding lines) · ×1
Edited copy of a member (28 corresponding lines) src/uni_modules/uni-createInnerAudioContext/utssdk/app-ios/UniAudioPlayer.swift:443— src/uni_modules/uni-createInnerAudioContext/utssdk/app-ios/UniAudioPlayer.swift:443-470 | src/uni_modules/uni-getBackgroundAudioManager/utssdk/app-ios/UniBackgroundAudioManager.swift:504-534 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 20+ corresponding lines) · ×1
Edited copies of one member (3 members, 20+ corresponding lines) src/uni_modules/uni-prompt/utssdk/app-ios/UniAlert/DCAlertView.Blocks.swift:54— src/uni_modules/uni-prompt/utssdk/app-ios/UniAlert/DCAlertView.Blocks.swift:54-73 | src/uni_modules/uni-prompt/utssdk/app-ios/UniAlert/DCAlertView.Blocks.swift:90-110 | src/uni_modules/uni-prompt/utssdk/app-ios/UniAlert/DCAlertView.Blocks.swift:112-134 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 20 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 13+ corresponding lines) · ×1
Edited copies of one member (3 members, 13+ corresponding lines) src/uni_modules/uni-fileSystemManager/utssdk/app-ios/UniFileSystemManager.swift:768— src/uni_modules/uni-fileSystemManager/utssdk/app-ios/UniFileSystemManager.swift:768-781 | src/uni_modules/uni-fileSystemManager/utssdk/app-ios/UniFileSystemManager.swift:997-1012 | src/uni_modules/uni-fileSystemManager/utssdk/app-ios/UniFileSystemManager.swift:1075-1087 — 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 (3 members, 16+ corresponding lines) · ×1
Edited copies of one member (3 members, 16+ corresponding lines) src/uni_modules/uni-virtualPayment/utssdk/app-ios/UniStoreKit+Closure.swift:40— src/uni_modules/uni-virtualPayment/utssdk/app-ios/UniStoreKit+Closure.swift:40-55 | src/uni_modules/uni-virtualPayment/utssdk/app-ios/UniStoreKit+Closure.swift:88-104 | src/uni_modules/uni-virtualPayment/utssdk/app-ios/UniStoreKit+Closure.swift:110-126 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 8+ corresponding lines) · ×1
Edited copies of one member (4 members, 8+ corresponding lines) src/uni_modules/uni-prompt/utssdk/app-ios/UniToast/MCToast+Loading.swift:34— src/uni_modules/uni-prompt/utssdk/app-ios/UniToast/MCToast+Loading.swift:34-41 | src/uni_modules/uni-prompt/utssdk/app-ios/UniToast/MCToast+Loading.swift:50-58 | src/uni_modules/uni-prompt/utssdk/app-ios/UniToast/MCToast+Loading.swift:89-96 | src/uni_modules/uni-prompt/utssdk/app-ios/UniToast/MCToast+Loading.swift:105-113 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (8 members, 7+ corresponding lines) · ×1
Edited copies of one member (8 members, 7+ corresponding lines) src/uni_modules/uni-prompt/utssdk/app-ios/UniToast/MCToast+Status.swift:31— src/uni_modules/uni-prompt/utssdk/app-ios/UniToast/MCToast+Status.swift:31-38 | src/uni_modules/uni-prompt/utssdk/app-ios/UniToast/MCToast+Status.swift:47-54 | src/uni_modules/uni-prompt/utssdk/app-ios/UniToast/MCToast+Status.swift:63-70 | src/uni_modules/uni-prompt/utssdk/app-ios/UniToast/MCToast+Status.swift:83-91 | src/uni_modules/uni-prompt/utssdk/app-ios/UniToast/MCToast+Status.swift:100-108 | src/uni_modules/uni-prompt/utssdk/app-ios/UniToast/MCToast+Status.swift:117-125 | src/uni_modules/uni-prompt/utssdk/app-ios/UniToast/MCToast+Text.swift:19-25 | src/uni_modules/uni-prompt/utssdk/app-ios/UniToast/MCToast+Text.swift:39-48 — These 8 members are one piece of code written 8 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 8 times and the copies will drift further apart.
Duplicated block (70–72 lines × 2) src/uni_modules/uni-createInnerAudioContext/utssdk/app-ios/UniAudioPlayer.swift:556— src/uni_modules/uni-createInnerAudioContext/utssdk/app-ios/UniAudioPlayer.swift:556-627 | src/uni_modules/uni-getBackgroundAudioManager/utssdk/app-ios/UniBackgroundAudioManager.swift:558-627 — before extracting anything, compare `src/uni_modules/uni-createInnerAudioContext/utssdk/app-ios/UniAudioPlayer.swift` and `src/uni_modules/uni-getBackgroundAudioManager/utssdk/app-ios/UniBackgroundAudioManager.swift` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 285 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (55 lines × 2) src/uni_modules/uni-fileSystemManager/utssdk/app-ios/UniFileSystemManager.swift:837— src/uni_modules/uni-fileSystemManager/utssdk/app-ios/UniFileSystemManager.swift:837-891 | src/uni_modules/uni-fileSystemManager/utssdk/app-ios/UniFileSystemManager.swift:1457-1511 — 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 `src/uni_modules/uni-fileSystemManager/utssdk/app-ios/UniFileSystemManager.swift:837` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also register a scope-exit action (a `defer`-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead — before the caller uses what it releases — so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register.
Duplicated block (32–33 lines × 2) src/uni_modules/uni-createInnerAudioContext/utssdk/app-ios/UniAudioPlayer.swift:375— src/uni_modules/uni-createInnerAudioContext/utssdk/app-ios/UniAudioPlayer.swift:375-406 | src/uni_modules/uni-getBackgroundAudioManager/utssdk/app-ios/UniBackgroundAudioManager.swift:417-449 — before extracting anything, compare `src/uni_modules/uni-createInnerAudioContext/utssdk/app-ios/UniAudioPlayer.swift` and `src/uni_modules/uni-getBackgroundAudioManager/utssdk/app-ios/UniBackgroundAudioManager.swift` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 285 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (31–32 lines × 2) src/uni_modules/uni-createInnerAudioContext/utssdk/app-ios/UniAudioPlayer.swift:841— src/uni_modules/uni-createInnerAudioContext/utssdk/app-ios/UniAudioPlayer.swift:841-871 | src/uni_modules/uni-getBackgroundAudioManager/utssdk/app-ios/UniBackgroundAudioManager.swift:865-896 — before extracting anything, compare `src/uni_modules/uni-createInnerAudioContext/utssdk/app-ios/UniAudioPlayer.swift` and `src/uni_modules/uni-getBackgroundAudioManager/utssdk/app-ios/UniBackgroundAudioManager.swift` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 285 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (25 lines × 2) src/uni_modules/uni-createInnerAudioContext/utssdk/app-ios/UniAudioPlayer.swift:411— src/uni_modules/uni-createInnerAudioContext/utssdk/app-ios/UniAudioPlayer.swift:411-435 | src/uni_modules/uni-getBackgroundAudioManager/utssdk/app-ios/UniBackgroundAudioManager.swift:467-491 — before extracting anything, compare `src/uni_modules/uni-createInnerAudioContext/utssdk/app-ios/UniAudioPlayer.swift` and `src/uni_modules/uni-getBackgroundAudioManager/utssdk/app-ios/UniBackgroundAudioManager.swift` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 285 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/uni_modules/uni-createInnerAudioContext/utssdk/app-ios/UniAudioPlayer.swift:411` 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 (16 lines × 2) src/uni_modules/uni-form/utssdk/app-ios/UniInputView.swift:74— src/uni_modules/uni-form/utssdk/app-ios/UniInputView.swift:74-89 | src/uni_modules/uni-form/utssdk/app-ios/UniTextareaView.swift:120-135 — before extracting anything, compare `src/uni_modules/uni-form/utssdk/app-ios/UniInputView.swift` and `src/uni_modules/uni-form/utssdk/app-ios/UniTextareaView.swift` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 54 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) src/uni_modules/uni-createInnerAudioContext/utssdk/app-ios/UniAudioPlayer.swift:875— src/uni_modules/uni-createInnerAudioContext/utssdk/app-ios/UniAudioPlayer.swift:875-889 | src/uni_modules/uni-getBackgroundAudioManager/utssdk/app-ios/UniBackgroundAudioManager.swift:1074-1088 — before extracting anything, compare `src/uni_modules/uni-createInnerAudioContext/utssdk/app-ios/UniAudioPlayer.swift` and `src/uni_modules/uni-getBackgroundAudioManager/utssdk/app-ios/UniBackgroundAudioManager.swift` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 285 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (12–13 lines × 2) src/uni_modules/uni-fileSystemManager/utssdk/app-ios/UniFileSystemManager.swift:673— src/uni_modules/uni-fileSystemManager/utssdk/app-ios/UniFileSystemManager.swift:673-685 | src/uni_modules/uni-fileSystemManager/utssdk/app-ios/UniFileSystemManager.swift:796-807 — 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 `src/uni_modules/uni-fileSystemManager/utssdk/app-ios/UniFileSystemManager.swift:673` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11–12 lines × 3) src/uni_modules/uni-fileSystemManager/utssdk/app-ios/UniFileSystemManager.swift:682— src/uni_modules/uni-fileSystemManager/utssdk/app-ios/UniFileSystemManager.swift:682-692 | src/uni_modules/uni-fileSystemManager/utssdk/app-ios/UniFileSystemManager.swift:1155-1165 | src/uni_modules/uni-fileSystemManager/utssdk/app-ios/UniFileSystemManager.swift:1570-1581 — 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 `src/uni_modules/uni-fileSystemManager/utssdk/app-ios/UniFileSystemManager.swift:682` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10–11 lines × 3) src/uni_modules/uni-fileSystemManager/utssdk/app-ios/UniFileSystemManager.swift:1305— src/uni_modules/uni-fileSystemManager/utssdk/app-ios/UniFileSystemManager.swift:1305-1315 | src/uni_modules/uni-fileSystemManager/utssdk/app-ios/UniFileSystemManager.swift:2079-2088 | src/uni_modules/uni-fileSystemManager/utssdk/app-ios/UniFileSystemManager.swift:2121-2130 — 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 `src/uni_modules/uni-fileSystemManager/utssdk/app-ios/UniFileSystemManager.swift:1305` 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `completionHandler` to `fileInfoCallback? = nil` in one and `stringCallback? = nil` 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 (10–11 lines × 2) src/uni_modules/uni-createInnerAudioContext/utssdk/app-ios/UniAudioPlayer.swift:815— src/uni_modules/uni-createInnerAudioContext/utssdk/app-ios/UniAudioPlayer.swift:815-824 | src/uni_modules/uni-getBackgroundAudioManager/utssdk/app-ios/UniBackgroundAudioManager.swift:837-847 — before extracting anything, compare `src/uni_modules/uni-createInnerAudioContext/utssdk/app-ios/UniAudioPlayer.swift` and `src/uni_modules/uni-getBackgroundAudioManager/utssdk/app-ios/UniBackgroundAudioManager.swift` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 285 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/uni_modules/uni-createInnerAudioContext/utssdk/app-ios/UniAudioPlayer.swift:815` 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 (18–19 lines × 2) src/uni_modules/uni-virtualPayment/utssdk/app-ios/PurchaseService.swift:39— src/uni_modules/uni-virtualPayment/utssdk/app-ios/PurchaseService.swift:39-57 | src/uni_modules/uni-virtualPayment/utssdk/app-ios/PurchaseService.swift:86-103 — 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 `src/uni_modules/uni-virtualPayment/utssdk/app-ios/PurchaseService.swift:39` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 4) src/uni_modules/uni-fileSystemManager/utssdk/app-ios/UniFileSystemManager.swift:380— src/uni_modules/uni-fileSystemManager/utssdk/app-ios/UniFileSystemManager.swift:380-389 | src/uni_modules/uni-fileSystemManager/utssdk/app-ios/UniFileSystemManager.swift:400-408 | src/uni_modules/uni-fileSystemManager/utssdk/app-ios/UniFileSystemManager.swift:422-431 | src/uni_modules/uni-fileSystemManager/utssdk/app-ios/UniFileSystemManager.swift:451-460 — 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 `src/uni_modules/uni-fileSystemManager/utssdk/app-ios/UniFileSystemManager.swift:380` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (17 lines × 2) src/uni_modules/uni-createInnerAudioContext/utssdk/app-android/AudioPlayer.kt:119— src/uni_modules/uni-createInnerAudioContext/utssdk/app-android/AudioPlayer.kt:119-135 | src/uni_modules/uni-getBackgroundAudioManager/utssdk/app-android/BackgroundAudioPlayer.kt:121-137 — before extracting anything, compare `src/uni_modules/uni-createInnerAudioContext/utssdk/app-android/AudioPlayer.kt` and `src/uni_modules/uni-getBackgroundAudioManager/utssdk/app-android/BackgroundAudioPlayer.kt` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 63 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/uni_modules/uni-createInnerAudioContext/utssdk/app-android/AudioPlayer.kt:119` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 3) src/uni_modules/uni-shareWithSystem/utssdk/app-android/UniShareWithSystem.kt:66— src/uni_modules/uni-shareWithSystem/utssdk/app-android/UniShareWithSystem.kt:66-75 | src/uni_modules/uni-shareWithSystem/utssdk/app-android/UniShareWithSystem.kt:78-87 | src/uni_modules/uni-shareWithSystem/utssdk/app-android/UniShareWithSystem.kt:90-99 — 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (13 lines × 3) src/uni_modules/uni-camera/utssdk/app-android/CameraImpl.kt:429— src/uni_modules/uni-camera/utssdk/app-android/CameraImpl.kt:429-441 | src/uni_modules/uni-camera/utssdk/app-android/CameraImpl.kt:484-496 | src/uni_modules/uni-camera/utssdk/app-android/CameraImpl.kt:892-904 — 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 `src/uni_modules/uni-camera/utssdk/app-android/CameraImpl.kt:429` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication· Edited copy of a member (86 corresponding lines) · ×1
Edited copy of a member (86 corresponding lines) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/MainThread/NodeRenderSystem/Nodes/OutputNodes/Renderables/GradientFillRenderer.swift:44— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/MainThread/NodeRenderSystem/Nodes/OutputNodes/Renderables/GradientFillRenderer.swift:44-129 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/MainThread/NodeRenderSystem/Nodes/OutputNodes/Renderables/LegacyGradientFillRenderer.swift:59-151 — These two members are one piece of code written twice and then edited apart: 86 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 (38 corresponding lines) · ×1
Edited copy of a member (38 corresponding lines) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/iOS/BundleImageProvider.swift:34— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/iOS/BundleImageProvider.swift:34-79 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/macOS/BundleImageProvider.macOS.swift:33-70 — These two members are one piece of code written twice and then edited apart: 38 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) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/Animation/LottieAnimationViewInitializers.swift:110— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/Animation/LottieAnimationViewInitializers.swift:110-129 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/Animation/LottieAnimationViewInitializers.swift:161-184 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/Animation/LottieAnimationViewInitializers.swift:192-210 — 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 (20 corresponding lines) · ×1
Edited copy of a member (20 corresponding lines) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/CoreAnimation/Animations/EllipseAnimation.swift:8— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/CoreAnimation/Animations/EllipseAnimation.swift:8-27 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/CoreAnimation/Animations/RectangleAnimation.swift:8-29 — 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 copies of one member (3 members, 11+ corresponding lines) · ×1
Edited copies of one member (3 members, 11+ corresponding lines) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/Animation/LottieAnimationViewInitializers.swift:21— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/Animation/LottieAnimationViewInitializers.swift:21-32 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/Animation/LottieAnimationViewInitializers.swift:39-49 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/Animation/LottieAnimationViewInitializers.swift:88-98 — 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 copies of one member (5 members, 12+ corresponding lines) · ×1
Edited copies of one member (5 members, 12+ corresponding lines) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/DotLottie/DotLottieFileHelpers.swift:121— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/DotLottie/DotLottieFileHelpers.swift:121-134 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/DotLottie/DotLottieFileHelpers.swift:168-179 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/DotLottie/DotLottieFileHelpers.swift:207-219 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/DotLottie/DotLottieFileHelpers.swift:273-285 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/DotLottie/DotLottieFileHelpers.swift:357-369 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 3+ corresponding lines) · ×1
Edited copies of one member (4 members, 3+ corresponding lines) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/LayerEffects/EffectValues/EffectValue.swift:13— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/LayerEffects/EffectValues/EffectValue.swift:13-15 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/LayerEffects/LayerEffect.swift:11-13 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/LayerStyles/LayerStyle.swift:10-12 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/ShapeItems/ShapeItem.swift:27-29 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 3 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.
Duplicated block (59 lines × 2) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/MainThread/NodeRenderSystem/Nodes/OutputNodes/Renderables/GradientFillRenderer.swift:71— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/MainThread/NodeRenderSystem/Nodes/OutputNodes/Renderables/GradientFillRenderer.swift:71-129 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/MainThread/NodeRenderSystem/Nodes/OutputNodes/Renderables/LegacyGradientFillRenderer.swift:93-151 — 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 `examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/MainThread/NodeRenderSystem/Nodes/OutputNodes/Renderables/GradientFillRenderer.swift:71` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/MainThread/NodeRenderSystem/Nodes/OutputNodes/Renderables/LegacyGradientFillRenderer.swift:89` calls `setAlpha`, `clip` and `examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/MainThread/NodeRenderSystem/Nodes/OutputNodes/Renderables/GradientFillRenderer.swift:68` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (30 lines × 2) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/iOS/BundleImageProvider.swift:34— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/iOS/BundleImageProvider.swift:34-63 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/macOS/BundleImageProvider.macOS.swift:33-62 — `examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/iOS/BundleImageProvider.swift` and `examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/macOS/BundleImageProvider.macOS.swift` 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 2 separate duplicated blocks between them, totalling at least 35 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 `examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/iOS/BundleImageProvider.swift:34` 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 (27 lines × 2) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/MainThread/LayerContainers/CompLayers/PreCompositionLayer.swift:46— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/MainThread/LayerContainers/CompLayers/PreCompositionLayer.swift:46-72 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/MainThread/LayerContainers/MainThreadAnimationLayer.swift:45-71 — 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 `examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/MainThread/LayerContainers/CompLayers/PreCompositionLayer.swift:46` 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, `examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/MainThread/LayerContainers/MainThreadAnimationLayer.swift:42` calls `CGFloat` and `examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/MainThread/LayerContainers/CompLayers/PreCompositionLayer.swift:43` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (21 lines × 2) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/ShapeItems/GradientFill.swift:38— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/ShapeItems/GradientFill.swift:38-58 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/ShapeItems/GradientStroke.swift:53-73 — before extracting anything, compare `examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/ShapeItems/GradientFill.swift` and `examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/ShapeItems/GradientStroke.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 36 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–13 lines × 2) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/ShapeItems/Repeater.swift:23— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/ShapeItems/Repeater.swift:23-29 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/ShapeItems/ShapeTransform.swift:28-40 — 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, `examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/ShapeItems/ShapeTransform.swift:44` calls `decodeIfPresent`, `KeyframeGroup`, `LottieVector1D` and `examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/ShapeItems/Repeater.swift:33` 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 × 3) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/ShapeItems/Ellipse.swift:30— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/ShapeItems/Ellipse.swift:30-40 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/ShapeItems/Rectangle.swift:21-31 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/ShapeItems/Star.swift:36-46 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/ShapeItems/Ellipse.swift:30` 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, `examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/ShapeItems/Star.swift:32` calls `decode` and `examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/ShapeItems/Ellipse.swift:26` 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–9 lines × 2) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Utility/Primitives/BezierPathRoundExtension.swift:120— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Utility/Primitives/BezierPathRoundExtension.swift:120-127 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Utility/Primitives/BezierPathRoundExtension.swift:138-146 — 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–8 lines × 2) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/Extensions/Bundle.swift:10— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/Extensions/Bundle.swift:10-17 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/Extensions/Bundle.swift:22-28 — 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 `examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/Model/Extensions/Bundle.swift:10` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 3) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/CoreAnimation/Extensions/Keyframes+combined.swift:82— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/CoreAnimation/Extensions/Keyframes+combined.swift:82-88 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/CoreAnimation/Extensions/Keyframes+combined.swift:117-123 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/CoreAnimation/Extensions/Keyframes+combined.swift:154-160 — 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.
Duplicated block (23 lines × 2) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/iOS/FilepathImageProvider.swift:39— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/iOS/FilepathImageProvider.swift:39-61 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Public/macOS/FilepathImageProvider.macOS.swift:38-60 — 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 (6 lines × 3) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/MainThread/LayerContainers/CompLayers/MaskContainerLayer.swift:60— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/MainThread/LayerContainers/CompLayers/MaskContainerLayer.swift:60-66 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/MainThread/LayerContainers/CompLayers/NullCompositionLayer.swift:20-26 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/MainThread/NodeRenderSystem/RenderLayers/ShapeContainerLayer.swift:31-36 — 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.
Duplicated block (5 lines × 4) examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/MainThread/NodeRenderSystem/Nodes/PathNodes/EllipseNode.swift:47— examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/MainThread/NodeRenderSystem/Nodes/PathNodes/EllipseNode.swift:47-51 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/MainThread/NodeRenderSystem/Nodes/PathNodes/PolygonNode.swift:58-62 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/MainThread/NodeRenderSystem/Nodes/PathNodes/ShapeNode.swift:42-46 | examples/hello-uts/uni_modules/uts-animation-view/utssdk/app-ios/lottie-ios/Private/MainThread/NodeRenderSystem/Nodes/PathNodes/StarNode.swift:70-74 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 4 call sites, so a change lands once.
Forked directory tree (8 identical files, ~450 lines × 2 trees) src/uni_modules/uni-payment-alipay/utssdk/app-ios/Frameworks/AlipaySDK.xcframework/ios-arm64/AlipaySDK.framework/Headers/AlipaySDK.h:1— src/uni_modules/uni-payment-alipay/utssdk/app-ios/Frameworks/AlipaySDK.xcframework/ios-arm64/AlipaySDK.framework/ and src/uni_modules/uni-payment-alipay/utssdk/app-ios/Frameworks/AlipaySDK.xcframework/ios-arm64_x86_64-simulator/AlipaySDK.framework/ are near-verbatim copies of each other: 8 files are byte-identical under the same relative paths (~450 lines; the trees hold 8 and 9 files). That is one structural fact, not 8 local ones: every edit made to one tree and not the other drifts silently, which is the failure whole-tree forks guarantee. Pick one tree as the single source and produce the other from it (generated, copied at build or release time, or re-exported) — or, if the copy is a stale snapshot nothing produces any more, delete it. Check first whether the copy is a deliberately published deliverable (a template consumers copy verbatim, a released sample frozen at a version); where it is, keep it produced from the source tree rather than edited in place.
Wholesale file copy (323 identical lines × 2 files) src/uni_modules/uni-icons/components/uni-icons/uniicons_file.ts:17— src/uni_modules/uni-icons/components/uni-icons/uniicons_file.ts:17 · src/uni_modules/uni-icons/components/uni-icons/uniicons_file_vue.js:2 — these 2 files are line-for-line copies of one another — 323 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Wholesale file copy (156 identical lines × 2 files) src/uni_modules/uni-canvas-dom2/utssdk/app-harmony/canvas.color.js:2— src/uni_modules/uni-canvas-dom2/utssdk/app-harmony/canvas.color.js:2 · src/uni_modules/uni-canvas/customElements/uni-canvas/uni-canvas.js:2 — these 2 files are line-for-line copies of one another — 156 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Duplicated block (63 lines × 2 locations) src/wxcomponents/vant/button/index.js:4— src/wxcomponents/vant/button/index.js:4 · src/wxcomponents/vant/button/index.vue:27 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Duplicated block (44 lines × 3 locations) src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/amap.js:554— src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/amap.js:554 · src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/amap.js:609 · src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/amap.js:664 — all 3 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication· Duplicated block with local edits (41 matched lines × 2 locations) · ×1
Duplicated block with local edits (41 matched lines × 2 locations) src/jest-setup.js:45— src/jest-setup.js:45 · src/jest-setup.js:90 — the two spans are one implementation copied and then locally edited — 170 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 (39 lines × 3 locations) src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/qqmap.js:550— src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/qqmap.js:550 · src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/qqmap.js:604 · src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/qqmap.js:657 — all 3 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 (37 lines × 2 locations) src/wxcomponents/vant/icon/index.js:3— src/wxcomponents/vant/icon/index.js:3 · src/wxcomponents/vant/icon/index.vue:15 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Duplicated block (35 lines × 2 locations) src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/amap.js:60— src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/amap.js:60 · src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/qqmap.js:16 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (32 lines × 2 locations) src/uni_modules/uni-animation-view/utssdk/app-android/index.vue:36— src/uni_modules/uni-animation-view/utssdk/app-android/index.vue:36 · src/uni_modules/uni-animation-view/utssdk/app-ios/index.vue:25 — 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 (30 lines × 2 locations) src/wxcomponents/vant/loading/index.js:3— src/wxcomponents/vant/loading/index.js:3 · src/wxcomponents/vant/loading/index.vue:17 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Duplicated block (27 lines × 2 locations) src/uni_modules/uni-pay-x/uniCloud/cloudfunctions/uni-pay-co/libs/wxpay.js:44— src/uni_modules/uni-pay-x/uniCloud/cloudfunctions/uni-pay-co/libs/wxpay.js:44 · src/uni_modules/uni-pay-x/uniCloud/cloudfunctions/uni-pay-co/libs/wxpay.js:78 — 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 (23 lines × 2 locations) src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/amap.js:345— src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/amap.js:345 · src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/qqmap.js:310 — 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 × 3 locations) src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/qqmap.js:600— src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/qqmap.js:600 · src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/qqmap.js:653 · src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/qqmap.js:706 — all 3 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Duplicated block (19 lines × 2 locations) src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/amap.js:649— src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/amap.js:649 · src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/amap.js:704 — all 2 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Duplicated block (17 lines × 8 locations) src/uni_modules/uni-editor/static/editor.js:744— src/uni_modules/uni-editor/static/editor.js:744 · src/uni_modules/uni-editor/static/editor.js:767 · src/uni_modules/uni-editor/static/editor.js:790 · src/uni_modules/uni-editor/static/editor.js:813 · +4 more site(s) not listed — all 8 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 (15 lines × 7 locations) src/uni_modules/uni-editor/static/editor.js:908— src/uni_modules/uni-editor/static/editor.js:908 · src/uni_modules/uni-editor/static/editor.js:930 · src/uni_modules/uni-editor/static/editor.js:952 · src/uni_modules/uni-editor/static/editor.js:974 · +3 more site(s) not listed — all 7 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 (15 lines × 2 locations) src/uni_modules/uni-map-common/uniCloud/cloudfunctions/uni-map-co/index.obj.js:202— src/uni_modules/uni-map-common/uniCloud/cloudfunctions/uni-map-co/index.obj.js:202 · src/uni_modules/uni-map-common/uniCloud/cloudfunctions/uni-map-co/index.obj.js:252 — 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 (14 lines × 2 locations) src/uni_modules/uni-editor/static/editor.js:861— src/uni_modules/uni-editor/static/editor.js:861 · src/uni_modules/uni-editor/static/editor.js:1022 — 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 (14 lines × 4 locations) src/uni_modules/uni-map-common/uniCloud/cloudfunctions/uni-map-co/index.obj.js:106— src/uni_modules/uni-map-common/uniCloud/cloudfunctions/uni-map-co/index.obj.js:106 · src/uni_modules/uni-map-common/uniCloud/cloudfunctions/uni-map-co/index.obj.js:129 · src/uni_modules/uni-map-common/uniCloud/cloudfunctions/uni-map-co/index.obj.js:149 · src/uni_modules/uni-map-common/uniCloud/cloudfunctions/uni-map-co/index.obj.js:170 — all 4 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication· Duplicated block with local edits (13 matched lines × 2 locations) · ×1
Duplicated block with local edits (13 matched lines × 2 locations) src/uni_modules/uni-pay-x/uniCloud/cloudfunctions/uni-pay-co/dao/uniIdUsers.js:3— src/uni_modules/uni-pay-x/uniCloud/cloudfunctions/uni-pay-co/dao/uniIdUsers.js:3 · src/uni_modules/uni-pay-x/uniCloud/cloudfunctions/uni-pay-co/dao/uniPayOrders.js:3 — 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.
Duplicated block (11 lines × 2 locations) src/uni_modules/uni-editor/static/quill/formats.js:223— src/uni_modules/uni-editor/static/quill/formats.js:223 · src/uni_modules/uni-editor/static/quill/formats.js:243 — 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 (11 lines × 3 locations) src/uni_modules/uni-pay-x/uniCloud/cloudfunctions/uni-pay-co/service/pay.js:574— src/uni_modules/uni-pay-x/uniCloud/cloudfunctions/uni-pay-co/service/pay.js:574 · src/uni_modules/uni-pay-x/uniCloud/cloudfunctions/uni-pay-co/service/pay.js:685 · src/uni_modules/uni-pay-x/uniCloud/cloudfunctions/uni-pay-co/service/pay.js:754 — all 3 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 (10 lines × 5 locations) src/uni_modules/uni-config-center/uniCloud/cloudfunctions/common/uni-config-center/uni-pay/config.js:16— src/uni_modules/uni-config-center/uniCloud/cloudfunctions/common/uni-config-center/uni-pay/config.js:16 · src/uni_modules/uni-config-center/uniCloud/cloudfunctions/common/uni-config-center/uni-pay/config.js:28 · src/uni_modules/uni-config-center/uniCloud/cloudfunctions/common/uni-config-center/uni-pay/config.js:40 · src/uni_modules/uni-config-center/uniCloud/cloudfunctions/common/uni-config-center/uni-pay/config.js:52 · +1 more site(s) not listed — all 5 copies are in the same file, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases.
Duplicated block (10 lines × 4 locations) src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/amap.js:518— src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/amap.js:518 · src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/qqmap.js:581 · src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/qqmap.js:635 · src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/qqmap.js:688 — the 4 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 (9 lines × 2 locations) src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/amap.js:502— src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/amap.js:502 · src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/amap.js:757 — all 2 copies are in the same file, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases.
Duplicated block (9 lines × 3 locations) src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/qqmap.js:517— src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/qqmap.js:517 · src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/qqmap.js:586 · src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/qqmap.js:693 — all 3 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 (8 lines × 2 locations) src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/amap.js:846— src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/amap.js:846 · src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/amap.js:854 — all 2 copies are in the same file, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases.
Complex function createOrder (cyclomatic 56, cognitive 84) src/uni_modules/uni-pay-x/uniCloud/cloudfunctions/uni-pay-co/service/pay.js:174— createOrder has cyclomatic complexity 56 and cognitive complexity 84; 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 format (cyclomatic 23, cognitive 33) · ×1
Complex function format (cyclomatic 23, cognitive 33) src/uni_modules/uni-editor/static/editor.js:330— format has cyclomatic complexity 23 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.
Complex function _getSign (cyclomatic 23, cognitive 22) src/uni_modules/uni-pay-x/uniCloud/cloudfunctions/uni-pay-co/libs/alipay.js:63— _getSign 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.
Complex function verifyReceiptFromAppleiap (cyclomatic 20, cognitive 29) src/uni_modules/uni-pay-x/uniCloud/cloudfunctions/uni-pay-co/service/pay.js:874— verifyReceiptFromAppleiap has cyclomatic complexity 20 and cognitive complexity 29; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function getOrder (cyclomatic 19, cognitive 27) src/uni_modules/uni-pay-x/uniCloud/cloudfunctions/uni-pay-co/service/pay.js:463— getOrder has cyclomatic complexity 19 and cognitive complexity 27; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 18, cognitive 16) src/pages/API/request/request.test.js:20— (anonymous) has cyclomatic complexity 18 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function refund (cyclomatic 16, cognitive 23) src/uni_modules/uni-pay-x/uniCloud/cloudfunctions/uni-pay-co/service/pay.js:565— refund has cyclomatic complexity 16 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 15, cognitive 18) src/pages/API/action-sheet/action-sheet.test.js:34— (anonymous) has cyclomatic complexity 15 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.
Complex function processReview (cyclomatic 13, cognitive 21) REDACTED:301— processReview has cyclomatic complexity 13 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function parseHTML (cyclomatic 13, cognitive 20) src/uni_modules/uni-editor/static/editor.js:33— parseHTML has cyclomatic complexity 13 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.
Complex function (anonymous) (cyclomatic 13, cognitive 12) src/pages/API/dialog-page/dialog-page.test.js:15— (anonymous) 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.
Complex function (anonymous) (cyclomatic 12, cognitive 14) src/pages/component/video/video.test.js:13— (anonymous) 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.
Complex function getProviderPayType (cyclomatic 12, cognitive 9) src/uni_modules/uni-pay-x/uniCloud/cloudfunctions/uni-pay-co/libs/common.js:106— getProviderPayType has cyclomatic complexity 12 and cognitive complexity 9; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function paymentNotify (cyclomatic 11, cognitive 18) src/uni_modules/uni-pay-x/uniCloud/cloudfunctions/uni-pay-co/service/pay.js:39— paymentNotify has cyclomatic complexity 11 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.
Complex function location2address (cyclomatic 11, cognitive 16) src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/qqmap.js:59— location2address has cyclomatic complexity 11 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function timeFormat (cyclomatic 11, cognitive 15) src/uni_modules/uni-pay-x/uniCloud/cloudfunctions/uni-pay-co/libs/common.js:8— timeFormat has cyclomatic complexity 11 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 11, cognitive 12) src/uni_modules/uni-upgrade-center-app/utils/call-check-version.ts:34— (anonymous) has cyclomatic complexity 11 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R3 · Large Files· src/uni_modules/uni-pay-x/uniCloud/cloudfunctions/uni-pay-co/service/pay.js · ×1
src/uni_modules/uni-pay-x/uniCloud/cloudfunctions/uni-pay-co/service/pay.js: 1223 lines of code src/uni_modules/uni-pay-x/uniCloud/cloudfunctions/uni-pay-co/service/pay.js:1— src/uni_modules/uni-pay-x/uniCloud/cloudfunctions/uni-pay-co/service/pay.js has 1223 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· src/uni_modules/uni-editor/static/editor.js · ×1
src/uni_modules/uni-editor/static/editor.js: 1044 lines of code src/uni_modules/uni-editor/static/editor.js:1— src/uni_modules/uni-editor/static/editor.js has 1044 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· src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/amap.js · ×1
src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/amap.js: 913 lines of code src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/amap.js:1— src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/amap.js has 913 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· src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/qqmap.js · ×1
src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/qqmap.js: 791 lines of code src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/qqmap.js:1— src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/qqmap.js has 791 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· src/wxcomponents/vant/icon/index.vue · ×1
src/wxcomponents/vant/icon/index.vue: 775 lines of code src/wxcomponents/vant/icon/index.vue:1— src/wxcomponents/vant/icon/index.vue has 775 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· src/uni_modules/uni-upgrade-center-app/pages/upgrade-popup.vue · ×1
src/uni_modules/uni-upgrade-center-app/pages/upgrade-popup.vue: 620 lines of code src/uni_modules/uni-upgrade-center-app/pages/upgrade-popup.vue:1— src/uni_modules/uni-upgrade-center-app/pages/upgrade-popup.vue has 620 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· src/uni_modules/uni-map-common/uniCloud/cloudfunctions/uni-map-co/index.obj.js · ×1
src/uni_modules/uni-map-common/uniCloud/cloudfunctions/uni-map-co/index.obj.js: 497 lines of code src/uni_modules/uni-map-common/uniCloud/cloudfunctions/uni-map-co/index.obj.js:1— src/uni_modules/uni-map-common/uniCloud/cloudfunctions/uni-map-co/index.obj.js has 497 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· src/uni_modules/uni-editor/static/quill/formats.js · ×1
src/uni_modules/uni-editor/static/quill/formats.js: 408 lines of code src/uni_modules/uni-editor/static/quill/formats.js:1— src/uni_modules/uni-editor/static/quill/formats.js has 408 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
No lint or typecheck script — test ✓ · lint ✗ · typecheck ✗ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
Dead file (~226 LoC) src/components/api-set-tabbar/api-set-tabbar.vue— no import path from any entry point (42 application, 21 tooling, 232 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 (~191 LoC) src/jest-setup.js— no import path from any entry point (42 application, 21 tooling, 232 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 (~120 LoC) src/wxcomponents/vant/mixins/transition.js— no import path from any entry point (42 application, 21 tooling, 232 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 (~100 LoC) src/components/uni-collapse-item/uni-collapse-item.vue— no import path from any entry point (42 application, 21 tooling, 232 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 (~92 LoC) src/wxcomponents/vant/button/index.vue— no import path from any entry point (42 application, 21 tooling, 232 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 (~68 LoC) src/wxcomponents/vant/button/index.js— no import path from any entry point (42 application, 21 tooling, 232 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 (~56 LoC) src/components/u-link/u-link.vue— no import path from any entry point (42 application, 21 tooling, 232 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 (~52 LoC) src/wxcomponents/vant/icon/index.vue— no import path from any entry point (42 application, 21 tooling, 232 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/wxcomponents/vant/button/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 (~47 LoC) src/wxcomponents/vant/loading/index.vue— no import path from any entry point (42 application, 21 tooling, 232 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/wxcomponents/vant/button/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 (~39 LoC) src/wxcomponents/vant/icon/index.js— no import path from any entry point (42 application, 21 tooling, 232 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 (~38 LoC) src/components/uni-collapse/uni-collapse.vue— no import path from any entry point (42 application, 21 tooling, 232 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 (~36 LoC) src/uni_modules/uni-map-common/uniCloud/cloudfunctions/uni-map-co/uni-map-co.param.js— no import path from any entry point (42 application, 21 tooling, 232 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 (~35 LoC) src/wxcomponents/vant/mixins/touch.js— no import path from any entry point (42 application, 21 tooling, 232 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 (~31 LoC) src/pages/component/unicloud-db/unicloud-db.test1.js— no import path from any entry point (42 application, 21 tooling, 232 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 (~25 LoC) src/wxcomponents/vant/mixins/open-type.js— no import path from any entry point (42 application, 21 tooling, 232 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (src/wxcomponents/vant/button/index.js, src/wxcomponents/vant/button/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 (~22 LoC) src/wxcomponents/vant/mixins/basic.js— no import path from any entry point (42 application, 21 tooling, 232 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/wxcomponents/vant/common/component.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~19 LoC) src/wxcomponents/vant/mixins/observer/index.js— no import path from any entry point (42 application, 21 tooling, 232 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/wxcomponents/vant/common/component.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~18 LoC) src/wxcomponents/vant/mixins/button.js— no import path from any entry point (42 application, 21 tooling, 232 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (src/wxcomponents/vant/button/index.js, src/wxcomponents/vant/button/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
Deprecated: glob REDACTED:2045— glob 7.2.3 is resolved in REDACTED and is marked deprecated by its publisher: "Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: inflight REDACTED:2216— inflight 1.0.6 is resolved in REDACTED and is marked deprecated by its publisher: "This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @babel/plugin-proposal-async-generator-functions REDACTED:885— @babel/plugin-proposal-async-generator-functions 7.20.7 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-async-generator-functions instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @babel/plugin-proposal-async-generator-functions REDACTED:895— @babel/plugin-proposal-async-generator-functions 7.8.3 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-async-generator-functions instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @babel/plugin-proposal-class-properties REDACTED:903— @babel/plugin-proposal-class-properties 7.18.6 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-class-properties instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @babel/plugin-proposal-class-properties REDACTED:911— @babel/plugin-proposal-class-properties 7.8.3 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-class-properties instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @babel/plugin-proposal-class-static-block REDACTED:918— @babel/plugin-proposal-class-static-block 7.21.0 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-class-static-block instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @babel/plugin-proposal-dynamic-import REDACTED:935— @babel/plugin-proposal-dynamic-import 7.18.6 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-dynamic-import instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @babel/plugin-proposal-dynamic-import REDACTED:943— @babel/plugin-proposal-dynamic-import 7.8.3 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-dynamic-import instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @babel/plugin-proposal-export-namespace-from REDACTED:950— @babel/plugin-proposal-export-namespace-from 7.18.9 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-export-namespace-from instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @babel/plugin-proposal-json-strings REDACTED:958— @babel/plugin-proposal-json-strings 7.18.6 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-json-strings instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @babel/plugin-proposal-json-strings REDACTED:966— @babel/plugin-proposal-json-strings 7.8.3 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-json-strings instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @babel/plugin-proposal-logical-assignment-operators REDACTED:973— @babel/plugin-proposal-logical-assignment-operators 7.20.7 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-logical-assignment-operators instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @babel/plugin-proposal-nullish-coalescing-operator REDACTED:981— @babel/plugin-proposal-nullish-coalescing-operator 7.18.6 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-nullish-coalescing-operator instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @babel/plugin-proposal-nullish-coalescing-operator REDACTED:989— @babel/plugin-proposal-nullish-coalescing-operator 7.8.3 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-nullish-coalescing-operator instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @babel/plugin-proposal-numeric-separator REDACTED:996— @babel/plugin-proposal-numeric-separator 7.18.6 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-numeric-separator instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @babel/plugin-proposal-numeric-separator REDACTED:1004— @babel/plugin-proposal-numeric-separator 7.8.3 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-numeric-separator instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @babel/plugin-proposal-object-rest-spread REDACTED:1011— @babel/plugin-proposal-object-rest-spread 7.20.7 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-object-rest-spread instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @babel/plugin-proposal-object-rest-spread REDACTED:1022— @babel/plugin-proposal-object-rest-spread 7.9.5 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-object-rest-spread instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @babel/plugin-proposal-optional-catch-binding REDACTED:1030— @babel/plugin-proposal-optional-catch-binding 7.18.6 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-optional-catch-binding instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @babel/plugin-proposal-optional-catch-binding REDACTED:1038— @babel/plugin-proposal-optional-catch-binding 7.8.3 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-optional-catch-binding instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @babel/plugin-proposal-optional-chaining REDACTED:1045— @babel/plugin-proposal-optional-chaining 7.21.0 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-optional-chaining instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @babel/plugin-proposal-optional-chaining REDACTED:1054— @babel/plugin-proposal-optional-chaining 7.9.0 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-optional-chaining instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @babel/plugin-proposal-private-methods REDACTED:1061— @babel/plugin-proposal-private-methods 7.18.6 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-private-methods instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @babel/plugin-proposal-private-property-in-object REDACTED:1074— @babel/plugin-proposal-private-property-in-object 7.21.0 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-private-property-in-object instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Duplicated predicate src/uni_modules/uni-createInnerAudioContext/utssdk/app-android/AudioPlayer.kt:262— `!this.player.isPlaying && !this.isPausedByUser && !this.player.isLoading` appears character-identically in 2 files — src/uni_modules/uni-createInnerAudioContext/utssdk/app-android/AudioPlayer.kt, src/uni_modules/uni-getBackgroundAudioManager/utssdk/app-android/BackgroundAudioPlayer.kt. 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 src/uni_modules/uni-createInnerAudioContext/utssdk/app-android/AudioPlayer.kt:120— `_src.startsWith("http:") || _src.startsWith("https:")` appears character-identically in 2 files — src/uni_modules/uni-createInnerAudioContext/utssdk/app-android/AudioPlayer.kt, src/uni_modules/uni-getBackgroundAudioManager/utssdk/app-android/BackgroundAudioPlayer.kt. 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 src/uni_modules/uni-createInnerAudioContext/utssdk/app-android/AudioPlayer.kt:135— `cacheDataSourceFactory != null && this._cache == true` appears character-identically in 2 files — src/uni_modules/uni-createInnerAudioContext/utssdk/app-android/AudioPlayer.kt, src/uni_modules/uni-getBackgroundAudioManager/utssdk/app-android/BackgroundAudioPlayer.kt. 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 src/uni_modules/uni-createInnerAudioContext/utssdk/app-android/AudioPlayer.kt:103— `src.startsWith("http:") || src.startsWith("https:")` appears character-identically in 2 files — src/uni_modules/uni-createInnerAudioContext/utssdk/app-android/AudioPlayer.kt, src/uni_modules/uni-getBackgroundAudioManager/utssdk/app-android/BackgroundAudioPlayer.kt. 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 src/uni_modules/uni-createInnerAudioContext/utssdk/app-android/AudioPlayer.kt:195— `this.player.playbackState == Player.STATE_READY || this.player.playbackState == Player.STATE_ENDED` appears character-identically in 2 files — src/uni_modules/uni-createInnerAudioContext/utssdk/app-android/AudioPlayer.kt, src/uni_modules/uni-getBackgroundAudioManager/utssdk/app-android/BackgroundAudioPlayer.kt. 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 src/uni_modules/uni-createInnerAudioContext/utssdk/app-ios/UniAudioPlayer.swift:455— `!seekTime.isValid || seekTime.isIndefinite` appears character-identically in 2 files — src/uni_modules/uni-createInnerAudioContext/utssdk/app-ios/UniAudioPlayer.swift, src/uni_modules/uni-getBackgroundAudioManager/utssdk/app-ios/UniBackgroundAudioManager.swift. 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 src/uni_modules/uni-createInnerAudioContext/utssdk/app-ios/UniAudioPlayer.swift:424— `(current < rangeStart || current > rangeEnd) && !isSupportDVR` appears character-identically in 2 files — src/uni_modules/uni-createInnerAudioContext/utssdk/app-ios/UniAudioPlayer.swift, src/uni_modules/uni-getBackgroundAudioManager/utssdk/app-ios/UniBackgroundAudioManager.swift. 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 src/uni_modules/uni-prompt/utssdk/app-ios/UniToast/MCToast+Loading.swift:163— `(kToastImageSize.width > kToastSize.width) || (kToastImageSize.height > kToastSize.height)` appears character-identically in 2 files — src/uni_modules/uni-prompt/utssdk/app-ios/UniToast/MCToast+Loading.swift, src/uni_modules/uni-prompt/utssdk/app-ios/UniToast/MCToast+Status.swift. 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 src/uni_modules/uni-createInnerAudioContext/utssdk/app-ios/UniAudioPlayer.swift:225— `_playbackRate != newValue && !isHLSLiveOrEvent()` appears character-identically in 2 files — src/uni_modules/uni-createInnerAudioContext/utssdk/app-ios/UniAudioPlayer.swift, src/uni_modules/uni-getBackgroundAudioManager/utssdk/app-ios/UniBackgroundAudioManager.swift. 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 src/uni_modules/uni-createInnerAudioContext/utssdk/app-ios/UniAudioPlayer.swift:585— `asset.url == url || asset.url == tempCacheUrl` appears character-identically in 2 files — src/uni_modules/uni-createInnerAudioContext/utssdk/app-ios/UniAudioPlayer.swift, src/uni_modules/uni-getBackgroundAudioManager/utssdk/app-ios/UniBackgroundAudioManager.swift. 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 src/uni_modules/uni-video/utssdk/app-ios/VideoPlayer/Managers/UniVideoPlayerManager.swift:1092— `pathExtension == "m3u8" || pathExtension == "m3u"` appears character-identically in 2 files — src/uni_modules/uni-video/utssdk/app-ios/VideoPlayer/Managers/UniVideoPlayerManager.swift, src/uni_modules/uni-video/utssdk/app-ios/VideoPlayer/Protocols/M3U8ResourceLoaderDelegate.swift. 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 src/uni_modules/uni-createInnerAudioContext/utssdk/app-ios/UniAudioPlayer.swift:117— `player?.rate != 0 && player?.error == nil && currentItem.status == .readyToPlay && currentItem.isPlaybackLikelyToKeepUp` appears character-identically in 2 files — src/uni_modules/uni-createInnerAudioContext/utssdk/app-ios/UniAudioPlayer.swift, src/uni_modules/uni-getBackgroundAudioManager/utssdk/app-ios/UniBackgroundAudioManager.swift. 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 src/uni_modules/uni-createInnerAudioContext/utssdk/app-ios/UniAudioPlayer.swift:99— `player?.timeControlStatus != .playing && !_isManualPause` appears character-identically in 2 files — src/uni_modules/uni-createInnerAudioContext/utssdk/app-ios/UniAudioPlayer.swift, src/uni_modules/uni-getBackgroundAudioManager/utssdk/app-ios/UniBackgroundAudioManager.swift. 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 src/uni_modules/uni-createInnerAudioContext/utssdk/app-ios/UniAudioPlayer.swift:178— `player?.timeControlStatus == .paused || player?.timeControlStatus == .waitingToPlayAtSpecifiedRate` appears character-identically in 2 files — src/uni_modules/uni-createInnerAudioContext/utssdk/app-ios/UniAudioPlayer.swift, src/uni_modules/uni-getBackgroundAudioManager/utssdk/app-ios/UniBackgroundAudioManager.swift. 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 src/uni_modules/uni-createInnerAudioContext/utssdk/app-ios/UniAudioPlayer.swift:564— `self.src.startsWith("http") || self.src.startsWith("https")` appears character-identically in 2 files — src/uni_modules/uni-createInnerAudioContext/utssdk/app-ios/UniAudioPlayer.swift, src/uni_modules/uni-getBackgroundAudioManager/utssdk/app-ios/UniBackgroundAudioManager.swift. 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 src/uni_modules/uni-form/utssdk/app-ios/UniInputView.swift:97— `view is UITextField || view is UITextView` appears character-identically in 2 files — src/uni_modules/uni-form/utssdk/app-ios/UniInputView.swift, src/uni_modules/uni-form/utssdk/app-ios/UniTextareaView.swift. 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.
redundant comment src/pages/API/get-current-pages/get-current-pages.test.js:74— "setPageStyle" repeats the code it sits on: 3 of its 3 words (set, page, style) are already in `await page.callMethod('setPageStyle', {`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/pages/API/get-current-pages/get-current-pages.test.js:105— "setPageStyle" repeats the code it sits on: 3 of its 3 words (set, page, style) are already in `await page.callMethod('setPageStyle', {`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/pages/API/get-current-pages/set-page-style-disable-pull-down-refresh.test.js:44— "setPageStyle" repeats the code it sits on: 3 of its 3 words (set, page, style) are already in `await page.callMethod('setPageStyle', false)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/pages/API/get-file-system-manager/get-file-system-manager.test.js:1366— "testAppendFileBuffer" repeats the code it sits on: 4 of its 4 words (test, append, file, buffer) are already in `it('testAppendFileBuffer', async () =>`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/pages/CSS/set-css.test.js:875— "console.log('batch',batch)" repeats the code it sits on: 3 of its 3 words (console, log, batch) are already in `console.log('batchIndex',batchIndex)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/pages/CSS/transition/transition.test.js:25— "changeTransitionAll" repeats the code it sits on: 3 of its 3 words (change, transition, all) are already in `await page.callMethod('changeTransitionAll')`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/uni_modules/uni-upgrade-center-app/utils/call-check-version.ts:37— "systemInfo.appVersion" repeats the code it sits on: 4 of its 4 words (system, info, app, version) are already in `const appVersion = systemInfo.appVersion //systemInfo.appVersion`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
Silent fallback default in catch src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/qqmap.js:814— `polylineFormat` 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 src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/qqmap.js:827— `priceFormat` swallows every exception into `return -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 src/uni_modules/uni-map-common/uniCloud/cloudfunctions/common/uni-map-common/service/amap.js:930— `priceFormat` swallows every exception into `return -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.
Outdated (npm): minimatch examples/hello-uvue/code-review/package.json:14— minimatch is pinned at 5.1.6; registry.npmjs.org publishes 11.0.8 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Documentation: no build, run or usage example src/readme.md:1— `src` is a published package (`package.json` without `"private": true`) and neither `src/readme.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
Thin README README.md:1— The root README is 119 words, against a bar of 120. Of the three newcomer-critical sections this check looks for by heading, in the README and in the repository documents it links, it found no a testing section, no an architecture or project-map section. Sections are matched on HEADING text only, so material written under a heading this check does not recognise — or with no heading at all — is not seen and this row may understate what the document covers.
No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
P1 · CI/CD gates· CI test execution not evidenced · ×1
CI test execution not evidenced — A CI pipeline exists but no test-runner invocation (your stack's test command, or a test job) was found — changes may merge without the suite running.
P1 · CI/CD gates· CI build step not evidenced · ×1
CI build step not evidenced — A CI pipeline exists but no build step was matched — changes may merge without the build ever running. A build step may be invoked directly as a command, or declared as a task that a runner named in the pipeline resolves.
No SAST — No static application security testing detected. For this repository's stack, add CodeQL's Swift pack (Swift/Xcode) (or `semgrep --config=auto`, which runs on any language) — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
No dependency-update automation examples/hello-uts/package.json:14— `examples/hello-uts/package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`.
Not-null assertions (`!!`) override null safety — ~7.6 `!!` not-null assertions per 1k Kotlin product lines — 54 across the 7086 line(s) of the 24 Kotlin file(s) read (generated, test and sample code not counted). Densest: src/uni_modules/uni-createInnerAudioContext/utssdk/app-android/AudioPlayer.kt (12), src/uni_modules/uni-camera/utssdk/app-android/CameraImpl.kt (11), src/uni_modules/uni-getBackgroundAudioManager/utssdk/app-android/AudioService.kt (8). Each one tells the compiler to trust the author about null and becomes a `NullPointerException` the first time the author is wrong. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
Skipped (documented): (unnamed test) examples/hello-uvue/pages/render-function/withModifiers/withModifiers.test.js:36— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) examples/hello-uvue/pages/render-function/withModifiers/withModifiers.test.js:41— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) examples/hello-uvue/pages/render-function/withDirectives/withDirectives.test.js:28— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) examples/hello-uvue/pages/render-function/withDirectives/withDirectives.test.js:33— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) examples/hello-uvue/pages/render-function/resolveComponent/resolveComponent.test.js:28— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) examples/hello-uvue/pages/render-function/resolveComponent/resolveComponent.test.js:33— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) examples/hello-uvue/pages/render-function/render/render.test.js:56— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) examples/hello-uvue/pages/render-function/render/render.test.js:61— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) examples/hello-uvue/pages/render-function/mergeProps/mergeProps.test.js:33— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) examples/hello-uvue/pages/render-function/mergeProps/mergeProps.test.js:37— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) examples/hello-uvue/pages/render-function/isVNode/isVNode.test.js:28— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) examples/hello-uvue/pages/render-function/isVNode/isVNode.test.js:32— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) examples/hello-uvue/pages/render-function/cloneVNode/cloneVNode.test.js:40— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) examples/hello-uvue/pages/render-function/cloneVNode/cloneVNode.test.js:45— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) examples/hello-uvue/pages/reactivity/core/computed/computed.test.js:39— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) examples/hello-uvue/pages/reactivity/core/computed/computed.test.js:44— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) examples/hello-uvue/pages/lifecycle/page/page.test.js:130— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) examples/hello-uvue/pages/lifecycle/page/page.test.js:135— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) examples/hello-uvue/pages/examples/set-custom-child-component-root-node-class/set-custom-child-component-root-node-class.test.js:25— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) examples/hello-uvue/pages/examples/set-custom-child-component-root-node-class/set-custom-child-component-root-node-class.test.js:30— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) examples/hello-uvue/pages/examples/nested-component-communication/nested-component-communication.test.js:48— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) examples/hello-uvue/pages/examples/nested-component-communication/nested-component-communication.test.js:52— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) examples/hello-uvue/pages/error/throw-error/throw-error.test.js:51— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) examples/hello-uvue/pages/error/throw-error/throw-error.test.js:55— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) examples/hello-uvue/pages/error/runtime-error/runtime-error.test.js:18— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Outdated (npm): @gitbeaker/rest — @gitbeaker/rest is pinned at 42.5.0; registry.npmjs.org publishes 44.0.6 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): axios — axios is pinned at 1.8.4; registry.npmjs.org publishes 1.21.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): dotenv — dotenv is pinned at 16.5.0; registry.npmjs.org publishes 18.0.10 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): yaml — yaml is pinned at 2.7.1; registry.npmjs.org publishes 2.9.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
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.
trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
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) — `src/uni_modules/uni-event/utssdk/app-ios/native.swift`, `src/uni_modules/uni-upgrade-center-app/utils/check-update.ts` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
Run 01a1ddad-3ea6-76d4-96dd-7d47e1e16119 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 149 · Warnings: 617 · Recommendations: 153 · Info: 99 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 15-11-2026 @ 05:28 UTC.
Downloadable artifacts
Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.