Public report of NovaWorks/ZCard, published 17 November 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive 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, 17 November 2026, 18:43 UTC · Survey ID cd_9efcf1f3ae974399a6cc554828bafaa4
NovaWorks/ZCard
Measured 17 November 2026, 18:22 UTC, at code version fcc8a79
First survey, so nothing to compare with yet
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: 84,407 lines of product code in 4 projects, tests not counted · Estimated rebuild effort: about 0.6 person-years · Weakest lens: Production Readiness, 38.9
Findings by how serious they are
151 critical398 serious117 minor
18 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Canine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
17 November 2026, 18:22 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 ▸
69of 69 dimensions measured by tools.
655of 666 findings point to an exact file and line, so you can open each one in the code. The other 11 concern the repository as a whole, such as missing documentation.
69dimensions across 7 lenses, read from 84,407 lines of product code in 4 projects.
NovaWorks/ZCard is rated At risk because critical security findings are open, most of them in the packages it uses. Its score is held back because we found no working pipeline that builds or tests changes to the code and no automated security scanning of the code, its secrets or its dependencies. It scores 45.7 out of 100, which the At risk rating leaves unchanged.
Production Readiness, at 38.9, is the weakest lens and counts most in the score. The best first step is making the controls keyboard-usable, worth about 3.3 points. Adding an automated build and test pipeline would lift Production Readiness itself, worth about 3.0 points. Raising Production Readiness to 70 would lift the score to about 50.9.
Fifty-three known security holes in the packages the code depends on can be used by attackers. One automatic update takes new releases before a bad one can be spotted, and forty controls can't be used without a mouse. Making the controls work with a keyboard, updating the vulnerable packages and setting a waiting period for automatic updates would close these risks. The 23 form fields without a label need a label.
The product code is 84,407 lines, about €85,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 Production Readiness rose from 38.9 to 70, the lowest score rated Strong, the score would rise from 45.7 to about 50.9.
Code composition: what the lines of code are
Product code 89%Tests 11%
Rebuild cost: about €85,000 · Estimate
Cost to rebuild
€28,000 to €140,000, for 469 to 1,489 hours of work, about 0.6 person-years for 1 to 2 engineers
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 46. 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: 84,407 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
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
Raises the score by about 3.3 points · Medium effort · Keyboard semantics
2
Add a CI workflow that builds and runs the test suite on every push/PR.
The repository declares its tests as `cd storefront && pnpm test` (`storefront/package.json`): run that.
Raises the score by about 3.0 points · Medium effort · CI/CD gates
3
Run what this repository's stack ships: phpstan or psalm — 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.
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 €85,000 to build again, about 0.6 person-years of work. Its weakest lens is Production Readiness, at 38.9 (Weak). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
If you do one thing first · First action
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href. Of all the actions in this report, it raises the score most for the work it takes: about 3.3 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
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.
172 modules, with 92 dependencies between them. 2 loops run through 4 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 132 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.
App.Payment uses App.Payment.Contracts, so a change to App.Payment.Contracts can break App.Payment, while a change to App.Payment can't break App.Payment.Contracts.
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.
sysadmin.src.api uses storefront.src.api.categories, so a change to storefront.src.api.categories can break sysadmin.src.api, while a change to sysadmin.src.api can't break storefront.src.api.categories.
Position
Below the diagonal: sysadmin.src.api uses a module listed above it, which is the healthy direction.
sysadmin.src.hooks.core.useChart uses sysadmin.src.types.component.chart, so a change to sysadmin.src.types.component.chart can break sysadmin.src.hooks.core.useChart, while a change to sysadmin.src.hooks.core.useChart can't break sysadmin.src.types.component.chart.
Position
Below the diagonal: sysadmin.src.hooks.core.useChart uses a module listed above it, which is the healthy direction.
sysadmin.src.router.core.IframeRouteManager uses sysadmin.src.types.router, so a change to sysadmin.src.types.router can break sysadmin.src.router.core.IframeRouteManager, while a change to sysadmin.src.router.core.IframeRouteManager can't break sysadmin.src.types.router.
Position
Below the diagonal: sysadmin.src.router.core.IframeRouteManager uses a module listed above it, which is the healthy direction.
sysadmin.src.router.core.RouteValidator uses sysadmin.src.types.router, so a change to sysadmin.src.types.router can break sysadmin.src.router.core.RouteValidator, while a change to sysadmin.src.router.core.RouteValidator can't break sysadmin.src.types.router.
Position
Below the diagonal: sysadmin.src.router.core.RouteValidator uses a module listed above it, which is the healthy direction.
sysadmin.src.types.store uses sysadmin.src.enums.appEnum, so a change to sysadmin.src.enums.appEnum can break sysadmin.src.types.store, while a change to sysadmin.src.types.store can't break sysadmin.src.enums.appEnum.
Position
Below the diagonal: sysadmin.src.types.store uses a module listed above it, which is the healthy direction.
sysadmin.src.utils.table uses sysadmin.src.utils.table.tableCache, so a change to sysadmin.src.utils.table.tableCache can break sysadmin.src.utils.table, while a change to sysadmin.src.utils.table can't break sysadmin.src.utils.table.tableCache.
Position
Below the diagonal: sysadmin.src.utils.table uses a module listed above it, which is the healthy direction.
App.Payment.Contracts uses App.Payment, so a change to App.Payment can break App.Payment.Contracts, while a change to App.Payment.Contracts can't break App.Payment.
Position
Below the diagonal: App.Payment.Contracts uses a module listed above it, which is the healthy direction.
sysadmin.src.hooks.core uses sysadmin.src.enums.appEnum, so a change to sysadmin.src.enums.appEnum can break sysadmin.src.hooks.core, while a change to sysadmin.src.hooks.core can't break sysadmin.src.enums.appEnum.
Position
Below the diagonal: sysadmin.src.hooks.core uses a module listed above it, which is the healthy direction.
sysadmin.src.hooks.core uses sysadmin.src.types.component.chart, so a change to sysadmin.src.types.component.chart can break sysadmin.src.hooks.core, while a change to sysadmin.src.hooks.core can't break sysadmin.src.types.component.chart.
Position
Below the diagonal: sysadmin.src.hooks.core uses a module listed above it, which is the healthy direction.
sysadmin.src.hooks.core uses sysadmin.src.utils.table.tableCache, so a change to sysadmin.src.utils.table.tableCache can break sysadmin.src.hooks.core, while a change to sysadmin.src.hooks.core can't break sysadmin.src.utils.table.tableCache.
Position
Below the diagonal: sysadmin.src.hooks.core uses a module listed above it, which is the healthy direction.
sysadmin.src.hooks.core uses sysadmin.src.hooks.core.useChart, so a change to sysadmin.src.hooks.core.useChart can break sysadmin.src.hooks.core, while a change to sysadmin.src.hooks.core can't break sysadmin.src.hooks.core.useChart.
Position
Below the diagonal: sysadmin.src.hooks.core uses a module listed above it, which is the healthy direction.
sysadmin.src.router.core.RouteTransformer uses sysadmin.src.router.core.ComponentLoader, so a change to sysadmin.src.router.core.ComponentLoader can break sysadmin.src.router.core.RouteTransformer, while a change to sysadmin.src.router.core.RouteTransformer can't break sysadmin.src.router.core.ComponentLoader.
Position
Below the diagonal: sysadmin.src.router.core.RouteTransformer uses a module listed above it, which is the healthy direction.
sysadmin.src.router.core.RouteTransformer uses sysadmin.src.types.router, so a change to sysadmin.src.types.router can break sysadmin.src.router.core.RouteTransformer, while a change to sysadmin.src.router.core.RouteTransformer can't break sysadmin.src.types.router.
Position
Below the diagonal: sysadmin.src.router.core.RouteTransformer uses a module listed above it, which is the healthy direction.
sysadmin.src.router.core.RouteTransformer uses sysadmin.src.router.core.IframeRouteManager, so a change to sysadmin.src.router.core.IframeRouteManager can break sysadmin.src.router.core.RouteTransformer, while a change to sysadmin.src.router.core.RouteTransformer can't break sysadmin.src.router.core.IframeRouteManager.
Position
Below the diagonal: sysadmin.src.router.core.RouteTransformer uses a module listed above it, which is the healthy direction.
sysadmin.src.store.modules.worktab uses sysadmin.src.types.store, so a change to sysadmin.src.types.store can break sysadmin.src.store.modules.worktab, while a change to sysadmin.src.store.modules.worktab can't break sysadmin.src.types.store.
Position
Below the diagonal: sysadmin.src.store.modules.worktab uses a module listed above it, which is the healthy direction.
App.Models uses App.Payment.Contracts, so a change to App.Payment.Contracts can break App.Models, while a change to App.Models can't break App.Payment.Contracts.
Position
Below the diagonal: App.Models uses a module listed above it, which is the healthy direction.
App.Payment.Drivers uses App.Payment, so a change to App.Payment can break App.Payment.Drivers, while a change to App.Payment.Drivers can't break App.Payment.
Position
Below the diagonal: App.Payment.Drivers uses a module listed above it, which is the healthy direction.
App.Payment.Drivers uses App.Payment.Contracts, so a change to App.Payment.Contracts can break App.Payment.Drivers, while a change to App.Payment.Drivers can't break App.Payment.Contracts.
Position
Below the diagonal: App.Payment.Drivers uses a module listed above it, which is the healthy direction.
sysadmin.src.router.core.RouteRegistry uses sysadmin.src.router.core.ComponentLoader, so a change to sysadmin.src.router.core.ComponentLoader can break sysadmin.src.router.core.RouteRegistry, while a change to sysadmin.src.router.core.RouteRegistry can't break sysadmin.src.router.core.ComponentLoader.
Position
Below the diagonal: sysadmin.src.router.core.RouteRegistry uses a module listed above it, which is the healthy direction.
sysadmin.src.router.core.RouteRegistry uses sysadmin.src.router.core.RouteValidator, so a change to sysadmin.src.router.core.RouteValidator can break sysadmin.src.router.core.RouteRegistry, while a change to sysadmin.src.router.core.RouteRegistry can't break sysadmin.src.router.core.RouteValidator.
Position
Below the diagonal: sysadmin.src.router.core.RouteRegistry uses a module listed above it, which is the healthy direction.
sysadmin.src.router.core.RouteRegistry uses sysadmin.src.router.core.RouteTransformer, so a change to sysadmin.src.router.core.RouteTransformer can break sysadmin.src.router.core.RouteRegistry, while a change to sysadmin.src.router.core.RouteRegistry can't break sysadmin.src.router.core.RouteTransformer.
Position
Below the diagonal: sysadmin.src.router.core.RouteRegistry uses a module listed above it, which is the healthy direction.
sysadmin.src.store.modules uses sysadmin.src.enums.appEnum, so a change to sysadmin.src.enums.appEnum can break sysadmin.src.store.modules, while a change to sysadmin.src.store.modules can't break sysadmin.src.enums.appEnum.
Position
Below the diagonal: sysadmin.src.store.modules uses a module listed above it, which is the healthy direction.
sysadmin.src.store.modules uses sysadmin.src.types.store, so a change to sysadmin.src.types.store can break sysadmin.src.store.modules, while a change to sysadmin.src.store.modules can't break sysadmin.src.types.store.
Position
Below the diagonal: sysadmin.src.store.modules uses a module listed above it, which is the healthy direction.
sysadmin.src.store.modules uses sysadmin.src.store.modules.worktab, so a change to sysadmin.src.store.modules.worktab can break sysadmin.src.store.modules, while a change to sysadmin.src.store.modules can't break sysadmin.src.store.modules.worktab.
Position
Below the diagonal: sysadmin.src.store.modules uses a module listed above it, which is the healthy direction.
App.Filament.Pages uses App.Models, so a change to App.Models can break App.Filament.Pages, while a change to App.Filament.Pages can't break App.Models.
Position
Below the diagonal: App.Filament.Pages uses a module listed above it, which is the healthy direction.
App.Supply.Contracts uses App.Supply.Dto, so a change to App.Supply.Dto can break App.Supply.Contracts, while a change to App.Supply.Contracts can't break App.Supply.Dto.
Position
Below the diagonal: App.Supply.Contracts uses a module listed above it, which is the healthy direction.
App.Supply.Contracts uses App.Models, so a change to App.Models can break App.Supply.Contracts, while a change to App.Supply.Contracts can't break App.Models.
Position
Below the diagonal: App.Supply.Contracts uses a module listed above it, which is the healthy direction.
App.Supply.Drivers uses App.Supply.Dto, so a change to App.Supply.Dto can break App.Supply.Drivers, while a change to App.Supply.Drivers can't break App.Supply.Dto.
Position
Below the diagonal: App.Supply.Drivers uses a module listed above it, which is the healthy direction.
App.Supply.Drivers uses App.Models, so a change to App.Models can break App.Supply.Drivers, while a change to App.Supply.Drivers can't break App.Models.
Position
Below the diagonal: App.Supply.Drivers uses a module listed above it, which is the healthy direction.
App.Supply.Drivers uses App.Supply.Contracts, so a change to App.Supply.Contracts can break App.Supply.Drivers, while a change to App.Supply.Drivers can't break App.Supply.Contracts.
Position
Below the diagonal: App.Supply.Drivers uses a module listed above it, which is the healthy direction.
App.Support uses App.Payment.Contracts, so a change to App.Payment.Contracts can break App.Support, while a change to App.Support can't break App.Payment.Contracts.
Position
Below the diagonal: App.Support uses a module listed above it, which is the healthy direction.
App.Http.Controllers.Api uses App.Http.Controllers, so a change to App.Http.Controllers can break App.Http.Controllers.Api, while a change to App.Http.Controllers.Api can't break App.Http.Controllers.
Position
Below the diagonal: App.Http.Controllers.Api uses a module listed above it, which is the healthy direction.
App.Http.Controllers.Api uses App.Models, so a change to App.Models can break App.Http.Controllers.Api, while a change to App.Http.Controllers.Api can't break App.Models.
Position
Below the diagonal: App.Http.Controllers.Api uses a module listed above it, which is the healthy direction.
App.Http.Controllers.Api uses App.Support, so a change to App.Support can break App.Http.Controllers.Api, while a change to App.Http.Controllers.Api can't break App.Support.
Position
Below the diagonal: App.Http.Controllers.Api uses a module listed above it, which is the healthy direction.
App.Supply uses App.Supply.Contracts, so a change to App.Supply.Contracts can break App.Supply, while a change to App.Supply can't break App.Supply.Contracts.
Position
Below the diagonal: App.Supply uses a module listed above it, which is the healthy direction.
App.Console.Commands uses App.Support, so a change to App.Support can break App.Console.Commands, while a change to App.Console.Commands can't break App.Support.
Position
Below the diagonal: App.Console.Commands uses a module listed above it, which is the healthy direction.
App.Console.Commands uses App.Supply, so a change to App.Supply can break App.Console.Commands, while a change to App.Console.Commands can't break App.Supply.
Position
Below the diagonal: App.Console.Commands uses a module listed above it, which is the healthy direction.
26 pairs of types, where a type in App.Http.Controllers.Api.Admin uses a type in App.Http.Controllers. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
App.Http.Controllers.Api.Admin uses App.Http.Controllers, so a change to App.Http.Controllers can break App.Http.Controllers.Api.Admin, while a change to App.Http.Controllers.Api.Admin can't break App.Http.Controllers.
Position
Below the diagonal: App.Http.Controllers.Api.Admin uses a module listed above it, which is the healthy direction.
App.Http.Controllers.Api.Admin uses App.Models, so a change to App.Models can break App.Http.Controllers.Api.Admin, while a change to App.Http.Controllers.Api.Admin can't break App.Models.
Position
Below the diagonal: App.Http.Controllers.Api.Admin uses a module listed above it, which is the healthy direction.
App.Http.Controllers.Api.Admin uses App.Support, so a change to App.Support can break App.Http.Controllers.Api.Admin, while a change to App.Http.Controllers.Api.Admin can't break App.Support.
Position
Below the diagonal: App.Http.Controllers.Api.Admin uses a module listed above it, which is the healthy direction.
App.Http.Controllers.Api.Admin uses App.Supply, so a change to App.Supply can break App.Http.Controllers.Api.Admin, while a change to App.Http.Controllers.Api.Admin can't break App.Supply.
Position
Below the diagonal: App.Http.Controllers.Api.Admin uses a module listed above it, which is the healthy direction.
App.Http.Controllers.Api.Supply uses App.Http.Controllers, so a change to App.Http.Controllers can break App.Http.Controllers.Api.Supply, while a change to App.Http.Controllers.Api.Supply can't break App.Http.Controllers.
Position
Below the diagonal: App.Http.Controllers.Api.Supply uses a module listed above it, which is the healthy direction.
App.Http.Controllers.Api.Supply uses App.Models, so a change to App.Models can break App.Http.Controllers.Api.Supply, while a change to App.Http.Controllers.Api.Supply can't break App.Models.
Position
Below the diagonal: App.Http.Controllers.Api.Supply uses a module listed above it, which is the healthy direction.
App.Http.Controllers.Api.Supply uses App.Supply, so a change to App.Supply can break App.Http.Controllers.Api.Supply, while a change to App.Http.Controllers.Api.Supply can't break App.Supply.
Position
Below the diagonal: App.Http.Controllers.Api.Supply uses a module listed above it, which is the healthy direction.
App.Http.Middleware uses App.Supply, so a change to App.Supply can break App.Http.Middleware, while a change to App.Http.Middleware can't break App.Supply.
Position
Below the diagonal: App.Http.Middleware uses a module listed above it, which is the healthy direction.
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
67
High / Critical
A05:2025 — Injection
4
High / Critical
A02:2025 — Security Misconfiguration
2
Medium
A01:2025 — Broken Access Control
1
Medium
Roadmap
Top priorities: Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href; Add a CI workflow that builds and runs the test suite on every push/PR. The repository declares its tests as `cd storefront && pnpm test` (`storefront/package.json`): run that; Run what this repository's stack ships: phpstan or psalm — 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.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
Add a CI workflow that builds and runs the test suite on every push/PR. The repository declares its tests as `cd storefront && pnpm test` (`storefront/package.json`): run that.
Run what this repository's stack ships: phpstan or psalm — 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.
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.
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 — 151
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 — 398
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 — 117
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 18
Something this survey could not settle
from the outside, and which could be critical or serious. Either a control was required and no
positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves
nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean
result. These are excluded from the score rather than awarded a pass, so the number on the cover neither
rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each
one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 69 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
Every figure here is one of two kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10.
What we checked — 69 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, 655 of 666 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.
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: this repository's production source spans .ts, .php, and our analyzer cannot run the .php test suite(s) — so no coverage was collected for the repository as a whole. The JavaScript/TypeScript half did build and run, and its own line coverage came back at 100.0% — but that is a figure for one half of the product, and we do not publish a partial one as if it were complete. This is OUR limitation, not a defect in the repo — coverage is excluded from the score rather than counted as a near-zero.
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 12 test(s) behind this row are the ones the code-model census could read, and this repository also carries at least 1 test source file(s) (.mjs) that it cannot: it reads the test types the .php frontend declared, so a suite in any other language 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 SCORED: this repository's production source includes .php, and the built-in reliability runner cannot re-run the .php test suite(s) — so reliability was not measured for the repository as a whole. The JavaScript/TypeScript (node:test via `pnpm install --frozen-lockfile --ignore-scripts` in storefront/ (1 tests)): measured (0 flaky) suite(s) did re-run, and came back with 0 flaky across 1 measured tier(s) — but that is a figure for one half of the product, and we do not publish a partial one as if it were complete. This is OUR limitation, not a defect in the repo — test reliability is excluded from the score rather than counted.
D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares package.json, but the licence verdict published here was taken over its Composer package dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (2 contributor(s) across 483 commit(s) sampled, automation and bot accounts excluded). One of them holds 100% of the history; the other 1 hold 0% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. D21's naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is a COLLECTOR gap, not an environment fault: no published-package marker D22 reads admitted any project here, so this ecosystem's public API has no collector, and the remedy is to write one — no change to the scan image can close it.
D24 Comment Value — 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. 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 — 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. 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.
D28 Secrets (history) — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. No commit of the history (483 commits) was scanned. `gitleaks` TIMED OUT after 180s against a 180s budget, so we killed its process tree. The budget is ours; the work may simply be larger than it allows. The working tree WAS scanned in full, and every row of the scanned ranges is reported. Nothing about the unscanned commits is asserted by the absence of a result; the budget is ours to raise.
D32 Data Compliance (PII/GDPR) — 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. `app/Http/Controllers/Api/Admin/MediaCategoryController.php`, `app/Http/Controllers/Api/Admin/MediaController.php`, `app/Http/Middleware/SupplyAuth.php`, `app/Jobs/FetchFromUpstream.php`, `app/Jobs/SyncSupplySourceProducts.php`, … (+35 more) 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.
AC2 Forms & labels — 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. 47 further occurrence(s) are not listed individually; the score already reflects all 87.
AC4 Keyboard semantics — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 39 further occurrence(s) are not listed individually; the score already reflects all 79.
AC6 Visual & motion safety — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Visual & motion safety could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository. Engine failure: ArgumentOutOfRangeException: startIndex cannot be larger than length of string. (Parameter 'startIndex').
AX1 Captive dependencies — 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 Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository's container is Laravel's service container, whose lifetimes are not modelled 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.
AXB2 Runtime readiness — 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. The image build failed, and its output does not match a cause we recognise. (rule: unrecognised-build-failure). The renderer reported: compose up failed (exit 17 — an image could not be built) — time="2026-11-17T18:42:54Z" level=warning msg="The \"DB_PASSWORD\" variable is not set. Defaulting to a blank string." laravel.test Pulling laravel.test Warning Get "https://sail-8.5/v2/": Forbidden unable to prepare context: path "vendor/laravel/sail/runtimes/8.5" not found; likely cause (not identified): the image build failed, and its output does not match a cause we recognise; runtime evidence skipped.
AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DockerCompose (REDACTED). compose up failed (exit 17 — an image could not be built) — time="2026-11-17T18:42:54Z" level=warning msg="The \"DB_PASSWORD\" variable is not set. Defaulting to a blank string." laravel.test Pulling laravel.test Warning Get "https://sail-8.5/v2/": Forbidden unable to prepare context: path "vendor/laravel/sail/runtimes/8.5" not found; likely cause (not identified): the image build failed, and its output does not match a cause we recognise; runtime evidence skipped.
C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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.
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. 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.
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. 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.
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. 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.
GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java source only, and this repository's PHP, Vue components is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby, Scala and Rust source only, and this repository's PHP, Vue components is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
P2 Observability — 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. 23 further occurrence(s) are not listed individually; the score already reflects all 63.
R10 Code Duplication — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 40 further occurrence(s) are not listed individually; the score already reflects all 80.
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. 134 further occurrence(s) are not listed individually; the score already reflects all 174.
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. 36 further occurrence(s) are not listed individually; the score already reflects all 76.
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 — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
X12 Unreachable branch — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
X24 Document value interpolated into markup unescaped — 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.
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. 110 further occurrence(s) are not listed individually; the score already reflects all 150.
Repo exclusion declarations: 6 pattern(s) declared (.gitattributes linguist-generated/vendored, .editorconfig generated_code) excluded 0 source file(s) from code-quality scoring. Declarations are the repo's own visible statement that a tree is machine-written or vendored — auditable in any diff, honored by GitHub the same way.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 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.
D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
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.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
D32 Data Compliance (PII/GDPR): PII/GDPR signals are heuristic pattern matches in code — they flag likely handling concerns, not legal compliance, and cannot trace where data actually flows at runtime.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
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.
+ 19 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 1 body over 30 down to 30 or less in Cyclomatic Complexity — start with OrderService.createOrder (cyclomatic 54). — Refactoring it lifts Cyclomatic Complexity from 6.7 to about 7.4/10.
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.
+ 35 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 1 body over 60 down to 60 or less in Cognitive Complexity — start with OrderService.createOrder (cognitive 75). — Refactoring it lifts Cognitive Complexity from 6.3 to about 6.5/10.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes9.2 / 10Stronggated by 17 serious findings✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 6 MethodTooLong finding(s) in God Classes — start with OrderService.php, StorefrontConfig.php, SupplyOrderService.php. — One of this dimension's main actionable groups (6 warning-level).
Resolve the 4 FunctionTooLong finding(s) in God Classes — start with useChart.ts, useTable.ts, useSettingsConfig.ts. — One of this dimension's main actionable groups (4 warning-level).
Resolve the 3 ClassTooLong finding(s) in God Classes — start with AcgFakaDriver.php, UpdateController.php, OrderService.php. — One of this dimension's main actionable groups (3 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.
28 duplicated block group(s) detected. 1.2 % of the production lines (975 of 84,407) are in a reported copy. A further 18 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. Measured on part of this repository only: .ts (37% of production source) was not exposed to THIS dimension's token comparison and is not in this count; duplication there is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream.
Edited copy of a member (4 corresponding lines) · ×2app/Supply/Drivers/DujiaoNextDriver.php:78
Edited copy of a member (8 corresponding lines) · ×2app/Support/SubsiteWithdrawalService.php:69
+ 28 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 4 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with SubsiteConsoleController.php, OkPayDriver.php, AcgFakaDriver.php. — One of this dimension's main actionable groups (4 warning-level).
Resolve the 3 Edited copy of a member (12 corresponding lines) finding(s) in Code Duplication — start with ZCardDriver.php, WithdrawalController.php, OkPayDriver.php. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 3 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with UpdateController.php, DujiaoNextDriver.php, CouponController.php. — One of this dimension's main actionable groups (3 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.
4 production modules (npm+Composer), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 0 module(s) off the main sequence, with abstractness counted on 3 of the 4 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
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.
D10 · Test Quality10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the tests truly assert behaviour rather than just running the code.
Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.
0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 12 tests. Measured on the .php suite only — at least 1 test source file(s) (.mjs) went unread, so its test quality is unmeasured and is not in these counts.
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.
6 outdated, 0 abandoned direct Composer dependencies. PLATFORM requirements (php, ext-*, lib-*) are deliberately not graded here: they name the runtime rather than a Packagist package, so there is no release for them to be behind — whether that runtime is still supported is a separate question with a separate remedy. Development requirements are excluded, because a consumer never installs them. A newer release is reported only where this repository's OWN constraint already admits it, so the remedy is `composer update` and never a manifest edit. Known CVEs in this dependency graph are D30's question.
Outdated: filament/filament · ×6
✓ On the Gold path — maintain.
Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
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 123 locked Composer package(s) use a banned license. Licences were read from this repository's REDACTED, which records the `license` each package declares, over every package in its production `packages` list, direct and transitive, at the locked version; the 48 package(s) under `packages-dev` are not installed for a consumer and are excluded. ★ COVERAGE OF THIS VERDICT: it grades this repository's Composer package dependencies and nothing else. The repository also declares package.json, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
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.
Top hotspots: sysadmin/src/views/product/list/index.vue (27×40=1080); app/Support/OrderService.php (19×54=1026); app/Supply/SupplySyncService.php (25×22=550) Repeated repair below the complexity floor: storefront/src/views/PayResult.vue (9 of 13 changes were fixes); app/Supply/Drivers/ZCardDriver.php (7 of 11 changes were fixes); app/Supply/Drivers/DujiaoNextDriver.php (6 of 10 changes were fixes)
Resolve the 23 Repeated repair finding(s) in Churn × Complexity Hotspots — start with REDACTED (3), PayResult.vue, ZCardDriver.php. — One of this dimension's main actionable groups (23 warning-level).
Resolve the 21 Hotspot finding(s) in Churn × Complexity Hotspots — start with REDACTED (2), OrderService.php, SupplySyncService.php. — One of this dimension's main actionable groups (21 warning-level).
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
0 deducted task-comment markers across 48343 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.
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.
1 of 1 documentation facets pass in full. 24 document(s) read across 3 unit(s).
✓ On the Gold path — maintain.
Detailed fixes: d19_recommendation.md.
Do you agree with this assessment?
D20 · ADR Quality0.0 / 10Critical✓ Tool-verified
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.
What it measures: Whether names — types, methods, variables — are clear and consistent.
Method: Seven vocabulary-free rules (N1-N7) mine each naming convention from the repository and flag a name that breaks a convention its structural peers in the same unit follow; production C# and TypeScript, each its own population. Deterministic, no model, no sample. Advisory.
1 naming inconsistencies among 20 declarations measured against a convention their peers follow.
`validateChineseIDCard` spells `ID` where 19 names in the project spell it `Id`sysadmin/src/utils/form/validator.ts:252
What to do
Resolve the 1 `validateChineseIDCard` spells `ID` where 19 names in the project spell… finding(s) in Naming Consistency — start with validator.ts. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d21_recommendation.md · top locations in Appendix A, every location in findings.md.
2 of 3 build units (npm) flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesion · ×2package.json:1
What to do
Resolve the 2 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with package.json (2). — One of this dimension's main actionable groups (2 recommendation-level).
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
gitleaks scanned the current working tree and the part of the history named below, and found no secrets. History coverage: No commit of the history (483 commits) was scanned. `gitleaks` TIMED OUT after 180s against a 180s budget, so we killed its process tree. The budget is ours; the work may simply be larger than it allows.
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).
4 finding(s): 0 critical, 1 high, 3 medium, 0 low. semgrep hit a parse error in 65 file(s) — `app/Http/Controllers/Api/Admin/MediaCategoryController.php` (line 13), `app/Http/Controllers/Api/Admin/MediaController.php` (line 12), `app/Http/Middleware/SupplyAuth.php` (line 21), `app/Jobs/FetchFromUpstream.php` (line 29), `app/Jobs/SyncSupplySourceProducts.php` (line 49, line 50, line 51, …), … (+60 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
REDACTED
REDACTED
REDACTED
What to do
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 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.
Resolve the 48 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (45), REDACTED (3). — One of this dimension's main actionable groups (48 issue-level).
Resolve the 5 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (4), REDACTED. — One of this dimension's main actionable groups (5 issue-level).
Resolve the 11 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (9), REDACTED (2). — One of this dimension's main actionable groups (11 warning-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
Resolve the 2 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d31_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D32 · Data Compliance (PII/GDPR)9.0 / 10Stronggated by 1 serious finding✓ Tool-verified
What it measures: Likely personal-data (PII / GDPR) handling concerns — logging or storing data without safeguards.
Method: Heuristic PII/GDPR LEAK scan via semgrep across the repo, using our own ruleset: personal data crossing a boundary it should not — reaching a log/console sink, a URL or query string, or unprotected browser storage. Matches map to severity and a 0-10 wide normalizer. A clean sweep is unscored rather than an unearned 10, and is a statement about the leak paths checked only — this dimension does not inventory the personal data a repository holds (the personal-data map and the C1-C5 compliance cards do that), so it never reports that a repository has no personal-data surface. Reported LOUDLY as a measurement gap if the ruleset is missing from the analyzer image. Exhaustive over the leak paths, advisory-leaning; degrades on parse failure.
1 finding(s): 0 critical, 0 high, 1 medium, 0 low. semgrep could not parse 40 file(s) — `app/Http/Controllers/Api/Admin/MediaCategoryController.php`, `app/Http/Controllers/Api/Admin/MediaController.php`, `app/Http/Middleware/SupplyAuth.php`, `app/Jobs/FetchFromUpstream.php`, `app/Jobs/SyncSupplySourceProducts.php`, … (+35 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
REDACTED
What to do
Resolve the 1 REDACTED finding(s) in Data Compliance (PII/GDPR) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d32_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 276 of the 699 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
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.
Resolve the 1 Boundary-crossing change coupling finding(s) in Change Coupling — start with UpdateController.php. — One of this dimension's main actionable groups (1 issue-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.
Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 0 platform declaration(s) and 27 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
✓ On the Gold path — maintain.
Detailed fixes: d44_recommendation.md.
Do you agree with this assessment?
Frontend & cross-cutting dimensions
R = React/JS · M = Maturity · P = Readiness.
AC1 · Text alternatives4.2 / 10Weak✓ Tool-verified
Other · Accessibility — Whether non-text content carries a text alternative — img/area/input[type=image] have alt, a meaningful svg has a title or aria-label, video has a captions track, and object/embed/canvas have a name or fallback content. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: every img/area/input[type=image] checked for alt, svg[role=img] for a title/aria-label, video for a captions <track>. Components skipped, spreads suppressed. Deterministic, hard fact per element.
Coverage: Population: image/media elements — img, area, input[type=image], svg, video, object, embed, canvas — across the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and dynamic-attribute elements are skipped. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is NOT read by any producer, so it contributes no element to this population; where such a frontend is present the card discloses it as an analyzer gap rather than scoring around it.
An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative. (×12) — storefront/src/components/ProductCard.vue:35, storefront/src/components/ProductCard.vue:56, storefront/src/views/Checkout.vue:522, …
A <canvas> with no aria-label/title and no inner fallback content can't be described by assistive tech. Add a name or fallback content. — sysadmin/src/components/core/layouts/art-fireworks-effect/index.vue:3
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 & labels4.3 / 10Weak✓ Tool-verified
Other · Accessibility — Whether form controls have a programmatic label (an associated label, aria-label or aria-labelledby), buttons have text, links have an accessible name, a click handler on a plain element names the control it declares, fieldsets have a non-empty legend, known UI-library field components carry a label prop, and a placeholder isn't used as the only label. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: inputs/selects/textareas checked for an associated label[for]/wrapping label/aria-label/aria-labelledby (per document), buttons for accessible text, fieldsets for a legend; placeholder-only labelling flagged. Deterministic, hard fact per control.
Coverage: Population: form controls, buttons, links, fieldsets and known UI-library field components in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and spread/dynamic-attribute elements are skipped, so a control whose label arrives through a spread or a runtime expression is deliberately not judged. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id. (×16) — resources/views/filament/pages/payment-channels.blade.php:71, storefront/src/views/Checkout.vue:560, storefront/src/views/ForgetPassword.vue:112, …
A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one). — storefront/src/components/AppHeader.vue:149
This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×10) — storefront/src/components/AppHeader.vue:179, storefront/src/components/AppHeader.vue:182, storefront/src/views/Checkout.vue:561, …
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. (×13) — storefront/src/views/Checkout.vue:572, storefront/src/views/Checkout.vue:575, storefront/src/views/Checkout.vue:587, …
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.
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"). (×2) — public/admin/index.html:2, sysadmin/index.html:2
Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one. (×2) — storefront/src/views/Checkout.vue:586, storefront/src/views/Product.vue:495
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. — sysadmin/src/views/outside/Iframe.vue:3
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. (×37) — storefront/src/components/HotTags.vue:25, storefront/src/components/ProductCard.vue:32, storefront/src/views/Checkout.vue:599, …
The repo's own CSS styles .preview-thumb with `cursor: pointer`, so this <div> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler. — sysadmin/src/components/business/image-picker/index.vue:56
The repo's own CSS styles .box with `cursor: pointer`, so this <div> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler. — sysadmin/src/components/core/layouts/art-global-search/index.vue:31
The repo's own CSS styles .c-p with `cursor: pointer`, so this <div> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler. — sysadmin/src/components/core/layouts/art-global-search/index.vue:64
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 · 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.
Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').
Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.
Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
What to do
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.
sysadmin/README.md links to `./CHANGELOG.en.md`, but `sysadmin/CHANGELOG.en.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — sysadmin/README.md:48
What to do
Reconcile the README with reality: sysadmin/README.md links to `./CHANGELOG.en.md`, but `sysadmin/CHANGELOG.en.md` does not exist.
Do you agree with this assessment?
P1 · CI/CD gates0.0 / 10Critical✓ Tool-verified
Readiness · Readiness — Whether an automated pipeline builds and tests every change.
Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.
No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.
What to do
Add a CI workflow that builds and runs the test suite on every push/PR. The repository declares its tests as `cd storefront && pnpm test` (`storefront/package.json`): run that.
Do you agree with this assessment?
P2 · Observability8.0 / 10Strong✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
`sysadmin/src/utils/table/tableCache.ts` reports through `console.*` at line 90 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — sysadmin/src/utils/table/tableCache.ts:90
`sysadmin/src/utils/table/tableUtils.ts` reports through `console.*` at line 127 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — sysadmin/src/utils/table/tableUtils.ts:127
`sysadmin/src/utils/table/tableUtils.ts` reports through `console.*` at line 160 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — sysadmin/src/utils/table/tableUtils.ts:160
`sysadmin/src/utils/table/tableUtils.ts` reports through `console.*` at line 161 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — sysadmin/src/utils/table/tableUtils.ts:161
`sysadmin/src/utils/table/tableUtils.ts` reports through `console.*` at line 162 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — sysadmin/src/utils/table/tableUtils.ts:162
`sysadmin/src/utils/table/tableUtils.ts` reports through `console.*` at line 275 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — sysadmin/src/utils/table/tableUtils.ts:275
`sysadmin/src/utils/sys/console.ts` reports through `console.*` at line 13 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — sysadmin/src/utils/sys/console.ts:13
`sysadmin/src/utils/sys/upgrade.ts` reports through `console.*` at line 171 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — sysadmin/src/utils/sys/upgrade.ts:171
`sysadmin/src/utils/sys/upgrade.ts` reports through `console.*` at line 177 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — sysadmin/src/utils/sys/upgrade.ts:177
`sysadmin/src/utils/sys/upgrade.ts` reports through `console.*` at line 187 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — sysadmin/src/utils/sys/upgrade.ts:187
`sysadmin/src/utils/sys/upgrade.ts` reports through `console.*` at line 189 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — sysadmin/src/utils/sys/upgrade.ts:189
`sysadmin/src/utils/sys/upgrade.ts` reports through `console.*` at line 202 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — sysadmin/src/utils/sys/upgrade.ts:202
`sysadmin/src/utils/sys/upgrade.ts` reports through `console.*` at line 223 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — sysadmin/src/utils/sys/upgrade.ts:223
`sysadmin/src/utils/sys/upgrade.ts` reports through `console.*` at line 225 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — sysadmin/src/utils/sys/upgrade.ts:225
`sysadmin/src/utils/sys/upgrade.ts` reports through `console.*` at line 235 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — sysadmin/src/utils/sys/upgrade.ts:235
`sysadmin/src/utils/sys/upgrade.ts` reports through `console.*` at line 244 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — sysadmin/src/utils/sys/upgrade.ts:244
`sysadmin/src/utils/sys/upgrade.ts` reports through `console.*` at line 250 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — sysadmin/src/utils/sys/upgrade.ts:250
`sysadmin/src/utils/sys/upgrade.ts` reports through `console.*` at line 258 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — sysadmin/src/utils/sys/upgrade.ts:258
`sysadmin/src/utils/storage/storage-key-manager.ts` reports through `console.*` at line 71 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — sysadmin/src/utils/storage/storage-key-manager.ts:71
`sysadmin/src/utils/storage/storage-key-manager.ts` reports through `console.*` at line 74 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — sysadmin/src/utils/storage/storage-key-manager.ts:74
`sysadmin/src/utils/storage/storage.ts` reports through `console.*` at line 91 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — sysadmin/src/utils/storage/storage.ts:91
`sysadmin/src/utils/storage/storage.ts` reports through `console.*` at line 117 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — sysadmin/src/utils/storage/storage.ts:117
`sysadmin/src/utils/storage/storage.ts` reports through `console.*` at line 119 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — sysadmin/src/utils/storage/storage.ts:119
`sysadmin/src/utils/storage/storage.ts` reports through `console.*` at line 140 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — sysadmin/src/utils/storage/storage.ts:140
`sysadmin/src/utils/storage/storage.ts` reports through `console.*` at line 146 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — sysadmin/src/utils/storage/storage.ts:146
`sysadmin/src/utils/storage/storage.ts` reports through `console.*` at line 155 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — sysadmin/src/utils/storage/storage.ts:155
`sysadmin/src/utils/storage/storage.ts` reports through `console.*` at line 160 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — sysadmin/src/utils/storage/storage.ts:160
`sysadmin/src/utils/storage/storage.ts` reports through `console.*` at line 164 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — sysadmin/src/utils/storage/storage.ts:164
`sysadmin/src/utils/storage/storage.ts` reports through `console.*` at line 167 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — sysadmin/src/utils/storage/storage.ts:167
`sysadmin/src/utils/storage/storage.ts` reports through `console.*` at line 206 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — sysadmin/src/utils/storage/storage.ts:206
`sysadmin/src/utils/storage/storage.ts` reports through `console.*` at line 210 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — sysadmin/src/utils/storage/storage.ts:210
`sysadmin/src/utils/storage/storage.ts` reports through `console.*` at line 213 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — sysadmin/src/utils/storage/storage.ts:213
`sysadmin/src/utils/http/error.ts` reports through `console.*` at line 154 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — sysadmin/src/utils/http/error.ts:154
`sysadmin/src/utils/http/error.ts` reports through `console.*` at line 193 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — sysadmin/src/utils/http/error.ts:193
`sysadmin/src/store/modules/user.ts` reports through `console.*` at line 190 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — sysadmin/src/store/modules/user.ts:190
`sysadmin/src/store/modules/worktab.ts` reports through `console.*` at line 97 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — sysadmin/src/store/modules/worktab.ts:97
`sysadmin/src/store/modules/worktab.ts` reports through `console.*` at line 107 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — sysadmin/src/store/modules/worktab.ts:107
`sysadmin/src/store/modules/worktab.ts` reports through `console.*` at line 116 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — sysadmin/src/store/modules/worktab.ts:116
`sysadmin/src/store/modules/worktab.ts` reports through `console.*` at line 189 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — sysadmin/src/store/modules/worktab.ts:189
`sysadmin/src/store/modules/worktab.ts` reports through `console.*` at line 194 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — sysadmin/src/store/modules/worktab.ts:194
What to do
Route service-code `console.*` output through the module's structured logger (with named fields), so delivery outcomes and failures reach the log pipeline with a level.
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 phpstan or psalm (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.
`package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — package.json:18
What to do
Run what this repository's stack ships: phpstan or psalm — 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 · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
What to do
Add an approval/environment gate (required reviewers / protection rules) before production promotion.
Readiness · Readiness — Whether outbound HTTP calls are wrapped in resilience (retry/timeout/circuit-breaker) so a failing dependency doesn't cascade.
Method: Source scan: outbound HTTP clients and what bounds them — resilience handlers (Polly, AddStandardResilienceHandler) on .NET; on Go, the JVM, Python, JavaScript/TypeScript, Ruby, PHP, Rust, Elixir, Swift, Dart and Erlang, a timeout, deadline, retry or breaker beside each call, or a process-wide client default (a framework-wide deadline such as Drupal core's, Laravel's or actix's awc counts). Exhaustive, deterministic.
Readiness · Readiness — Whether database schema changes go through versioned migrations rather than being auto-created from the model at startup.
Method: Roslyn scan: EF Core DbContext for a versioned migrations directory versus bare EnsureCreated usage; off .NET, a file scan of dependency manifests, migration histories (Flyway, Liquibase, Alembic, Django, Rails, Prisma, TypeORM, Knex/Sequelize, golang-migrate, goose, Laravel, Doctrine, Diesel/sqlx) and schema auto-create in production source or config. Exhaustive, deterministic.
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.
Do you agree with this assessment?
R1 · Type Safety9.6 / 10Exemplary✓ 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.
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.
32 duplicated blocks under sysadmin/src/views/ have copies in at least two of the sibling directories bill, card, category, commission, coupon, currency (+12 more sibling(s) not listed) — 23 of them are reported below, and 9 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 32 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 32 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 32 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — sysadmin/src/views/category/list/index.vue:89
10 duplicated blocks under sysadmin/src/components/core/charts/ have copies in at least two of the sibling directories art-bar-chart, art-dual-bar-compare-chart, art-h-bar-chart, art-k-line-chart, art-line-chart, art-radar-chart (+2 more sibling(s) not listed) — 7 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 10 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 10 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 10 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — sysadmin/src/components/core/charts/art-bar-chart/index.vue:7
6 duplicated blocks under the repository root have copies in at least two of the sibling directories storefront, sysadmin — 2 of them are reported below, and 4 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 6 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 6 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 6 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — storefront/src/api/distribution.ts:10
sysadmin/src/components/core/forms/art-form/index.vue:123 · sysadmin/src/components/core/forms/art-search-bar/index.vue:130 — the two spans are one implementation copied and then locally edited — 1039 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. — sysadmin/src/components/core/forms/art-form/index.vue:123
sysadmin/src/components/core/charts/art-bar-chart/index.vue:7 · sysadmin/src/components/core/charts/art-h-bar-chart/index.vue:12 — these 2 files are line-for-line copies of one another — 94 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — sysadmin/src/components/core/charts/art-bar-chart/index.vue:7
sysadmin/src/views/category/list/index.vue:89 · sysadmin/src/views/currency/list/index.vue:70 — the two spans are one implementation copied and then locally edited — 406 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. — sysadmin/src/views/category/list/index.vue:89
storefront/src/views/MySubsite.vue:52 · storefront/src/views/Withdraw.vue:29 — the two spans are one implementation copied and then locally edited — 389 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. — storefront/src/views/MySubsite.vue:52
storefront/src/views/Login.vue:11 · storefront/src/views/Register.vue:10 — the two spans are one implementation copied and then locally edited — 398 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. — storefront/src/views/Login.vue:11
sysadmin/src/views/commission/list/index.vue:18 · sysadmin/src/views/review/list/index.vue:18 — the two spans are one implementation copied and then locally edited — 389 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. — sysadmin/src/views/commission/list/index.vue:18
sysadmin/src/views/coupon/list/index.vue:8 · sysadmin/src/views/withdrawal/list/index.vue:11 — the two spans are one implementation copied and then locally edited — 556 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. — sysadmin/src/views/coupon/list/index.vue:8
sysadmin/src/views/card/list/index.vue:713 · sysadmin/src/views/card/list/index.vue:821 — 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. — sysadmin/src/views/card/list/index.vue:713
sysadmin/src/views/product/list/index.vue:1920 · sysadmin/src/views/user/list/index.vue:500 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — sysadmin/src/views/product/list/index.vue:1920
storefront/src/views/Checkout.vue:453 · storefront/src/views/Pay.vue:50 — 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. — storefront/src/views/Checkout.vue:453
storefront/src/views/Pay.vue:52 · storefront/src/views/RechargePay.vue:59 — 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. — storefront/src/views/Pay.vue:52
storefront/src/views/Pay.vue:115 · storefront/src/views/RechargePay.vue:126 — 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. — storefront/src/views/Pay.vue:115
sysadmin/src/views/currency/list/index.vue:13 · sysadmin/src/views/subsite/list/index.vue:14 — the two spans are one implementation copied and then locally edited — 163 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. — sysadmin/src/views/currency/list/index.vue:13
sysadmin/src/components/core/layouts/art-global-search/index.vue:236 · sysadmin/src/components/core/layouts/art-global-search/index.vue:261 — 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. — sysadmin/src/components/core/layouts/art-global-search/index.vue:236
sysadmin/scripts/clean-dev.ts:87 · sysadmin/scripts/clean-dev.ts:735 — 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. — sysadmin/scripts/clean-dev.ts:87
sysadmin/src/components/core/charts/art-dual-bar-compare-chart/index.vue:79 · sysadmin/src/components/core/charts/art-k-line-chart/index.vue:40 — the two spans are one implementation copied and then locally edited — 55 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. — sysadmin/src/components/core/charts/art-dual-bar-compare-chart/index.vue:79
sysadmin/src/hooks/core/useLayoutHeight.ts:34 · sysadmin/src/hooks/core/useLayoutHeight.ts:88 — 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. — sysadmin/src/hooks/core/useLayoutHeight.ts:34
sysadmin/src/components/core/cards/art-bar-chart-card/index.vue:59 · sysadmin/src/components/core/cards/art-line-chart-card/index.vue:62 — 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. — sysadmin/src/components/core/cards/art-bar-chart-card/index.vue:59
sysadmin/src/views/order/list/index.vue:425 · sysadmin/src/views/supply/list/index.vue:988 — the two spans are one implementation copied and then locally edited — 69 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. — sysadmin/src/views/order/list/index.vue:425
sysadmin/src/views/card/list/index.vue:860 · sysadmin/src/views/coupon/list/index.vue:66 — 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. — sysadmin/src/views/card/list/index.vue:860
sysadmin/src/views/bill/list/index.vue:37 · sysadmin/src/views/withdrawal/list/index.vue:46 — 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. — sysadmin/src/views/bill/list/index.vue:37
sysadmin/src/views/order/list/index.vue:429 · sysadmin/src/views/user/list/index.vue:333 — the two spans are one implementation copied and then locally edited — 62 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. — sysadmin/src/views/order/list/index.vue:429
sysadmin/src/views/subsite/list/index.vue:120 · sysadmin/src/views/subsite/list/index.vue: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. — sysadmin/src/views/subsite/list/index.vue:120
sysadmin/src/utils/form/validator.ts:51 · sysadmin/src/utils/form/validator.ts:81 — 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. — sysadmin/src/utils/form/validator.ts:51
sysadmin/src/views/card/list/index.vue:1069 · sysadmin/src/views/card/list/index.vue:1085 — 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. — sysadmin/src/views/card/list/index.vue:1069
sysadmin/src/views/card/list/index.vue:655 · sysadmin/src/views/supply/list/index.vue:986 — the two spans are one implementation copied and then locally edited — 60 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. — sysadmin/src/views/card/list/index.vue:655
sysadmin/src/views/product/list/index.vue:1237 · sysadmin/src/views/product/list/index.vue:1257 — 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. — sysadmin/src/views/product/list/index.vue:1237
sysadmin/src/components/core/charts/art-bar-chart/index.vue:128 · sysadmin/src/components/core/charts/art-h-bar-chart/index.vue:132 · sysadmin/src/components/core/charts/art-line-chart/index.vue:311 — the 3 copies are spread across 3 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — sysadmin/src/components/core/charts/art-bar-chart/index.vue:128
sysadmin/src/views/subsite/list/index.vue:173 · sysadmin/src/views/subsite/list/index.vue:196 — 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. — sysadmin/src/views/subsite/list/index.vue:173
storefront/src/components/ServiceWidget.vue:36 · storefront/src/components/SiteAnalytics.vue:29 — the two spans are one implementation copied and then locally edited — 54 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. — storefront/src/components/ServiceWidget.vue:36
storefront/src/views/Pay.vue:96 · storefront/src/views/RechargePay.vue:113 — 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. — storefront/src/views/Pay.vue:96
sysadmin/src/api/cards.ts:188 · sysadmin/src/api/coupons.ts:79 — 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. — sysadmin/src/api/cards.ts:188
sysadmin/src/utils/form/validator.ts:182 · sysadmin/src/utils/form/validator.ts:244 — 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. — sysadmin/src/utils/form/validator.ts:182
sysadmin/src/views/supplierAccount/list/index.vue:459 · sysadmin/src/views/supply/list/index.vue:1911 — 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. — sysadmin/src/views/supplierAccount/list/index.vue:459
storefront/src/views/ForgetPassword.vue:10 · storefront/src/views/Register.vue:12 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of MODULE-LEVEL DECLARATIONS — bindings the module declares and exports — rather than statements with a call site. Do not read this as an extract-a-helper row: a call expression cannot stand where a declaration was, and putting one there would delete the names themselves, which are what the rest of the codebase imports. What actually repeats here is the INITIALISER — the same expression shape written once per binding. So give that expression one name (a small helper the initialisers call, or a shared base value they are each derived from) and keep every binding under the name it already has. Where the run is an enumeration — one binding per distinct thing, differing precisely in the thing each one names — the repetition IS the enumeration and collapsing it would delete entries; consider instead whether the set belongs in one exported table the individual names are read out of. Reported because the copies drift apart the first time only one of them is edited. — storefront/src/views/ForgetPassword.vue:10
storefront/src/views/ForgetPassword.vue:30 · storefront/src/views/Login.vue:27 · storefront/src/views/Register.vue:32 — the 3 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — storefront/src/views/ForgetPassword.vue:30
storefront/src/views/Pay.vue:28 · storefront/src/views/RechargePay.vue:37 — 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. — storefront/src/views/Pay.vue:28
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.
openEdit has cyclomatic complexity 40 and cognitive complexity 38; 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. — sysadmin/src/views/product/list/index.vue:1756
doSubmit has cyclomatic complexity 22 and cognitive complexity 29; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — storefront/src/views/Checkout.vue:352
loadSingle has cyclomatic complexity 22 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 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. — storefront/src/views/Checkout.vue:151
(anonymous) has cyclomatic complexity 21 and cognitive complexity 28; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — sysadmin/src/hooks/core/useTable.ts:282
token has cyclomatic complexity 21 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. — public/admin/assets/forth-POgR1ypr.js:1
(anonymous) has cyclomatic complexity 18 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. (×2) — sysadmin/src/components/core/forms/art-form/index.vue:364, sysadmin/src/components/core/forms/art-search-bar/index.vue:360
handleSubmit has cyclomatic complexity 18 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — sysadmin/src/views/product/list/index.vue:1861
loadSettings has cyclomatic complexity 18 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — sysadmin/src/views/setting/index.vue:887
loadAll has cyclomatic complexity 16 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. — storefront/src/views/MySubsite.vue:97
submit has cyclomatic complexity 16 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — storefront/src/views/Checkout.vue:317
submit has cyclomatic complexity 16 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. — storefront/src/views/Register.vue:47
extractPagination has cyclomatic complexity 14 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — sysadmin/src/utils/table/tableUtils.ts:78
loadAll has cyclomatic complexity 14 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — sysadmin/src/views/dashboard/console/index.vue:612
handleSubmit has cyclomatic complexity 14 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — sysadmin/src/views/user/list/index.vue:475
(anonymous) has cyclomatic complexity 14 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. — sysadmin/src/router/core/RouteValidator.ts:105
(anonymous) has cyclomatic complexity 13 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. — sysadmin/src/store/modules/worktab.ts:114
submit has cyclomatic complexity 13 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. — storefront/src/views/Login.vue:43
openEdit 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. — sysadmin/src/views/supply/list/index.vue:1105
handleImport has cyclomatic complexity 13 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — sysadmin/src/views/card/list/index.vue:944
load 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. — storefront/src/stores/preferences.ts:36
handleSendCode 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. — storefront/src/views/ForgetPassword.vue:51
(anonymous) has cyclomatic complexity 12 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — sysadmin/src/api/supply.ts:282
addToCart has cyclomatic complexity 12 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — storefront/src/views/Product.vue:274
useTableImpl has cyclomatic complexity 12 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — sysadmin/src/hooks/core/useTable.ts:132
matchRoute has cyclomatic complexity 11 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. — sysadmin/src/router/core/RoutePermissionValidator.ts:96
handleSubmit has cyclomatic complexity 11 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — sysadmin/src/views/auth/login/index.vue:182
(anonymous) has cyclomatic complexity 11 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — sysadmin/src/utils/table/tableUtils.ts:114
handleSave has cyclomatic complexity 11 and cognitive complexity 10; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — sysadmin/src/views/setting/index.vue:1029
Do you agree with this assessment?
R3 · Large Files6.4 / 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.
sysadmin/src/views/supply/list/index.vue has 2439 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — sysadmin/src/views/supply/list/index.vue:1
sysadmin/src/views/product/list/index.vue has 2076 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — sysadmin/src/views/product/list/index.vue:1
sysadmin/src/views/setting/index.vue has 1226 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — sysadmin/src/views/setting/index.vue:1
sysadmin/src/views/card/list/index.vue has 1220 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — sysadmin/src/views/card/list/index.vue:1
sysadmin/src/components/business/media-manager/index.vue has 1006 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — sysadmin/src/components/business/media-manager/index.vue:1
sysadmin/src/views/dashboard/console/index.vue has 818 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — sysadmin/src/views/dashboard/console/index.vue:1
sysadmin/scripts/clean-dev.ts has 745 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — sysadmin/scripts/clean-dev.ts:1
sysadmin/src/views/order/list/index.vue has 731 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — sysadmin/src/views/order/list/index.vue:1
storefront/src/views/Checkout.vue has 687 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — storefront/src/views/Checkout.vue:1
sysadmin/src/hooks/core/useChart.ts has 668 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — sysadmin/src/hooks/core/useChart.ts:1
sysadmin/src/views/update/index.vue has 663 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — sysadmin/src/views/update/index.vue:1
sysadmin/src/hooks/core/useTable.ts has 656 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — sysadmin/src/hooks/core/useTable.ts:1
storefront/src/views/Product.vue has 637 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — storefront/src/views/Product.vue:1
sysadmin/src/views/user/list/index.vue has 613 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — sysadmin/src/views/user/list/index.vue:1
sysadmin/src/components/core/layouts/art-fireworks-effect/index.vue has 561 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — sysadmin/src/components/core/layouts/art-fireworks-effect/index.vue:1
sysadmin/src/views/payment/list/index.vue has 553 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — sysadmin/src/views/payment/list/index.vue:1
sysadmin/src/components/core/forms/art-search-bar/index.vue has 516 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — sysadmin/src/components/core/forms/art-search-bar/index.vue:1
sysadmin/src/components/core/views/login/LoginLeftView.vue has 507 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — sysadmin/src/components/core/views/login/LoginLeftView.vue:1
sysadmin/src/components/core/layouts/art-work-tab/index.vue has 498 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — sysadmin/src/components/core/layouts/art-work-tab/index.vue:1
sysadmin/src/views/supplierAccount/list/index.vue has 491 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — sysadmin/src/views/supplierAccount/list/index.vue:1
sysadmin/src/store/modules/worktab.ts has 489 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — sysadmin/src/store/modules/worktab.ts:1
sysadmin/src/views/subsite/list/index.vue has 468 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — sysadmin/src/views/subsite/list/index.vue:1
storefront/src/views/MySubsite.vue has 459 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — storefront/src/views/MySubsite.vue:1
sysadmin/src/components/core/forms/art-form/index.vue has 448 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — sysadmin/src/components/core/forms/art-form/index.vue:1
sysadmin/src/components/core/layouts/art-header-bar/index.vue has 443 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — sysadmin/src/components/core/layouts/art-header-bar/index.vue:1
sysadmin/src/views/currency/list/index.vue has 428 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — sysadmin/src/views/currency/list/index.vue:1
storefront/src/views/UserCenter.vue has 420 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — storefront/src/views/UserCenter.vue:1
sysadmin/src/store/modules/setting.ts has 409 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — sysadmin/src/store/modules/setting.ts:1
sysadmin/src/components/core/layouts/art-notification/index.vue has 406 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — sysadmin/src/components/core/layouts/art-notification/index.vue: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 Coverage3.4 / 10Weak✓ 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) — sysadmin/scripts/clean-dev.ts:1, sysadmin/src/components/core/layouts/art-fireworks-effect/index.vue:1, sysadmin/src/components/core/forms/art-form/index.vue:1, …
What to do
Add tests that import the unreached modules (directly or through their public entry).
Do you agree with this assessment?
R6 · Tooling10.0 / 10Exemplary✓ 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.
Do you agree with this assessment?
R7 · Dead Code7.5 / 10Strong✓ Tool-verified
React / JS · Code Health — Files unreachable from every application/tooling/test entry point, and exports nothing imports (module-graph reachability, D-386).
Method: Dead code: files unreachable from every application/tooling/test entry point plus exports nothing imports, via module-graph reachability. Deterministic, exhaustive over the import graph.
Unreachable from the 38 application, 12 tooling and 29 test entry point(s) detected in this repo. Gate removals on `pnpm run build` — an undetected custom entry would make these reachable.
no import path from any entry point (38 application, 12 tooling, 29 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make (×10) — sysadmin/src/mock/temp/formData.ts, sysadmin/src/utils/sys/error-handle.ts, sysadmin/src/store/index.ts, …
Nothing imports this binding — it is safe to review for removal. (×18) — sysadmin/src/api/commission.ts:34, sysadmin/src/api/supplierAccounts.ts:86, sysadmin/src/api/supplierAccounts.ts:112, …
Nothing ultimately consumes this binding: its only referrer is the re-export in sysadmin/src/hooks/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in sysadmin/src/hooks/index.ts in the same commit, or the barrel will import a name that no longer exists. (×2) — sysadmin/src/hooks/core/useLayoutHeight.ts:34, sysadmin/src/hooks/core/useTable.ts:115
Nothing ultimately consumes this binding: its only referrer is the re-export in sysadmin/src/types/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in sysadmin/src/types/index.ts in the same commit, or the barrel will import a name that no longer exists. (×9) — sysadmin/src/types/common/index.ts:34, sysadmin/src/types/common/index.ts:37, sysadmin/src/types/common/index.ts:40, …
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.
Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. — package.json:19
Declared in storefront/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. — storefront/package.json:25
Declared in sysadmin/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×5) — sysadmin/package.json:94, sysadmin/package.json:59, sysadmin/package.json:96, …
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.
sysadmin/src/utils/storage/index.ts → sysadmin/src/utils/storage/storage-key-manager.ts → sysadmin/src/utils/storage/index.ts (one verified cycle inside a mutually-dependent group of 35 files) — sysadmin/src/utils/storage/index.ts:7
What to do
Break each cycle by extracting the shared piece into a module both sides can import.
Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.
Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.
Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.
Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.
Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.
Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.
Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether async functions that make a cancellable request accept or pass on an AbortSignal (adoption curve).
Method: Roslyn scan: every async method (excluding framework-fixed overrides/Blazor handlers) checked for CancellationToken parameter presence. Deterministic, adoption percentage. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same question: every named async function that itself makes a request an AbortSignal can cancel (global `fetch`, axios and its file-local instances, ky, ofetch) counts, and it is compliant when its parameters or body name a signal or it hands one of its own parameters to the request as options; signatures a framework fixes (JSX event handlers, route and lifecycle exports, request-first handlers, `override`, `'use server'` modules, TanStack `mutationFn`) are exempt unless they take a signal. Deterministic, adoption percentage.
Only 0/2 async functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
`exportCards` awaits `axios.get(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `axios.get(url, { signal })`. — sysadmin/src/api/cards.ts:183
`exportCoupons` awaits `axios.get(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `axios.get(url, { signal })`. — sysadmin/src/api/coupons.ts:72
What to do
Thread an AbortSignal through async functions that make requests, so the work stops when its caller gives up.
Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.
Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether the work a diagnostic log line costs is paid only when that line is wanted — C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.
Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` — outside any arrow or function passed as an argument, which the logger calls only when the level is on — with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X24 · Document value interpolated into markup unescaped3.7 / 10Weak✓ Tool-verified
Other · Security — Whether text read out of the document being converted is escaped before it is written into generated markup — a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.
Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF — the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.
`sanitizedNotice` is text this program did not author, and it is written into the text of an element through Vue's `v-html` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — storefront/src/components/NoticeModal.vue:63
`sanitizedHtml` is text this program did not author, and it is written into the text of an element through Vue's `v-html` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — storefront/src/components/OrderInstructions.vue:22
`sanitizedDescription` is text this program did not author, and it is written into the text of an element through Vue's `v-html` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — storefront/src/views/Product.vue:564
`sanitizedText` is text this program did not author, and it is written into the text of an element through Vue's `v-html` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. (×2) — sysadmin/src/components/core/text-effect/art-text-scroll/index.vue:23, sysadmin/src/components/core/text-effect/art-text-scroll/index.vue:29
`svgContent` is text this program did not author, and it is written into the text of an element through Vue's `v-html` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — sysadmin/src/components/core/theme/theme-svg/index.vue:5
`line` is text this program did not author, and it is written into the text of an element through markup built here with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — sysadmin/src/directives/business/highlight.ts:63
`renderMd(versionDetailData.notes)` is text this program did not author, and it is written into the text of an element through Vue's `v-html` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — sysadmin/src/views/update/index.vue:323
What to do
Each finding names the expression, the attribute it lands in and the line. Confirm the value's origin from the read this analyzer traced, then escape it at the sink or validate it against the shape the attribute accepts before interpolating.
Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.
Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.
Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.
Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.
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. (×11) — sysadmin/src/views/withdrawal/list/index.vue:70, sysadmin/src/views/withdrawal/list/index.vue:82, sysadmin/src/views/user/list/index.vue:535, …
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. (×24) — sysadmin/src/views/user/list/index.vue:318, sysadmin/src/views/user/list/index.vue:385, sysadmin/src/views/user/list/index.vue:512, …
`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, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included. (×5) — sysadmin/src/views/user/list/index.vue:479, sysadmin/src/views/update/index.vue:197, sysadmin/src/views/supply/list/index.vue:1151, …
Other · Code Health — Whether log calls use message templates (queryable) rather than interpolated strings.
Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `trace`/`debug`/`info`/`warn`/`error`/`fatal`/`verbose`/`silly`/`http`/`log` call on a receiver named for a logger, in a package whose own or an enclosing `package.json` declares a logger that carries values as fields (pino, pino-http, nestjs-pino, Fastify, winston, bunyan, tslog, LogTape, roarr), whose first deciding argument is a template literal with substitutions; an object-literal fields argument is stepped over, a plain string message clears the call. Python is read the same way: a `debug`/`info`/`warning`/`error`/`exception`/`critical`/`log` call on a logger in a file that imports the standard library’s `logging` or structlog (loguru, which formats at the call, is not judged), whose message is a whole f-string with a non-constant field; a `%`-formatted, `.format()`-ed or concatenated message is not convicted, as in C#. PHP is read the same way: a PSR-3 level call (`emergency`…`debug`, `log`) on a logger (`$logger`, `$this->logger`, Laravel’s `Log::`, `logger()`, `\Drupal::logger()`) in a package whose `composer.json` requires a PSR-3 logger or a framework that hands one out (psr/log, Monolog, Laravel, Symfony, Drupal, CakePHP), or a file that imports one, whose message is a double-quoted string interpolating a variable; a single-quoted message clears the call, and `sprintf` or `.` concatenation is not convicted, as in C#. Dart is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on Sentry’s structured logger (`Sentry.logger`) whose message is a whole string literal interpolating a value (`$name`, `${…}`); the `Sentry.logger.fmt` template API clears the call. Dart that logs only through loggers with one message and no fields (package:logging, package:logger, talker, dart:developer) is not applicable rather than a reach gap. Ruby is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on the console gem’s `Console` (declared by a Gemfile, gemspec or Gemfile.lock, or required) or, where SemanticLogger, Ougai or dry-logger is declared or required, on a receiver named for a logger (`logger`, `@logger`, `Rails.logger`, `log`), whose first deciding argument is, as the whole argument, a double-quoted string interpolating a non-constant value (`#{…}`, `#@ivar`); a plain literal clears the call, keyword arguments are the fields, and a block, `%`-format or `+` concatenation is not convicted. Ruby that logs only through the standard Logger (Rails.logger) is not applicable rather than a reach gap. Deterministic.
`info` at line 88 is handed a double-quoted string with variables interpolated into it as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values in the PSR-3 context array instead: `$logger->info('Order {order_id} moved to {status}', ['order_id' => $orderId, 'status' => $status])`, which Monolog and every PSR-3 handler keep as fields beside the message (Monolog's PsrLogMessageProcessor fills the placeholders), or `Log::info('order moved', ['order_id' => $orderId])` with Laravel's facade. — app/Support/DeliveryService.php:88
`debug` at line 90 is handed a double-quoted string with variables interpolated into it as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values in the PSR-3 context array instead: `$logger->debug('Order {order_id} moved to {status}', ['order_id' => $orderId, 'status' => $status])`, which Monolog and every PSR-3 handler keep as fields beside the message (Monolog's PsrLogMessageProcessor fills the placeholders), or `Log::debug('order moved', ['order_id' => $orderId])` with Laravel's facade. — app/Support/DomainVerificationService.php:90
`debug` at line 129 is handed a double-quoted string with variables interpolated into it as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values in the PSR-3 context array instead: `$logger->debug('Order {order_id} moved to {status}', ['order_id' => $orderId, 'status' => $status])`, which Monolog and every PSR-3 handler keep as fields beside the message (Monolog's PsrLogMessageProcessor fills the placeholders), or `Log::debug('order moved', ['order_id' => $orderId])` with Laravel's facade. — app/Support/DomainVerificationService.php:129
`info` at line 192 is handed a double-quoted string with variables interpolated into it as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values in the PSR-3 context array instead: `$logger->info('Order {order_id} moved to {status}', ['order_id' => $orderId, 'status' => $status])`, which Monolog and every PSR-3 handler keep as fields beside the message (Monolog's PsrLogMessageProcessor fills the placeholders), or `Log::info('order moved', ['order_id' => $orderId])` with Laravel's facade. — app/Support/DomainVerificationService.php:192
`warning` at line 98 is handed a double-quoted string with variables interpolated into it as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values in the PSR-3 context array instead: `$logger->warning('Order {order_id} moved to {status}', ['order_id' => $orderId, 'status' => $status])`, which Monolog and every PSR-3 handler keep as fields beside the message (Monolog's PsrLogMessageProcessor fills the placeholders), or `Log::warning('order moved', ['order_id' => $orderId])` with Laravel's facade. — app/Support/FulfillmentService.php:98
`warning` at line 109 is handed a double-quoted string with variables interpolated into it as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values in the PSR-3 context array instead: `$logger->warning('Order {order_id} moved to {status}', ['order_id' => $orderId, 'status' => $status])`, which Monolog and every PSR-3 handler keep as fields beside the message (Monolog's PsrLogMessageProcessor fills the placeholders), or `Log::warning('order moved', ['order_id' => $orderId])` with Laravel's facade. — app/Support/FulfillmentService.php:109
`warning` at line 97 is handed a double-quoted string with variables interpolated into it as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values in the PSR-3 context array instead: `$logger->warning('Order {order_id} moved to {status}', ['order_id' => $orderId, 'status' => $status])`, which Monolog and every PSR-3 handler keep as fields beside the message (Monolog's PsrLogMessageProcessor fills the placeholders), or `Log::warning('order moved', ['order_id' => $orderId])` with Laravel's facade. — app/Supply/SupplyCallbackService.php:97
`warning` at line 54 is handed a double-quoted string with variables interpolated into it as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values in the PSR-3 context array instead: `$logger->warning('Order {order_id} moved to {status}', ['order_id' => $orderId, 'status' => $status])`, which Monolog and every PSR-3 handler keep as fields beside the message (Monolog's PsrLogMessageProcessor fills the placeholders), or `Log::warning('order moved', ['order_id' => $orderId])` with Laravel's facade. — app/Supply/UpstreamOrderService.php:54
`info` at line 147 is handed a double-quoted string with variables interpolated into it as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values in the PSR-3 context array instead: `$logger->info('Order {order_id} moved to {status}', ['order_id' => $orderId, 'status' => $status])`, which Monolog and every PSR-3 handler keep as fields beside the message (Monolog's PsrLogMessageProcessor fills the placeholders), or `Log::info('order moved', ['order_id' => $orderId])` with Laravel's facade. — app/Supply/UpstreamOrderService.php:147
`warning` at line 150 is handed a double-quoted string with variables interpolated into it as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values in the PSR-3 context array instead: `$logger->warning('Order {order_id} moved to {status}', ['order_id' => $orderId, 'status' => $status])`, which Monolog and every PSR-3 handler keep as fields beside the message (Monolog's PsrLogMessageProcessor fills the placeholders), or `Log::warning('order moved', ['order_id' => $orderId])` with Laravel's facade. — app/Supply/UpstreamOrderService.php:150
`warning` at line 163 is handed a double-quoted string with variables interpolated into it as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values in the PSR-3 context array instead: `$logger->warning('Order {order_id} moved to {status}', ['order_id' => $orderId, 'status' => $status])`, which Monolog and every PSR-3 handler keep as fields beside the message (Monolog's PsrLogMessageProcessor fills the placeholders), or `Log::warning('order moved', ['order_id' => $orderId])` with Laravel's facade. — app/Supply/UpstreamOrderService.php:163
`info` at line 197 is handed a double-quoted string with variables interpolated into it as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values in the PSR-3 context array instead: `$logger->info('Order {order_id} moved to {status}', ['order_id' => $orderId, 'status' => $status])`, which Monolog and every PSR-3 handler keep as fields beside the message (Monolog's PsrLogMessageProcessor fills the placeholders), or `Log::info('order moved', ['order_id' => $orderId])` with Laravel's facade. — app/Jobs/SyncSupplySourceProducts.php:197
`info` at line 205 is handed a double-quoted string with variables interpolated into it as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values in the PSR-3 context array instead: `$logger->info('Order {order_id} moved to {status}', ['order_id' => $orderId, 'status' => $status])`, which Monolog and every PSR-3 handler keep as fields beside the message (Monolog's PsrLogMessageProcessor fills the placeholders), or `Log::info('order moved', ['order_id' => $orderId])` with Laravel's facade. — app/Jobs/SyncSupplySourceProducts.php:205
`error` at line 210 is handed a double-quoted string with variables interpolated into it as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values in the PSR-3 context array instead: `$logger->error('Order {order_id} moved to {status}', ['order_id' => $orderId, 'status' => $status])`, which Monolog and every PSR-3 handler keep as fields beside the message (Monolog's PsrLogMessageProcessor fills the placeholders), or `Log::error('order moved', ['order_id' => $orderId])` with Laravel's facade. — app/Jobs/SyncSupplySourceProducts.php:210
Other · Code Health — Whether PHP's static analysis checks null and is not undermined by a nullness baseline — PHPStan from level 8 (`checkNullables`) or Psalm at `errorLevel` 3 or stricter is what makes `?User` a type whose method call is an error, and the null entries of a baseline, `@psalm-suppress PossiblyNull…` and `@phpstan-ignore *.nonObject` are what silence it.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
This repository commits no PHPStan or Psalm configuration (`phpstan.neon[.dist]`, `phpstan.dist.neon`, `psalm.xml[.dist]`, or one a composer.json script names with `--configuration`), so nothing checks null: a `?Customer` reaches `->name()` silently and throws `Error: Call to a member function name() on null` the first time it is null. If the build passes a level on a command line instead, put it in a committed configuration — this check reads configuration, and configuration is all it can read.
What to do
Raise PHPStan to level 8 (`level: 8` in `phpstan.neon.dist`, or `max`) or Psalm to `errorLevel="3"` or stricter, so `?Type` is a type the checker holds you to; generate a baseline for what that surfaces only to pay it down, not to keep it. Then resolve the baselined nullness errors rather than adding to them: each is a call on a value the checker showed could be null — narrow it (`if ($x === null) { … }`, `?->`, an early return), make the property non-nullable and initialise it in the constructor, or change the return type so the null cannot arrive.
Do you agree with this assessment?
WCAG coverage — what static analysis assessed
Statically assessed 13 of 55 WCAG 2.2 Level A/AA success criteria (24%; ≈26% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 42 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).
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.
X10 Duplicated predicate — 8 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X6 Hand-rolled structured-format parsing — 3 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 5 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 4 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
C3 Audit Trail — C3 reached only 34% of this repository's production lines — typescript (52,152 lines), javascript (121 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
C4 Data Retention — C4 reached only 34% of this repository's production lines — typescript (52,152 lines), javascript (121 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 52 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AC6 Visual & motion safety — Visual & motion safety could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository.
AX1 Captive dependencies — 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
AX2 Stateful singletons — Not applicable: PHP builds its object graph per request and shares none of it between requests. 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
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX8 Test isolation — no test/production split to check
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — compose up failed (exit 17 — an image could not be built) — time="2026-11-17T18:42:54Z" level=warning msg="The \"DB_PASSWORD\" variable is not set. Defaulting to a blank string." laravel.test Pulling laravel.test Warning Get "https://sail-8.5/v2/": Forbidden unable to prepare context: path "vendor/laravel/sail/runtimes/8.5" not found; likely cause (not identified): the image build failed, and its output does not match a cause we recognise; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
C1 Data Protection — C1 reached only 34% of this repository's production lines — typescript (52,152 lines), javascript (121 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
C2 Access Controls — C2 reached only 34% of this repository's production lines — typescript (52,152 lines), javascript (121 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
D11 Test Reliability — Test reliability not scored — polyglot repository, one half has no runner
D16 Bus Factor — single-maintainer repository — bus factor is not applicable
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Aggregate roots were found in only one source directory (Models), which is a layered codebase, not two contexts. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D24 Comment Value — 1103 of 1105 comment blocks were not judged (1089 in a non-Latin script, 14 in a language other than English): redundancy is judged by word overlap with the code's identifiers, which cannot be measured across languages.
D25 ADR Conformance — no ADRs to check
D27 Navigability — symbol resolution incomplete — navigability not assessed
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.
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 — polyglot repository, one half has no runner
DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (36 aggregate root(s) (types guarding their own state behind command methods — this language has no AggregateRoot base to inherit))
ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
P12 CI test-gate honesty — no CI workflow found
P9 Domain vs controller coverage — coverage data present for 1 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
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.
R5 Dependency Freshness — uses a pnpm lockfile — dependency freshness not measured here; JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
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.
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
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
X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. PHP gives a request one thread of its own; the event-loop libraries (ReactPHP, Amp) run callbacks one at a time, and ext-parallel copies every value across its channels, so no array or collection is reachable from two threads at once. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
X27 Collection changed while being enumerated — X27 reached only 34% of this repository's production lines — typescript (52,152 lines), javascript (121 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
AC4 · Keyboard semantics· Click handler on a non-interactive <div> · ×23
Click handler on a non-interactive <div> storefront/src/components/ProductCard.vue:32— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
Click handler on a non-interactive <div> storefront/src/views/Home.vue:107— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
Click handler on a non-interactive <div> storefront/src/views/Product.vue:326— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
Click handler on a non-interactive <div> storefront/src/views/Product.vue:335— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
Click handler on a non-interactive <div> storefront/src/views/Product.vue:405— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
Click handler on a non-interactive <div> storefront/src/views/Product.vue:560— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
Click handler on a non-interactive <div> sysadmin/src/components/business/comment-widget/widget/CommentItem.vue:16— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
Click handler on a non-interactive <div> sysadmin/src/components/core/banners/art-basic-banner/index.vue:3— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
Click handler on a non-interactive <div> sysadmin/src/components/core/banners/art-card-banner/index.vue:13— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
Click handler on a non-interactive <div> sysadmin/src/components/core/banners/art-card-banner/index.vue:24— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
Click handler on a non-interactive <div> sysadmin/src/components/core/base/art-back-to-top/index.vue:11— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
Click handler on a non-interactive <div> sysadmin/src/components/core/cards/art-image-card/index.vue:3— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
Click handler on a non-interactive <div> sysadmin/src/components/core/forms/art-button-table/index.vue:3— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
Click handler on a non-interactive <div> sysadmin/src/components/core/forms/art-search-bar/index.vue:89— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
Click handler on a non-interactive <div> sysadmin/src/components/core/layouts/art-breadcrumb/index.vue:10— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
Click handler on a non-interactive <div> sysadmin/src/components/core/layouts/art-fast-enter/index.vue:26— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
Click handler on a non-interactive <div> sysadmin/src/components/core/layouts/art-global-search/index.vue:36— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
Click handler on a non-interactive <div> sysadmin/src/components/core/layouts/art-global-search/index.vue:51— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
Click handler on a non-interactive <div> sysadmin/src/components/core/layouts/art-header-bar/index.vue:19— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
Click handler on a non-interactive <div> sysadmin/src/components/core/layouts/art-header-bar/index.vue:65— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
Click handler on a non-interactive <div> sysadmin/src/components/core/layouts/art-header-bar/index.vue:113— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
Click handler on a non-interactive <div> sysadmin/src/components/core/layouts/art-menus/art-mixed-menu/index.vue:5— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
Click handler on a non-interactive <div> sysadmin/src/components/core/layouts/art-menus/art-mixed-menu/index.vue:47— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
AC2 · Forms & labels· <input> without a programmatic label · ×19
<input> without a programmatic label storefront/src/views/Checkout.vue:575— 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 storefront/src/views/Checkout.vue:587— 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 storefront/src/views/Checkout.vue:591— 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 storefront/src/views/Checkout.vue:597— 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 storefront/src/views/Checkout.vue:611— 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 storefront/src/views/ForgetPassword.vue:113— 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 storefront/src/views/ForgetPassword.vue:119— 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 storefront/src/views/ForgetPassword.vue:138— 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 storefront/src/views/ForgetPassword.vue:148— 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 storefront/src/views/ForgetPassword.vue:153— 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 storefront/src/views/Home.vue:197— 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 storefront/src/views/Install.vue:204— 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 storefront/src/views/Install.vue:210— 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 storefront/src/views/Install.vue:215— 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 storefront/src/views/Install.vue:221— 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 storefront/src/views/Install.vue:226— 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 storefront/src/views/Install.vue:256— 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 storefront/src/views/Install.vue:261— 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 storefront/src/views/Install.vue:266— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
AC2 · Forms & labels· <label> that labels no control · ×16
<label> that labels no control resources/views/filament/pages/payment-channels.blade.php:71— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control storefront/src/views/Checkout.vue:560— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control storefront/src/views/ForgetPassword.vue:112— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control storefront/src/views/ForgetPassword.vue:117— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control storefront/src/views/ForgetPassword.vue:136— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control storefront/src/views/ForgetPassword.vue:147— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control storefront/src/views/ForgetPassword.vue:152— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control storefront/src/views/Install.vue:203— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control storefront/src/views/Install.vue:209— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control storefront/src/views/Install.vue:214— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control storefront/src/views/Install.vue:220— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control storefront/src/views/Install.vue:225— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control storefront/src/views/Install.vue:255— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control storefront/src/views/Install.vue:260— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control storefront/src/views/Install.vue:265— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control storefront/src/views/Login.vue:90— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
AC1 · Text alternatives· <img> without a text alternative · ×12
<img> without a text alternative storefront/src/components/ProductCard.vue:35— 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 storefront/src/components/ProductCard.vue:56— 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 storefront/src/views/Checkout.vue:522— 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 storefront/src/views/Product.vue:327— 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 storefront/src/views/Product.vue:337— 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 storefront/src/views/Product.vue:358— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative sysadmin/src/components/business/image-picker/index.vue:57— 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 sysadmin/src/components/business/media-picker/index.vue:86— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative sysadmin/src/components/core/layouts/art-notification/index.vue:61— 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 sysadmin/src/components/core/layouts/art-settings-panel/widget/MenuLayoutSettings.vue:12— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative sysadmin/src/components/core/layouts/art-settings-panel/widget/MenuStyleSettings.vue:17— 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 sysadmin/src/components/core/layouts/art-settings-panel/widget/ThemeSettings.vue:11— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
AC4 · Keyboard semantics· Click handler on a non-interactive <img> · ×6
Click handler on a non-interactive <img> storefront/src/views/Checkout.vue:599— 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 <img> storefront/src/views/ForgetPassword.vue:121— 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 <img> storefront/src/views/Login.vue:105— 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 <img> storefront/src/views/Product.vue:358— 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 <img> storefront/src/views/Register.vue:143— 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 <img> sysadmin/src/components/business/media-picker/index.vue:86— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
AC4 · Keyboard semantics· Click handler on a non-interactive <li> · ×5
Click handler on a non-interactive <li> sysadmin/src/components/business/media-manager/index.vue:459— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
Click handler on a non-interactive <li> sysadmin/src/components/business/media-manager/index.vue:467— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
Click handler on a non-interactive <li> sysadmin/src/components/business/media-manager/index.vue:475— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
Click handler on a non-interactive <li> sysadmin/src/components/business/media-manager/index.vue:553— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
Click handler on a non-interactive <li> sysadmin/src/components/core/layouts/art-fast-enter/index.vue:50— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
AC2 · Forms & labels· <select> without a programmatic label · ×3
<select> without a programmatic label storefront/src/components/AppHeader.vue:179— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<select> without a programmatic label storefront/src/components/AppHeader.vue:182— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<select> without a programmatic label storefront/src/views/Checkout.vue:561— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
AC4 · Keyboard semantics· Click handler on a non-interactive <span> · ×3
Click handler on a non-interactive <span> storefront/src/components/HotTags.vue:25— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
Click handler on a non-interactive <span> sysadmin/src/components/business/icon-picker/index.vue:68— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
Click handler on a non-interactive <span> sysadmin/src/components/business/icon-picker/index.vue:81— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
AC4 · Keyboard semantics· Clickable element isn't keyboard-operable · ×3
Clickable element isn't keyboard-operable sysadmin/src/components/business/image-picker/index.vue:56— The repo's own CSS styles .preview-thumb with `cursor: pointer`, so this <div> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler.
Clickable element isn't keyboard-operable sysadmin/src/components/core/layouts/art-global-search/index.vue:31— The repo's own CSS styles .box with `cursor: pointer`, so this <div> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler.
Clickable element isn't keyboard-operable sysadmin/src/components/core/layouts/art-global-search/index.vue:64— The repo's own CSS styles .c-p with `cursor: pointer`, so this <div> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler.
<html> without a lang public/admin/index.html:2— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang sysadmin/index.html:2— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
AC2 · Forms & labels· <button> with no accessible text · ×1
<button> with no accessible text storefront/src/components/AppHeader.vue:149— A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
AC2 · Forms & labels· <textarea> without a programmatic label · ×1
<textarea> without a programmatic label storefront/src/views/Checkout.vue:572— 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 sysadmin/src/views/outside/Iframe.vue:3— 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.
Boundary-crossing change coupling: UpdateController.php ↔ app.php app/Http/Controllers/Api/Admin/UpdateController.php:1— `app/Http/Controllers/Api/Admin/UpdateController.php` (context Http) and `config/app.php` (context config) sit in DIFFERENT parts of the tree yet change together 54% of the time (7 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `66eac6da` fix(update): .git/objects 权限不足修复 + 明确错误指引; `eb523132` fix(update): 在线更新后自动校验前端产物完整性(防止 404 白屏); `05c49e46` fix(update): 彻底解决在线更新权限+未跟踪文件冲突 — run `git show` on any of them.
Import cycle (2 files) sysadmin/src/utils/storage/index.ts:7— sysadmin/src/utils/storage/index.ts → sysadmin/src/utils/storage/storage-key-manager.ts → sysadmin/src/utils/storage/index.ts (one verified cycle inside a mutually-dependent group of 35 files)
Serious — 398 finding(s)
R4 · Test Coverage· No test reaches this file · ×40
No test reaches this file sysadmin/scripts/clean-dev.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 sysadmin/src/components/core/layouts/art-fireworks-effect/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 sysadmin/src/components/core/forms/art-form/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 sysadmin/src/components/core/forms/art-search-bar/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 storefront/src/views/Checkout.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 sysadmin/src/components/core/layouts/art-work-tab/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 sysadmin/src/components/core/layouts/art-notification/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 sysadmin/src/components/core/forms/art-excel-export/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 sysadmin/src/components/core/charts/art-line-chart/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 sysadmin/src/components/core/layouts/art-global-search/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 sysadmin/src/components/core/tables/art-table/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 sysadmin/src/components/core/layouts/art-header-bar/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 sysadmin/src/components/core/layouts/art-menus/art-sidebar-menu/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 sysadmin/src/components/core/others/art-menu-right/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 sysadmin/src/components/core/forms/art-drag-verify/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 sysadmin/src/components/core/tables/art-table-header/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 storefront/src/views/Product.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 sysadmin/src/components/core/text-effect/art-count-to/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 sysadmin/src/components/core/text-effect/art-text-scroll/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 sysadmin/src/components/core/charts/art-map-chart/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 sysadmin/src/components/core/layouts/art-chat-window/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 sysadmin/src/directives/business/highlight.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 sysadmin/src/components/core/forms/art-wang-editor/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 sysadmin/src/components/core/media/art-cutter-img/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 sysadmin/src/components/core/layouts/art-settings-panel/composables/useSettingsConfig.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.
Swallowed exception (empty catch) sysadmin/src/views/withdrawal/list/index.vue: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) sysadmin/src/views/withdrawal/list/index.vue:82— `.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) sysadmin/src/views/user/list/index.vue:318— 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) sysadmin/src/views/user/list/index.vue:385— 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) sysadmin/src/views/user/list/index.vue:512— 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) sysadmin/src/views/user/list/index.vue:531— 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) sysadmin/src/views/user/list/index.vue:535— `.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) sysadmin/src/views/update/index.vue:214— `.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) sysadmin/src/views/supply/list/index.vue:1181— 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) sysadmin/src/views/supply/list/index.vue:1200— 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) sysadmin/src/views/supply/list/index.vue:1204— `.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) sysadmin/src/views/supply/list/index.vue:1224— 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) sysadmin/src/views/supply/list/index.vue:1241— 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) sysadmin/src/views/supply/list/index.vue:1266— 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) sysadmin/src/views/supply/list/index.vue:1294— 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) sysadmin/src/views/supply/list/index.vue:1329— 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) sysadmin/src/views/supply/list/index.vue:1344— 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) sysadmin/src/views/supply/list/index.vue:1383— 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) sysadmin/src/views/supply/list/index.vue:1430— `.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) sysadmin/src/views/supply/list/index.vue:1634— 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) sysadmin/src/views/supply/list/index.vue:1783— 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) sysadmin/src/views/supply/list/index.vue:1906— 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) sysadmin/src/views/supplierAccount/list/index.vue:299— 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) sysadmin/src/views/supplierAccount/list/index.vue:320— 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) sysadmin/src/views/supplierAccount/list/index.vue:324— `.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.
Repeated repair: storefront/src/views/PayResult.vue storefront/src/views/PayResult.vue:102— storefront/src/views/PayResult.vue changed 13 times in last 90 days and 9 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 9 (its worst body is (anonymous) at line 102), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(v1.14.0): 游客查单凭证链修复 — 顾客付款后按邮箱/手机号查不到订单、看不到卡密”; “fix(v1.12.85): 安全审计整改 — 默认管理员凭据/安装接管/零价供货/回调SSRF/优惠券双花/CSV注入/微信回调验签等 30+ 项修复”; “fix(v1.12.61): 修复安全漏洞与高危接口”; “fix(v1.12.47): 倒计时484:39——后端时间改带时区ISO8601,前端直接解析”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-06-11..2026-09-09, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-11 01:44:17 +07:00' --until='2026-09-09 01:44:17 +07:00' --full-history --no-merges -- storefront/src/views/PayResult.vue`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: app/Supply/Drivers/ZCardDriver.php app/Supply/Drivers/ZCardDriver.php:181— app/Supply/Drivers/ZCardDriver.php changed 11 times in last 90 days and 7 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 8 (its worst body is ZCardDriver.verifyCallback at line 181), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(v1.12.85): 安全审计整改 — 默认管理员凭据/安装接管/零价供货/回调SSRF/优惠券双花/CSV注入/微信回调验签等 30+ 项修复”; “fix(v1.12.83): 修复货源同步卡死与运行时混版”; “fix(v1.12.82): 自动删除同步中失效的上游商品”; “fix(v1.12.54): 上游库存全-1——同步时并发补查真实库存(acg-faka手动发货)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-06-11..2026-09-09, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-11 01:44:17 +07:00' --until='2026-09-09 01:44:17 +07:00' --full-history --no-merges -- app/Supply/Drivers/ZCardDriver.php`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: app/Supply/Drivers/DujiaoNextDriver.php app/Supply/Drivers/DujiaoNextDriver.php:284— app/Supply/Drivers/DujiaoNextDriver.php changed 10 times in last 90 days and 6 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 11 (its worst body is DujiaoNextDriver.localizedText at line 284), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(v1.12.85): 安全审计整改 — 默认管理员凭据/安装接管/零价供货/回调SSRF/优惠券双花/CSV注入/微信回调验签等 30+ 项修复”; “fix(v1.12.83): 修复货源同步卡死与运行时混版”; “fix(v1.12.82): 自动删除同步中失效的上游商品”; “fix(v1.12.54): 上游库存全-1——同步时并发补查真实库存(acg-faka手动发货)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-06-11..2026-09-09, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-11 01:44:17 +07:00' --until='2026-09-09 01:44:17 +07:00' --full-history --no-merges -- app/Supply/Drivers/DujiaoNextDriver.php`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: app/Support/ServiceWidgetScript.php app/Support/ServiceWidgetScript.php:25— app/Support/ServiceWidgetScript.php changed 6 times in last 90 days and 6 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 1 (its worst body is ServiceWidgetScript.label at line 25), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(v1.14.1): 统计代码静默失效(issue #39) + 注册/登录验证码第 5 位被裁”; “fix(v1.12.93): 修复 PHP8.3(PCRE2<10.43)下变长 lookbehind 导致客服白名单配置接口 500(issue #14)”; “fix(v1.12.92): 客服脚本端点改为无扩展名路径 — 修复 nginx 把 .js API 路径当静态文件导致线上客服 404”; “fix(v1.12.91): 客服脚本 CSP 放行口径修复 — 白名单域名全量进 CSP + 默认域名合并 + 补 Crisp relay/image/storage 子域名”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-06-11..2026-09-09, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-11 01:44:17 +07:00' --until='2026-09-09 01:44:17 +07:00' --full-history --no-merges -- app/Support/ServiceWidgetScript.php`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: storefront/src/views/RechargePay.vue storefront/src/views/RechargePay.vue:135— storefront/src/views/RechargePay.vue changed 9 times in last 90 days and 5 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 9 (its worst body is handleResult at line 135), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(v1.12.61): 修复安全漏洞与高危接口”; “fix(v1.12.59): 重构易支付配置与回调链路”; “fix(v1.12.34): 支付宝配置缺失证书参数报错 + 扩展当面付/扫码/H5支付方式”; “fix(v1.12.7): 充值支付页按 pay_types 展开具体支付方式(与收银台一致)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-06-11..2026-09-09, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-11 01:44:17 +07:00' --until='2026-09-09 01:44:17 +07:00' --full-history --no-merges -- storefront/src/views/RechargePay.vue`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: storefront/src/views/Login.vue storefront/src/views/Login.vue:43— storefront/src/views/Login.vue changed 7 times in last 90 days and 5 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 13 (its worst body is submit at line 43), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(v1.14.9): 兼容出海版 ACG-Faka 并修复充值/验证码/定价输入”; “fix(v1.12.85): 安全审计整改 — 默认管理员凭据/安装接管/零价供货/回调SSRF/优惠券双花/CSV注入/微信回调验签等 30+ 项修复”; “fix(v1.12.14): 充值支付跳登录 + 登录支持用户名 + 自定义金额交互”; “fix(v1.12.9): 登录态安全修复——token 7 天过期 + 登录超时提示 + 老客户被误登出”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-06-11..2026-09-09, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-11 01:44:17 +07:00' --until='2026-09-09 01:44:17 +07:00' --full-history --no-merges -- storefront/src/views/Login.vue`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: storefront/src/components/ProductCard.vue storefront/src/components/ProductCard.vue:20— storefront/src/components/ProductCard.vue changed 7 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 5 (its worst body is (anonymous) at line 20), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(v1.15.0): 缺货商品禁止下单 — 上游商品付款前拒单 + 前台售罄态”; “fix(v1.12.65): 上游商品库存显示口径统一”; “fix(v1.12.54): 上游库存全-1——同步时并发补查真实库存(acg-faka手动发货)”; “fix(v1.12.2): 多货币显示符号与金额错乱 + 下单快照货币取中间件解析值”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-06-11..2026-09-09, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-11 01:44:17 +07:00' --until='2026-09-09 01:44:17 +07:00' --full-history --no-merges -- storefront/src/components/ProductCard.vue`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: sysadmin/src/views/auth/login/index.vue sysadmin/src/views/auth/login/index.vue:182— sysadmin/src/views/auth/login/index.vue changed 7 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 11 (its worst body is handleSubmit at line 182), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(v1.14.9): 兼容出海版 ACG-Faka 并修复充值/验证码/定价输入”; “fix(v1.12.97): sysadmin 移除不可用的注册页与找回密码页(issue #24)”; “fix(v1.12.42): 后台登录滑块联动开关 + 支付宝错误提示增强 + 超时关单Cron配置”; “fix(v1.11.6): 后台登录滑块验证默认成功且无法滑动”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-06-11..2026-09-09, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-11 01:44:17 +07:00' --until='2026-09-09 01:44:17 +07:00' --full-history --no-merges -- sysadmin/src/views/auth/login/index.vue`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: app/Models/SupplySource.php app/Models/SupplySource.php:67— app/Models/SupplySource.php changed 7 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 5 (its worst body is SupplySource.getCredentialsAttribute at line 67), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(v1.12.85): 安全审计整改 — 默认管理员凭据/安装接管/零价供货/回调SSRF/优惠券双花/CSV注入/微信回调验签等 30+ 项修复”; “fix(v1.12.81): 修复同步任务统计与上游商品链接”; “fix(v1.9.3): 复查修复 4 个支付/货源问题”; “fix(supply): 模型质量修复(SupplySource状态常量+3模型冒烟测试+api_secret注释)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-06-11..2026-09-09, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-11 01:44:17 +07:00' --until='2026-09-09 01:44:17 +07:00' --full-history --no-merges -- app/Models/SupplySource.php`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: sysadmin/src/views/user/list/index.vue sysadmin/src/views/user/list/index.vue:475— sysadmin/src/views/user/list/index.vue changed 6 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 14 (its worst body is handleSubmit at line 475), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(v1.14.9): 兼容出海版 ACG-Faka 并修复充值/验证码/定价输入”; “fix(v1.12.88): 用户管理余额修改恢复并强制走 BillService 流水(禁自调/负余额防护)”; “fix(v1.9.7): 列表页分页栏被卡片裁切,数据满页时无法看到/切换分页”; “fix(v1.9.7): 列表页 keep-alive 缓存导致数据/分页不刷新”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-06-11..2026-09-09, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-11 01:44:17 +07:00' --until='2026-09-09 01:44:17 +07:00' --full-history --no-merges -- sysadmin/src/views/user/list/index.vue`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: app/Models/SupplySyncTask.php app/Models/SupplySyncTask.php:58— app/Models/SupplySyncTask.php changed 6 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 1 (its worst body is SupplySyncTask.source at line 58), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(v1.14.2): 修复队列探针误报并补齐取消审计(issue #42)”; “fix(v1.12.83): 修复货源同步卡死与运行时混版”; “fix(v1.12.82): 自动删除同步中失效的上游商品”; “fix(v1.12.80): 修复上游渠道加价未应用”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-06-11..2026-09-09, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-11 01:44:17 +07:00' --until='2026-09-09 01:44:17 +07:00' --full-history --no-merges -- app/Models/SupplySyncTask.php`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: storefront/vite.config.ts storefront/vite.config.ts:6— storefront/vite.config.ts changed 6 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 3 (its worst body is (anonymous) at line 6), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(v1.12.55): Cloudflare Rocket Loader 致 admin 空白——module入口加data-cfasync=false(issue #11)”; “fix(v1.9.26): 前台分类图标图片不加载(路径当文本渲染)”; “fix(storefront): vite 加 base '/storefront/' 修复安装向导静态资源 404”; “fix: storefront 编译到 public/storefront/ + Laravel SPA 路由 + 更新容错”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-06-11..2026-09-09, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-11 01:44:17 +07:00' --until='2026-09-09 01:44:17 +07:00' --full-history --no-merges -- storefront/vite.config.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: app/Http/Controllers/Api/StorefrontSettingsController.php app/Http/Controllers/Api/StorefrontSettingsController.php:15— app/Http/Controllers/Api/StorefrontSettingsController.php changed 5 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 3 (its worst body is StorefrontSettingsController.show at line 15), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(v1.14.1): 统计代码静默失效(issue #39) + 注册/登录验证码第 5 位被裁”; “fix(v1.12.85): 安全审计整改 — 默认管理员凭据/安装接管/零价供货/回调SSRF/优惠券双花/CSV注入/微信回调验签等 30+ 项修复”; “fix(v1.12.84): 修复第三方客服脚本无法加载”; “fix(v1.12.55): 修复若干漏洞”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-06-11..2026-09-09, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-11 01:44:17 +07:00' --until='2026-09-09 01:44:17 +07:00' --full-history --no-merges -- app/Http/Controllers/Api/StorefrontSettingsController.php`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: app/Http/Middleware/SecurityHeaders.php app/Http/Middleware/SecurityHeaders.php:14— app/Http/Middleware/SecurityHeaders.php changed 5 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 7 (its worst body is SecurityHeaders.handle at line 14), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(v1.14.1): 统计代码静默失效(issue #39) + 注册/登录验证码第 5 位被裁”; “fix(v1.12.91): 客服脚本 CSP 放行口径修复 — 白名单域名全量进 CSP + 默认域名合并 + 补 Crisp relay/image/storage 子域名”; “fix(v1.12.85): 安全审计整改 — 默认管理员凭据/安装接管/零价供货/回调SSRF/优惠券双花/CSV注入/微信回调验签等 30+ 项修复”; “fix(v1.12.84): 修复第三方客服脚本无法加载”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-06-11..2026-09-09, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-11 01:44:17 +07:00' --until='2026-09-09 01:44:17 +07:00' --full-history --no-merges -- app/Http/Middleware/SecurityHeaders.php`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: app/Support/AppHelper.php app/Support/AppHelper.php:32— app/Support/AppHelper.php changed 4 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 3 (its worst body is AppHelper.resolveVersion at line 32), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(v1.11.7): 顶栏版本号更新后仍显示旧版——版本缓存 5 分钟”; “fix(version): 版本号写死 VERSION 文件,彻底解决宝塔环境显示 v1.0.0”; “fix(update): 版本号 v1.0.0 + 在线更新 shell_exec 报错”; “fix: 在线更新图标不显示 + 版本号自动同步 git tag”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-06-11..2026-09-09, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-11 01:44:17 +07:00' --until='2026-09-09 01:44:17 +07:00' --full-history --no-merges -- app/Support/AppHelper.php`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: app/Http/Controllers/Api/SubsiteConsoleController.php app/Http/Controllers/Api/SubsiteConsoleController.php:64— app/Http/Controllers/Api/SubsiteConsoleController.php changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 8 (its worst body is SubsiteConsoleController.bindDomain at line 64), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(v1.12.85): 安全审计整改 — 默认管理员凭据/安装接管/零价供货/回调SSRF/优惠券双花/CSV注入/微信回调验签等 30+ 项修复”; “fix(v1.12.55): 修复若干漏洞”; “fix: 分站完整复查修复 G1-G3”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-06-11..2026-09-09, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-11 01:44:17 +07:00' --until='2026-09-09 01:44:17 +07:00' --full-history --no-merges -- app/Http/Controllers/Api/SubsiteConsoleController.php`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: storefront/src/views/Recharge.vue storefront/src/views/Recharge.vue:50— storefront/src/views/Recharge.vue changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 7 (its worst body is submit at line 50), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(v1.12.14): 充值支付跳登录 + 登录支持用户名 + 自定义金额交互”; “fix(v1.12.5): 手机 H5 前端修复 + 上游库存 + 默认货币 + session cookie”; “fix(v1.12.2): 多货币显示符号与金额错乱 + 下单快照货币取中间件解析值”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-06-11..2026-09-09, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-11 01:44:17 +07:00' --until='2026-09-09 01:44:17 +07:00' --full-history --no-merges -- storefront/src/views/Recharge.vue`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: sysadmin/src/components/business/media-manager/index.vue sysadmin/src/components/business/media-manager/index.vue:107— sysadmin/src/components/business/media-manager/index.vue changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 9 (its worst body is loadMedia at line 107), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(v1.11.14): 素材选择弹窗缺少删除图片功能”; “fix(v1.11.8): 素材选择弹窗闪退 + 删除按钮难用”; “fix(v1.11.2): 素材管理删除图片无效——管理模式无法选中”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-06-11..2026-09-09, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-11 01:44:17 +07:00' --until='2026-09-09 01:44:17 +07:00' --full-history --no-merges -- sysadmin/src/components/business/media-manager/index.vue`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: storefront/src/stores/preferences.ts storefront/src/stores/preferences.ts:36— storefront/src/stores/preferences.ts changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 12 (its worst body is load at line 36), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(v1.12.5): 手机 H5 前端修复 + 上游库存 + 默认货币 + session cookie”; “fix(v1.12.2): 多货币显示符号与金额错乱 + 下单快照货币取中间件解析值”; “fix(I-3): storefront consumes enabled_languages/default_language/default_display_currency”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-06-11..2026-09-09, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-11 01:44:17 +07:00' --until='2026-09-09 01:44:17 +07:00' --full-history --no-merges -- storefront/src/stores/preferences.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: sysadmin/src/utils/http/index.ts sysadmin/src/utils/http/index.ts:68— sysadmin/src/utils/http/index.ts changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 9 (its worst body is index.axiosInstance.interceptors.request.use() at line 68), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(v1.13.1): 后台写请求 CSRF 补缺 — 修复连通性测试/写操作 419 CSRF token mismatch”; “fix(v1.12.85): 安全审计整改 — 默认管理员凭据/安装接管/零价供货/回调SSRF/优惠券双花/CSV注入/微信回调验签等 30+ 项修复”; “fix(v1.12.40): 后台开启登录验证码后 sysadmin 登录恒报验证码错误”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-06-11..2026-09-09, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-11 01:44:17 +07:00' --until='2026-09-09 01:44:17 +07:00' --full-history --no-merges -- sysadmin/src/utils/http/index.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: app/Supply/Drivers/Concerns/MakesHttpRequests.php app/Supply/Drivers/Concerns/MakesHttpRequests.php:56— app/Supply/Drivers/Concerns/MakesHttpRequests.php changed 3 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 4 (its worst body is MakesHttpRequests.postRaw at line 56), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(v1.14.7): 修复 ACG-Faka 完整协议对接”; “fix(v1.12.83): 修复货源同步卡死与运行时混版”; “fix(v1.9.6): 上游驱动签名字节一致性修复(双重 md5)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-06-11..2026-09-09, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-11 01:44:17 +07:00' --until='2026-09-09 01:44:17 +07:00' --full-history --no-merges -- app/Supply/Drivers/Concerns/MakesHttpRequests.php`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: storefront/src/components/ServiceWidget.vue storefront/src/components/ServiceWidget.vue:22— storefront/src/components/ServiceWidget.vue changed 3 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 4 (its worst body is (anonymous) at line 22), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(v1.12.92): 客服脚本端点改为无扩展名路径 — 修复 nginx 把 .js API 路径当静态文件导致线上客服 404”; “fix(v1.12.84): 修复第三方客服脚本无法加载”; “fix(v1.12.68): 客服浮窗原生脚本模式 + favicon 支持”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-06-11..2026-09-09, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-11 01:44:17 +07:00' --until='2026-09-09 01:44:17 +07:00' --full-history --no-merges -- storefront/src/components/ServiceWidget.vue`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: app/Support/CurrencyService.php app/Support/CurrencyService.php:76— app/Support/CurrencyService.php changed 3 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 5 (its worst body is CurrencyService.format at line 76), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(v1.9.21): /api/currencies Attempt to read property code on array”; “fix(v1.9.7): database cache 存 Eloquent 对象被 MySQL 存坏 + 上游商品导入价格恒 0”; “fix: CurrencyService rounding + negative formatting + test coverage”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-06-11..2026-09-09, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-11 01:44:17 +07:00' --until='2026-09-09 01:44:17 +07:00' --full-history --no-merges -- app/Support/CurrencyService.php`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: sysadmin/src/views/product/list/index.vue sysadmin/src/views/product/list/index.vue:1756— sysadmin/src/views/product/list/index.vue changed 27 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 40 in openEdit at line 1756. 4 of those changes were fix/bug commits, and the other 23 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-06-11..2026-09-09, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-11 01:44:17 +07:00' --until='2026-09-09 01:44:17 +07:00' --full-history --no-merges -- sysadmin/src/views/product/list/index.vue`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: app/Support/OrderService.php app/Support/OrderService.php:32— app/Support/OrderService.php changed 19 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 54 in OrderService.createOrder at line 32. 7 of those changes were fix/bug commits, and the other 12 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-06-11..2026-09-09, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-11 01:44:17 +07:00' --until='2026-09-09 01:44:17 +07:00' --full-history --no-merges -- app/Support/OrderService.php`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: app/Supply/SupplySyncService.php app/Supply/SupplySyncService.php:43— app/Supply/SupplySyncService.php changed 25 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 22 in SupplySyncService.upsertProduct at line 43. 19 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-06-11..2026-09-09, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-11 01:44:17 +07:00' --until='2026-09-09 01:44:17 +07:00' --full-history --no-merges -- app/Supply/SupplySyncService.php`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: storefront/src/views/Checkout.vue storefront/src/views/Checkout.vue:151— storefront/src/views/Checkout.vue changed 25 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 22 in loadSingle at line 151. 13 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-06-11..2026-09-09, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-11 01:44:17 +07:00' --until='2026-09-09 01:44:17 +07:00' --full-history --no-merges -- storefront/src/views/Checkout.vue`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: sysadmin/src/views/setting/index.vue sysadmin/src/views/setting/index.vue:887— sysadmin/src/views/setting/index.vue changed 29 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in loadSettings at line 887. 10 of those changes were fix/bug commits, and the other 19 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-06-11..2026-09-09, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-11 01:44:17 +07:00' --until='2026-09-09 01:44:17 +07:00' --full-history --no-merges -- sysadmin/src/views/setting/index.vue`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: app/Supply/Drivers/AcgFakaDriver.php app/Supply/Drivers/AcgFakaDriver.php:177— app/Supply/Drivers/AcgFakaDriver.php changed 17 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 24 in AcgFakaDriver.fillMissingStocks at line 177. 12 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-06-11..2026-09-09, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-11 01:44:17 +07:00' --until='2026-09-09 01:44:17 +07:00' --full-history --no-merges -- app/Supply/Drivers/AcgFakaDriver.php`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: app/Support/StorefrontConfig.php app/Support/StorefrontConfig.php:358— app/Support/StorefrontConfig.php changed 24 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in StorefrontConfig.setMany at line 358. 7 of those changes were fix/bug commits, and the other 17 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-06-11..2026-09-09, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-11 01:44:17 +07:00' --until='2026-09-09 01:44:17 +07:00' --full-history --no-merges -- app/Support/StorefrontConfig.php`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: app/Http/Controllers/Api/Admin/UpdateController.php app/Http/Controllers/Api/Admin/UpdateController.php:269— app/Http/Controllers/Api/Admin/UpdateController.php changed 25 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in UpdateController.rollback at line 269. 21 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-06-11..2026-09-09, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-11 01:44:17 +07:00' --until='2026-09-09 01:44:17 +07:00' --full-history --no-merges -- app/Http/Controllers/Api/Admin/UpdateController.php`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: app/Http/Controllers/Api/Admin/SupplySourceController.php app/Http/Controllers/Api/Admin/SupplySourceController.php:318— app/Http/Controllers/Api/Admin/SupplySourceController.php changed 22 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in SupplySourceController.queueStatus at line 318. 12 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-06-11..2026-09-09, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-11 01:44:17 +07:00' --until='2026-09-09 01:44:17 +07:00' --full-history --no-merges -- app/Http/Controllers/Api/Admin/SupplySourceController.php`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: sysadmin/src/api/supply.ts sysadmin/src/api/supply.ts:282— sysadmin/src/api/supply.ts changed 13 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in supply.readSupplySchedule at line 282. 5 of those changes were fix/bug commits, and the other 8 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-06-11..2026-09-09, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-11 01:44:17 +07:00' --until='2026-09-09 01:44:17 +07:00' --full-history --no-merges -- sysadmin/src/api/supply.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: app/Jobs/SyncSupplySourceProducts.php app/Jobs/SyncSupplySourceProducts.php:64— app/Jobs/SyncSupplySourceProducts.php changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 27 in SyncSupplySourceProducts.handle at line 64. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-11..2026-09-09, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-11 01:44:17 +07:00' --until='2026-09-09 01:44:17 +07:00' --full-history --no-merges -- app/Jobs/SyncSupplySourceProducts.php`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: app/Payment/Drivers/EpayDriver.php app/Payment/Drivers/EpayDriver.php:215— app/Payment/Drivers/EpayDriver.php changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in EpayDriver.verifyCallback at line 215. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-11..2026-09-09, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-11 01:44:17 +07:00' --until='2026-09-09 01:44:17 +07:00' --full-history --no-merges -- app/Payment/Drivers/EpayDriver.php`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: app/Console/Commands/InstallCommand.php app/Console/Commands/InstallCommand.php:22— app/Console/Commands/InstallCommand.php changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in InstallCommand.handle at line 22. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-11..2026-09-09, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-11 01:44:17 +07:00' --until='2026-09-09 01:44:17 +07:00' --full-history --no-merges -- app/Console/Commands/InstallCommand.php`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: app/Http/Controllers/InstallController.php app/Http/Controllers/InstallController.php:245— app/Http/Controllers/InstallController.php changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in InstallController.run at line 245. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-11..2026-09-09, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-11 01:44:17 +07:00' --until='2026-09-09 01:44:17 +07:00' --full-history --no-merges -- app/Http/Controllers/InstallController.php`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: app/Support/CardImportService.php app/Support/CardImportService.php:92— app/Support/CardImportService.php changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in CardImportService.processChunk at line 92. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-11..2026-09-09, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-11 01:44:17 +07:00' --until='2026-09-09 01:44:17 +07:00' --full-history --no-merges -- app/Support/CardImportService.php`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: app/Http/Controllers/Api/Admin/SettingController.php app/Http/Controllers/Api/Admin/SettingController.php:28— app/Http/Controllers/Api/Admin/SettingController.php changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 22 in SettingController.update at line 28. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-11..2026-09-09, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-11 01:44:17 +07:00' --until='2026-09-09 01:44:17 +07:00' --full-history --no-merges -- app/Http/Controllers/Api/Admin/SettingController.php`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: app/Http/Controllers/Api/Admin/UserController.php app/Http/Controllers/Api/Admin/UserController.php:121— app/Http/Controllers/Api/Admin/UserController.php changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 26 in UserController.update at line 121. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-11..2026-09-09, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-11 01:44:17 +07:00' --until='2026-09-09 01:44:17 +07:00' --full-history --no-merges -- app/Http/Controllers/Api/Admin/UserController.php`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: storefront/src/views/Register.vue storefront/src/views/Register.vue:47— storefront/src/views/Register.vue changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in submit at line 47. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-11..2026-09-09, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-11 01:44:17 +07:00' --until='2026-09-09 01:44:17 +07:00' --full-history --no-merges -- storefront/src/views/Register.vue`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: app/Http/Controllers/Api/Admin/OrderController.php app/Http/Controllers/Api/Admin/OrderController.php:28— app/Http/Controllers/Api/Admin/OrderController.php changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in OrderController.buildQuery at line 28. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-11..2026-09-09, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-11 01:44:17 +07:00' --until='2026-09-09 01:44:17 +07:00' --full-history --no-merges -- app/Http/Controllers/Api/Admin/OrderController.php`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: app/Supply/SupplyOrderService.php app/Supply/SupplyOrderService.php:33— app/Supply/SupplyOrderService.php changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 23 in SupplyOrderService.createOrder at line 33. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-11..2026-09-09, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-11 01:44:17 +07:00' --until='2026-09-09 01:44:17 +07:00' --full-history --no-merges -- app/Supply/SupplyOrderService.php`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: app/Http/Middleware/SupplyAuth.php app/Http/Middleware/SupplyAuth.php:23— app/Http/Middleware/SupplyAuth.php changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in SupplyAuth.handle at line 23. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-11..2026-09-09, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-11 01:44:17 +07:00' --until='2026-09-09 01:44:17 +07:00' --full-history --no-merges -- app/Http/Middleware/SupplyAuth.php`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
D30 · Dependency Vulnerabilities· Medium CVE · ×11
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
X24 · Document value interpolated into markup unescaped· Untrusted text written into markup unescaped · ×8
Untrusted text written into markup unescaped storefront/src/components/NoticeModal.vue:63— `sanitizedNotice` is text this program did not author, and it is written into the text of an element through Vue's `v-html` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped storefront/src/components/OrderInstructions.vue:22— `sanitizedHtml` is text this program did not author, and it is written into the text of an element through Vue's `v-html` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped storefront/src/views/Product.vue:564— `sanitizedDescription` is text this program did not author, and it is written into the text of an element through Vue's `v-html` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped sysadmin/src/components/core/text-effect/art-text-scroll/index.vue:23— `sanitizedText` is text this program did not author, and it is written into the text of an element through Vue's `v-html` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped sysadmin/src/components/core/text-effect/art-text-scroll/index.vue:29— `sanitizedText` is text this program did not author, and it is written into the text of an element through Vue's `v-html` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped sysadmin/src/components/core/theme/theme-svg/index.vue:5— `svgContent` is text this program did not author, and it is written into the text of an element through Vue's `v-html` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped sysadmin/src/directives/business/highlight.ts:63— `line` is text this program did not author, and it is written into the text of an element through markup built here with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped sysadmin/src/views/update/index.vue:323— `renderMd(versionDetailData.notes)` is text this program did not author, and it is written into the text of an element through Vue's `v-html` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
MethodTooLong: OrderService.createOrder app/Support/OrderService.php:32— MethodTooLong — createOrder runs 173 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 73 over it, 1.73× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: StorefrontConfig.defaults app/Support/StorefrontConfig.php:47— MethodTooLong — defaults runs 136 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 36 over it, 1.36× 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: SupplyOrderService.createOrder app/Supply/SupplyOrderService.php:33— MethodTooLong — createOrder runs 105 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 5 over it, 1.05× 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: InstallCommand.handle app/Console/Commands/InstallCommand.php:22— MethodTooLong — handle runs 101 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 1 over it, 1.01× 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: InstallController.run app/Http/Controllers/InstallController.php:245— MethodTooLong — run runs 101 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 1 over it, 1.01× 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: SyncSupplySourceProducts.handle app/Jobs/SyncSupplySourceProducts.php:64— MethodTooLong — handle runs 101 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 1 over it, 1.01× 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.
Swallowed exception (caught, then discarded) sysadmin/src/views/user/list/index.vue:479— `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, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included.
Swallowed exception (caught, then discarded) sysadmin/src/views/update/index.vue:197— `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, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included.
Swallowed exception (caught, then discarded) sysadmin/src/views/supply/list/index.vue:1151— `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, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included.
Swallowed exception (caught, then discarded) sysadmin/src/views/supply/list/index.vue:1256— `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, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included.
Swallowed exception (caught, then discarded) sysadmin/src/views/supplierAccount/list/index.vue:272— `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, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included.
FunctionTooLong: useChart.useChart sysadmin/src/hooks/core/useChart.ts:85— FunctionTooLong — useChart runs 337 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 237 over it, 3.37× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: useTable.useTableImpl sysadmin/src/hooks/core/useTable.ts:132— FunctionTooLong — useTableImpl runs 320 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 220 over it, 3.20× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: useSettingsConfig.useSettingsConfig sysadmin/src/components/core/layouts/art-settings-panel/composables/useSettingsConfig.ts:10— FunctionTooLong — useSettingsConfig runs 144 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 44 over it, 1.44× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: useSettingsPanel.useSettingsPanel sysadmin/src/components/core/layouts/art-settings-panel/composables/useSettingsPanel.ts:17— FunctionTooLong — useSettingsPanel runs 120 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 20 over it, 1.20× 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.
Duplicated block (7 lines × 2) app/Http/Controllers/Api/SubsiteConsoleController.php:137— app/Http/Controllers/Api/SubsiteConsoleController.php:137-143 | app/Http/Controllers/Api/SubsiteConsoleController.php:158-164 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `app/Http/Controllers/Api/SubsiteConsoleController.php:137` 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) app/Payment/Drivers/OkPayDriver.php:38— app/Payment/Drivers/OkPayDriver.php:38-44 | app/Payment/Drivers/TokenPayDriver.php:38-44 — 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, `app/Payment/Drivers/OkPayDriver.php:45` calls `rtrim`, `number_format` and `app/Payment/Drivers/TokenPayDriver.php:46` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (7 lines × 2) app/Supply/Drivers/AcgFakaDriver.php:102— app/Supply/Drivers/AcgFakaDriver.php:102-110 | app/Supply/Drivers/Concerns/MakesHttpRequests.php:88-94 — 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 `app/Supply/Drivers/AcgFakaDriver.php:102` 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 (7 lines × 2) app/Http/Controllers/Api/Admin/SupplierAccountController.php:178— app/Http/Controllers/Api/Admin/SupplierAccountController.php:178-184 | app/Http/Controllers/Api/MySupplyController.php:98-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. 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 locations) storefront/src/views/Pay.vue:96— storefront/src/views/Pay.vue:96 · storefront/src/views/RechargePay.vue:113 — 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 (12 lines × 2 locations) sysadmin/src/api/cards.ts:188— sysadmin/src/api/cards.ts:188 · sysadmin/src/api/coupons.ts:79 — 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 (12 lines × 2 locations) sysadmin/src/utils/form/validator.ts:182— sysadmin/src/utils/form/validator.ts:182 · sysadmin/src/utils/form/validator.ts:244 — 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 (12 lines × 2 locations) sysadmin/src/views/supplierAccount/list/index.vue:459— sysadmin/src/views/supplierAccount/list/index.vue:459 · sysadmin/src/views/supply/list/index.vue:1911 — 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.
ClassTooLong: AcgFakaDriver app/Supply/Drivers/AcgFakaDriver.php:18— ClassTooLong — 559 significant lines (blank, comment-only and punctuation-only lines excluded), 36 methods. The bar is 400 significant lines; this is 159 over it, 1.40× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: UpdateController app/Http/Controllers/Api/Admin/UpdateController.php:27— ClassTooLong — 495 significant lines (blank, comment-only and punctuation-only lines excluded), 30 methods. The bar is 400 significant lines; this is 95 over it, 1.24× 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: OrderService app/Support/OrderService.php:19— ClassTooLong — 453 significant lines (blank, comment-only and punctuation-only lines excluded), 15 methods. The bar is 400 significant lines; this is 53 over it, 1.13× 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.
FileTooLong: Drivers/AcgFakaDriver.php app/Supply/Drivers/AcgFakaDriver.php— FileTooLong — 573 significant lines (blank, comment-only and punctuation-only lines excluded), about 98% of them inside a single declaration: AcgFakaDriver (18-1008). The bar is 500 significant lines; this is 73 over it, 1.15× 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: scripts/clean-dev.ts sysadmin/scripts/clean-dev.ts— FileTooLong — 559 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 59 over it, 1.12× 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: Admin/UpdateController.php app/Http/Controllers/Api/Admin/UpdateController.php— FileTooLong — 508 significant lines (blank, comment-only and punctuation-only lines excluded), about 97% of them inside a single declaration: UpdateController (27-1030). The bar is 500 significant lines; this is 8 over it, 1.02× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
D4 · Code Duplication· Edited copy of a member (12 corresponding lines) · ×3
Edited copy of a member (12 corresponding lines) app/Supply/Drivers/ZCardDriver.php:136— app/Supply/Drivers/ZCardDriver.php:136-154 | app/Supply/Drivers/ZCardDriver.php:159-170 — 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) app/Http/Controllers/Api/Admin/WithdrawalController.php:63— app/Http/Controllers/Api/Admin/WithdrawalController.php:63-74 | app/Http/Controllers/Api/Admin/WithdrawalController.php:79-93 — 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) app/Payment/Drivers/OkPayDriver.php:20— app/Payment/Drivers/OkPayDriver.php:20-31 | app/Payment/Drivers/TokenPayDriver.php:20-32 — 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.
Duplicated block (9 lines × 2) app/Http/Controllers/Api/Admin/UpdateController.php:178— app/Http/Controllers/Api/Admin/UpdateController.php:178-186 | app/Http/Controllers/Api/Admin/UpdateController.php:350-358 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `app/Http/Controllers/Api/Admin/UpdateController.php:178` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `app/Http/Controllers/Api/Admin/UpdateController.php:175` calls `assertGitReferenceMatches` and `app/Http/Controllers/Api/Admin/UpdateController.php:347` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9 lines × 2) app/Supply/Drivers/DujiaoNextDriver.php:105— app/Supply/Drivers/DujiaoNextDriver.php:105-113 | app/Supply/Drivers/ZCardDriver.php:98-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 both call sites, so a change lands once.
Duplicated block (9 lines × 2) app/Http/Controllers/Api/Admin/CouponController.php:88— app/Http/Controllers/Api/Admin/CouponController.php:88-96 | app/Http/Controllers/Api/Admin/WithdrawalController.php:22-30 — 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 `app/Http/Controllers/Api/Admin/CouponController.php:88` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `app/Http/Controllers/Api/Admin/WithdrawalController.php:31` calls `where`, `input` and `app/Http/Controllers/Api/Admin/CouponController.php:97` 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 (28 lines × 2 locations) storefront/src/views/Checkout.vue:453— storefront/src/views/Checkout.vue:453 · storefront/src/views/Pay.vue:50 — 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 (28 lines × 2 locations) storefront/src/views/Pay.vue:52— storefront/src/views/Pay.vue:52 · storefront/src/views/RechargePay.vue:59 — 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 (28 lines × 2 locations) storefront/src/views/Pay.vue:115— storefront/src/views/Pay.vue:115 · storefront/src/views/RechargePay.vue:126 — 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 (14 lines × 2 locations) sysadmin/src/utils/form/validator.ts:51— sysadmin/src/utils/form/validator.ts:51 · sysadmin/src/utils/form/validator.ts:81 — 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) sysadmin/src/views/card/list/index.vue:1069— sysadmin/src/views/card/list/index.vue:1069 · sysadmin/src/views/card/list/index.vue:1085 — 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 × 2 locations) sysadmin/src/views/product/list/index.vue:1237— sysadmin/src/views/product/list/index.vue:1237 · sysadmin/src/views/product/list/index.vue:1257 — 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.
AC3 · Page structure· Heading level jumps from h1 to h3 · ×2
Heading level jumps from h1 to h3 storefront/src/views/Checkout.vue:586— Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
Heading level jumps from h1 to h3 storefront/src/views/Product.vue:495— Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
D4 · Code Duplication· Edited copy of a member (4 corresponding lines) · ×2
Edited copy of a member (4 corresponding lines) app/Supply/Drivers/DujiaoNextDriver.php:78— app/Supply/Drivers/DujiaoNextDriver.php:78-84 | app/Supply/Drivers/ZCardDriver.php:77-80 — 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) app/Supply/Drivers/DujiaoNextDriver.php:187— app/Supply/Drivers/DujiaoNextDriver.php:187-190 | app/Supply/Drivers/ZCardDriver.php:175-178 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (8 corresponding lines) · ×2
Edited copy of a member (8 corresponding lines) app/Support/SubsiteWithdrawalService.php:69— app/Support/SubsiteWithdrawalService.php:69-76 | app/Support/SubsiteWithdrawalService.php:81-89 — 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) app/Http/Controllers/Api/SubsiteConsoleController.php:53— app/Http/Controllers/Api/SubsiteConsoleController.php:53-60 | app/Http/Controllers/Api/SubsiteConsoleController.php:174-181 — 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.
Duplicated block (19 lines × 2) app/Http/Controllers/Api/Admin/SupplierPriceController.php:31— app/Http/Controllers/Api/Admin/SupplierPriceController.php:31-49 | app/Http/Controllers/Api/Admin/SupplierPriceController.php:73-91 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (19 lines × 2) app/Payment/Drivers/BEpusdtDriver.php:86— app/Payment/Drivers/BEpusdtDriver.php:86-104 | app/Payment/Drivers/EpuSdtDriver.php:68-86 — 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–8 lines × 2) app/Http/Controllers/Api/Admin/BillController.php:22— app/Http/Controllers/Api/Admin/BillController.php:22-29 | app/Http/Controllers/Api/Admin/WithdrawalController.php: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. Read the line range as the matched WINDOW rather than a finished unit: at `app/Http/Controllers/Api/Admin/BillController.php:22` 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–8 lines × 2) app/Http/Controllers/Api/Admin/MigrationController.php:258— app/Http/Controllers/Api/Admin/MigrationController.php:258-264 | app/Support/CardCipher.php:117-124 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. 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 (8 lines × 2) app/Payment/Drivers/CodePayDriver.php:19— app/Payment/Drivers/CodePayDriver.php:19-26 | app/Payment/Drivers/EpayDriver.php:50-57 — 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 (8 lines × 2) app/Supply/Drivers/ZCardDriver.php:145— app/Supply/Drivers/ZCardDriver.php:145-152 | app/Supply/Drivers/ZCardDriver.php:161-168 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) app/Http/Controllers/Api/ProductController.php:44— app/Http/Controllers/Api/ProductController.php:44-48 | app/Http/Controllers/Api/ProductController.php:109-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 `app/Http/Controllers/Api/ProductController.php:44` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) app/Http/Controllers/Api/Supply/SupplyOrderController.php:61— app/Http/Controllers/Api/Supply/SupplyOrderController.php:61-65 | app/Http/Controllers/Api/Supply/SupplyOrderController.php:92-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.
R10 · Code Duplication· Duplicated block with local edits (43 matched lines × 2 locations) · ×2
Duplicated block with local edits (43 matched lines × 2 locations) sysadmin/src/views/commission/list/index.vue:18— sysadmin/src/views/commission/list/index.vue:18 · sysadmin/src/views/review/list/index.vue:18 — the two spans are one implementation copied and then locally edited — 389 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block with local edits (43 matched lines × 2 locations) sysadmin/src/views/coupon/list/index.vue:8— sysadmin/src/views/coupon/list/index.vue:8 · sysadmin/src/views/withdrawal/list/index.vue:11 — the two spans are one implementation copied and then locally edited — 556 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) storefront/src/views/ForgetPassword.vue:10— storefront/src/views/ForgetPassword.vue:10 · storefront/src/views/Register.vue:12 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of MODULE-LEVEL DECLARATIONS — bindings the module declares and exports — rather than statements with a call site. Do not read this as an extract-a-helper row: a call expression cannot stand where a declaration was, and putting one there would delete the names themselves, which are what the rest of the codebase imports. What actually repeats here is the INITIALISER — the same expression shape written once per binding. So give that expression one name (a small helper the initialisers call, or a shared base value they are each derived from) and keep every binding under the name it already has. Where the run is an enumeration — one binding per distinct thing, differing precisely in the thing each one names — the repetition IS the enumeration and collapsing it would delete entries; consider instead whether the set belongs in one exported table the individual names are read out of. Reported because the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2 locations) storefront/src/views/Pay.vue:28— storefront/src/views/Pay.vue:28 · storefront/src/views/RechargePay.vue:37 — 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.
Complex function (anonymous) (cyclomatic 18, cognitive 23) sysadmin/src/components/core/forms/art-form/index.vue:364— (anonymous) has cyclomatic complexity 18 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 18, cognitive 23) sysadmin/src/components/core/forms/art-search-bar/index.vue:360— (anonymous) has cyclomatic complexity 18 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.
Dead file (~6 LoC) storefront/src/stores/index.ts— no import path from any entry point (38 application, 12 tooling, 29 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 (~6 LoC) sysadmin/src/plugins/index.ts— no import path from any entry point (38 application, 12 tooling, 29 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
X2 · Cancellation propagation· Async function without AbortSignal · ×2
Async function without AbortSignal: exportCards sysadmin/src/api/cards.ts:183— `exportCards` awaits `axios.get(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `axios.get(url, { signal })`.
Async function without AbortSignal: exportCoupons sysadmin/src/api/coupons.ts:72— `exportCoupons` awaits `axios.get(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `axios.get(url, { signal })`.
AC1 · Text alternatives· <canvas> without a text alternative · ×1
<canvas> without a text alternative sysadmin/src/components/core/layouts/art-fireworks-effect/index.vue:3— A <canvas> with no aria-label/title and no inner fallback content can't be described by assistive tech. Add a name or fallback content.
OrderService.createOrder (cyclomatic 54) app/Support/OrderService.php:32— OrderService.createOrder has cyclomatic complexity 54 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This file is where this pass's cyclomatic complexity CONCENTRATES: app/Support/OrderService.php holds 2 of the 24 methods over the threshold — including the worst — and 53 of the 167 points over it (32%), 3.8× the next-largest file (app/Supply/Drivers/AcgFakaDriver.php at 14). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
OrderService.validateControlValues (cyclomatic 29) app/Support/OrderService.php:296— OrderService.validateControlValues has cyclomatic complexity 29 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This file is where this pass's cyclomatic complexity CONCENTRATES: app/Support/OrderService.php holds 2 of the 24 methods over the threshold — including the worst — and 53 of the 167 points over it (32%), 3.8× the next-largest file (app/Supply/Drivers/AcgFakaDriver.php at 14). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
MigrationController.preflight (cyclomatic 28) app/Http/Controllers/Api/Admin/MigrationController.php:28— MigrationController.preflight has cyclomatic complexity 28 (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.
SyncSupplySourceProducts.handle (cyclomatic 27) app/Jobs/SyncSupplySourceProducts.php:64— SyncSupplySourceProducts.handle 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.
UserController.update (cyclomatic 26) app/Http/Controllers/Api/Admin/UserController.php:121— UserController.update has cyclomatic complexity 26 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AcgFakaDriver.fillMissingStocks (cyclomatic 24) app/Supply/Drivers/AcgFakaDriver.php:177— AcgFakaDriver.fillMissingStocks 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.
SupplyOrderService.createOrder (cyclomatic 23) app/Supply/SupplyOrderService.php:33— SupplyOrderService.createOrder 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.
SettingController.update (cyclomatic 22) app/Http/Controllers/Api/Admin/SettingController.php:28— SettingController.update has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
SupplySyncService.upsertProduct (cyclomatic 22) app/Supply/SupplySyncService.php:43— SupplySyncService.upsertProduct has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
useTable.useTableImpl.fetchData (cyclomatic 21) sysadmin/src/hooks/core/useTable.ts:279— useTable.useTableImpl.fetchData 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.
token (cyclomatic 21) public/admin/assets/forth-POgR1ypr.js:1— token 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.
EpayDriver.verifyCallback (cyclomatic 20) app/Payment/Drivers/EpayDriver.php:215— EpayDriver.verifyCallback has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AcgFakaDriver.mapControls (cyclomatic 20) app/Supply/Drivers/AcgFakaDriver.php:869— AcgFakaDriver.mapControls has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CardImportService.processChunk (cyclomatic 20) app/Support/CardImportService.php:92— CardImportService.processChunk has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
SupplyAuth.handle (cyclomatic 19) app/Http/Middleware/SupplyAuth.php:23— SupplyAuth.handle 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.
InstallCommand.handle (cyclomatic 18) app/Console/Commands/InstallCommand.php:22— InstallCommand.handle 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.
useTable.useTableImpl (cyclomatic 18) sysadmin/src/hooks/core/useTable.ts:132— useTable.useTableImpl has cyclomatic complexity 18 (threshold 15). Of this number, 12 points are the body's own statements and 6 belong to 5 function literals inside it that branch. 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.
PaymentUrlGenerator.named (cyclomatic 17) app/Payment/PaymentUrlGenerator.php:16— PaymentUrlGenerator.named 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.
StorefrontConfig.setMany (cyclomatic 17) app/Support/StorefrontConfig.php:358— StorefrontConfig.setMany 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.
supply.readSupplySchedule (cyclomatic 17) sysadmin/src/api/supply.ts:282— supply.readSupplySchedule has cyclomatic complexity 17 (threshold 15). Of this number, 11 points are the body's own statements and 6 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.
OrderController.buildQuery (cyclomatic 16) app/Http/Controllers/Api/Admin/OrderController.php:28— OrderController.buildQuery 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.
SupplySourceController.queueStatus (cyclomatic 16) app/Http/Controllers/Api/Admin/SupplySourceController.php:318— SupplySourceController.queueStatus 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.
UpdateController.rollback (cyclomatic 16) app/Http/Controllers/Api/Admin/UpdateController.php:269— UpdateController.rollback 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.
InstallController.run (cyclomatic 16) app/Http/Controllers/InstallController.php:245— InstallController.run 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.
OrderService.createOrder (cognitive 75) app/Support/OrderService.php:32— OrderService.createOrder has cognitive complexity 75 (threshold 15). Drivers by points: if/else 26 (41 pts), ternaries 14 (18 pts), boolean chains 13, loops 1 (3 pts) (nesting depth added 21). 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.
OrderService.validateControlValues (cognitive 60) app/Support/OrderService.php:296— OrderService.validateControlValues has cognitive complexity 60 (threshold 15). Drivers by points: if/else 13 (31 pts), ternaries 7 (19 pts), boolean chains 6, loops 2 (4 pts) (nesting depth added 32). 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.
AcgFakaDriver.fillMissingStocks (cognitive 50) app/Supply/Drivers/AcgFakaDriver.php:177— AcgFakaDriver.fillMissingStocks has cognitive complexity 50 (threshold 15). Drivers by points: if/else 9 (20 pts), ternaries 5 (15 pts), loops 5 (8 pts), error handling 1 (4 pts), boolean chains 3 (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.
SyncSupplySourceProducts.handle (cognitive 42) app/Jobs/SyncSupplySourceProducts.php:64— SyncSupplySourceProducts.handle has cognitive complexity 42 (threshold 15). Drivers by points: if/else 13 (26 pts), boolean chains 7, ternaries 3 (4 pts), loops 2 (3 pts), error handling 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.
MigrationController.preflight (cognitive 38) app/Http/Controllers/Api/Admin/MigrationController.php:28— MigrationController.preflight has cognitive complexity 38 (threshold 15). Drivers by points: ternaries 9 (15 pts), if/else 6 (9 pts), error handling 5 (7 pts), loops 3 (4 pts), boolean chains 2, match/switch 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AcgFakaDriver.probeStockQuery (cognitive 37) app/Supply/Drivers/AcgFakaDriver.php:418— AcgFakaDriver.probeStockQuery has cognitive complexity 37 (threshold 15). Drivers by points: if/else 8 (25 pts), ternaries 1 (4 pts), error handling 1 (3 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 23). 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.
SupplySyncService.upsertProduct (cognitive 35) app/Supply/SupplySyncService.php:43— SupplySyncService.upsertProduct has cognitive complexity 35 (threshold 15). Drivers by points: if/else 10 (20 pts), ternaries 4 (8 pts), boolean chains 6, error handling 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.
UserController.update (cognitive 34) app/Http/Controllers/Api/Admin/UserController.php:121— UserController.update has cognitive complexity 34 (threshold 15). Drivers by points: ternaries 10 (13 pts), if/else 7 (11 pts), boolean chains 6, error handling 1 (2 pts), loops 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.
StorefrontConfig.setMany (cognitive 33) app/Support/StorefrontConfig.php:358— StorefrontConfig.setMany has cognitive complexity 33 (threshold 15). Drivers by points: if/else 6 (14 pts), ternaries 3 (12 pts), boolean chains 6, 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.
AcgFakaDriver.mapControls (cognitive 32) app/Supply/Drivers/AcgFakaDriver.php:869— AcgFakaDriver.mapControls has cognitive complexity 32 (threshold 15). Drivers by points: if/else 6 (12 pts), ternaries 6 (12 pts), boolean chains 5, loops 2 (3 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CardImportService.processChunk (cognitive 32) app/Support/CardImportService.php:92— CardImportService.processChunk has cognitive complexity 32 (threshold 15). Drivers by points: if/else 10 (20 pts), ternaries 4 (7 pts), boolean chains 3, loops 2 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ThirdPartyScript.normalizeHosts (cognitive 28) app/Support/ThirdPartyScript.php:179— ThirdPartyScript.normalizeHosts has cognitive complexity 28 (threshold 15). Drivers by points: if/else 6 (16 pts), ternaries 3 (6 pts), loops 2 (5 pts), boolean chains 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.
useTable.useTableImpl.fetchData (cognitive 28) sysadmin/src/hooks/core/useTable.ts:279— useTable.useTableImpl.fetchData has cognitive complexity 28 (threshold 15). Drivers by points: if/else 15 (23 pts), boolean chains 4, 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.
token (cognitive 27) public/admin/assets/forth-POgR1ypr.js:1— token has cognitive complexity 27 (threshold 15). Drivers by points: if/else 10 (17 pts), ternaries 9, boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
clean-dev.cleanLanguageFiles (cognitive 26) sysadmin/scripts/clean-dev.ts:430— clean-dev.cleanLanguageFiles has cognitive complexity 26 (threshold 15). Drivers by points: if/else 7 (23 pts), error handling 1 (2 pts), loops 1 (nesting depth added 17). Of this number, 19 points are the body's own statements and 7 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SettingController.update (cognitive 25) app/Http/Controllers/Api/Admin/SettingController.php:28— SettingController.update has cognitive complexity 25 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 9, ternaries 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.
EpayDriver.verifyCallback (cognitive 25) app/Payment/Drivers/EpayDriver.php:215— EpayDriver.verifyCallback has cognitive complexity 25 (threshold 15). Drivers by points: if/else 12 (17 pts), boolean chains 7, loops 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.
AcgFakaDriver.mapSkus (cognitive 25) app/Supply/Drivers/AcgFakaDriver.php:748— AcgFakaDriver.mapSkus has cognitive complexity 25 (threshold 15). Drivers by points: if/else 6 (13 pts), loops 4 (8 pts), boolean chains 2, ternaries 2 (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.
SupplyOrderService.createOrder (cognitive 25) app/Supply/SupplyOrderService.php:33— SupplyOrderService.createOrder has cognitive complexity 25 (threshold 15). Drivers by points: if/else 11 (15 pts), ternaries 4, boolean chains 3, loops 1 (2 pts), error handling 1 (nesting depth added 5). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
InstallCommand.handle (cognitive 24) app/Console/Commands/InstallCommand.php:22— InstallCommand.handle has cognitive complexity 24 (threshold 15). Drivers by points: if/else 12 (14 pts), ternaries 2 (5 pts), boolean chains 3, error handling 1, loops 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.
AcgFakaDriver.parseConfig (cognitive 24) app/Supply/Drivers/AcgFakaDriver.php:820— AcgFakaDriver.parseConfig has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (18 pts), loops 2 (3 pts), boolean chains 2, ternaries 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.
SupplySourceController.importProducts (cognitive 20) app/Http/Controllers/Api/Admin/SupplySourceController.php:460— SupplySourceController.importProducts has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (13 pts), error handling 2 (4 pts), boolean chains 1, loops 1, 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.
InstallController.isPublicDbHost (cognitive 20) app/Http/Controllers/InstallController.php:109— InstallController.isPublicDbHost has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (10 pts), loops 3 (5 pts), ternaries 2 (4 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.
SupplyAuth.handle (cognitive 20) app/Http/Middleware/SupplyAuth.php:23— SupplyAuth.handle has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (10 pts), boolean chains 6, ternaries 2 (3 pts), error handling 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
PaymentUrlGenerator.named (cognitive 20) app/Payment/PaymentUrlGenerator.php:16— PaymentUrlGenerator.named has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 6, ternaries 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
tableUtils.extractPagination (cognitive 20) sysadmin/src/utils/table/tableUtils.ts:78— tableUtils.extractPagination has cognitive complexity 20 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 4 (6 pts), boolean chains 3 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
UpdateController.rollback (cognitive 19) app/Http/Controllers/Api/Admin/UpdateController.php:269— UpdateController.rollback has cognitive complexity 19 (threshold 15). Drivers by points: error handling 5 (7 pts), if/else 6 (7 pts), ternaries 2 (3 pts), boolean chains 2 (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.
OkPayDriver.verifyCallback (cognitive 18) app/Payment/Drivers/OkPayDriver.php:74— OkPayDriver.verifyCallback has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (8 pts), loops 2 (4 pts), boolean chains 3, ternaries 3 (nesting depth added 3). 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.
ThirdPartyScript.compile (cognitive 18) app/Support/ThirdPartyScript.php:31— ThirdPartyScript.compile has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (16 pts), loops 1, 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.
OrderService.batchCreate (cognitive 17) app/Support/OrderService.php:378— OrderService.batchCreate has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (9 pts), boolean chains 3, error handling 1 (2 pts), ternaries 1 (2 pts), loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
supply.readSupplySchedule (cognitive 17) sysadmin/src/api/supply.ts:282— supply.readSupplySchedule has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 7, ternaries 6, if/else 3 (4 pts) (nesting depth added 1). Of this number, 11 points are the body's own statements and 6 belong to one function item inside it that branches. 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.
SupplyScheduledSyncCommand.handle (cognitive 16) app/Console/Commands/SupplyScheduledSyncCommand.php:30— SupplyScheduledSyncCommand.handle has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (10 pts), loops 2 (3 pts), ternaries 1 (3 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SupplySourceController.previewProducts (cognitive 16) app/Http/Controllers/Api/Admin/SupplySourceController.php:375— SupplySourceController.previewProducts has cognitive complexity 16 (threshold 15). Drivers by points: if/else 3 (5 pts), loops 4, ternaries 2 (4 pts), error handling 2, boolean chains 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ProductController.transform (cognitive 16) app/Http/Controllers/Api/ProductController.php:142— ProductController.transform has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 7 (12 pts), if/else 3 (4 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.
InstallController.run (cognitive 16) app/Http/Controllers/InstallController.php:245— InstallController.run has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10, error handling 3, boolean chains 2, loops 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.
CallbackUrlGuard.ipInCidr (cognitive 16) app/Supply/CallbackUrlGuard.php:155— CallbackUrlGuard.ipInCidr has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (9 pts), boolean chains 5, loops 1 (2 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AcgFakaDriver.productUrl (cognitive 16) app/Supply/Drivers/AcgFakaDriver.php:928— AcgFakaDriver.productUrl has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (7 pts), ternaries 2 (5 pts), error handling 1 (3 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
coupons.exportCoupons (cognitive 16) sysadmin/src/api/coupons.ts:72— coupons.exportCoupons has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (9 pts), error handling 2 (4 pts), boolean chains 2, 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.
useTable.useTableImpl (cognitive 16) sysadmin/src/hooks/core/useTable.ts:132— useTable.useTableImpl has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 7, if/else 7, ternaries 2. Of this number, 11 points are the body's own statements and 5 belong to 5 function literals inside it that branch. 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.
WebSocketClient.flushMessageQueue (cognitive 16) sysadmin/src/utils/socket/index.ts:172— WebSocketClient.flushMessageQueue has cognitive complexity 16 (threshold 15). Drivers by points: if/else 3 (9 pts), error handling 1 (4 pts), loops 1 (2 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.
TooManyMethods: AcgFakaDriver app/Supply/Drivers/AcgFakaDriver.php:18— TooManyMethods — 36 methods. The bar is 30 methods; this is 6 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.
D30 · Dependency Vulnerabilities· Medium vulnerability · ×1
D4 · Code Duplication· Edited copy of a member (42 corresponding lines) · ×1
Edited copy of a member (42 corresponding lines) app/Payment/Drivers/BEpusdtDriver.php:55— app/Payment/Drivers/BEpusdtDriver.php:55-104 | app/Payment/Drivers/EpuSdtDriver.php:45-86 — These two members are one piece of code written twice and then edited apart: 42 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 (55 corresponding lines) · ×1
Edited copy of a member (55 corresponding lines) app/Http/Controllers/Api/OrderController.php:23— app/Http/Controllers/Api/OrderController.php:23-77 | app/Http/Controllers/Api/OrderController.php:119-182 — These two members are one piece of code written twice and then edited apart: 55 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) app/Http/Controllers/Api/Admin/DashboardController.php:95— app/Http/Controllers/Api/Admin/DashboardController.php:95-133 | app/Http/Controllers/Api/Admin/DashboardController.php:146-170 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 21+ corresponding lines) · ×1
Edited copies of one member (4 members, 21+ corresponding lines) app/Http/Controllers/Api/Admin/BillController.php:18— app/Http/Controllers/Api/Admin/BillController.php:18-47 | app/Http/Controllers/Api/Admin/CouponController.php:83-103 | app/Http/Controllers/Api/Admin/RechargeController.php:21-49 | app/Http/Controllers/Api/Admin/WithdrawalController.php:16-41 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 21 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (18 corresponding lines) · ×1
Edited copy of a member (18 corresponding lines) app/Supply/Drivers/Concerns/MakesHttpRequests.php:58— app/Supply/Drivers/Concerns/MakesHttpRequests.php:58-77 | app/Supply/Drivers/Concerns/MakesHttpRequests.php:82-99 — 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, 19+ corresponding lines) · ×1
Edited copies of one member (3 members, 19+ corresponding lines) app/Http/Controllers/Api/ReviewController.php:21— app/Http/Controllers/Api/ReviewController.php:21-45 | app/Http/Controllers/Api/SubsiteConsoleController.php:210-228 | app/Http/Controllers/Api/WithdrawalController.php:17-37 — 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 (14 corresponding lines) · ×1
Edited copy of a member (14 corresponding lines) app/Http/Controllers/Api/Admin/ReviewController.php:19— app/Http/Controllers/Api/Admin/ReviewController.php:19-32 | app/Http/Controllers/Api/CardController.php:24-38 — 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 copies of one member (3 members, 9+ corresponding lines) · ×1
Edited copies of one member (3 members, 9+ corresponding lines) app/Http/Controllers/Api/Admin/MediaCategoryController.php:24— app/Http/Controllers/Api/Admin/MediaCategoryController.php:24-32 | app/Http/Controllers/Api/Admin/MediaCategoryController.php:38-46 | app/Http/Controllers/Api/Admin/MediaCategoryController.php:64-72 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (10 corresponding lines) · ×1
Edited copy of a member (10 corresponding lines) app/Payment/Drivers/BEpusdtDriver.php:37— app/Payment/Drivers/BEpusdtDriver.php:37-50 | app/Payment/Drivers/EpuSdtDriver.php:31-40 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (11 corresponding lines) · ×1
Edited copy of a member (11 corresponding lines) app/Http/Middleware/RequireActiveUser.php:14— app/Http/Middleware/RequireActiveUser.php:14-26 | app/Http/Middleware/RequireAdminRole.php:19-29 — 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 copies of one member (3 members, 3+ corresponding lines) · ×1
Edited copies of one member (3 members, 3+ corresponding lines) app/Http/Controllers/Api/Admin/CardController.php:213— app/Http/Controllers/Api/Admin/CardController.php:213-218 | app/Http/Controllers/Api/Admin/CouponController.php:17-19 | app/Http/Controllers/Api/Admin/SupplierAccountController.php:171-173 — These 3 members are one piece of code written 3 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 3 times and the copies will drift further apart.
Duplicated block (29 lines × 2) app/Http/Controllers/Api/OrderController.php:23— app/Http/Controllers/Api/OrderController.php:23-51 | app/Http/Controllers/Api/OrderController.php:119-147 — 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 `app/Http/Controllers/Api/OrderController.php:23` 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 (23–28 lines × 2) app/Http/Controllers/Api/OrderController.php:55— app/Http/Controllers/Api/OrderController.php:55-77 | app/Http/Controllers/Api/OrderController.php:149-176 — 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 `app/Http/Controllers/Api/OrderController.php:55` 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. 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 (25 lines × 2) app/Payment/Drivers/BEpusdtDriver.php:109— app/Payment/Drivers/BEpusdtDriver.php:109-133 | app/Payment/Drivers/EpuSdtDriver.php:91-115 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (19–21 lines × 2) app/Support/PaymentService.php:296— app/Support/PaymentService.php:296-316 | app/Support/PaymentService.php:369-387 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `app/Support/PaymentService.php:295` calls `lockForUpdate` and `app/Support/PaymentService.php:368` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (18–19 lines × 2) app/Http/Controllers/Api/Admin/UpdateController.php:244— app/Http/Controllers/Api/Admin/UpdateController.php:244-262 | app/Http/Controllers/Api/Admin/UpdateController.php:399-416 — 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 `app/Http/Controllers/Api/Admin/UpdateController.php:244` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `app/Http/Controllers/Api/Admin/UpdateController.php:243` calls `log` and `app/Http/Controllers/Api/Admin/UpdateController.php:398` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (16 lines × 2) app/Console/Commands/InstallCommand.php:341— app/Console/Commands/InstallCommand.php:341-356 | app/Http/Controllers/InstallController.php:452-467 — 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 `app/Console/Commands/InstallCommand.php:341` 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 (14–15 lines × 2) app/Http/Controllers/Api/Admin/DashboardController.php:102— app/Http/Controllers/Api/Admin/DashboardController.php:102-116 | app/Http/Controllers/Api/Admin/DashboardController.php:149-162 — 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 `app/Http/Controllers/Api/Admin/DashboardController.php: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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `app/Http/Controllers/Api/Admin/DashboardController.php:100` calls `raw`, `COUNT` and `app/Http/Controllers/Api/Admin/DashboardController.php:149` 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 (4–14 lines × 3) app/Http/Controllers/Api/Admin/ProductController.php:62— app/Http/Controllers/Api/Admin/ProductController.php:62-65 | app/Http/Controllers/Api/ProductController.php:52-65 | app/Http/Controllers/Api/ProductController.php:117-130 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `app/Http/Controllers/Api/Admin/ProductController.php:62` 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `app/Http/Controllers/Api/ProductController.php:51` calls `orWhere`, `where`, `whereNotNull` and `app/Http/Controllers/Api/Admin/ProductController.php:62` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9–11 lines × 4) app/Http/Controllers/Api/Admin/BillController.php:33— app/Http/Controllers/Api/Admin/BillController.php:33-42 | app/Http/Controllers/Api/Admin/BillController.php:59-67 | app/Http/Controllers/Api/Admin/RechargeController.php:37-47 | app/Http/Controllers/Api/Admin/WithdrawalController.php:30-38 — there are 4 copies across 3 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (11 lines × 2) app/Supply/CallbackUrlGuard.php:83— app/Supply/CallbackUrlGuard.php:83-93 | app/Support/DomainVerificationService.php:152-162 — 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 (9–10 lines × 2) app/Supply/Drivers/AcgFakaDriver.php:373— app/Supply/Drivers/AcgFakaDriver.php:373-381 | app/Supply/Drivers/AcgFakaDriver.php:424-433 — 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 `app/Supply/Drivers/AcgFakaDriver.php:373` 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–9 lines × 3) app/Http/Controllers/Api/Admin/BillController.php:29— app/Http/Controllers/Api/Admin/BillController.php:29-37 | app/Http/Controllers/Api/Admin/BillController.php:56-62 | app/Http/Controllers/Api/Admin/CommissionController.php:39-45 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `app/Http/Controllers/Api/Admin/BillController.php:29` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) app/Support/PaymentService.php:80— app/Support/PaymentService.php:80-85 | app/Support/PaymentService.php:202-207 — 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.
Duplication concentrated across 18 sibling directories (32 clone groups) sysadmin/src/views/category/list/index.vue:89— 32 duplicated blocks under sysadmin/src/views/ have copies in at least two of the sibling directories bill, card, category, commission, coupon, currency (+12 more sibling(s) not listed) — 23 of them are reported below, and 9 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 32 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 32 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 32 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 8 sibling directories (10 clone groups) sysadmin/src/components/core/charts/art-bar-chart/index.vue:7— 10 duplicated blocks under sysadmin/src/components/core/charts/ have copies in at least two of the sibling directories art-bar-chart, art-dual-bar-compare-chart, art-h-bar-chart, art-k-line-chart, art-line-chart, art-radar-chart (+2 more sibling(s) not listed) — 7 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 10 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 10 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 10 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 2 sibling directories (6 clone groups) storefront/src/api/distribution.ts:10— 6 duplicated blocks under the repository root have copies in at least two of the sibling directories storefront, sysadmin — 2 of them are reported below, and 4 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 6 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 6 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 6 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication· Duplicated block with local edits (160 matched lines × 2 locations) · ×1
Duplicated block with local edits (160 matched lines × 2 locations) sysadmin/src/components/core/forms/art-form/index.vue:123— sysadmin/src/components/core/forms/art-form/index.vue:123 · sysadmin/src/components/core/forms/art-search-bar/index.vue:130 — the two spans are one implementation copied and then locally edited — 1039 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.
Wholesale file copy (94 identical lines × 2 files) sysadmin/src/components/core/charts/art-bar-chart/index.vue:7— sysadmin/src/components/core/charts/art-bar-chart/index.vue:7 · sysadmin/src/components/core/charts/art-h-bar-chart/index.vue:12 — these 2 files are line-for-line copies of one another — 94 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication· Duplicated block with local edits (63 matched lines × 2 locations) · ×1
Duplicated block with local edits (63 matched lines × 2 locations) sysadmin/src/views/category/list/index.vue:89— sysadmin/src/views/category/list/index.vue:89 · sysadmin/src/views/currency/list/index.vue:70 — the two spans are one implementation copied and then locally edited — 406 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (56 matched lines × 2 locations) · ×1
Duplicated block with local edits (56 matched lines × 2 locations) storefront/src/views/MySubsite.vue:52— storefront/src/views/MySubsite.vue:52 · storefront/src/views/Withdraw.vue:29 — the two spans are one implementation copied and then locally edited — 389 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (55 matched lines × 2 locations) · ×1
Duplicated block with local edits (55 matched lines × 2 locations) storefront/src/views/Login.vue:11— storefront/src/views/Login.vue:11 · storefront/src/views/Register.vue:10 — the two spans are one implementation copied and then locally edited — 398 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 (37 lines × 2 locations) sysadmin/src/views/card/list/index.vue:713— sysadmin/src/views/card/list/index.vue:713 · sysadmin/src/views/card/list/index.vue:821 — 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 (35 lines × 2 locations) sysadmin/src/views/product/list/index.vue:1920— sysadmin/src/views/product/list/index.vue:1920 · sysadmin/src/views/user/list/index.vue:500 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
R10 · Code Duplication· Duplicated block with local edits (26 matched lines × 2 locations) · ×1
Duplicated block with local edits (26 matched lines × 2 locations) sysadmin/src/views/currency/list/index.vue:13— sysadmin/src/views/currency/list/index.vue:13 · sysadmin/src/views/subsite/list/index.vue:14 — the two spans are one implementation copied and then locally edited — 163 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 (24 lines × 2 locations) sysadmin/src/components/core/layouts/art-global-search/index.vue:236— sysadmin/src/components/core/layouts/art-global-search/index.vue:236 · sysadmin/src/components/core/layouts/art-global-search/index.vue:261 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (22 lines × 2 locations) sysadmin/scripts/clean-dev.ts:87— sysadmin/scripts/clean-dev.ts:87 · sysadmin/scripts/clean-dev.ts:735 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
R10 · Code Duplication· Duplicated block with local edits (22 matched lines × 2 locations) · ×1
Duplicated block with local edits (22 matched lines × 2 locations) sysadmin/src/components/core/charts/art-dual-bar-compare-chart/index.vue:79— sysadmin/src/components/core/charts/art-dual-bar-compare-chart/index.vue:79 · sysadmin/src/components/core/charts/art-k-line-chart/index.vue:40 — the two spans are one implementation copied and then locally edited — 55 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 (21 lines × 2 locations) sysadmin/src/hooks/core/useLayoutHeight.ts:34— sysadmin/src/hooks/core/useLayoutHeight.ts:34 · sysadmin/src/hooks/core/useLayoutHeight.ts:88 — 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 (20 lines × 2 locations) sysadmin/src/components/core/cards/art-bar-chart-card/index.vue:59— sysadmin/src/components/core/cards/art-bar-chart-card/index.vue:59 · sysadmin/src/components/core/cards/art-line-chart-card/index.vue:62 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication· Duplicated block with local edits (18 matched lines × 2 locations) · ×1
Duplicated block with local edits (18 matched lines × 2 locations) sysadmin/src/views/order/list/index.vue:425— sysadmin/src/views/order/list/index.vue:425 · sysadmin/src/views/supply/list/index.vue:988 — the two spans are one implementation copied and then locally edited — 69 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 (17 lines × 2 locations) sysadmin/src/views/card/list/index.vue:860— sysadmin/src/views/card/list/index.vue:860 · sysadmin/src/views/coupon/list/index.vue:66 — 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 (16 lines × 2 locations) sysadmin/src/views/bill/list/index.vue:37— sysadmin/src/views/bill/list/index.vue:37 · sysadmin/src/views/withdrawal/list/index.vue:46 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication· Duplicated block with local edits (16 matched lines × 2 locations) · ×1
Duplicated block with local edits (16 matched lines × 2 locations) sysadmin/src/views/order/list/index.vue:429— sysadmin/src/views/order/list/index.vue:429 · sysadmin/src/views/user/list/index.vue:333 — the two spans are one implementation copied and then locally edited — 62 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 (15 lines × 2 locations) sysadmin/src/views/subsite/list/index.vue:120— sysadmin/src/views/subsite/list/index.vue:120 · sysadmin/src/views/subsite/list/index.vue: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.
R10 · Code Duplication· Duplicated block with local edits (14 matched lines × 2 locations) · ×1
Duplicated block with local edits (14 matched lines × 2 locations) sysadmin/src/views/card/list/index.vue:655— sysadmin/src/views/card/list/index.vue:655 · sysadmin/src/views/supply/list/index.vue:986 — the two spans are one implementation copied and then locally edited — 60 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 (13 lines × 3 locations) sysadmin/src/components/core/charts/art-bar-chart/index.vue:128— sysadmin/src/components/core/charts/art-bar-chart/index.vue:128 · sysadmin/src/components/core/charts/art-h-bar-chart/index.vue:132 · sysadmin/src/components/core/charts/art-line-chart/index.vue:311 — the 3 copies are spread across 3 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete.
Duplicated block (13 lines × 2 locations) sysadmin/src/views/subsite/list/index.vue:173— sysadmin/src/views/subsite/list/index.vue:173 · sysadmin/src/views/subsite/list/index.vue:196 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication· Duplicated block with local edits (12 matched lines × 2 locations) · ×1
Duplicated block with local edits (12 matched lines × 2 locations) storefront/src/components/ServiceWidget.vue:36— storefront/src/components/ServiceWidget.vue:36 · storefront/src/components/SiteAnalytics.vue:29 — the two spans are one implementation copied and then locally edited — 54 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 × 3 locations) storefront/src/views/ForgetPassword.vue:30— storefront/src/views/ForgetPassword.vue:30 · storefront/src/views/Login.vue:27 · storefront/src/views/Register.vue:32 — the 3 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete.
Complex function openEdit (cyclomatic 40, cognitive 38) sysadmin/src/views/product/list/index.vue:1756— openEdit has cyclomatic complexity 40 and cognitive complexity 38; 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 doSubmit (cyclomatic 22, cognitive 29) storefront/src/views/Checkout.vue:352— doSubmit has cyclomatic complexity 22 and cognitive complexity 29; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function loadSingle (cyclomatic 22, cognitive 21) storefront/src/views/Checkout.vue:151— loadSingle has cyclomatic complexity 22 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 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 21, cognitive 28) sysadmin/src/hooks/core/useTable.ts:282— (anonymous) has cyclomatic complexity 21 and cognitive complexity 28; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function token (cyclomatic 21, cognitive 27) public/admin/assets/forth-POgR1ypr.js:1— token has cyclomatic complexity 21 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 handleSubmit (cyclomatic 18, cognitive 17) sysadmin/src/views/product/list/index.vue:1861— handleSubmit has cyclomatic complexity 18 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function loadSettings (cyclomatic 18, cognitive 13) sysadmin/src/views/setting/index.vue:887— loadSettings has cyclomatic complexity 18 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function loadAll (cyclomatic 16, cognitive 27) storefront/src/views/MySubsite.vue:97— loadAll has cyclomatic complexity 16 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 submit (cyclomatic 16, cognitive 17) storefront/src/views/Checkout.vue:317— submit has cyclomatic complexity 16 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function submit (cyclomatic 16, cognitive 16) storefront/src/views/Register.vue:47— submit has cyclomatic complexity 16 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 extractPagination (cyclomatic 14, cognitive 21) sysadmin/src/utils/table/tableUtils.ts:78— extractPagination has cyclomatic complexity 14 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function loadAll (cyclomatic 14, cognitive 17) sysadmin/src/views/dashboard/console/index.vue:612— loadAll has cyclomatic complexity 14 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function handleSubmit (cyclomatic 14, cognitive 13) sysadmin/src/views/user/list/index.vue:475— handleSubmit has cyclomatic complexity 14 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 14, cognitive 12) sysadmin/src/router/core/RouteValidator.ts:105— (anonymous) has cyclomatic complexity 14 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 13, cognitive 16) sysadmin/src/store/modules/worktab.ts:114— (anonymous) has cyclomatic complexity 13 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 submit (cyclomatic 13, cognitive 14) storefront/src/views/Login.vue:43— submit has cyclomatic complexity 13 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 openEdit (cyclomatic 13, cognitive 12) sysadmin/src/views/supply/list/index.vue:1105— openEdit 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 handleImport (cyclomatic 13, cognitive 11) sysadmin/src/views/card/list/index.vue:944— handleImport has cyclomatic complexity 13 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function load (cyclomatic 12, cognitive 14) storefront/src/stores/preferences.ts:36— load 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 handleSendCode (cyclomatic 12, cognitive 14) storefront/src/views/ForgetPassword.vue:51— handleSendCode 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 (anonymous) (cyclomatic 12, cognitive 12) sysadmin/src/api/supply.ts:282— (anonymous) has cyclomatic complexity 12 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function addToCart (cyclomatic 12, cognitive 11) storefront/src/views/Product.vue:274— addToCart has cyclomatic complexity 12 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function useTableImpl (cyclomatic 12, cognitive 11) sysadmin/src/hooks/core/useTable.ts:132— useTableImpl has cyclomatic complexity 12 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function matchRoute (cyclomatic 11, cognitive 14) sysadmin/src/router/core/RoutePermissionValidator.ts:96— matchRoute has cyclomatic complexity 11 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 handleSubmit (cyclomatic 11, cognitive 13) sysadmin/src/views/auth/login/index.vue:182— handleSubmit has cyclomatic complexity 11 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 11, cognitive 11) sysadmin/src/utils/table/tableUtils.ts:114— (anonymous) has cyclomatic complexity 11 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function handleSave (cyclomatic 11, cognitive 10) sysadmin/src/views/setting/index.vue:1029— handleSave has cyclomatic complexity 11 and cognitive complexity 10; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R3 · Large Files· sysadmin/src/views/supply/list/index.vue · ×1
sysadmin/src/views/supply/list/index.vue: 2439 lines of code sysadmin/src/views/supply/list/index.vue:1— sysadmin/src/views/supply/list/index.vue has 2439 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· sysadmin/src/views/product/list/index.vue · ×1
sysadmin/src/views/product/list/index.vue: 2076 lines of code sysadmin/src/views/product/list/index.vue:1— sysadmin/src/views/product/list/index.vue has 2076 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· sysadmin/src/views/setting/index.vue · ×1
sysadmin/src/views/setting/index.vue: 1226 lines of code sysadmin/src/views/setting/index.vue:1— sysadmin/src/views/setting/index.vue has 1226 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· sysadmin/src/views/card/list/index.vue · ×1
sysadmin/src/views/card/list/index.vue: 1220 lines of code sysadmin/src/views/card/list/index.vue:1— sysadmin/src/views/card/list/index.vue has 1220 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· sysadmin/src/components/business/media-manager/index.vue · ×1
sysadmin/src/components/business/media-manager/index.vue: 1006 lines of code sysadmin/src/components/business/media-manager/index.vue:1— sysadmin/src/components/business/media-manager/index.vue has 1006 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· sysadmin/src/views/dashboard/console/index.vue · ×1
sysadmin/src/views/dashboard/console/index.vue: 818 lines of code sysadmin/src/views/dashboard/console/index.vue:1— sysadmin/src/views/dashboard/console/index.vue has 818 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· sysadmin/scripts/clean-dev.ts · ×1
sysadmin/scripts/clean-dev.ts: 745 lines of code sysadmin/scripts/clean-dev.ts:1— sysadmin/scripts/clean-dev.ts has 745 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· sysadmin/src/views/order/list/index.vue · ×1
sysadmin/src/views/order/list/index.vue: 731 lines of code sysadmin/src/views/order/list/index.vue:1— sysadmin/src/views/order/list/index.vue has 731 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· storefront/src/views/Checkout.vue · ×1
storefront/src/views/Checkout.vue: 687 lines of code storefront/src/views/Checkout.vue:1— storefront/src/views/Checkout.vue has 687 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· sysadmin/src/hooks/core/useChart.ts · ×1
sysadmin/src/hooks/core/useChart.ts: 668 lines of code sysadmin/src/hooks/core/useChart.ts:1— sysadmin/src/hooks/core/useChart.ts has 668 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· sysadmin/src/views/update/index.vue · ×1
sysadmin/src/views/update/index.vue: 663 lines of code sysadmin/src/views/update/index.vue:1— sysadmin/src/views/update/index.vue has 663 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· sysadmin/src/hooks/core/useTable.ts · ×1
sysadmin/src/hooks/core/useTable.ts: 656 lines of code sysadmin/src/hooks/core/useTable.ts:1— sysadmin/src/hooks/core/useTable.ts has 656 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· storefront/src/views/Product.vue · ×1
storefront/src/views/Product.vue: 637 lines of code storefront/src/views/Product.vue:1— storefront/src/views/Product.vue has 637 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· sysadmin/src/views/user/list/index.vue · ×1
sysadmin/src/views/user/list/index.vue: 613 lines of code sysadmin/src/views/user/list/index.vue:1— sysadmin/src/views/user/list/index.vue has 613 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· sysadmin/src/components/core/layouts/art-fireworks-effect/index.vue · ×1
sysadmin/src/components/core/layouts/art-fireworks-effect/index.vue: 561 lines of code sysadmin/src/components/core/layouts/art-fireworks-effect/index.vue:1— sysadmin/src/components/core/layouts/art-fireworks-effect/index.vue has 561 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· sysadmin/src/views/payment/list/index.vue · ×1
sysadmin/src/views/payment/list/index.vue: 553 lines of code sysadmin/src/views/payment/list/index.vue:1— sysadmin/src/views/payment/list/index.vue has 553 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· sysadmin/src/components/core/forms/art-search-bar/index.vue · ×1
sysadmin/src/components/core/forms/art-search-bar/index.vue: 516 lines of code sysadmin/src/components/core/forms/art-search-bar/index.vue:1— sysadmin/src/components/core/forms/art-search-bar/index.vue has 516 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· sysadmin/src/components/core/views/login/LoginLeftView.vue · ×1
sysadmin/src/components/core/views/login/LoginLeftView.vue: 507 lines of code sysadmin/src/components/core/views/login/LoginLeftView.vue:1— sysadmin/src/components/core/views/login/LoginLeftView.vue has 507 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· sysadmin/src/components/core/layouts/art-work-tab/index.vue · ×1
sysadmin/src/components/core/layouts/art-work-tab/index.vue: 498 lines of code sysadmin/src/components/core/layouts/art-work-tab/index.vue:1— sysadmin/src/components/core/layouts/art-work-tab/index.vue has 498 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· sysadmin/src/views/supplierAccount/list/index.vue · ×1
sysadmin/src/views/supplierAccount/list/index.vue: 491 lines of code sysadmin/src/views/supplierAccount/list/index.vue:1— sysadmin/src/views/supplierAccount/list/index.vue has 491 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· sysadmin/src/store/modules/worktab.ts · ×1
sysadmin/src/store/modules/worktab.ts: 489 lines of code sysadmin/src/store/modules/worktab.ts:1— sysadmin/src/store/modules/worktab.ts has 489 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· sysadmin/src/views/subsite/list/index.vue · ×1
sysadmin/src/views/subsite/list/index.vue: 468 lines of code sysadmin/src/views/subsite/list/index.vue:1— sysadmin/src/views/subsite/list/index.vue has 468 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· storefront/src/views/MySubsite.vue · ×1
storefront/src/views/MySubsite.vue: 459 lines of code storefront/src/views/MySubsite.vue:1— storefront/src/views/MySubsite.vue has 459 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· sysadmin/src/components/core/forms/art-form/index.vue · ×1
sysadmin/src/components/core/forms/art-form/index.vue: 448 lines of code sysadmin/src/components/core/forms/art-form/index.vue:1— sysadmin/src/components/core/forms/art-form/index.vue has 448 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· sysadmin/src/components/core/layouts/art-header-bar/index.vue · ×1
sysadmin/src/components/core/layouts/art-header-bar/index.vue: 443 lines of code sysadmin/src/components/core/layouts/art-header-bar/index.vue:1— sysadmin/src/components/core/layouts/art-header-bar/index.vue has 443 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· sysadmin/src/views/currency/list/index.vue · ×1
sysadmin/src/views/currency/list/index.vue: 428 lines of code sysadmin/src/views/currency/list/index.vue:1— sysadmin/src/views/currency/list/index.vue has 428 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· storefront/src/views/UserCenter.vue · ×1
storefront/src/views/UserCenter.vue: 420 lines of code storefront/src/views/UserCenter.vue:1— storefront/src/views/UserCenter.vue has 420 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· sysadmin/src/store/modules/setting.ts · ×1
sysadmin/src/store/modules/setting.ts: 409 lines of code sysadmin/src/store/modules/setting.ts:1— sysadmin/src/store/modules/setting.ts has 409 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· sysadmin/src/components/core/layouts/art-notification/index.vue · ×1
sysadmin/src/components/core/layouts/art-notification/index.vue: 406 lines of code sysadmin/src/components/core/layouts/art-notification/index.vue:1— sysadmin/src/components/core/layouts/art-notification/index.vue has 406 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
Dead file (~273 LoC) sysadmin/src/mock/temp/formData.ts— no import path from any entry point (38 application, 12 tooling, 29 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 (~143 LoC) sysadmin/src/utils/sys/error-handle.ts— no import path from any entry point (38 application, 12 tooling, 29 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) sysadmin/src/store/index.ts— no import path from any entry point (38 application, 12 tooling, 29 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) sysadmin/src/router/modules/user.ts— no import path from any entry point (38 application, 12 tooling, 29 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 (~24 LoC) sysadmin/src/router/modules/setting.ts— no import path from any entry point (38 application, 12 tooling, 29 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 (~13 LoC) sysadmin/src/utils/sys/console.ts— no import path from any entry point (38 application, 12 tooling, 29 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 (~9 LoC) storefront/src/api/health.ts— no import path from any entry point (38 application, 12 tooling, 29 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 (~0 LoC) sysadmin/src/utils/ui/iconify-loader.ts— no import path from any entry point (38 application, 12 tooling, 29 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
Unused dependency '@fontsource/instrument-sans' package.json:19— Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency '@iconify-json/ri' storefront/package.json:25— Declared in storefront/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency '@vue/compiler-sfc' sysadmin/package.json:94— Declared in sysadmin/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency '@vue/reactivity' sysadmin/package.json:59— Declared in sysadmin/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'cz-git' sysadmin/package.json:96— Declared in sysadmin/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'qrcode.vue' sysadmin/package.json:77— Declared in sysadmin/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'vue-demi' sysadmin/package.json:123— Declared in sysadmin/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Minor — 111 finding(s)
P2 · Observability· Console output used as the logging channel · ×40
Console output used as the logging channel sysadmin/src/utils/table/tableCache.ts:90— `sysadmin/src/utils/table/tableCache.ts` reports through `console.*` at line 90 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel sysadmin/src/utils/table/tableUtils.ts:127— `sysadmin/src/utils/table/tableUtils.ts` reports through `console.*` at line 127 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel sysadmin/src/utils/table/tableUtils.ts:160— `sysadmin/src/utils/table/tableUtils.ts` reports through `console.*` at line 160 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel sysadmin/src/utils/table/tableUtils.ts:161— `sysadmin/src/utils/table/tableUtils.ts` reports through `console.*` at line 161 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel sysadmin/src/utils/table/tableUtils.ts:162— `sysadmin/src/utils/table/tableUtils.ts` reports through `console.*` at line 162 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel sysadmin/src/utils/table/tableUtils.ts:275— `sysadmin/src/utils/table/tableUtils.ts` reports through `console.*` at line 275 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel sysadmin/src/utils/sys/console.ts:13— `sysadmin/src/utils/sys/console.ts` reports through `console.*` at line 13 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel sysadmin/src/utils/sys/upgrade.ts:171— `sysadmin/src/utils/sys/upgrade.ts` reports through `console.*` at line 171 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel sysadmin/src/utils/sys/upgrade.ts:177— `sysadmin/src/utils/sys/upgrade.ts` reports through `console.*` at line 177 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel sysadmin/src/utils/sys/upgrade.ts:187— `sysadmin/src/utils/sys/upgrade.ts` reports through `console.*` at line 187 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel sysadmin/src/utils/sys/upgrade.ts:189— `sysadmin/src/utils/sys/upgrade.ts` reports through `console.*` at line 189 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel sysadmin/src/utils/sys/upgrade.ts:202— `sysadmin/src/utils/sys/upgrade.ts` reports through `console.*` at line 202 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel sysadmin/src/utils/sys/upgrade.ts:223— `sysadmin/src/utils/sys/upgrade.ts` reports through `console.*` at line 223 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel sysadmin/src/utils/sys/upgrade.ts:225— `sysadmin/src/utils/sys/upgrade.ts` reports through `console.*` at line 225 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel sysadmin/src/utils/sys/upgrade.ts:235— `sysadmin/src/utils/sys/upgrade.ts` reports through `console.*` at line 235 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel sysadmin/src/utils/sys/upgrade.ts:244— `sysadmin/src/utils/sys/upgrade.ts` reports through `console.*` at line 244 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel sysadmin/src/utils/sys/upgrade.ts:250— `sysadmin/src/utils/sys/upgrade.ts` reports through `console.*` at line 250 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel sysadmin/src/utils/sys/upgrade.ts:258— `sysadmin/src/utils/sys/upgrade.ts` reports through `console.*` at line 258 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel sysadmin/src/utils/storage/storage-key-manager.ts:71— `sysadmin/src/utils/storage/storage-key-manager.ts` reports through `console.*` at line 71 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel sysadmin/src/utils/storage/storage-key-manager.ts:74— `sysadmin/src/utils/storage/storage-key-manager.ts` reports through `console.*` at line 74 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel sysadmin/src/utils/storage/storage.ts:91— `sysadmin/src/utils/storage/storage.ts` reports through `console.*` at line 91 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel sysadmin/src/utils/storage/storage.ts:117— `sysadmin/src/utils/storage/storage.ts` reports through `console.*` at line 117 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel sysadmin/src/utils/storage/storage.ts:119— `sysadmin/src/utils/storage/storage.ts` reports through `console.*` at line 119 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel sysadmin/src/utils/storage/storage.ts:140— `sysadmin/src/utils/storage/storage.ts` reports through `console.*` at line 140 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel sysadmin/src/utils/storage/storage.ts:146— `sysadmin/src/utils/storage/storage.ts` reports through `console.*` at line 146 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Interpolated log message defeats structured logging app/Support/DeliveryService.php:88— `info` at line 88 is handed a double-quoted string with variables interpolated into it as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values in the PSR-3 context array instead: `$logger->info('Order {order_id} moved to {status}', ['order_id' => $orderId, 'status' => $status])`, which Monolog and every PSR-3 handler keep as fields beside the message (Monolog's PsrLogMessageProcessor fills the placeholders), or `Log::info('order moved', ['order_id' => $orderId])` with Laravel's facade.
Interpolated log message defeats structured logging app/Support/DomainVerificationService.php:90— `debug` at line 90 is handed a double-quoted string with variables interpolated into it as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values in the PSR-3 context array instead: `$logger->debug('Order {order_id} moved to {status}', ['order_id' => $orderId, 'status' => $status])`, which Monolog and every PSR-3 handler keep as fields beside the message (Monolog's PsrLogMessageProcessor fills the placeholders), or `Log::debug('order moved', ['order_id' => $orderId])` with Laravel's facade.
Interpolated log message defeats structured logging app/Support/DomainVerificationService.php:129— `debug` at line 129 is handed a double-quoted string with variables interpolated into it as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values in the PSR-3 context array instead: `$logger->debug('Order {order_id} moved to {status}', ['order_id' => $orderId, 'status' => $status])`, which Monolog and every PSR-3 handler keep as fields beside the message (Monolog's PsrLogMessageProcessor fills the placeholders), or `Log::debug('order moved', ['order_id' => $orderId])` with Laravel's facade.
Interpolated log message defeats structured logging app/Support/DomainVerificationService.php:192— `info` at line 192 is handed a double-quoted string with variables interpolated into it as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values in the PSR-3 context array instead: `$logger->info('Order {order_id} moved to {status}', ['order_id' => $orderId, 'status' => $status])`, which Monolog and every PSR-3 handler keep as fields beside the message (Monolog's PsrLogMessageProcessor fills the placeholders), or `Log::info('order moved', ['order_id' => $orderId])` with Laravel's facade.
Interpolated log message defeats structured logging app/Support/FulfillmentService.php:98— `warning` at line 98 is handed a double-quoted string with variables interpolated into it as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values in the PSR-3 context array instead: `$logger->warning('Order {order_id} moved to {status}', ['order_id' => $orderId, 'status' => $status])`, which Monolog and every PSR-3 handler keep as fields beside the message (Monolog's PsrLogMessageProcessor fills the placeholders), or `Log::warning('order moved', ['order_id' => $orderId])` with Laravel's facade.
Interpolated log message defeats structured logging app/Support/FulfillmentService.php:109— `warning` at line 109 is handed a double-quoted string with variables interpolated into it as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values in the PSR-3 context array instead: `$logger->warning('Order {order_id} moved to {status}', ['order_id' => $orderId, 'status' => $status])`, which Monolog and every PSR-3 handler keep as fields beside the message (Monolog's PsrLogMessageProcessor fills the placeholders), or `Log::warning('order moved', ['order_id' => $orderId])` with Laravel's facade.
Interpolated log message defeats structured logging app/Supply/SupplyCallbackService.php:97— `warning` at line 97 is handed a double-quoted string with variables interpolated into it as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values in the PSR-3 context array instead: `$logger->warning('Order {order_id} moved to {status}', ['order_id' => $orderId, 'status' => $status])`, which Monolog and every PSR-3 handler keep as fields beside the message (Monolog's PsrLogMessageProcessor fills the placeholders), or `Log::warning('order moved', ['order_id' => $orderId])` with Laravel's facade.
Interpolated log message defeats structured logging app/Supply/UpstreamOrderService.php:54— `warning` at line 54 is handed a double-quoted string with variables interpolated into it as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values in the PSR-3 context array instead: `$logger->warning('Order {order_id} moved to {status}', ['order_id' => $orderId, 'status' => $status])`, which Monolog and every PSR-3 handler keep as fields beside the message (Monolog's PsrLogMessageProcessor fills the placeholders), or `Log::warning('order moved', ['order_id' => $orderId])` with Laravel's facade.
Interpolated log message defeats structured logging app/Supply/UpstreamOrderService.php:147— `info` at line 147 is handed a double-quoted string with variables interpolated into it as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values in the PSR-3 context array instead: `$logger->info('Order {order_id} moved to {status}', ['order_id' => $orderId, 'status' => $status])`, which Monolog and every PSR-3 handler keep as fields beside the message (Monolog's PsrLogMessageProcessor fills the placeholders), or `Log::info('order moved', ['order_id' => $orderId])` with Laravel's facade.
Interpolated log message defeats structured logging app/Supply/UpstreamOrderService.php:150— `warning` at line 150 is handed a double-quoted string with variables interpolated into it as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values in the PSR-3 context array instead: `$logger->warning('Order {order_id} moved to {status}', ['order_id' => $orderId, 'status' => $status])`, which Monolog and every PSR-3 handler keep as fields beside the message (Monolog's PsrLogMessageProcessor fills the placeholders), or `Log::warning('order moved', ['order_id' => $orderId])` with Laravel's facade.
Interpolated log message defeats structured logging app/Supply/UpstreamOrderService.php:163— `warning` at line 163 is handed a double-quoted string with variables interpolated into it as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values in the PSR-3 context array instead: `$logger->warning('Order {order_id} moved to {status}', ['order_id' => $orderId, 'status' => $status])`, which Monolog and every PSR-3 handler keep as fields beside the message (Monolog's PsrLogMessageProcessor fills the placeholders), or `Log::warning('order moved', ['order_id' => $orderId])` with Laravel's facade.
Interpolated log message defeats structured logging app/Jobs/SyncSupplySourceProducts.php:197— `info` at line 197 is handed a double-quoted string with variables interpolated into it as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values in the PSR-3 context array instead: `$logger->info('Order {order_id} moved to {status}', ['order_id' => $orderId, 'status' => $status])`, which Monolog and every PSR-3 handler keep as fields beside the message (Monolog's PsrLogMessageProcessor fills the placeholders), or `Log::info('order moved', ['order_id' => $orderId])` with Laravel's facade.
Interpolated log message defeats structured logging app/Jobs/SyncSupplySourceProducts.php:205— `info` at line 205 is handed a double-quoted string with variables interpolated into it as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values in the PSR-3 context array instead: `$logger->info('Order {order_id} moved to {status}', ['order_id' => $orderId, 'status' => $status])`, which Monolog and every PSR-3 handler keep as fields beside the message (Monolog's PsrLogMessageProcessor fills the placeholders), or `Log::info('order moved', ['order_id' => $orderId])` with Laravel's facade.
Interpolated log message defeats structured logging app/Jobs/SyncSupplySourceProducts.php:210— `error` at line 210 is handed a double-quoted string with variables interpolated into it as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values in the PSR-3 context array instead: `$logger->error('Order {order_id} moved to {status}', ['order_id' => $orderId, 'status' => $status])`, which Monolog and every PSR-3 handler keep as fields beside the message (Monolog's PsrLogMessageProcessor fills the placeholders), or `Log::error('order moved', ['order_id' => $orderId])` with Laravel's facade.
Duplicated predicate sysadmin/src/router/core/RoutePermissionValidator.ts:54— `!Array.isArray(menuList) || menuList.length === 0` appears character-identically in 2 files — sysadmin/src/router/core/RoutePermissionValidator.ts, sysadmin/src/utils/navigation/route.ts. 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 storefront/src/api/request.ts:24— `!['get', 'head', 'options'].includes(method) && !document.cookie.includes('XSRF-TOKEN')` appears character-identically in 2 files — storefront/src/api/request.ts, sysadmin/src/utils/http/index.ts. 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 app/Http/Controllers/Api/Admin/MigrationController.php:259— `$decoded === false || $decoded === '' || $cipher === ''` appears character-identically in 2 files — app/Http/Controllers/Api/Admin/MigrationController.php, app/Support/CardCipher.php. 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 app/Http/Controllers/InstallController.php:100— `$ipLong === false || $subnetLong === false || $bits <= 0` appears character-identically in 2 files — app/Http/Controllers/InstallController.php, app/Supply/CallbackUrlGuard.php. 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 app/Payment/Drivers/CodePayDriver.php:19— `$k !== 'sign' && $k !== 'sign_type' && $v !== '' && $v !== null` appears character-identically in 2 files — app/Payment/Drivers/CodePayDriver.php, app/Payment/Drivers/EpayDriver.php. 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 app/Console/Commands/InstallCommand.php:255— `extension_loaded('gd') || extension_loaded('imagick')` appears character-identically in 2 files — app/Console/Commands/InstallCommand.php, app/Http/Controllers/InstallController.php. 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 app/Http/Controllers/Api/Admin/MigrationController.php:264— `is_array($json) && isset($json['iv'], $json['value'], $json['mac'])` appears character-identically in 2 files — app/Http/Controllers/Api/Admin/MigrationController.php, app/Support/CardCipher.php. 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 app/Console/Commands/InstallCommand.php:346— `preg_match('/[\s#=]/', $value) || $value === ''` appears character-identically in 2 files — app/Console/Commands/InstallCommand.php, app/Http/Controllers/InstallController.php. 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.
Silent fallback default in catch app/Models/PaymentChannel.php:49— `config` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it propagate. 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 in the catch or in the docblock, and the row stops firing.
Silent fallback default in catch app/Payment/PaymentUrlGenerator.php:102— `setting` swallows every exception into `return ''` — a data error becomes a silent behavior change with no trail. Log the failure or let it propagate. 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 in the catch or in the docblock, and the row stops firing.
Silent fallback default in catch storefront/src/stores/cart.ts:23— `load` 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 REDACTED:76— `readContactIndex` 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 sysadmin/scripts/clean-dev.ts:198— `countFiles` swallows every exception into `return 0` — 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.
Hand-rolled JSON/XML parsing via regex public/admin/assets/index-BBCUiM4J.js:54— A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This JavaScript/TypeScript code already uses a real parser in the same package; use it here too.
Hand-rolled JSON/XML parsing via regex public/admin/assets/index.vue_vue_type_style_index_0_lang-rZp8y3ah.js:119— A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This JavaScript/TypeScript code already uses a real parser in the same package; use it here too.
Hand-rolled JSON/XML parsing via regex public/admin/assets/marked.esm-DkzVS-my.js:1— A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This JavaScript/TypeScript code already uses a real parser in the same package; use it here too.
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×2
Projects may be oversized for their cohesion package.json:1— `(repository root)` (27985 LoC, 269 module-visible types across 66 directories) overshoots its size bounds. 2 of 3 build unit(s) (npm) overshoot their size bounds, lowering Project Cohesion to 0.0/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
Projects may be oversized for their cohesion sysadmin/package.json:1— `sysadmin` (15966 LoC, 286 module-visible types across 32 directories) overshoots its size bounds. 2 of 3 build unit(s) (npm) overshoot their size bounds, lowering Project Cohesion to 0.0/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
No ADRs found artisan:1— No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`. ADRs are expected here because `artisan` makes this repository a deployable product (line 1).
D21 · Naming Consistency· `validateChineseIDCard` spells `ID` where 19 names in the project spell it `Id` · ×1
`validateChineseIDCard` spells `ID` where 19 names in the project spell it `Id` sysadmin/src/utils/form/validator.ts:252— 19 of 20 names in project zcard spell the token `Id` (19 of 20; unit: names in project zcard containing `Id`). Peers: payments.createPayment(channelId) (storefront/src/api/payments.ts:30); payments.createBatchPayment(channelId) (storefront/src/api/payments.ts:39); recharge.createRechargePayment(channelId) (storefront/src/api/recharge.ts:35); reviews.getReviewEligibility(productId) (storefront/src/api/reviews.ts:34); orderAccess.orderAccessTokensById (REDACTED:37). Rename to `validateChineseIdCard`. [rule N6]
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.
README/code drift sysadmin/README.md:48— sysadmin/README.md links to `./CHANGELOG.en.md`, but `sysadmin/CHANGELOG.en.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
No SAST — No static application security testing detected. For this repository's stack, add phpstan or psalm (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 package.json:18— `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`.
R7 · Dead Code· Unused export 'CommissionListParams' · ×1
Unused export 'CommissionListParams' sysadmin/src/api/commission.ts:34— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'getSupplierAccount' · ×1
Unused export 'getSupplierAccount' sysadmin/src/api/supplierAccounts.ts:86— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'adjustSupplierAccount' · ×1
Unused export 'adjustSupplierAccount' sysadmin/src/api/supplierAccounts.ts:112— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'getSupplierPrices' · ×1
Unused export 'getSupplierPrices' sysadmin/src/api/supplierAccounts.ts:120— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'updateSupplierPrices' · ×1
Unused export 'updateSupplierPrices' sysadmin/src/api/supplierAccounts.ts:124— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'deleteSupplierPrice' · ×1
Unused export 'deleteSupplierPrice' sysadmin/src/api/supplierAccounts.ts:128— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'DriverConfigField' · ×1
Unused export 'DriverConfigField' sysadmin/src/api/supply.ts:35— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'SupplySyncStatus' · ×1
Unused export 'SupplySyncStatus' sysadmin/src/api/supply.ts:59— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'getSupplySource' · ×1
Unused export 'getSupplySource' sysadmin/src/api/supply.ts:74— Nothing imports this binding — it is safe to review for removal.
Unused export 'PageModeEnum' sysadmin/src/enums/formEnum.ts:14— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'useLayoutHeight' · ×1
Unused export 'useLayoutHeight' sysadmin/src/hooks/core/useLayoutHeight.ts:34— Nothing ultimately consumes this binding: its only referrer is the re-export in sysadmin/src/hooks/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in sysadmin/src/hooks/index.ts in the same commit, or the barrel will import a name that no longer exists.
Unused export 'useTable' sysadmin/src/hooks/core/useTable.ts:115— Nothing ultimately consumes this binding: its only referrer is the re-export in sysadmin/src/hooks/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in sysadmin/src/hooks/index.ts in the same commit, or the barrel will import a name that no longer exists.
R7 · Dead Code· Unused export 'getRouteInitFailed' · ×1
Unused export 'getRouteInitFailed' sysadmin/src/router/guards/beforeEach.ts:89— Nothing imports this binding — it is safe to review for removal.
Unused export 'Status' sysadmin/src/types/common/index.ts:34— Nothing ultimately consumes this binding: its only referrer is the re-export in sysadmin/src/types/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in sysadmin/src/types/index.ts in the same commit, or the barrel will import a name that no longer exists.
Unused export 'Gender' sysadmin/src/types/common/index.ts:37— Nothing ultimately consumes this binding: its only referrer is the re-export in sysadmin/src/types/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in sysadmin/src/types/index.ts in the same commit, or the barrel will import a name that no longer exists.
Unused export 'SortOrder' sysadmin/src/types/common/index.ts:40— Nothing ultimately consumes this binding: its only referrer is the re-export in sysadmin/src/types/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in sysadmin/src/types/index.ts in the same commit, or the barrel will import a name that no longer exists.
Unused export 'ActionType' sysadmin/src/types/common/index.ts:43— Nothing ultimately consumes this binding: its only referrer is the re-export in sysadmin/src/types/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in sysadmin/src/types/index.ts in the same commit, or the barrel will import a name that no longer exists.
Unused export 'Recordable' sysadmin/src/types/common/index.ts:46— Nothing ultimately consumes this binding: its only referrer is the re-export in sysadmin/src/types/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in sysadmin/src/types/index.ts in the same commit, or the barrel will import a name that no longer exists.
Unused export 'KeyValue' sysadmin/src/types/common/index.ts:49— Nothing ultimately consumes this binding: its only referrer is the re-export in sysadmin/src/types/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in sysadmin/src/types/index.ts in the same commit, or the barrel will import a name that no longer exists.
Unused export 'TimeRange' sysadmin/src/types/common/index.ts:56— Nothing ultimately consumes this binding: its only referrer is the re-export in sysadmin/src/types/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in sysadmin/src/types/index.ts in the same commit, or the barrel will import a name that no longer exists.
Unused export 'FileInfo' sysadmin/src/types/common/index.ts:62— Nothing ultimately consumes this binding: its only referrer is the re-export in sysadmin/src/types/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in sysadmin/src/types/index.ts in the same commit, or the barrel will import a name that no longer exists.
Unused export 'Position' sysadmin/src/types/common/index.ts:71— Nothing ultimately consumes this binding: its only referrer is the re-export in sysadmin/src/types/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in sysadmin/src/types/index.ts in the same commit, or the barrel will import a name that no longer exists.
X2 · Cancellation propagation· Not all async functions that make a request accept an AbortSignal · ×1
Not all async functions that make a request accept an AbortSignal — Only 0/2 async functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
X5 · Nullable reference types· PHP static analysis does not check null everywhere · ×1
PHP static analysis does not check null everywhere — This repository commits no PHPStan or Psalm configuration (`phpstan.neon[.dist]`, `phpstan.dist.neon`, `psalm.xml[.dist]`, or one a composer.json script names with `--configuration`), so nothing checks null: a `?Customer` reaches `->name()` silently and throws `Error: Call to a member function name() on null` the first time it is null. If the build passes a level on a command line instead, put it in a committed configuration — this check reads configuration, and configuration is all it can read.
Outdated: filament/filament — `filament/filament` is locked at v5.7.3 but v5.11.4 is the current stable release on Packagist, and it already satisfies the `^5.0` constraint declared in composer.json — so the lockfile is behind this repository's own declared range. Run `composer update filament/filament` and commit the updated REDACTED.
Outdated: laravel/framework — `laravel/framework` is locked at v13.23.0 but v13.43.0 is the current stable release on Packagist, and it already satisfies the `^13.8` constraint declared in composer.json — so the lockfile is behind this repository's own declared range. Run `composer update laravel/framework` and commit the updated REDACTED.
Outdated: laravel/sanctum — `laravel/sanctum` is locked at v4.3.3 but v4.5.0 is the current stable release on Packagist, and it already satisfies the `^4.0` constraint declared in composer.json — so the lockfile is behind this repository's own declared range. Run `composer update laravel/sanctum` and commit the updated REDACTED.
Outdated: laravel/tinker — `laravel/tinker` is locked at v3.0.2 but v3.2.0 is the current stable release on Packagist, and it already satisfies the `^3.0` constraint declared in composer.json — so the lockfile is behind this repository's own declared range. Run `composer update laravel/tinker` and commit the updated REDACTED.
Outdated: mews/captcha — `mews/captcha` is locked at 3.5.0 but 3.5.1 is the current stable release on Packagist, and it already satisfies the `^3.5` constraint declared in composer.json — so the lockfile is behind this repository's own declared range. Run `composer update mews/captcha` and commit the updated REDACTED.
Outdated: spatie/laravel-permission — `spatie/laravel-permission` is locked at 8.3.0 but 8.5.0 is the current stable release on Packagist, and it already satisfies the `^8.0` constraint declared in composer.json — so the lockfile is behind this repository's own declared range. Run `composer update spatie/laravel-permission` and commit the updated REDACTED.
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.
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 01a1eabf-428f-7972-8685-ec427815ce89 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 151 · Warnings: 398 · Recommendations: 111 · Info: 6 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 17-11-2026 @ 18:22 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.