Public report of liteerp-oss/liteerp, published 9 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.2). 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, 9 November 2026, 03:57 UTC · Survey ID cd_daa907243833445091f4c73bd3671f9f
liteerp-oss/liteerp
Measured 9 November 2026, 03:55 UTC, at code version 3bbb6fe
CAI scoreAt riskNo change since the last survey
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A medium codebase: 49,771 lines of product code in 2 projects, tests not counted · Estimated rebuild effort: about 0.4 person-years · Weakest lens: Production Readiness, 26
Findings by how serious they are
99 critical473 serious54 minor
16 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
9 November 2026, 03:55 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 ▸
89of 89 dimensions measured by tools.
594of 626 findings point to an exact file and line, so you can open each one in the code. The other 32 concern the repository as a whole, such as missing documentation.
89dimensions across 8 lenses, read from 49,771 lines of product code in 2 projects.
liteerp-oss/liteerp is rated At risk because critical security findings are open, most of them in the packages it uses. Its score is held back because four passwords or keys sit in the current code and we found no automated security scanning of the code, its secrets or its dependencies. It scores 36 out of 100, which the At risk rating leaves unchanged.
Production Readiness, at 26, is the weakest lens and counts most in the score. The best first step is replacing the four exposed passwords or keys and switching the old ones off, worth about 8 points. Adding automated security scanning comes next, worth about 4 points. Raising Production Readiness to 70 would lift the score to about 44.
Twenty-five known security holes in the packages the code depends on can be used by attackers. Seven settings leave the servers or containers unsafe, and seventeen controls can't be used without a mouse. Updating the vulnerable packages, correcting the unsafe settings and making the controls work with a keyboard would close these risks. Pinning each tool to an exact version would fix the four pipeline tools referenced by a changeable name, and the four passwords or keys in the code and the two passwords or keys in the code's history need replacing, with the old ones switched off. The 26 labels or groups of fields with no name need connecting to their fields or naming.
The product code is 49,771 lines, about €63,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.
We compare every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.
Fixed since the last survey: 231 findings
These 231 critical or serious findings were in the previous survey, on 22 October 2026, and are gone from this one. The first 100 are listed here.
Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
€21,000 to €110,000, for 349 to 1,107 hours of work, about 0.4 person-years for one engineer
Difficulty of the problem
High, 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 36. 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: 49,771 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
Resolve the 4 Leaked secret finding(s) in Secret Scanning — start with REDACTED (2), REDACTED, REDACTED.
Raises the score by about 8 points · Low effort · Secret Scanning
2
Add a SAST step to CI running what this repository's stack ships: phpstan or psalm — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
Add tests that import the unreached modules (directly or through their public entry).
Raises the score by about 4 points · Medium effort · Test Coverage
Diagnosis: what the measurements show together
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
Where the investment is most exposed · Value at risk
This code would cost about €63,000 to build again, about 0.4 person-years of work. Its weakest lens is Production Readiness, at 26 (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.
One cause behind 48 Domain Modelling findings · Common cause
48 findings in the Domain Modelling lens come from the same cause. The code models the business as objects, such as an order or a customer, and each object should guard its own rules: an order, for example, should refuse to be shipped before it has been paid. Here the objects don't do that. Other code can change an object's data directly, so it can put an order into a state the rules forbid. Some objects only hold data, while the rules that should keep that data valid sit elsewhere in the code. Because all of these findings have the same cause, fixing it once, in the business objects themselves, deals with them together.
Based on: Encapsulated state (8 findings) · Rich vs anemic model (40 findings)
What to do: Give each business object the methods that enforce its rules, such as a method for shipping an order that first checks it has been paid, and let only those methods change its data. Give each kind of identifier a type of its own, so an order number can't be used where a customer number belongs.
If you do one thing first · First action
Resolve the 4 Leaked secret finding(s) in Secret Scanning. Of all the actions in this report, it raises the score most for the work it takes: about 8 points for low effort, because it clears the 4 Secret Scanning findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
Architecture: which parts of the code depend on which
The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.
608 modules, with 646 dependencies between them. Every module uses only modules listed above it, so there are no loops.
The table shows the 40 modules with the most connections; 568 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.Contracts.Hooks uses App.Supports.Hooks, so a change to App.Supports.Hooks can break App.Contracts.Hooks, while a change to App.Contracts.Hooks can't break App.Supports.Hooks.
Position
Below the diagonal: App.Contracts.Hooks uses a module listed above it, which is the healthy direction.
App.Http.Controllers uses App.Supports.Hooks, so a change to App.Supports.Hooks can break App.Http.Controllers, while a change to App.Http.Controllers can't break App.Supports.Hooks.
Position
Below the diagonal: App.Http.Controllers uses a module listed above it, which is the healthy direction.
Core.Authencation.Application.UseCases uses Core.AppToken.Application.UseCases, so a change to Core.AppToken.Application.UseCases can break Core.Authencation.Application.UseCases, while a change to Core.Authencation.Application.UseCases can't break Core.AppToken.Application.UseCases.
Position
Below the diagonal: Core.Authencation.Application.UseCases uses a module listed above it, which is the healthy direction.
Core.Customer.Application.UseCases uses App.Supports.Hooks, so a change to App.Supports.Hooks can break Core.Customer.Application.UseCases, while a change to Core.Customer.Application.UseCases can't break App.Supports.Hooks.
Position
Below the diagonal: Core.Customer.Application.UseCases uses a module listed above it, which is the healthy direction.
Core.Extension.Domain.Supports uses Core.Extension.Domain.Entities, so a change to Core.Extension.Domain.Entities can break Core.Extension.Domain.Supports, while a change to Core.Extension.Domain.Supports can't break Core.Extension.Domain.Entities.
Position
Below the diagonal: Core.Extension.Domain.Supports uses a module listed above it, which is the healthy direction.
Core.InvoiceIn.Application.UseCases uses App.Supports.Hooks, so a change to App.Supports.Hooks can break Core.InvoiceIn.Application.UseCases, while a change to Core.InvoiceIn.Application.UseCases can't break App.Supports.Hooks.
Position
Below the diagonal: Core.InvoiceIn.Application.UseCases uses a module listed above it, which is the healthy direction.
Core.InvoiceIn.Application.UseCases uses Core.InvoiceIn.Domain.Entities, so a change to Core.InvoiceIn.Domain.Entities can break Core.InvoiceIn.Application.UseCases, while a change to Core.InvoiceIn.Application.UseCases can't break Core.InvoiceIn.Domain.Entities.
Position
Below the diagonal: Core.InvoiceIn.Application.UseCases uses a module listed above it, which is the healthy direction.
Core.InvoiceOut.Application.UseCases uses App.Supports.Hooks, so a change to App.Supports.Hooks can break Core.InvoiceOut.Application.UseCases, while a change to Core.InvoiceOut.Application.UseCases can't break App.Supports.Hooks.
Position
Below the diagonal: Core.InvoiceOut.Application.UseCases uses a module listed above it, which is the healthy direction.
Core.Order.Application.UseCases uses App.Supports.Hooks, so a change to App.Supports.Hooks can break Core.Order.Application.UseCases, while a change to Core.Order.Application.UseCases can't break App.Supports.Hooks.
Position
Below the diagonal: Core.Order.Application.UseCases uses a module listed above it, which is the healthy direction.
Core.OrderItem.Application.UseCases uses App.Supports.Hooks, so a change to App.Supports.Hooks can break Core.OrderItem.Application.UseCases, while a change to Core.OrderItem.Application.UseCases can't break App.Supports.Hooks.
Position
Below the diagonal: Core.OrderItem.Application.UseCases uses a module listed above it, which is the healthy direction.
Core.OrderShipping.Application.UseCases uses App.Supports.Hooks, so a change to App.Supports.Hooks can break Core.OrderShipping.Application.UseCases, while a change to Core.OrderShipping.Application.UseCases can't break App.Supports.Hooks.
Position
Below the diagonal: Core.OrderShipping.Application.UseCases uses a module listed above it, which is the healthy direction.
Core.Permission.Application.UseCases uses App.Supports.Hooks, so a change to App.Supports.Hooks can break Core.Permission.Application.UseCases, while a change to Core.Permission.Application.UseCases can't break App.Supports.Hooks.
Position
Below the diagonal: Core.Permission.Application.UseCases uses a module listed above it, which is the healthy direction.
Core.Permission.Application.UseCases uses Core.Permission.Domain.Entities, so a change to Core.Permission.Domain.Entities can break Core.Permission.Application.UseCases, while a change to Core.Permission.Application.UseCases can't break Core.Permission.Domain.Entities.
Position
Below the diagonal: Core.Permission.Application.UseCases uses a module listed above it, which is the healthy direction.
Core.Permission.Application.UseCases uses Core.Permission.Infrastructure.Helpers, so a change to Core.Permission.Infrastructure.Helpers can break Core.Permission.Application.UseCases, while a change to Core.Permission.Application.UseCases can't break Core.Permission.Infrastructure.Helpers.
Position
Below the diagonal: Core.Permission.Application.UseCases uses a module listed above it, which is the healthy direction.
Core.Purchase.Application.UseCases uses App.Supports.Hooks, so a change to App.Supports.Hooks can break Core.Purchase.Application.UseCases, while a change to Core.Purchase.Application.UseCases can't break App.Supports.Hooks.
Position
Below the diagonal: Core.Purchase.Application.UseCases uses a module listed above it, which is the healthy direction.
Core.Purchase.Application.UseCases uses Core.Purchase.Domain.Entities, so a change to Core.Purchase.Domain.Entities can break Core.Purchase.Application.UseCases, while a change to Core.Purchase.Application.UseCases can't break Core.Purchase.Domain.Entities.
Position
Below the diagonal: Core.Purchase.Application.UseCases uses a module listed above it, which is the healthy direction.
Core.PurchaseItem.Application.UseCases uses App.Supports.Hooks, so a change to App.Supports.Hooks can break Core.PurchaseItem.Application.UseCases, while a change to Core.PurchaseItem.Application.UseCases can't break App.Supports.Hooks.
Position
Below the diagonal: Core.PurchaseItem.Application.UseCases uses a module listed above it, which is the healthy direction.
Core.StockIn.Application.UseCases uses App.Supports.Hooks, so a change to App.Supports.Hooks can break Core.StockIn.Application.UseCases, while a change to Core.StockIn.Application.UseCases can't break App.Supports.Hooks.
Position
Below the diagonal: Core.StockIn.Application.UseCases uses a module listed above it, which is the healthy direction.
Core.StockOut.Application.UseCases uses App.Supports.Hooks, so a change to App.Supports.Hooks can break Core.StockOut.Application.UseCases, while a change to Core.StockOut.Application.UseCases can't break App.Supports.Hooks.
Position
Below the diagonal: Core.StockOut.Application.UseCases uses a module listed above it, which is the healthy direction.
Core.StockOut.Application.UseCases uses Core.StockOut.Domain.Entities, so a change to Core.StockOut.Domain.Entities can break Core.StockOut.Application.UseCases, while a change to Core.StockOut.Application.UseCases can't break Core.StockOut.Domain.Entities.
Position
Below the diagonal: Core.StockOut.Application.UseCases uses a module listed above it, which is the healthy direction.
Core.Business.Application.UseCases uses App.Supports.Hooks, so a change to App.Supports.Hooks can break Core.Business.Application.UseCases, while a change to Core.Business.Application.UseCases can't break App.Supports.Hooks.
Position
Below the diagonal: Core.Business.Application.UseCases uses a module listed above it, which is the healthy direction.
Core.Business.Application.UseCases uses Core.AppToken.Application.UseCases, so a change to Core.AppToken.Application.UseCases can break Core.Business.Application.UseCases, while a change to Core.Business.Application.UseCases can't break Core.AppToken.Application.UseCases.
Position
Below the diagonal: Core.Business.Application.UseCases uses a module listed above it, which is the healthy direction.
Core.Business.Application.UseCases uses Core.Authencation.Application.UseCases, so a change to Core.Authencation.Application.UseCases can break Core.Business.Application.UseCases, while a change to Core.Business.Application.UseCases can't break Core.Authencation.Application.UseCases.
Position
Below the diagonal: Core.Business.Application.UseCases uses a module listed above it, which is the healthy direction.
Core.Extension.Application.UseCases uses Core.Extension.Domain.Supports, so a change to Core.Extension.Domain.Supports can break Core.Extension.Application.UseCases, while a change to Core.Extension.Application.UseCases can't break Core.Extension.Domain.Supports.
Position
Below the diagonal: Core.Extension.Application.UseCases uses a module listed above it, which is the healthy direction.
Core.Notifications.Application.UseCases uses Core.Permission.Application.UseCases, so a change to Core.Permission.Application.UseCases can break Core.Notifications.Application.UseCases, while a change to Core.Notifications.Application.UseCases can't break Core.Permission.Application.UseCases.
Position
Below the diagonal: Core.Notifications.Application.UseCases uses a module listed above it, which is the healthy direction.
Core.Shipping.Http.Controllers uses App.Http.Controllers, so a change to App.Http.Controllers can break Core.Shipping.Http.Controllers, while a change to Core.Shipping.Http.Controllers can't break App.Http.Controllers.
Position
Below the diagonal: Core.Shipping.Http.Controllers uses a module listed above it, which is the healthy direction.
Core.Overview.Application.UseCases uses App.Supports.Hooks, so a change to App.Supports.Hooks can break Core.Overview.Application.UseCases, while a change to Core.Overview.Application.UseCases can't break App.Supports.Hooks.
Position
Below the diagonal: Core.Overview.Application.UseCases uses a module listed above it, which is the healthy direction.
Core.Overview.Application.UseCases uses Core.Business.Application.UseCases, so a change to Core.Business.Application.UseCases can break Core.Overview.Application.UseCases, while a change to Core.Overview.Application.UseCases can't break Core.Business.Application.UseCases.
Position
Below the diagonal: Core.Overview.Application.UseCases uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 39% · Weak · gated by R1, X5 ·
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
46
High / Critical
A02:2025 — Security Misconfiguration
11
High / Critical
A05:2025 — Injection
8
High / Critical
A07:2025 — Authentication Failures
7
High / Critical
Roadmap
Top priorities: Resolve the 4 Leaked secret finding(s) in Secret Scanning — start with REDACTED (2), REDACTED, REDACTED; Add a SAST step to CI running what this repository's stack ships: phpstan or psalm — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing; Add tests that import the unreached modules (directly or through their public entry).
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 4 Leaked secret finding(s) in Secret Scanning — start with REDACTED (2), REDACTED, REDACTED.
Add a SAST step to CI running what this repository's stack ships: phpstan or psalm — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
Add a test runner (vitest / jest / playwright) and eslint and type checking (adopt TypeScript, or type-check the existing JavaScript with `checkJs`) as package.json scripts and run them in CI.
Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.
Strengthen data-at-rest protection: vault your keys (AWS KMS / Secrets Manager, GCP KMS / Secret Manager, HashiCorp Vault — not only APP_KEY in .env) and encrypt the most sensitive columns (Eloquent 'encrypted' casts, CipherSweet) — partial coverage still leaves gaps.
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 — 99
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 — 473
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 — 54
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 16
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 89 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 — 89 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, 594 of 626 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: test source is present (.php) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo. To have real coverage read, produce a coverage report in a standard format (Clover XML — with Xdebug (`XDEBUG_MODE=coverage`) or PCOV installed, `vendor/bin/phpunit --coverage-clover coverage.xml`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (Clover XML — with Xdebug (`XDEBUG_MODE=coverage`) or PCOV installed, `vendor/bin/phpunit --coverage-clover coverage.xml`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.php) but the built-in reliability runner does not support this repository's ecosystem, so flakiness couldn't be assessed. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
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 composer.json, but the licence verdict published here was taken over its npm package dependencies. Nothing was read about its Composer 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 (5 contributor(s) across 803 commit(s) sampled, automation and bot accounts excluded). One of them holds 98% of the history; the other 4 hold 0.5% 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. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict. For npm the surface is what a published package.json's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
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.
D31 IaC & Container Security — 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. REDACTED carries no `FROM` instruction, so it declares no build stage and every Dockerfile rule this engine owns — the runtime-hardening, key-material, mutable-clone, no-op-shim, build-context, trust-anchor, install-guard, setuid and world-writable-path rules — is outside its own premise there and returned nothing. That silence is deliberate and correct: with no base image there is no image to reason about. It is reported here because it is NOT the same fact as a clean file, and coverage is stated as 2 of 3 Infrastructure-as-Code manifest(s) fully judged rather than as 100%. The vendor scanners (trivy, checkov) do read these files and their findings above stand; only this engine's own stage-keyed rules are absent. No owner action: a build file with no FROM is a legitimate include fragment.
D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `app/app/Supports/Hooks/HookContext.php`, `app/core/StockMovementOut/Application/DTOs/CreateManyStockMovementOutRequest.php` 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. 75 further occurrence(s) are not listed individually; the score already reflects all 115.
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.
AX6 Interface segregation — 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 is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing 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.
AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DockerCompose (REDACTED). compose up failed (exit 17 — an image could not be built) — failed to solve: process "/bin/sh -c apt-get update && apt-get install -y ca-certificates libicu-dev unzip nodejs && update-ca-certificates && docker-php-ext-install intl && pecl install redis && docker-php-ext-enable redis" did not complete successfully: exit code: 1; runtime evidence skipped.
DM4 Rich vs anemic model — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 20 further occurrence(s) are not listed individually; the score already reflects all 60.
DM8 Value-object opportunities — 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 finds primitive parameters that travel together through several signatures of the domain (a missing value object). Its deterministic rule has not yet shown 95 % precision on adjudicated rows, so the clumps it finds are counted here and not published as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
DM9 Scattered domain decisions — 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. Arm two tells a construction that PRODUCES a measurement from one that merely passes it along, and this repository's frontend does not compute that fact. A measurement built independently in two places would not appear above.
DM9 Scattered domain decisions — 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. Some of this repository's production types come from a frontend that does not bind comparison operands to the members they read, which arm one needs, and those types were not walked for this dimension. The counts above speak for the languages that declare it.
GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and this repository's PHP is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and this repository's PHP 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.
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. 122 further occurrence(s) are not listed individually; the score already reflects all 162.
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 reads C# syntax, and Java, Rust, Erlang, F#, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded, no Java, Rust, Erlang, F#, Python, Dart, Ruby, Scala or Kotlin was found, and this repository's PHP 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.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
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.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
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.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a 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.
AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
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.
DM4 Rich vs anemic model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
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.
+ 6 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 11 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with CommonDataTableV2.CommonDataTableV2 (cyclomatic 37), EditOrder.EditOrder (cyclomatic 33), EditPurchase.EditPurchase (cyclomatic 28). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 11 together lifts Cyclomatic Complexity from 8.2 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
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.
+ 8 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 2 bodies over 30 down to 30 or less in Cognitive Complexity — start with EditOrder.EditOrder (cognitive 44), CommonDataTableV2.CommonDataTableV2 (cognitive 42). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cognitive Complexity from 7.8 to about 8.2/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes5.9 / 10Adequate✓ 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 38 FunctionTooLong finding(s) in God Classes — start with ShippingForm.jsx (2), InvoiceOutsDetail.jsx, ListProduct.jsx. — One of this dimension's main actionable groups (38 warning-level).
Resolve the 3 MethodTooLong finding(s) in God Classes — start with MakeModule.php, MakeExtension.php, IndexQuery.php. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 1 TooManyMethods finding(s) in God Classes — start with PermissionBuilder.php. — One of this dimension's main actionable groups (1 warning-level).
Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Copy-pasted code that should be shared instead.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.
140 duplicated block group(s) detected. A further 11 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted. 26 of the 151 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
+ 87 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 10 Duplicated block (14 lines × 2) finding(s) in Code Duplication — start with CreateCustomer.php, CreateInvoiceIn.php, ShowPermissionGroup.php. — One of this dimension's main actionable groups (10 warning-level).
Resolve the 6 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with MakeBroadcastModule.php, ExtensionInstallImpl.php, IndexQuery.php. — One of this dimension's main actionable groups (6 warning-level).
Resolve the 6 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with CreateNotificationRequest.php, CreatePurchaseItemRequest.php, MakeExtensionCommand.php. — One of this dimension's main actionable groups (6 warning-level).
Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with EloquentExtensionRepository.php. — One of this dimension's main actionable groups (1 warning-level).
Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D9 · Test Distribution10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the test suite has a healthy mix of unit / integration / end-to-end tests.
Method: Test projects classified (Unit/Integration/BDD/E2E) from compiled metadata; test methods counted exhaustively across projects with placement-agnostic disk fallback. Deterministic.
1 test methods: 1 unit, 0 integration, 0 BDD, 0 e2e.
✓ On the Gold path — maintain.
Detailed fixes: d9_recommendation.md.
Do you agree with this assessment?
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.
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.
10 outdated direct production npm dependency(ies) of 13 graded, 0 pinning defect(s), across 2 package.json (2 of them the product) and 2 committed lockfile(s). Development dependencies are deliberately not graded for currency: that grade is about what SHIPS. 0 direct dependency(ies) — production, development or optional — are marked DEPRECATED by their publisher (the registry's per-version mark, or the lockfile's copy of it when the registry could not be asked); deprecated transitive packages are listed but not charged. Whether any is UNMAINTAINED is not graded — the registry publishes no maintenance status, and release age does not stand in for one. Whether any is UNUSED is not graded either: that is a source question, and the frontend dependency lens (R8) answers it in this same run. Known CVEs in this dependency graph are D30's question, read from the manifest there.
Outdated (npm): @reduxjs/toolkit · ×10
✓ 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.
Resolve the 4 Leaked secret finding(s) in Secret Scanning — start with REDACTED (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (4 issue-level).
Enforce Secret Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d13_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
0 of 209 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 209 package(s) this repository's committed lockfile installs for a consumer — its 13 production, optional and peer dependency(ies), across 2 product package.json manifest(s), and everything those install in turn. Its 10 `devDependencies` declaration(s), and every package only they reach, are excluded: a consumer installs none of them. ★ Each licence is the one the registry publishes for the package's CURRENT release rather than for the pinned version, which is the same caveat the Hex and RubyGems arms carry. ★ COVERAGE OF THIS VERDICT: it grades this repository's npm package dependencies and nothing else. The repository also declares composer.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: app/resources/js/react/components/CommonDataTableV2.jsx (8×37=296); app/resources/js/react/components/Order/EditOrder.jsx (6×33=198); app/resources/js/react/components/Purchases/EditPurchase.jsx (6×28=168) Repeated repair below the complexity floor: app/resources/js/react/components/Product/Category.jsx (5 of 7 changes were fixes); app/resources/js/react/components/Customer/ListGroup.jsx (5 of 6 changes were fixes); app/resources/js/react/pages/warehouse.jsx (4 of 6 changes were fixes)
Resolve the 21 Repeated repair finding(s) in Churn × Complexity Hotspots — start with Category.jsx, ListGroup.jsx, warehouse.jsx. — One of this dimension's main actionable groups (21 warning-level).
Resolve the 10 Hotspot finding(s) in Churn × Complexity Hotspots — start with CommonDataTableV2.jsx, EditOrder.jsx, EditPurchase.jsx. — One of this dimension's main actionable groups (10 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.
7 deducted task-comment markers across 49771 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
Resolve the 7 TodoComment finding(s) in Explicit Debt — start with EloquentStockMovementOutRepository.php, EloquentShippingRepository.php, EloquentPurchaseRepository.php. — One of this dimension's main actionable groups (7 warning-level).
Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.
1 of 1 documentation facets pass in full. 34 document(s) read across 2 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.
2 of 2 build units (npm) flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesion
What to do
Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D27 · Navigability8.3 / 10Strong✓ Tool-verified
What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.
Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.
Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.
66 % of calls cross a namespace and 16 % go through an interface, but 73 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
What to do
Improve Navigability — currently 8.3/10. — 66 % of calls cross a namespace and 16 % go through an interface, but 73 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
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.
2 finding(s): 0 critical, 2 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
REDACTED
REDACTED
What to do
Resolve the 2 High secret finding(s) in Secrets (history) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
8 finding(s): 0 critical, 8 high, 0 medium, 0 low. 4 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 2 file(s) — `app/app/Supports/Hooks/HookContext.php` (line 7, line 8, line 9, …), `app/core/StockMovementOut/Application/DTOs/CreateManyStockMovementOutRequest.php` (line 17) — 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
What to do
Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (4 issue-level).
No action in Static Analysis (SAST) — all 4 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (4 issue-level, 0 of them charged here).
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 22 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (15), REDACTED (7). — One of this dimension's main actionable groups (22 issue-level).
Resolve the 10 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (6), REDACTED (4). — One of this dimension's main actionable groups (10 warning-level).
Resolve the 3 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 issue-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
Resolve the 7 High IaC finding(s) in IaC & Container Security — start with REDACTED (5), REDACTED, REDACTED. — One of this dimension's main actionable groups (7 issue-level).
Resolve the 3 Medium IaC finding(s) in IaC & Container Security — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 1 Low IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d31_recommendation.md · top locations in Appendix A, every location in findings.md.
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 90 of the 1314 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 Change coupling finding(s) in Change Coupling — start with IndexInvoiceOuts.jsx. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
+ 1 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the repository publishes a coordinated-vulnerability-disclosure policy (SECURITY.md or security.txt) with a reporting contact, so finders know how to report a vulnerability. Presence of a policy file with a contact, not whether the policy is adequate or honoured.
Method: Vulnerability-disclosure policy read deterministically from the repo: a SECURITY.md (root/.github/docs) or .well-known/security.txt / security.txt, regex-checked for a reporting contact (email / URL / mailto). Present + contact → 10; present without a contact → 4; NotApplicable when no policy file exists (it may live off-repo). Detects the policy file's presence + contact, not its adequacy.
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 1 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 alternatives5.4 / 10Adequate✓ Tool-verified
Other · Accessibility — Whether non-text content carries a text alternative — img/area/input[type=image] have alt, a meaningful svg has a title or aria-label, video has a captions track, and object/embed/canvas have a name or fallback content. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: every img/area/input[type=image] checked for alt, svg[role=img] for a title/aria-label, video for a captions <track>. Components skipped, spreads suppressed. Deterministic, hard fact per element.
Coverage: Population: image/media elements — img, area, input[type=image], svg, video, object, embed, canvas — across the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and dynamic-attribute elements are skipped. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is NOT read by any producer, so it contributes no element to this population; where such a frontend is present the card discloses it as an analyzer gap rather than scoring around it.
An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative. — app/resources/js/react/components/Footer.jsx:18
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 & labels2.9 / 10Weak✓ Tool-verified
Other · Accessibility — Whether form controls have a programmatic label (an associated label, aria-label or aria-labelledby), buttons have text, links have an accessible name, a click handler on a plain element names the control it declares, fieldsets have a non-empty legend, known UI-library field components carry a label prop, and a placeholder isn't used as the only label. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: inputs/selects/textareas checked for an associated label[for]/wrapping label/aria-label/aria-labelledby (per document), buttons for accessible text, fieldsets for a legend; placeholder-only labelling flagged. Deterministic, hard fact per control.
Coverage: Population: form controls, buttons, links, fieldsets and known UI-library field components in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and spread/dynamic-attribute elements are skipped, so a control whose label arrives through a spread or a runtime expression is deliberately not judged. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
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). (×4) — app/resources/js/react/components/AutoDataTable.jsx:88, app/resources/js/react/components/CommonDataTable.jsx:87, app/resources/js/react/components/CommonDataTableV2.jsx:206, …
This <li> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label. (×2) — app/resources/js/react/components/CommonDataTable.jsx:116, app/resources/js/react/components/CommonDataTableV2.jsx:251
This <label> has no htmlFor 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 htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id. (×26) — app/resources/js/react/components/Invoice/IndexCustomInvoiceIns.jsx:255, app/resources/js/react/components/Invoice/IndexCustomInvoiceIns.jsx:264, app/resources/js/react/components/Invoice/IndexCustomInvoiceIns.jsx:282, …
This UI-library field component has no label / aria-label / aria-labelledby / id at this call site, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id, even one the component sets on what it renders, names nothing until a label points at it) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed. (×5) — app/resources/js/react/components/Invoice/IndexCustomInvoiceIns.jsx:301, app/resources/js/react/components/Invoice/IndexCustomInvoiceIns.jsx:310, app/resources/js/react/components/Invoice/IndexCustomInvoiceOuts.jsx:328, …
This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. — app/resources/js/react/components/LanguageSwitcher.jsx:17
This <img> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label. — app/resources/js/react/components/LoadImage.jsx:9
This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed. — app/resources/js/react/components/Order/EditOrder.jsx:327
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.
A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope). (×3) — app/resources/js/react/components/Business/BusinessListItem.jsx:43, extension-examples/InvoiceInPDF/Views/index.blade.php:104, extension-examples/InvoiceOutPDF/Views/index.blade.php:98
Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one. (×12) — app/resources/js/react/pages/report.jsx:92, app/resources/js/react/pages/report.jsx:100, app/resources/js/react/pages/report.jsx:112, …
No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. (×3) — app/resources/views/admin/layouts/auth.blade.php:2, app/resources/views/admin/layouts/dashboard.blade.php:2, app/resources/views/home/layout.blade.php:2
What to do
Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
Other · Accessibility — Whether interactive behaviour is keyboard-reachable — no click handler on a non-interactive element lacking a role, tabindex and key handler, no element the repo's own CSS styles `cursor: pointer` without giving it any of the three, no unfocusable element whose only binding is a mouse enter/leave pair or a double-click, no positive tabindex, no href-less anchor, no placeholder-href (#/javascript) link acting as a button. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: click handlers on non-interactive elements lacking role+tabindex+key handler, positive tabindex values, and href-less anchors. Components skipped, spreads suppressed. Deterministic, hard fact per element.
Coverage: Population: elements that pose a keyboard-semantics question, in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) — a non-natively-interactive element carrying a click handler, a double-click or hover enter/leave binding, a pointer-only gesture on a tabindex="0" element, or `cursor: pointer` from the repo's own CSS; an href-less or placeholder-href (#, javascript:) anchor; and any element with a positive tabindex. Natively interactive elements used correctly (<button>, <a href>, form controls) are NOT in the population — there is nothing to judge — so a page of nothing but correct controls gives AC4 nothing to measure. Keyboard reachability is judged from the markup, never from a rendered page. ★ An interactive element declared in a tagged-template (html`…`) or hyperscript frontend is NOT in this population — no producer reads either — so an empty population is reported as an analyzer gap, never as "this repository has no interactive elements".
A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler. (×17) — app/resources/js/react/components/CommonDataTable.jsx:26, app/resources/js/react/components/CommonDataTable.jsx:116, app/resources/js/react/components/CommonDataTableV2.jsx:138, …
An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action. (×2) — app/resources/js/react/components/CommonDataTable.jsx:124, app/resources/js/react/components/CommonDataTableV2.jsx:259
This <div role="dialog"> is a modal dialog, but nothing moves focus into it when it opens and nothing keeps focus inside it while it is open, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close. — app/resources/js/react/layouts/PopupLayout.jsx:14
What to do
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
Other · Accessibility — Whether ARIA is used correctly — valid non-abstract roles, the ARIA state a role requires, valid (non-misspelled) aria-* attribute names, in-enum values for token-typed aria-* attributes, and no aria-hidden on (or wrapping) a focusable element. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: role values checked against the WAI-ARIA role set (abstract/invalid flagged), required ARIA state for a role, and aria-hidden on a focusable element. Deterministic, role/attribute level.
Coverage: Population: elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) that carry a role or an aria-* attribute; roles and token values are checked against the ARIA enums exhaustively within that set. An expression-valued (dynamic) role or aria-* value is skipped rather than guessed, and markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
Other · Accessibility — Whether focus outlines aren't removed without a replacement, motion respects prefers-reduced-motion, and literal CSS colour pairs meet contrast — PARTIAL: inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS literals are read (hex/rgb/hsl/named), never computed/runtime/external-CDN colour. Static markup readiness, not a WCAG conformance claim.
Method: Static markup/CSS scan: inline outline:none/0, literal inline colour/background contrast against the 4.5:1 AA floor, and <style>-block animation without a prefers-reduced-motion guard. Deterministic but PARTIAL — only inline styles and in-repo CSS literals are visible.
Coverage: Population: styled elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx), plus in-repo <style> blocks, in-repo .css files and CSS-in-JS literals. Colour contrast is computed from LITERAL colour pairs only (hex/rgb/hsl/named, including var() tokens and Tailwind neutral utilities) — computed, runtime-themed and external-CDN colour is never resolved, so this is a partial read of contrast by construction. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
`.erp-search-box input:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — app/resources/css/topbar.css:21
`.menu-mobile-item` moves (`transition: transform 0.15s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — app/resources/css/app.css:120
`.popup-card` moves (`animation: fadeIn 0.2s ease-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — app/resources/css/popup.css:18
What to do
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
Do you agree with this assessment?
AC7 · A11y enforcement4.0 / 10Weak✓ Tool-verified
Other · Accessibility — Whether accessibility is ENFORCED in the toolchain — an accessibility checker configured over the markup (an a11y lint rule set, e.g. eslint-plugin-jsx-a11y or vuejs-accessibility where the project lints JavaScript) and an automated accessibility assertion wired into tests or CI (axe/pa11y/Lighthouse or an equivalent) — on the Documented→Verified→Prevented ladder.
Method: Repo config/CI scan: an accessibility checker configured over the markup (an a11y lint rule set such as eslint-plugin-jsx-a11y / vuejs-accessibility where JavaScript is linted) and an automated accessibility assertion in tests or CI (axe/pa11y/Lighthouse or equivalent), graded on the Documented→Verified→Prevented rungs. Deterministic, presence/rung detection.
Coverage: Population: the repository's own tooling configuration — lint config, test and CI files — NOT the markup. It is read for a configured accessibility checker and an automated accessibility assertion (axe/pa11y/Lighthouse, or a native-toolkit equivalent), and it credits an INVOCATION, never a mention: a licence filename, an import comment or a doc reference earns no rung. Enforcement configured entirely outside the repository leaves no evidence here and cannot be credited.
No accessibility enforcement found — no a11y linter (eslint-plugin-jsx-a11y) and no axe/pa11y/Lighthouse in tests or CI. Start with the linter to catch issues at author time. What was searched, so you can tell an absence from a miss: the 197 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here. — package.json:2
What to do
Enforce accessibility in the toolchain: add eslint-plugin-jsx-a11y, then assert with your test runner's axe binding (jest-axe, vitest-axe, cypress-axe or @axe-core/playwright) in tests, then gate axe/pa11y/Lighthouse in CI.
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.
What to do
The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
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 the codebase has a recognisable, scale-appropriate structure (a named architectural style, or modular enough for its size) rather than being an ad-hoc ball of mud.
Method: Roslyn plus csproj analysis: architecture style detection (DDD, clean, vertical-slice, CQRS) and structure fitness for repo size. Deterministic.
Do you agree with this assessment?
C1 · Data Protection1.0 / 10Critical✓ Tool-verified
Other · Security — Whether sensitive data is encrypted at rest and in transit and keys are vaulted.
Method: Roslyn plus filesystem scan: encryption presence (EF ColumnEncryption, key-vault references, HTTPS enforcement) and key-derivation KDF detection. Deterministic.
What to do
Strengthen data-at-rest protection: vault your keys (AWS KMS / Secrets Manager, GCP KMS / Secret Manager, HashiCorp Vault — not only APP_KEY in .env) and encrypt the most sensitive columns (Eloquent 'encrypted' casts, CipherSweet) — partial coverage still leaves gaps.
Enforce HTTPS (URL::forceScheme('https') / URL::forceHttps() in Laravel, or requires_channel: https / route schemes in Symfony) so data in transit is always encrypted.
Do you agree with this assessment?
C2 · Access Controls7.0 / 10Strong✓ Tool-verified
Other · Security — Whether access is authorized by default — a framework authorization attribute/decorator or policy, or imperative guard methods (throw-on-violation) called from handlers.
Method: Roslyn scan: [Authorize] usage and authorization policies, plus imperative throw-on-violation guard methods detected via syntax. Deterministic.
Authorization IS enforced here (by route guards, auth middleware or checks that refuse a caller) — this is NOT a claim that endpoints are unprotected. What's missing is a NAMED rule set: who may do what is encoded inline where it is checked, so the rules can't be listed, reviewed or tested apart from the code that applies them. Recommendation, not a defect.
What to do
Name the access rules — Gate abilities and policy classes (Gate::define, a UserPolicy), spatie/laravel-permission roles and permissions, or a Symfony Voter — and consult them where access is checked ($this->authorize, a can: middleware, #[IsGranted]), so the rule set is reviewable and testable on its own.
Other · Domain Modelling — Whether aggregates reference each other by identity (id) rather than by direct object reference — the core DDD consistency-boundary rule.
Method: Roslyn (DDD-gated): aggregate roots identified by convention; each aggregate field checked for direct references to other aggregates versus id-only. Deterministic, DDD-native.
Coverage: Population: aggregate roots identified by AggregateRoot/IAggregateRoot base/interface NAME convention; reference-by-identity then checked exhaustively within that set — a root not using those names is invisible.
Do you agree with this assessment?
DM10 · One transaction, one aggregate10.0 / 10Exemplary○ Nothing flagged
Other · Domain Modelling — Whether a single operation mutates more than one aggregate root. An aggregate is a consistency boundary, so saving two together fuses them into one — the second's invariants come to depend on the first's transaction, and the pair can no longer be separated. Reads of other aggregates are not counted.
Method: Neutral body surface (DDD-gated): every method body scanned for repository WRITE calls (Add/Update/Save/Remove/Delete/Insert/Store and their async forms), keyed on the ARGUMENT type rather than the repository type — three `IRepository<T>` writes collapse to one repository but are three distinct aggregates. Reads (Get/Find/Load/Query) are excluded, so loading another aggregate for context never counts. Score is offending methods over methods that write at all. Deterministic.
Other · Domain Modelling — Whether an aggregate can be constructed in a state its own rules forbid — a public constructor that takes a raw primitive, stores it, and validates nothing, with no factory beside it. A constructor taking only value objects is not counted: each parameter has already validated itself.
Method: Neutral surface (DDD-gated): each non-abstract entity/aggregate checked for a PUBLIC constructor taking at least one RAW PRIMITIVE parameter whose body contains no guard token (throw / Guard. / Ensure. / ArgumentException / CheckRule / an XException.ThrowIf* helper). C#: a static factory beside a public constructor does not exempt it, and a public parameterless constructor followed by public raw-primitive setters that refuse nothing is charged when the type also declares a validating way in (a guarded constructor or a guarding static method returning the type); TypeScript: a static Create/Of/From/New factory exempts the type. A constructor taking only value objects is never charged -- measured: 64 of 87 unguarded public constructors on the C# corpus take value objects only, so ignoring parameter types would be 73% false positives. One finding per entity. Deterministic.
Do you agree with this assessment?
DM12 · Ambient inputs in the domain10.0 / 10Exemplary○ Nothing flagged
Other · Domain Modelling — Whether domain types receive the time and randomness their rules depend on, rather than reading the process clock or a global random source directly — an ambient read makes the rule it feeds untestable at the instant that matters and lets two reads inside one operation disagree.
Method: Roslyn (DDD-gated, C#/VB only): domain-layer types scanned for ambient reads — DateTime/DateTimeOffset.Now/UtcNow/Today, Random.Shared, new Random(), Stopwatch.GetTimestamp — resolved against the semantic model, with a comment/string-stripped token fallback only where resolution fails. Body reads are scored; field/property initialisers are surfaced unscored. Apply/When folds excluded (ES1 owns them). Deterministic, symbol-resolved.
Do you agree with this assessment?
DM4 · Rich vs anemic model3.0 / 10Weak✓ Tool-verified
Other · Domain Modelling — Whether aggregates/entities carry the behaviour that protects their invariants, rather than being data bags driven by external services.
Method: Roslyn (DDD-gated): entity method BODIES classified mutator-vs-query — only methods that mutate the entity's own declared state count as invariant-protecting behaviour, so a getter/passthrough doesn't rescue an anemic class. Deterministic, exhaustive over domain-layer entities.
Coverage: Population: entities by name/base convention; rich-vs-anemic judged by classifying each method body mutator-vs-query — logic-bearing domain types outside the convention are invisible.
`ActivityLogModel` is an aggregate/entity with 2 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/app/Models/ActivityLogModel.php:8
`BusinessMemberShipModel` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/app/Models/BusinessMemberShipModel.php:7
`BusinessModel` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/app/Models/BusinessModel.php:7
`CategoryProductModel` is an aggregate/entity with 2 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/app/Models/CategoryProductModel.php:9
`CustomInvoiceInModel` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/app/Models/CustomInvoiceInModel.php:8
`CustomInvoiceOutModel` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/app/Models/CustomInvoiceOutModel.php:9
`CustomerGroupModel` is an aggregate/entity with 2 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/app/Models/CustomerGroupModel.php:8
`CustomerModel` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/app/Models/CustomerModel.php:9
`ExtensionModel` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/app/Models/ExtensionModel.php:7
`ImageModel` is an aggregate/entity with 2 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/app/Models/ImageModel.php:8
`InventoryAdjustmentModel` is an aggregate/entity with 2 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/app/Models/InventoryAdjustmentModel.php:8
`InvoiceInModel` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/app/Models/InvoiceInModel.php:9
`InvoiceOutModel` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/app/Models/InvoiceOutModel.php:10
`NotificationModel` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/app/Models/NotificationModel.php:10
`OrderCancelModel` is an aggregate/entity with 2 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/app/Models/OrderCancelModel.php:7
`OrderItemModel` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/app/Models/OrderItemModel.php:10
`OrderModel` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/app/Models/OrderModel.php:8
`PermissionGroupModel` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/app/Models/PermissionGroupModel.php:7
`PermissionGroupUserModel` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/app/Models/PermissionGroupUserModel.php:7
`PermissionModel` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/app/Models/PermissionModel.php:7
`PriceListModel` is an aggregate/entity with 2 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/app/Models/PriceListModel.php:8
`ProductModel` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/app/Models/ProductModel.php:10
`PurchaseCancelModel` is an aggregate/entity with 2 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/app/Models/PurchaseCancelModel.php:7
`PurchaseItemModel` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/app/Models/PurchaseItemModel.php:10
`PurchaseModel` is an aggregate/entity with 4 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/app/Models/PurchaseModel.php:8
`ShippingModel` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/app/Models/ShippingModel.php:8
`ShippingProviderModel` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/app/Models/ShippingProviderModel.php:8
`StockInModel` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/app/Models/StockInModel.php:12
`StockMovementInModel` is an aggregate/entity with 2 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/app/Models/StockMovementInModel.php:7
`StockMovementOutModel` is an aggregate/entity with 2 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/app/Models/StockMovementOutModel.php:7
`StockOutModel` is an aggregate/entity with 2 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/app/Models/StockOutModel.php:10
`SupplierModel` is an aggregate/entity with 4 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/app/Models/SupplierModel.php:8
`WarehouseModel` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/app/Models/WarehouseModel.php:8
`AppSSLModel` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — extension-examples/AppSSL/Models/AppSSLModel.php:7
`CategoryProductThumbnailModel` is an aggregate/entity with 2 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — extension-examples/CategoryProductThumbnail/Models/CategoryProductThumbnailModel.php:7
`CustomBusinessRoleModel` is an aggregate/entity with 2 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — extension-examples/CustomBusinessRole/Models/CustomBusinessRoleModel.php:7
`CustomHomePageModel` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — extension-examples/CustomHomePage/Models/CustomHomePageModel.php:7
`ExampleModel` is an aggregate/entity with 2 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. (×3) — extension-examples/CustomInvoiceIn/Models/ExampleModel.php:7, extension-examples/CustomInvoiceOut/Models/ExampleModel.php:7, extension-examples/CustomerFax/Models/ExampleModel.php:7
What to do
Move business rules onto the aggregates/entities they govern so invariants are enforced at the source, not in anemic services.
Other · Domain Modelling — Whether entities protect their state — private/init-only setters, and collections handed out as read-only views rather than the mutable backing collection — instead of exposing writable state that bypasses invariants. Softened when a rehydration framework (Marten/EF) is present.
Method: Roslyn (DDD-gated): entities scanned for publicly writable state — public setters, and (C#/VB) own mutable collections handed out through an auto-property, a public field or a bare-field expression getter, where a computed/copying getter is never charged. One finding per entity; score softened when Marten/EF rehydration frameworks present. Deterministic, framework-aware.
Coverage: Population: entities by convention; encapsulation (setter shape) checked exhaustively within the set.
`BusinessMemberShipModel` exposes publicly writable state (table). — app/app/Models/BusinessMemberShipModel.php:7
`BusinessModel` exposes publicly writable state (table). — app/app/Models/BusinessModel.php:7
`ExtensionModel` exposes publicly writable state (table). — app/app/Models/ExtensionModel.php:7
`PermissionGroupModel` exposes publicly writable state (table). — app/app/Models/PermissionGroupModel.php:7
`PermissionGroupUserModel` exposes publicly writable state (table). — app/app/Models/PermissionGroupUserModel.php:7
`PermissionModel` exposes publicly writable state (table). — app/app/Models/PermissionModel.php:7
`WarehouseModel` exposes publicly writable state (table). — app/app/Models/WarehouseModel.php:8
`SupplierFaxModel` exposes publicly writable state (table). — extension-examples/SupplierFax/Models/SupplierFaxModel.php:7
What to do
Make entity setters private/init-only and hand collections out as IReadOnlyList/IReadOnlyCollection over a private backing field; change state only through methods that enforce the invariants (Marten/EF can bind via constructor or private setters).
Other · Domain Modelling — Whether the domain layer stays free of infrastructure dependencies (EF/Marten/HTTP/ASP.NET) — the clean-architecture dependency rule.
Method: Roslyn (DDD-gated): domain-layer types scanned for infrastructure usage in member SIGNATURES and inside method/accessor BODIES — resolved calls and object-creations into EF/Marten/HTTP/Mongo/Redis/message-bus types (not just a namespace allowlist). Deterministic, symbol-resolved, exhaustive over domain-layer bodies, DDD-native.
Coverage: Domain layer identified by NAMESPACE heuristic; infrastructure then resolved by symbol in member SIGNATURES and method/accessor BODIES — rename the layer and the check evaporates.
Other · Domain Modelling — Whether one domain rule is decided — or one measurement produced — in more than one place, rather than living on the type that owns it.
Method: Neutral body surface plus Roslyn (DDD-gated), two arms. DECISION (Roslyn only): a predicate over a domain type's members judged in two or more types, where none of those decisions live on the owning type — operands of comparisons and relational property patterns only, so a member merely passed as an argument is not judged. DERIVATION: a plain all-numeric carrier of ≥2 members, with no base type and exactly one constructor, CONSTRUCTED as the result of a method (returned or assigned, never inline as an argument) in two or more types other than its own — the same measurement produced twice, which centralising the judgement does not fix. DERIVATION runs on every language whose frontend declares the produced-or-passed fact per construction (Roslyn and the Java sidecar today); a target with only the derivation arm carries an engine gap naming the decision arm as not assessed, and a frontend that declares nothing keeps the dimension not measured rather than clean. Single-member rules, test code and generated code are out of population for both. Advisory.
Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
36 code files changed in the last 6 months but the README was not touched — it may no longer reflect the system.
What to do
Add a README to the 1 of 1 project(s) that lack one — worth up to 2 pts.
Review the README against recent changes; refresh the parts that drifted.
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 repo is organised deliberately — src/test separation and consistent project naming.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Production code isn't grouped under a src/ folder — it's spread across several top-level directories, so there's no one place that says 'this is the product'.
What to do
Group production code under src/ (or split deliberately, e.g. backend/ + frontend/) so production and tooling code aren't mixed at the root.
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) as a CI step. What was searched, so you can tell an absence from a miss: the 2348 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:2
What to do
Add a SAST step to CI running what this repository's stack ships: phpstan or psalm — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
Deployment is orchestrated by compose, but no service declares a `healthcheck:` and nothing pins a previous image to fall back to — the runtime can tell that the container is up, not that it is serving, so a bad release is harder to detect and reverse.
What to do
Add a `healthcheck:` to the served compose service — probing the endpoint it already answers on where it has one — with `depends_on: condition: service_healthy` on whatever waits for it, and keep the deployed image tag immutable and recorded so rolling back is re-pointing at the previous tag rather than rebuilding.
Add an approval/environment gate (required reviewers / protection rules) before production promotion.
Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.
Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.
What to do
Stamp a version in your build/package manifest (e.g. csproj <Version>, package.json, pyproject.toml, Cargo.toml, or a VERSION file) or tag releases with semver so builds and releases are traceable.
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 Safety0.0 / 10Critical✓ Tool-verified
React / JS · Code Health — How much of the frontend is typed TypeScript vs untyped JavaScript.
Method: Frontend file inventory: the share of typed TypeScript vs untyped JavaScript across the source tree. Deterministic, exhaustive over frontend files.
0 typed · 269 plain JS — the untyped files are app/resources/js/admin.jsx, app/resources/js/app.js, app/resources/js/core/Extension.js, app/resources/js/core/PermissionNode.js, app/resources/js/core/RegisterRoute.js, app/resources/js/core/RouteRegistry.js (+263 more).
What to do
Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.
React / JS · Code Health — Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm over JS/TS tokens, D-386): a block is reported only where its copies still agree on most of their own identifiers and literals, or were renamed as they were pasted but kept most of their constants, and where the copies carry enough code to stand on their own or the copied extent reaches 30 lines — so a re-implementation sharing neither names nor values, and a small pasted declaration, are both found and deliberately not reported, and a clean R10 is not a claim that nothing was copied.
Method: Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm run over JS/TS tokens). Masking finds the candidates; a block is reported when its copies still agree on most of their own identifiers and literals, or when a renamed copy still agrees on most of its constants, AND the copies carry enough code to stand on their own — or when the copied extent reaches 30 lines. So a re-implementation sharing neither names nor values, and a small pasted declaration, are deliberately not counted. Deterministic.
37 duplicated blocks under app/resources/js/react/components/ have copies in at least two of the sibling directories Customer, Inventory, Invoice, Order, Product, Purchases (+1 more sibling(s) not listed) — 27 of them are reported below, and 10 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 37 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 37 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 37 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. — app/resources/js/react/components/Order/ListOrder.jsx:15
27 duplicated blocks under app/resources/js/react/ have copies in at least two of the sibling directories components, layouts, pages — 20 of them are reported below, and 7 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 27 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 27 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 27 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — app/resources/js/react/components/Inventory/IndexInventoryAdjustment.jsx:26
9 of the duplicated blocks reported below have copies in at least two of the sibling directories InvoiceIns, InvoiceOuts under app/resources/js/react/components/Invoice/. That concentration is one structural fact, not 9 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 9 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — app/resources/js/react/components/Invoice/InvoiceIns/InvoiceInDetail.jsx:32
5 duplicated blocks under app/resources/js/react/components/Stock/ have copies in at least two of the sibling directories StockInDetail, StockOutDetail — 4 of them are reported below, and 1 is counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 5 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 5 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 5 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. — app/resources/js/react/components/Stock/StockInDetail/ProductTable.jsx:3
app/resources/js/react/components/Invoice/IndexCustomInvoiceIns.jsx:1 · app/resources/js/react/components/Invoice/IndexCustomInvoiceOuts.jsx:1 — these 2 files are line-for-line copies of one another — 228 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. — app/resources/js/react/components/Invoice/IndexCustomInvoiceIns.jsx:1
extension-examples/Hrm/Resources/js/components/IndexLeave.jsx:1 · extension-examples/Hrm/Resources/js/components/LeaveApprovalList.jsx:1 — these 2 files are line-for-line copies of one another — 185 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. — extension-examples/Hrm/Resources/js/components/IndexLeave.jsx:1
extension-examples/Hrm/Resources/js/components/IndexTimeAttendance.jsx:1 · extension-examples/Hrm/Resources/js/components/TimeAttendance.jsx:1 — these 2 files are line-for-line copies of one another — 185 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. — extension-examples/Hrm/Resources/js/components/IndexTimeAttendance.jsx:1
extension-examples/Hrm/Resources/js/components/EndOfDayReportForm.jsx:1 · extension-examples/Hrm/Resources/js/components/IndexReport.jsx:1 — these 2 files are line-for-line copies of one another — 158 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. — extension-examples/Hrm/Resources/js/components/EndOfDayReportForm.jsx:1
app/resources/js/react/components/Product/AddProduct.jsx:2 · app/resources/js/react/components/Product/UpdateProduct.jsx:2 — these 2 files are line-for-line copies of one another — 134 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. — app/resources/js/react/components/Product/AddProduct.jsx:2
app/resources/js/react/components/Stock/StockList/IndexStockIns.jsx:13 · app/resources/js/react/components/Stock/StockList/IndexStockOuts.jsx:13 — the two spans are one implementation copied and then locally edited — 554 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. — app/resources/js/react/components/Stock/StockList/IndexStockIns.jsx:13
app/resources/js/react/components/Order/ListOrder.jsx:15 · app/resources/js/react/components/Purchases/ListPurchases.jsx:17 — the two spans are one implementation copied and then locally edited — 517 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. — app/resources/js/react/components/Order/ListOrder.jsx:15
app/resources/js/react/components/CommonDataTable.jsx:26 · app/resources/js/react/components/CommonDataTableV2.jsx:138 — the two spans are one implementation copied and then locally edited — 680 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. — app/resources/js/react/components/CommonDataTable.jsx:26
app/resources/js/react/components/Customer/ListCustomer.jsx:47 · app/resources/js/react/components/Customer/ListGroup.jsx:45 — the two spans are one implementation copied and then locally edited — 477 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. — app/resources/js/react/components/Customer/ListCustomer.jsx:47
app/resources/js/react/components/Product/Category.jsx:179 · app/resources/js/react/components/Product/IndexPriceList.jsx:144 — the two spans are one implementation copied and then locally edited — 444 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. — app/resources/js/react/components/Product/Category.jsx:179
app/resources/js/react/components/Invoice/IndexInvoiceIns.jsx:64 · app/resources/js/react/components/Invoice/IndexInvoiceOuts.jsx:65 — the two spans are one implementation copied and then locally edited — 403 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. — app/resources/js/react/components/Invoice/IndexInvoiceIns.jsx:64
app/resources/js/react/components/Invoice/InvoiceIns/InvoiceInDetail.jsx:32 · app/resources/js/react/components/Invoice/InvoiceOuts/InvoiceOutsDetail.jsx:31 — 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. — app/resources/js/react/components/Invoice/InvoiceIns/InvoiceInDetail.jsx:32
app/resources/js/react/components/Order/AddOrder.jsx:32 · app/resources/js/react/components/Purchases/AddPurchase.jsx:33 — the two spans are one implementation copied and then locally edited — 294 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. — app/resources/js/react/components/Order/AddOrder.jsx:32
extension-examples/Hrm/Resources/js/components/IndexMonthlyAttendanceSummary.jsx:7 · extension-examples/Hrm/Resources/js/components/MonthlyAttendanceSummary.jsx:7 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — extension-examples/Hrm/Resources/js/components/IndexMonthlyAttendanceSummary.jsx:7
app/resources/js/react/components/Invoice/InvoiceOuts/InvoiceOutsDetail.jsx:135 · app/resources/js/react/components/Stock/StockOutDetail.jsx:171 — 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. — app/resources/js/react/components/Invoice/InvoiceOuts/InvoiceOutsDetail.jsx:135
app/resources/js/react/components/Inventory/IndexInventory.jsx:11 · app/resources/js/react/components/Inventory/IndexInventoryAdjustment.jsx:42 — the two spans are one implementation copied and then locally edited — 261 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. — app/resources/js/react/components/Inventory/IndexInventory.jsx:11
app/resources/js/react/components/Product/Category.jsx:48 · app/resources/js/react/components/Product/Category.jsx:95 — 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. — app/resources/js/react/components/Product/Category.jsx:48
app/resources/js/react/components/Stock/StockOutDetail/CustomerInfo.jsx:4 · app/resources/js/react/components/Stock/StockOutDetail/ShippingInformation.jsx:6 — the two spans are one implementation copied and then locally edited — 291 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. — app/resources/js/react/components/Stock/StockOutDetail/CustomerInfo.jsx:4
app/resources/js/react/components/Inventory/IndexInventoryAdjustment.jsx:26 · app/resources/js/react/pages/warehouse.jsx:21 — the two spans are one implementation copied and then locally edited — 212 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. — app/resources/js/react/components/Inventory/IndexInventoryAdjustment.jsx:26
app/resources/js/react/components/UI/Input/GalleryImage.jsx:5 · app/resources/js/react/components/UI/Input/UploadImage.jsx:4 — the two spans are one implementation copied and then locally edited — 230 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. — app/resources/js/react/components/UI/Input/GalleryImage.jsx:5
app/resources/js/react/pages/suppliers.jsx:292 · app/resources/js/react/pages/suppliers.jsx:334 — all 2 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — app/resources/js/react/pages/suppliers.jsx:292
app/resources/js/react/components/Invoice/InvoiceIns/InvoiceInDetail.jsx:173 · app/resources/js/react/components/Invoice/InvoiceOuts/InvoiceOutsDetail.jsx:191 — 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. — app/resources/js/react/components/Invoice/InvoiceIns/InvoiceInDetail.jsx:173
app/resources/js/react/pages/login.jsx:40 · app/resources/js/react/pages/register.jsx:45 — the two spans are one implementation copied and then locally edited — 233 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. — app/resources/js/react/pages/login.jsx:40
app/resources/js/react/components/Invoice/InvoiceOuts/InvoiceOutsDetail.jsx:304 · app/resources/js/react/components/Stock/StockOutDetail/ShippingInformation.jsx:54 — 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. — app/resources/js/react/components/Invoice/InvoiceOuts/InvoiceOutsDetail.jsx:304
app/resources/js/react/pages/reset-password.jsx:6 · app/resources/js/react/pages/verify-account.jsx:6 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — app/resources/js/react/pages/reset-password.jsx:6
app/resources/js/react/components/Invoice/InvoiceIns/InvoiceInDetail.jsx:405 · app/resources/js/react/components/Invoice/InvoiceOuts/InvoiceOutsDetail.jsx:469 — 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. — app/resources/js/react/components/Invoice/InvoiceIns/InvoiceInDetail.jsx:405
app/resources/js/react/components/Order/DetailOrder/ProductAdded.jsx:12 · app/resources/js/react/components/Order/EditOrder/Products/ProductAdded.jsx:27 — the two spans are one implementation copied and then locally edited — 118 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. — app/resources/js/react/components/Order/DetailOrder/ProductAdded.jsx:12
app/resources/js/react/components/Customer/ListCustomer.jsx:81 · app/resources/js/react/pages/suppliers.jsx:56 — 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. — app/resources/js/react/components/Customer/ListCustomer.jsx:81
app/resources/js/react/components/Invoice/InvoiceOuts/InvoiceOutsDetail.jsx:370 · app/resources/js/react/components/Stock/StockOutDetail.jsx:312 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — app/resources/js/react/components/Invoice/InvoiceOuts/InvoiceOutsDetail.jsx:370
app/resources/js/react/components/Stock/StockInDetail.jsx:139 · app/resources/js/react/components/Stock/StockInDetail.jsx: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. — app/resources/js/react/components/Stock/StockInDetail.jsx:139
app/resources/js/react/pages/forget-password.jsx:10 · app/resources/js/react/pages/register.jsx:11 — the two spans are one implementation copied and then locally edited — 201 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. — app/resources/js/react/pages/forget-password.jsx:10
app/resources/js/react/pages/suppliers.jsx:90 · app/resources/js/react/pages/suppliers.jsx:130 — 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. — app/resources/js/react/pages/suppliers.jsx:90
app/resources/js/react/pages/setting.jsx:85 · app/resources/js/react/pages/setting.jsx:117 · app/resources/js/react/pages/setting.jsx:164 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. — app/resources/js/react/pages/setting.jsx:85
app/resources/js/react/common/api-upload.js:9 · app/resources/js/react/common/api.js:9 — 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. — app/resources/js/react/common/api-upload.js:9
app/resources/js/react/components/UI/PermissionButtons/ApproveButton.jsx:6 · app/resources/js/react/components/UI/PermissionButtons/CancelButton.jsx:5 · app/resources/js/react/components/UI/PermissionButtons/DeleteButton.jsx:5 · app/resources/js/react/components/UI/PermissionButtons/UpdateButton.jsx:5 — the 4 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 4 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. — app/resources/js/react/components/UI/PermissionButtons/ApproveButton.jsx:6
app/resources/js/react/common/api-upload.js:1 · app/resources/js/react/common/authApi.js:1 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — app/resources/js/react/common/api-upload.js:1
What to do
Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
React / JS · Architecture — Conformance to the detected frontend architecture layout (feature-sliced / layered src) plus cross-package deep-import rules (D-386).
Method: Conformance to the detected frontend layout (feature-sliced / layered src) plus cross-package deep-import rules, over the module graph. Deterministic.
app/resources/css/app.css:2 reaches into another package with a relative path (../../node_modules/bootstrap-icons/font/bootstrap-icons.css) — import the package by name instead. — app/resources/css/app.css:2
What to do
Fix the listed violations: import through public entries (package exports / slice index), never reach into another layer or package's internals.
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.
CommonDataTableV2 has cyclomatic complexity 21 and cognitive complexity 24; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — app/resources/js/react/components/CommonDataTableV2.jsx:11
EditPurchase has cyclomatic complexity 19 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — app/resources/js/react/components/Purchases/EditPurchase.jsx:27
InvoiceOutDetail 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. — app/resources/js/react/components/Invoice/InvoiceOuts/InvoiceOutsDetail.jsx:24
EditOrder 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. — app/resources/js/react/components/Order/EditOrder.jsx:27
StockInDetail 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. — app/resources/js/react/components/Stock/StockInDetail.jsx:26
StockOutDetail 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. — app/resources/js/react/components/Stock/StockOutDetail.jsx:29
InvoiceInDetail 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. — app/resources/js/react/components/Invoice/InvoiceIns/InvoiceInDetail.jsx:22
InputForm 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. — app/resources/js/react/components/UI/Input/InputForm.jsx:2
ListProducts 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. — app/resources/js/react/components/Purchases/AddProduct/ListProduct.jsx:20
(anonymous) has cyclomatic complexity 11 and cognitive complexity 9; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — app/resources/js/react/components/CommonDataTableV2.jsx:175
What to do
Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.
Do you agree with this assessment?
R3 · Large Files8.8 / 10Strong✓ Tool-verified
React / JS · Code Health — How many source files exceed the large-file threshold.
Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.
app/resources/js/react/components/Invoice/InvoiceOuts/InvoiceOutsDetail.jsx has 510 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — app/resources/js/react/components/Invoice/InvoiceOuts/InvoiceOutsDetail.jsx:1
app/resources/js/i18n/locales/en.js 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. — app/resources/js/i18n/locales/en.js:1
app/resources/js/react/components/Purchases/AddProduct/ListProduct.jsx has 493 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — app/resources/js/react/components/Purchases/AddProduct/ListProduct.jsx:1
app/resources/js/react/components/Invoice/InvoiceIns/InvoiceInDetail.jsx has 442 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — app/resources/js/react/components/Invoice/InvoiceIns/InvoiceInDetail.jsx:1
app/resources/js/react/components/Stock/StockInDetail.jsx has 413 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — app/resources/js/react/components/Stock/StockInDetail.jsx:1
app/resources/js/react/components/Stock/StockOutDetail.jsx has 407 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — app/resources/js/react/components/Stock/StockOutDetail.jsx:1
What to do
Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
Do you agree with this assessment?
R4 · Test Coverage0.0 / 10Critical✓ Tool-verified
React / JS · Readiness — Static test reachability (D-386): the share of production files reachable from any test via the import graph — measured without running anything.
Method: Static test reachability: the share of production files reachable from any test via the import graph — measured without running anything. Deterministic.
0% of 251 production file(s) reachable from 0 test file(s) via the import graph — 'production' here is the RESIDUE: every source file left once tests, tooling, generated output, config, declarations and declaration-only modules, fixture corpora, type fixtures, behaviour-free data modules, re-export barrels, registration/constant data modules and service workers are set aside, so the percentage is taken over a smaller denominator than the workspace's file count
What to do
Add tests that import the unreached modules (directly or through their public entry).
React / JS · Readiness — How outdated the npm dependencies are (a maturity signal). JS/npm CVEs are scored separately in D30 (JS/npm Dependency Vulnerabilities).
Method: npm dependency staleness from manifest/registry metadata (a maturity signal; JS/npm CVEs are scored separately in D30, which answers dependency vulnerabilities for every ecosystem). Deterministic.
What to do
Bump outdated dependencies to current versions to limit upgrade debt.
Do you agree with this assessment?
R6 · Tooling0.0 / 10Critical✓ Tool-verified
React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each package.json script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.
Method: package.json scanned for test/lint/typecheck script wiring. Deterministic presence check.
test ✗ · lint ✗ · typecheck ✗ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
What to do
Add a test runner (vitest / jest / playwright) and eslint and type checking (adopt TypeScript, or type-check the existing JavaScript with `checkJs`) as package.json scripts and run them in CI.
Do you agree with this assessment?
R7 · Dead Code8.0 / 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.
44 file(s) (~2914 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package.
Unreachable from the 7 application, 1 tooling and 0 test entry point(s) detected in this repo. Gate removals on `npm run build` — an undetected custom entry would make these reachable.
no import path from any entry point (7 application, 1 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make (×20) — app/resources/js/react/pages/report.jsx, app/resources/js/react/components/Order/DetailOrder/ShippingForm.jsx, app/resources/js/react/components/AutoDataTable.jsx, …
no import path from any entry point (7 application, 1 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app/resources/js/react/components/RenderTableSearch.jsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — app/resources/js/react/components/UI/Input/SearchInput.jsx
Nothing imports this binding — it is safe to review for removal. (×4) — app/resources/js/react/libraries/common.js:21, app/resources/js/react/redux/NotificationSlice.js:29, app/resources/js/react/redux/businessInfoSlice.js:33, …
What to do
Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
React / JS · Readiness — npm dependency truthfulness (D-386): unused dependencies, imports not declared anywhere, and type-/test-only packages shipped as production deps.
Method: npm dependency truthfulness: unused dependencies, imports declared nowhere, and type-/test-only packages shipped as production deps — from the manifest + import graph. Deterministic.
Imported but not declared in any reachable package.json — installs work only by hoisting accident. — extension-examples/CustomHomePage/Resources/js/app.jsx:1
Declared in app/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. (×3)
What to do
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.
Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.
Other · Security — Only what this repository's own non-C# files could be read for was assessed — and because this repository commits the configuration that serves its own HTTP surface, that configuration could be read in full for the security response headers it sets. Nothing else in this dimension was assessed: the transport, cookie, input-validation and crypto controls are read from a source model that was not loaded for this repository’s language, so their absence here is not a finding about this repository.
Method: Roslyn plus filesystem scan: HSTS/security headers, secure cookies, input validation, middleware order, weak crypto (MD5/SHA1/DES); HTTPS-metadata context-aware. On a repository with no .NET source it reads JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Elixir source itself (test, vendored, generated and minified paths not) for the arms that hold whether or not the code serves HTTP: a weak hash or cipher, key material fixed in the source, a TLS client that accepts any certificate, and (JavaScript/TypeScript, Ruby, Scala, Rust and Elixir) an obsolete TLS version; the server controls are not assessed there, and a Dart, Ruby, Scala, Rust or Elixir repository that serves no HTTP of its own is N/A on them. Deterministic.
None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. This is reported because `host.conf` is committed to this repository and declares the server that serves it, so the configuration that would carry these headers is in this repository and was read in full. (−2.0 on this card.) — docker-config/host.conf:1
What to do
Set security response headers on the surface this repository serves: an `add_header` directive per header in the nginx/Caddy/Apache config, a `_headers` / `vercel.json` / `netlify.toml` entry for a static host, or `helmet()` in the HTTP server. `Content-Security-Policy` is the one that pays for itself first — it is what contains an injected script once one reaches the page — followed by `X-Content-Type-Options: nosniff` and a frame policy (`X-Frame-Options: DENY`, or CSP `frame-ancestors`). Where the app is served from a build container, the header configuration belongs in the image beside the built assets, so it ships with them rather than depending on where it lands.
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.
Do you agree with this assessment?
X13 · Undrained process stream10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.
Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.
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.
Do you agree with this assessment?
X15 · Unvalidated length from an untrusted reader10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether a length read out of the stream being parsed is bounded before it is allocated or read — an unchecked count taken from the input lets the input choose the allocation.
Method: Roslyn syntax + semantics: integer lengths read from a BinaryReader and spent on a bulk read or an array allocation, checked for any comparison or bounding call on the value anywhere in the method. 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.
Do you agree with this assessment?
X17 · Uncapped recursion over a caller-supplied document10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether a walk that recurses through a JSON/XML tree handed in by its caller bounds how deep it will go — an uncapped walk lets the document's nesting choose the stack depth, and the resulting StackOverflowException cannot be caught.
Method: Roslyn syntax + semantics: methods that take a JSON/XML document node and call themselves with a child of it, reachable from an externally-callable member of the same type that accepts a document, checked for any depth parameter, descent counter or threaded arithmetic anywhere in the walk. On a repository with no .NET source it reads TypeScript off the engine’s own token stream (test, vendored, generated and minified paths and `.d.ts` not) with the same rule: a function or method with a parameter typed as a document value — `unknown`, `any`, `object`, `Record<string, unknown|any>`, a JSON alias (`JsonValue`, `JSONObject`, …) or a DOM node global the file does not rebind — that calls itself (bare, or through `this` for a method, or hands itself to a call over the value as in `value.map(walk)`) with something it took out of that value and never through an ancestor accessor such as `closest()` or `parentElement`, that is exported or reached from an exported function (a public method of the same exported class) taking such a value, and that names no depth, level, nesting, recursion, remaining or budget anywhere and threads no `+`/`-` arithmetic through a self-call. Plain JavaScript is not read: with no annotation nothing tells a parsed document from a tree the code built itself. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.
Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.
Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. Deterministic, provable per finding. Advisory.
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 a method that TAKES a lock or semaphore and gives it back from a flag-guarded `finally` returns the value that flag implies — reporting success while the guard hands the primitive back admits a second caller the exclusion was there to keep out, and reporting failure while the guard keeps it leaves nothing to ever give it back. Also whether a `finally` that gives the primitive back unconditionally can run in a state where the method does not hold it: after a timed wait whose result was discarded, after an acquire inside the `try` that can fail, after the body already released it, or never, because a `return` left between the acquire and the `try`.
Method: Roslyn syntax: `try` statements whose `finally` releases a synchronisation primitive under a bare local-bool guard, where the method also TOOK that same primitive before the `try`, checked for a `return` of a bool literal whose value disagrees with the flag state the method's own straight-line assignments put it in. 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 unescaped2.0 / 10Critical✓ 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.
`link.label` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` 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. — app/resources/js/react/components/AutoDataTable.jsx:90
`item.label` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` 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) — app/resources/js/react/components/CommonDataTable.jsx:124, app/resources/js/react/components/CommonDataTableV2.jsx:259
`data` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` 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. — app/resources/js/react/components/RenderFieldTableByList.jsx:21
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. (×7) — app/resources/js/react/pages/activity-logs.jsx:23, app/resources/js/react/pages/user.jsx:36, app/resources/js/react/components/Purchases/EditPurchase/PurchaseInformation.jsx:35, …
`.catch((error) => {})` 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. (×23) — app/resources/js/react/pages/user.jsx:186, app/resources/js/react/layouts/DashboardLayout.jsx:25, app/resources/js/react/components/NotificationList.jsx:25, …
`catch (\Throwable)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — app/core/Extension/Infrastructure/Repositories/EloquentExtensionRepository.php:118
What to do
Swallowed exception (empty catch)
Do you agree with this assessment?
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.
Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.
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.
`warning` at line 79 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/app/Providers/AppServiceProvider.php:79
`error` 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->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/app/Providers/AppServiceProvider.php:88
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 15 of 55 WCAG 2.2 Level A/AA success criteria (27%; ≈30% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 40 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 3 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
X10 Duplicated predicate — 16 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 2 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 — Repo shows no audit-logging mechanism (an audit-log table or model, a change-history library on the models — spatie/laravel-activitylog's LogsActivity, owen-it/laravel-auditing's Auditable, venturecraft/revisionable, Gedmo Loggable — or an Eloquent model event, observer or Doctrine listener that records each change) for sensitive changes — absence of evidence is not evidence of a working control. Record an audit trail in code (or document where it lives) so this dimension can be scored.
C4 Data Retention — Repo shows no data-retention / TTL / cleanup mechanism for personal data — absence of evidence is not evidence of a working control. Define retention periods and a purge/cleanup job (or TTL) in code, or document where retention is enforced, so this dimension can be scored.
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 — 46 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AX1 Captive dependencies — not 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).
AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX8 Test isolation — no test/production split to check
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — compose up failed (exit 17 — an image could not be built) — failed to solve: process "/bin/sh -c apt-get update && apt-get install -y ca-certificates libicu-dev unzip nodejs && update-ca-certificates && docker-php-ext-install intl && pecl install redis && docker-php-ext-enable redis" did not complete successfully: exit code: 1; 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.
D11 Test Reliability — Test reliability not included — no .php test 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.
D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; JavaScript, PHP not measured.
D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Aggregate roots were found in only one source directory (extension-examples), 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 — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .php source were not judged.
D25 ADR Conformance — no ADRs to check
D32 Data Compliance (PII/GDPR) — 2 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D5 Coupling — Not applicable — this Composer build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
D8 Code Coverage — Coverage not included — suite not readable by the collector
DM2 Strongly-typed ids — no id-bearing domain types detected — strongly-typed-id adoption not assessable
DM3 Integration-event coupling — no integration events detected — coupling check not applicable
DM7 Repository granularity — no repository abstraction detected (e.g. uses a document session)
DM8 Value-object opportunities — not scored — the deterministic rule found 0 candidate clump(s); its rows are withheld until it has a measured precision of 95 % (a sample of fewer than 10 rows cannot show one)
ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
M4 Documentation accuracy — Not applicable: the 34 current-state document(s) make no claim of a kind M4 checks. 3 claim(s) of kinds M4 does not check were not checked (environment variable 3); M4 checks only links and versions and artefact counts.
P7 Outbound HTTP resilience — no outbound HTTP usage detected — no HTTP client call or construction in the JavaScript/TypeScript, PHP source (service entry point: app/routes/api.php:6 (Route::get())
P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (Clover XML — with Xdebug (`XDEBUG_MODE=coverage`) or PCOV installed, `vendor/bin/phpunit --coverage-clover coverage.xml`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for PHPBench subjects (`bench*` methods, or `@Subject`/`#[Subject]` ones) in a file importing PhpBench or carrying its annotations, `bench*` methods in a `*Bench.php` file where PHPBench is installed, or phpbench/phpbench in a composer.json or a phpbench.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.
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X2 Cancellation propagation — no C# was loaded; this repository's PHP was read and makes no request a caller can cancel (amphp's HttpClient or connect) — synchronous PHP offers its callers no cancellation to take
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.
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 — 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
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.
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
Critical — 99 finding(s)
AC2 · Forms & labels· <label> that labels no control · ×26
<label> that labels no control app/resources/js/react/components/Invoice/IndexCustomInvoiceIns.jsx:255— This <label> has no htmlFor 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 htmlFor="<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 app/resources/js/react/components/Invoice/IndexCustomInvoiceIns.jsx:264— This <label> has no htmlFor 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 htmlFor="<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 app/resources/js/react/components/Invoice/IndexCustomInvoiceIns.jsx:282— This <label> has no htmlFor 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 htmlFor="<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 app/resources/js/react/components/Invoice/IndexCustomInvoiceIns.jsx:291— This <label> has no htmlFor 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 htmlFor="<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 app/resources/js/react/components/Invoice/IndexCustomInvoiceIns.jsx:300— This <label> has no htmlFor 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 htmlFor="<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 app/resources/js/react/components/Invoice/IndexCustomInvoiceIns.jsx:309— This <label> has no htmlFor 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 htmlFor="<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 app/resources/js/react/components/Invoice/IndexCustomInvoiceIns.jsx:323— This <label> has no htmlFor 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 htmlFor="<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 app/resources/js/react/components/Invoice/IndexCustomInvoiceOuts.jsx:282— This <label> has no htmlFor 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 htmlFor="<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 app/resources/js/react/components/Invoice/IndexCustomInvoiceOuts.jsx:291— This <label> has no htmlFor 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 htmlFor="<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 app/resources/js/react/components/Invoice/IndexCustomInvoiceOuts.jsx:309— This <label> has no htmlFor 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 htmlFor="<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 app/resources/js/react/components/Invoice/IndexCustomInvoiceOuts.jsx:318— This <label> has no htmlFor 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 htmlFor="<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 app/resources/js/react/components/Invoice/IndexCustomInvoiceOuts.jsx:327— This <label> has no htmlFor 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 htmlFor="<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 app/resources/js/react/components/Invoice/IndexCustomInvoiceOuts.jsx:336— This <label> has no htmlFor 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 htmlFor="<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 app/resources/js/react/components/Invoice/IndexCustomInvoiceOuts.jsx:350— This <label> has no htmlFor 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 htmlFor="<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 app/resources/js/react/components/Invoice/InvoiceIns/InvoiceInDetail.jsx:434— This <label> has no htmlFor 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 htmlFor="<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 app/resources/js/react/components/Order/DetailOrder/ShippingForm.jsx:98— This <label> has no htmlFor 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 htmlFor="<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 app/resources/js/react/components/Order/DetailOrder/ShippingForm.jsx:109— This <label> has no htmlFor 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 htmlFor="<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 app/resources/js/react/components/Order/DetailOrder/ShippingForm.jsx:120— This <label> has no htmlFor 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 htmlFor="<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 app/resources/js/react/components/Order/DetailOrder/ShippingForm.jsx:131— This <label> has no htmlFor 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 htmlFor="<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 app/resources/js/react/components/Order/DetailOrder/ShippingForm.jsx:142— This <label> has no htmlFor 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 htmlFor="<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 app/resources/js/react/components/Order/EditOrder.jsx:326— This <label> has no htmlFor 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 htmlFor="<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 app/resources/js/react/components/Order/EditOrder/Products.jsx:192— This <label> has no htmlFor 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 htmlFor="<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 app/resources/js/react/components/Order/EditOrder/Products.jsx:198— This <label> has no htmlFor 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 htmlFor="<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 app/resources/js/react/components/Order/EditOrder/Products.jsx:206— This <label> has no htmlFor 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 htmlFor="<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 app/resources/js/react/components/Order/EditOrder/Products.jsx:212— This <label> has no htmlFor 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 htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
AC4 · Keyboard semantics· Click handler on a non-interactive <div> · ×7
Click handler on a non-interactive <div> app/resources/js/react/components/NotificationList.jsx:129— 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> app/resources/js/react/components/NotificationList/ListItem.jsx:44— 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> app/resources/js/react/components/Purchases/EditPurchase/PurchaseInformation.jsx:69— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> app/resources/js/react/components/Topbar.jsx:62— 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> app/resources/js/react/components/Topbar/MenuMobile.jsx:29— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> app/resources/js/react/pages/business.jsx:131— 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> extension-examples/Hrm/Resources/js/components/LeaveApprovalList.jsx:35— 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· <button> with no accessible text · ×4
<button> with no accessible text app/resources/js/react/components/AutoDataTable.jsx:88— A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
<button> with no accessible text app/resources/js/react/components/CommonDataTable.jsx:87— A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
<button> with no accessible text app/resources/js/react/components/CommonDataTableV2.jsx:206— A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
<button> with no accessible text app/resources/js/react/components/CommonDataTableV2.jsx:217— 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).
AC4 · Keyboard semantics· Click handler on a non-interactive <span> · ×4
Click handler on a non-interactive <span> app/resources/js/react/components/CommonDataTable.jsx: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 <span> app/resources/js/react/components/CommonDataTableV2.jsx:138— 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> app/resources/js/react/components/UI/Input/SearchInput.jsx: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 <span> app/resources/js/react/layouts/ExtensionLayout.jsx:26— 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> · ×3
Click handler on a non-interactive <li> app/resources/js/react/components/CommonDataTable.jsx:116— 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> app/resources/js/react/components/CommonDataTableV2.jsx:251— 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> app/resources/js/react/components/UI/Input/Select2.jsx:46— 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· Custom control with no accessible name on <li> · ×2
Custom control with no accessible name on <li> app/resources/js/react/components/CommonDataTable.jsx:116— This <li> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.
Custom control with no accessible name on <li> app/resources/js/react/components/CommonDataTableV2.jsx:251— This <li> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.
AC1 · Text alternatives· <img> without a text alternative · ×1
<img> without a text alternative app/resources/js/react/components/Footer.jsx:18— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
AC2 · Forms & labels· <select> without a programmatic label · ×1
<select> without a programmatic label app/resources/js/react/components/LanguageSwitcher.jsx:17— This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
AC2 · Forms & labels· Custom control with no accessible name on <img> · ×1
Custom control with no accessible name on <img> app/resources/js/react/components/LoadImage.jsx:9— This <img> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.
AC4 · Keyboard semantics· Click handler on a non-interactive <tr> · ×1
Click handler on a non-interactive <tr> app/resources/js/react/components/CommonDataTableV2.jsx:231— 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 <img> · ×1
Click handler on a non-interactive <img> app/resources/js/react/components/LoadImage.jsx:9— 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 <i> · ×1
Click handler on a non-interactive <i> app/resources/js/react/components/Topbar/MenuMobile.jsx:12— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Unlisted import 'react' extension-examples/CustomHomePage/Resources/js/app.jsx:1— Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Anemic entity: ActivityLogModel app/app/Models/ActivityLogModel.php:8— `ActivityLogModel` is an aggregate/entity with 2 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
Anemic entity: BusinessMemberShipModel app/app/Models/BusinessMemberShipModel.php:7— `BusinessMemberShipModel` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
Anemic entity: BusinessModel app/app/Models/BusinessModel.php:7— `BusinessModel` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
Anemic entity: CategoryProductModel app/app/Models/CategoryProductModel.php:9— `CategoryProductModel` is an aggregate/entity with 2 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
Anemic entity: CustomInvoiceInModel app/app/Models/CustomInvoiceInModel.php:8— `CustomInvoiceInModel` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
Anemic entity: CustomInvoiceOutModel app/app/Models/CustomInvoiceOutModel.php:9— `CustomInvoiceOutModel` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
Anemic entity: CustomerGroupModel app/app/Models/CustomerGroupModel.php:8— `CustomerGroupModel` is an aggregate/entity with 2 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
Anemic entity: CustomerModel app/app/Models/CustomerModel.php:9— `CustomerModel` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
Anemic entity: ExtensionModel app/app/Models/ExtensionModel.php:7— `ExtensionModel` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
Anemic entity: ImageModel app/app/Models/ImageModel.php:8— `ImageModel` is an aggregate/entity with 2 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
Anemic entity: InventoryAdjustmentModel app/app/Models/InventoryAdjustmentModel.php:8— `InventoryAdjustmentModel` is an aggregate/entity with 2 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
Anemic entity: InvoiceInModel app/app/Models/InvoiceInModel.php:9— `InvoiceInModel` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
Anemic entity: InvoiceOutModel app/app/Models/InvoiceOutModel.php:10— `InvoiceOutModel` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
Anemic entity: NotificationModel app/app/Models/NotificationModel.php:10— `NotificationModel` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
Anemic entity: OrderCancelModel app/app/Models/OrderCancelModel.php:7— `OrderCancelModel` is an aggregate/entity with 2 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
Anemic entity: OrderItemModel app/app/Models/OrderItemModel.php:10— `OrderItemModel` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
Anemic entity: OrderModel app/app/Models/OrderModel.php:8— `OrderModel` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
Anemic entity: PermissionGroupModel app/app/Models/PermissionGroupModel.php:7— `PermissionGroupModel` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
Anemic entity: PermissionGroupUserModel app/app/Models/PermissionGroupUserModel.php:7— `PermissionGroupUserModel` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
Anemic entity: PermissionModel app/app/Models/PermissionModel.php:7— `PermissionModel` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
Anemic entity: PriceListModel app/app/Models/PriceListModel.php:8— `PriceListModel` is an aggregate/entity with 2 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
Anemic entity: ProductModel app/app/Models/ProductModel.php:10— `ProductModel` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
Anemic entity: PurchaseCancelModel app/app/Models/PurchaseCancelModel.php:7— `PurchaseCancelModel` is an aggregate/entity with 2 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
Anemic entity: PurchaseItemModel app/app/Models/PurchaseItemModel.php:10— `PurchaseItemModel` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
Anemic entity: PurchaseModel app/app/Models/PurchaseModel.php:8— `PurchaseModel` is an aggregate/entity with 4 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
FunctionTooLong: InvoiceOutsDetail.InvoiceOutDetail app/resources/js/react/components/Invoice/InvoiceOuts/InvoiceOutsDetail.jsx:24— FunctionTooLong — InvoiceOutDetail runs 437 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 337 over it, 4.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: ListProduct.ListProducts app/resources/js/react/components/Purchases/AddProduct/ListProduct.jsx:20— FunctionTooLong — ListProducts runs 394 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 294 over it, 3.94× 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: InvoiceInDetail.InvoiceInDetail app/resources/js/react/components/Invoice/InvoiceIns/InvoiceInDetail.jsx:22— FunctionTooLong — InvoiceInDetail runs 382 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 282 over it, 3.82× 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: StockInDetail.StockInDetail app/resources/js/react/components/Stock/StockInDetail.jsx:26— FunctionTooLong — StockInDetail runs 338 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 238 over it, 3.38× 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: suppliers.Suppliers app/resources/js/react/pages/suppliers.jsx:20— FunctionTooLong — Suppliers runs 311 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 211 over it, 3.11× 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: StockOutDetail.StockOutDetail app/resources/js/react/components/Stock/StockOutDetail.jsx:29— FunctionTooLong — StockOutDetail runs 306 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 206 over it, 3.06× 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: IndexCustomInvoiceOuts.IndexCustomInvoiceOuts app/resources/js/react/components/Invoice/IndexCustomInvoiceOuts.jsx:21— FunctionTooLong — IndexCustomInvoiceOuts runs 268 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 168 over it, 2.68× 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: shipping.Shipping app/resources/js/react/pages/shipping.jsx:17— FunctionTooLong — Shipping runs 251 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 151 over it, 2.51× 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: IndexCustomInvoiceIns.IndexCustomInvoiceIns app/resources/js/react/components/Invoice/IndexCustomInvoiceIns.jsx:21— FunctionTooLong — IndexCustomInvoiceIns runs 247 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 147 over it, 2.47× 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: EditOrder.EditOrder app/resources/js/react/components/Order/EditOrder.jsx:27— FunctionTooLong — EditOrder runs 244 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 144 over it, 2.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: CommonDataTableV2.CommonDataTableV2 app/resources/js/react/components/CommonDataTableV2.jsx:11— FunctionTooLong — CommonDataTableV2 runs 242 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 142 over it, 2.42× 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: business.Business app/resources/js/react/pages/business.jsx:21— FunctionTooLong — Business runs 227 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 127 over it, 2.27× 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: EditPurchase.EditPurchase app/resources/js/react/components/Purchases/EditPurchase.jsx:27— FunctionTooLong — EditPurchase runs 211 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 111 over it, 2.11× 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: user.User app/resources/js/react/pages/user.jsx:17— FunctionTooLong — User runs 204 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 104 over it, 2.04× 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: Category.Category app/resources/js/react/components/Product/Category.jsx:16— FunctionTooLong — Category runs 194 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 94 over it, 1.94× 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: warehouse.Warehouse app/resources/js/react/pages/warehouse.jsx:15— FunctionTooLong — Warehouse runs 188 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 88 over it, 1.88× 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: setting.Setting app/resources/js/react/pages/setting.jsx:14— FunctionTooLong — Setting runs 187 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 87 over it, 1.87× 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: Products.Products app/resources/js/react/components/Order/EditOrder/Products.jsx:14— FunctionTooLong — Products runs 184 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 84 over it, 1.84× 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: IndexInventoryAdjustment.IndexInventoryAdjustment app/resources/js/react/components/Inventory/IndexInventoryAdjustment.jsx:19— FunctionTooLong — IndexInventoryAdjustment runs 178 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 78 over it, 1.78× 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: IndexPriceList.IndexPriceList app/resources/js/react/components/Product/IndexPriceList.jsx:17— FunctionTooLong — IndexPriceList runs 178 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 78 over it, 1.78× 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: CustomerForm.CustomerForm app/resources/js/react/components/Customer/ListCustomer/CustomerForm.jsx:10— FunctionTooLong — CustomerForm 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.
FunctionTooLong: ListPurchases.ListPurchases app/resources/js/react/components/Purchases/ListPurchases.jsx:17— FunctionTooLong — ListPurchases runs 164 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 64 over it, 1.64× 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: permissions.Permissions app/resources/js/react/pages/permissions.jsx:15— FunctionTooLong — Permissions runs 158 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 58 over it, 1.58× 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: UpdateProduct.UpdateProduct app/resources/js/react/components/Product/UpdateProduct.jsx:15— FunctionTooLong — UpdateProduct runs 154 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 54 over it, 1.54× 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: report.Report app/resources/js/react/pages/report.jsx:16— FunctionTooLong — Report runs 147 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 47 over it, 1.47× 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 (empty catch) app/resources/js/react/pages/activity-logs.jsx:23— `.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) app/resources/js/react/pages/user.jsx:36— `.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) app/resources/js/react/pages/user.jsx:186— `.catch((error) => {})` 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) app/resources/js/react/layouts/DashboardLayout.jsx:25— `.catch((error) => {})` 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) app/resources/js/react/components/NotificationList.jsx:25— `.catch((error) => {})` 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) app/resources/js/react/components/Topbar.jsx:24— `.catch((error) => {})` 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) app/resources/js/react/components/Stock/StockInDetail.jsx:67— `.catch((error) => {})` 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) app/resources/js/react/components/Stock/StockInDetail/InventoryForm.jsx:28— `.catch((error) => {})` 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) app/resources/js/react/components/Purchases/EditPurchase/PurchaseInformation.jsx:35— `.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) app/resources/js/react/components/Purchases/AddProduct/ListProduct.jsx:173— `.catch((error) => {})` 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) app/resources/js/react/components/Purchases/AddProduct/ListProduct.jsx:189— `.catch((error) => {})` 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) app/resources/js/react/components/Purchases/AddProduct/ListProduct.jsx:231— `.catch((error) => {})` 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) app/resources/js/react/components/Purchases/AddProduct/ListProduct.jsx:319— `.catch((error) => {})` 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) app/resources/js/react/components/Product/UpdateProduct.jsx:89— `.catch((error) => {})` 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) app/resources/js/react/components/Order/AddOrder.jsx:54— `.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) app/resources/js/react/components/Order/EditOrder.jsx:92— `.catch((error) => {})` 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) app/resources/js/react/components/Order/EditOrder.jsx:147— `.catch((error) => {})` 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) app/resources/js/react/components/Order/EditOrder.jsx:207— `.catch((error) => {})` 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) app/resources/js/react/components/Order/EditOrder.jsx:216— `.catch((error) => {})` 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) app/resources/js/react/components/Order/EditOrder.jsx:226— `.catch((error) => {})` 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) app/resources/js/react/components/Order/ListOrder.jsx:59— `.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) app/resources/js/react/components/Order/EditOrder/CustomerInformation.jsx:29— `.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) app/resources/js/react/components/Order/EditOrder/Products.jsx:37— `.catch((error) => {})` 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) app/resources/js/react/components/Order/EditOrder/Products/ListProduct.jsx:62— `.catch((error) => {})` 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) app/resources/js/react/components/Invoice/IndexCustomInvoiceIns.jsx:161— `.catch((error) => {})` 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: app/resources/js/react/components/Product/Category.jsx app/resources/js/react/components/Product/Category.jsx:16— app/resources/js/react/components/Product/Category.jsx 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 10 (its worst body is Category.Category at line 16), 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: “refactor: fix UI, optimizer load”; “refactor: add translate, fix SearchSelect component error can not change keyword search”; “fix: Add permission for extension. refactor: change solution check permission for Frontend”; “fix: add translate. refactor: implement label into common component input form”. 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-02-11..2026-05-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-02-11 20:25:02 +07:00' --until='2026-05-12 20:25:02 +07:00' --full-history --no-merges -- app/resources/js/react/components/Product/Category.jsx`: 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/resources/js/react/components/Customer/ListGroup.jsx app/resources/js/react/components/Customer/ListGroup.jsx:11— app/resources/js/react/components/Customer/ListGroup.jsx changed 6 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 10 (its worst body is ListGroup.ListGroup at line 11), 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: “refactor: fix UI, optimizer load”; “fix: fix bug, refactor code. implement new rule for api index, clean code”; “fix: Add permission for extension. refactor: change solution check permission for Frontend”; “fix: add translate. refactor: implement label input input form”. 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-02-11..2026-05-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-02-11 20:25:02 +07:00' --until='2026-05-12 20:25:02 +07:00' --full-history --no-merges -- app/resources/js/react/components/Customer/ListGroup.jsx`: 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/resources/js/react/pages/warehouse.jsx app/resources/js/react/pages/warehouse.jsx:15— app/resources/js/react/pages/warehouse.jsx 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 12 (its worst body is warehouse.Warehouse at line 15), 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: “refactor: fix UI, optimizer load”; “fix: Add permission for extension. refactor: change solution check permission for Frontend”; “fix: add translate. refactor: implement label input input form”; “fix: update UI CommonDataTable to CommonDataTableV2”. 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-02-11..2026-05-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-02-11 20:25:02 +07:00' --until='2026-05-12 20:25:02 +07:00' --full-history --no-merges -- app/resources/js/react/pages/warehouse.jsx`: 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/resources/js/react/components/Product/ListProducts.jsx app/resources/js/react/components/Product/ListProducts.jsx:11— app/resources/js/react/components/Product/ListProducts.jsx 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 ListProducts.ListProducts at line 11), 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: “refactor: add translate, fix SearchSelect component error can not change keyword search”; “fix: Add permission for extension. refactor: change solution check permission for Frontend”; “fix: add translate. refactor: implement label into common component input form”; “fix: update UI CommonDataTable to CommonDataTableV2”. 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-02-11..2026-05-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-02-11 20:25:02 +07:00' --until='2026-05-12 20:25:02 +07:00' --full-history --no-merges -- app/resources/js/react/components/Product/ListProducts.jsx`: 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/resources/js/react/components/Customer/ListCustomer.jsx app/resources/js/react/components/Customer/ListCustomer.jsx:13— app/resources/js/react/components/Customer/ListCustomer.jsx 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 10 (its worst body is ListCustomer.ListCustomer at line 13), 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: fix bug, refactor code. implement new rule for api index, clean code”; “fix: Add permission for extension. refactor: change solution check permission for Frontend”; “fix: add translate. refactor: implement label input input form”; “fix: update UI CommonDataTable to CommonDataTableV2”. 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-02-11..2026-05-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-02-11 20:25:02 +07:00' --until='2026-05-12 20:25:02 +07:00' --full-history --no-merges -- app/resources/js/react/components/Customer/ListCustomer.jsx`: 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/resources/js/react/components/Invoice/InvoiceOuts/InvoiceOutsDetail.jsx app/resources/js/react/components/Invoice/InvoiceOuts/InvoiceOutsDetail.jsx:24— app/resources/js/react/components/Invoice/InvoiceOuts/InvoiceOutsDetail.jsx 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 13 (its worst body is InvoiceOutsDetail.InvoiceOutDetail at line 24), 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: Fix UI”; “fix: fix router display for invoices detail. change key display total price of invoice out”; “fix: fix bug, refactor code. implement new rule for api index, clean code”; “fix: add translate. refactor: implement label into input form”. 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-02-11..2026-05-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-02-11 20:25:02 +07:00' --until='2026-05-12 20:25:02 +07:00' --full-history --no-merges -- app/resources/js/react/components/Invoice/InvoiceOuts/InvoiceOutsDetail.jsx`: 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/resources/js/react/components/Purchases/ListPurchases.jsx app/resources/js/react/components/Purchases/ListPurchases.jsx:17— app/resources/js/react/components/Purchases/ListPurchases.jsx 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 ListPurchases.ListPurchases at line 17), 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: change logic display index table of Purchase”; “fix: Add permission for extension. refactor: change solution check permission for Frontend”; “fix: display data on table for purchase”; “fix: update UI CommonDataTable to CommonDataTableV2”. 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-02-11..2026-05-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-02-11 20:25:02 +07:00' --until='2026-05-12 20:25:02 +07:00' --full-history --no-merges -- app/resources/js/react/components/Purchases/ListPurchases.jsx`: 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/resources/js/react/pages/user.jsx app/resources/js/react/pages/user.jsx:17— app/resources/js/react/pages/user.jsx 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 9 (its worst body is user.User at line 17), 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: fix bug, refactor code. implement new rule for api index, clean code”; “fix: Add permission for extension. refactor: change solution check permission for Frontend”; “fix: add translate. refactor: implement label into input form”; “fix: update UI CommonDataTable to CommonDataTableV2”. 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-02-11..2026-05-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-02-11 20:25:02 +07:00' --until='2026-05-12 20:25:02 +07:00' --full-history --no-merges -- app/resources/js/react/pages/user.jsx`: 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/resources/js/react/components/Invoice/InvoiceIns/InvoiceInDetail.jsx app/resources/js/react/components/Invoice/InvoiceIns/InvoiceInDetail.jsx:22— app/resources/js/react/components/Invoice/InvoiceIns/InvoiceInDetail.jsx 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 13 (its worst body is InvoiceInDetail.InvoiceInDetail at line 22), 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: “refactor: fix UI, optimizer load”; “fix: fix bug, refactor code. implement new rule for api index, clean code”; “fix: add translate. refactor: implement label into input form”; “fix: UI button common”. 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-02-11..2026-05-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-02-11 20:25:02 +07:00' --until='2026-05-12 20:25:02 +07:00' --full-history --no-merges -- app/resources/js/react/components/Invoice/InvoiceIns/InvoiceInDetail.jsx`: 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/resources/js/react/pages/suppliers.jsx app/resources/js/react/pages/suppliers.jsx:20— app/resources/js/react/pages/suppliers.jsx 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 14 (its worst body is suppliers.Suppliers at line 20), 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: “refactor: fix UI, optimizer load”; “fix: Add permission for extension. refactor: change solution check permission for Frontend”; “fix: add translate. refactor: implement label into common component input form”; “fix: update UI CommonDataTable to CommonDataTableV2”. 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-02-11..2026-05-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-02-11 20:25:02 +07:00' --until='2026-05-12 20:25:02 +07:00' --full-history --no-merges -- app/resources/js/react/pages/suppliers.jsx`: 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/resources/js/react/pages/setting.jsx app/resources/js/react/pages/setting.jsx:14— app/resources/js/react/pages/setting.jsx 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 setting.Setting at line 14), 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: “refactor: clean code, fix ui”; “fix: Add permission for extension. refactor: change solution check permission for Frontend”; “fix: add translate. refactor: implement label into input form”; “fix: UI button common”. 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-02-11..2026-05-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-02-11 20:25:02 +07:00' --until='2026-05-12 20:25:02 +07:00' --full-history --no-merges -- app/resources/js/react/pages/setting.jsx`: 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/core/Purchase/Application/Queries/IndexQuery.php app/core/Purchase/Application/Queries/IndexQuery.php:21— app/core/Purchase/Application/Queries/IndexQuery.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 3 (its worst body is IndexQuery.handle at line 21), 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: change logic display index table of Purchase”; “refactor: change hardcode event name to Permission enum class, clean code. Fix: update namespace module for define path at provider module”; “fix: add hook, fix bug, clean code. refactor: index query, adapter, optimizer query db”. 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-02-11..2026-05-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-02-11 20:25:02 +07:00' --until='2026-05-12 20:25:02 +07:00' --full-history --no-merges -- app/core/Purchase/Application/Queries/IndexQuery.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/core/OrderItem/Infrastructure/Listeners/OrderItemListener.php app/core/OrderItem/Infrastructure/Listeners/OrderItemListener.php:21— app/core/OrderItem/Infrastructure/Listeners/OrderItemListener.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 4 (its worst body is OrderItemListener.handle at line 21), 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: “refactor: refactor structure. fix: fix bug update resever qty of inventory”; “fix: update logic for Summary Order Item”; “fix: add hook, fix bug, clean code. refactor: index query, adapter, optimizer query db”. 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-02-11..2026-05-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-02-11 20:25:02 +07:00' --until='2026-05-12 20:25:02 +07:00' --full-history --no-merges -- app/core/OrderItem/Infrastructure/Listeners/OrderItemListener.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/core/OrderShipping/Application/UseCases/CreateOrderShipping.php app/core/OrderShipping/Application/UseCases/CreateOrderShipping.php:18— app/core/OrderShipping/Application/UseCases/CreateOrderShipping.php 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 1 (its worst body is CreateOrderShipping.__construct at line 18), 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: “refactor: change hardcode event name to Permission enum class, clean code. Fix: update namespace module for define path at provider module”; “fix: add hook, fix bug, clean code. refactor: index query, adapter, optimizer query db”; “fix: Add permission for extension. refactor: change solution check permission for Frontend”. 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-02-11..2026-05-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-02-11 20:25:02 +07:00' --until='2026-05-12 20:25:02 +07:00' --full-history --no-merges -- app/core/OrderShipping/Application/UseCases/CreateOrderShipping.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/resources/js/react/components/Order/EditOrder/Products/ProductAdded.jsx app/resources/js/react/components/Order/EditOrder/Products/ProductAdded.jsx:7— app/resources/js/react/components/Order/EditOrder/Products/ProductAdded.jsx 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 3 (its worst body is ProductAdded.ProductAdded at line 7), 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: fix bug, refactor code. implement new rule for api index, clean code”; “fix: Add permission for extension. refactor: change solution check permission for Frontend”; “fix: add translate. refactor input label for order”. 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-02-11..2026-05-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-02-11 20:25:02 +07:00' --until='2026-05-12 20:25:02 +07:00' --full-history --no-merges -- app/resources/js/react/components/Order/EditOrder/Products/ProductAdded.jsx`: 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/core/OrderItem/Application/UseCases/UpdateOrderItem.php app/core/OrderItem/Application/UseCases/UpdateOrderItem.php:19— app/core/OrderItem/Application/UseCases/UpdateOrderItem.php 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 1 (its worst body is UpdateOrderItem.__construct at line 19), 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: “refactor: change hardcode event name to Permission enum class, clean code. Fix: update namespace module for define path at provider module”; “refactor: refactor structure. fix: fix bug update resever qty of inventory”; “fix: add hook, fix bug, clean code. refactor: index query, adapter, optimizer query db”. 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-02-11..2026-05-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-02-11 20:25:02 +07:00' --until='2026-05-12 20:25:02 +07:00' --full-history --no-merges -- app/core/OrderItem/Application/UseCases/UpdateOrderItem.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/core/User/Application/UseCases/DeleteUser.php app/core/User/Application/UseCases/DeleteUser.php:22— app/core/User/Application/UseCases/DeleteUser.php 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 2 (its worst body is DeleteUser.handle at line 22), 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: “refactor: change hardcode event name to Permission enum class, clean code. Fix: update namespace module for define path at provider module”; “fix: add hook, fix bug, clean code. refactor: index query, adapter, optimizer query db”; “fix: update translate for user”. 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-02-11..2026-05-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-02-11 20:25:02 +07:00' --until='2026-05-12 20:25:02 +07:00' --full-history --no-merges -- app/core/User/Application/UseCases/DeleteUser.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/core/User/Application/UseCases/UpdateUser.php app/core/User/Application/UseCases/UpdateUser.php:26— app/core/User/Application/UseCases/UpdateUser.php 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 3 (its worst body is UpdateUser.handle at line 26), 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: “refactor: change hardcode event name to Permission enum class, clean code. Fix: update namespace module for define path at provider module”; “fix: add hook, fix bug, clean code. refactor: index query, adapter, optimizer query db”; “fix: update translate for user”. 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-02-11..2026-05-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-02-11 20:25:02 +07:00' --until='2026-05-12 20:25:02 +07:00' --full-history --no-merges -- app/core/User/Application/UseCases/UpdateUser.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/resources/js/react/components/Purchases/AddPurchase.jsx app/resources/js/react/components/Purchases/AddPurchase.jsx:14— app/resources/js/react/components/Purchases/AddPurchase.jsx 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 AddPurchase.AddPurchase at line 14), 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(purchase): fix default date error when creating new purchase”; “refactor: fix UI, optimizer load”; “fix: update validate, update input form UI, fix bug select all for change tax, implement translate”. 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-02-11..2026-05-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-02-11 20:25:02 +07:00' --until='2026-05-12 20:25:02 +07:00' --full-history --no-merges -- app/resources/js/react/components/Purchases/AddPurchase.jsx`: 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/core/Order/Http/Requests/IndexOrderRequest.php app/core/Order/Http/Requests/IndexOrderRequest.php:14— app/core/Order/Http/Requests/IndexOrderRequest.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 1 (its worst body is IndexOrderRequest.rules at line 14), 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: fix notification title, message”; “fix: update module name for hook”; “fix: add hook, fix bug, clean code. refactor: index query, adapter, optimizer query db”. 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-02-11..2026-05-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-02-11 20:25:02 +07:00' --until='2026-05-12 20:25:02 +07:00' --full-history --no-merges -- app/core/Order/Http/Requests/IndexOrderRequest.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/resources/js/react/pages/shipping.jsx app/resources/js/react/pages/shipping.jsx:17— app/resources/js/react/pages/shipping.jsx 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 13 (its worst body is shipping.Shipping at line 17), 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: Add permission for extension. refactor: change solution check permission for Frontend”; “fix: add translate. refactor: implement label into input form”; “fix: update UI CommonDataTable to CommonDataTableV2”. 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-02-11..2026-05-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-02-11 20:25:02 +07:00' --until='2026-05-12 20:25:02 +07:00' --full-history --no-merges -- app/resources/js/react/pages/shipping.jsx`: 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/resources/js/react/components/CommonDataTableV2.jsx app/resources/js/react/components/CommonDataTableV2.jsx:11— app/resources/js/react/components/CommonDataTableV2.jsx changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 37 in CommonDataTableV2.CommonDataTableV2 at line 11. 6 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-02-11..2026-05-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-02-11 20:25:02 +07:00' --until='2026-05-12 20:25:02 +07:00' --full-history --no-merges -- app/resources/js/react/components/CommonDataTableV2.jsx`: 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/resources/js/react/components/Order/EditOrder.jsx app/resources/js/react/components/Order/EditOrder.jsx:27— app/resources/js/react/components/Order/EditOrder.jsx changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 33 in EditOrder.EditOrder at line 27. 5 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-02-11..2026-05-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-02-11 20:25:02 +07:00' --until='2026-05-12 20:25:02 +07:00' --full-history --no-merges -- app/resources/js/react/components/Order/EditOrder.jsx`: 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/resources/js/react/components/Purchases/EditPurchase.jsx app/resources/js/react/components/Purchases/EditPurchase.jsx:27— app/resources/js/react/components/Purchases/EditPurchase.jsx changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 28 in EditPurchase.EditPurchase at line 27. 5 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-02-11..2026-05-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-02-11 20:25:02 +07:00' --until='2026-05-12 20:25:02 +07:00' --full-history --no-merges -- app/resources/js/react/components/Purchases/EditPurchase.jsx`: 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/resources/js/react/components/Stock/StockInDetail.jsx app/resources/js/react/components/Stock/StockInDetail.jsx:26— app/resources/js/react/components/Stock/StockInDetail.jsx changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in StockInDetail.StockInDetail at line 26. 4 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-02-11..2026-05-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-02-11 20:25:02 +07:00' --until='2026-05-12 20:25:02 +07:00' --full-history --no-merges -- app/resources/js/react/components/Stock/StockInDetail.jsx`: 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/resources/js/react/components/Invoice/IndexCustomInvoiceOuts.jsx app/resources/js/react/components/Invoice/IndexCustomInvoiceOuts.jsx:21— app/resources/js/react/components/Invoice/IndexCustomInvoiceOuts.jsx changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 15 in IndexCustomInvoiceOuts.IndexCustomInvoiceOuts at line 21. 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-02-11..2026-05-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-02-11 20:25:02 +07:00' --until='2026-05-12 20:25:02 +07:00' --full-history --no-merges -- app/resources/js/react/components/Invoice/IndexCustomInvoiceOuts.jsx`: 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/resources/js/react/components/UI/Input/SearchSelect.jsx app/resources/js/react/components/UI/Input/SearchSelect.jsx:5— app/resources/js/react/components/UI/Input/SearchSelect.jsx changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in SearchSelect.SearchSelect at line 5. 4 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-02-11..2026-05-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-02-11 20:25:02 +07:00' --until='2026-05-12 20:25:02 +07:00' --full-history --no-merges -- app/resources/js/react/components/UI/Input/SearchSelect.jsx`: 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/resources/js/react/components/Purchases/AddProduct/ListProduct.jsx app/resources/js/react/components/Purchases/AddProduct/ListProduct.jsx:20— app/resources/js/react/components/Purchases/AddProduct/ListProduct.jsx changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 22 in ListProduct.ListProducts at line 20. 2 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-02-11..2026-05-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-02-11 20:25:02 +07:00' --until='2026-05-12 20:25:02 +07:00' --full-history --no-merges -- app/resources/js/react/components/Purchases/AddProduct/ListProduct.jsx`: 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/resources/js/react/components/Order/EditOrder/Products.jsx app/resources/js/react/components/Order/EditOrder/Products.jsx:14— app/resources/js/react/components/Order/EditOrder/Products.jsx changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in Products.Products at line 14. 3 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-02-11..2026-05-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-02-11 20:25:02 +07:00' --until='2026-05-12 20:25:02 +07:00' --full-history --no-merges -- app/resources/js/react/components/Order/EditOrder/Products.jsx`: 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/resources/js/react/components/Stock/StockOutDetail.jsx app/resources/js/react/components/Stock/StockOutDetail.jsx:29— app/resources/js/react/components/Stock/StockOutDetail.jsx changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in StockOutDetail.StockOutDetail at line 29. 2 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-02-11..2026-05-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-02-11 20:25:02 +07:00' --until='2026-05-12 20:25:02 +07:00' --full-history --no-merges -- app/resources/js/react/components/Stock/StockOutDetail.jsx`: 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/resources/js/react/components/popups/PopupContext.jsx app/resources/js/react/components/popups/PopupContext.jsx:12— app/resources/js/react/components/popups/PopupContext.jsx changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in PopupContext.PopupProvider at line 12. 2 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-02-11..2026-05-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-02-11 20:25:02 +07:00' --until='2026-05-12 20:25:02 +07:00' --full-history --no-merges -- app/resources/js/react/components/popups/PopupContext.jsx`: 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 · ×10
Duplicated block (14 lines × 2) app/core/Customer/Application/UseCases/CreateCustomer.php:25— app/core/Customer/Application/UseCases/CreateCustomer.php:25-38 | app/core/Customer/Application/UseCases/CreateOrUpdateCustomer.php:25-38 — before extracting anything, compare `app/core/Customer/Application/UseCases/CreateCustomer.php` and `app/core/Customer/Application/UseCases/CreateOrUpdateCustomer.php` as WHOLE FILES: 90% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (14 lines × 2) app/core/InvoiceIn/Application/UseCases/CreateInvoiceIn.php:23— app/core/InvoiceIn/Application/UseCases/CreateInvoiceIn.php:23-36 | app/core/InvoiceIn/Application/UseCases/UpdateInvoiceIn.php:25-38 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (14 lines × 2) app/core/PermissionGroup/Application/UseCases/ShowPermissionGroup.php:26— app/core/PermissionGroup/Application/UseCases/ShowPermissionGroup.php:26-39 | app/core/PermissionGroupUser/Application/UseCases/ShowPermissionGroupUser.php:25-38 — 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 (14 lines × 2) app/core/Purchase/Application/Queries/IndexQuery.php:62— app/core/Purchase/Application/Queries/IndexQuery.php:62-75 | app/core/Shipping/Application/Queries/IndexQuery.php:26-42 — 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/core/Purchase/Application/Queries/IndexQuery.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.
Duplicated block (14 lines × 2) app/core/CustomerGroup/Application/DTOs/DeleteCustomerGroupRequest.php:15— app/core/CustomerGroup/Application/DTOs/DeleteCustomerGroupRequest.php:15-28 | app/core/CustomerGroup/Application/DTOs/ShowCustomerGroupRequest.php:15-28 — before extracting anything, compare `app/core/CustomerGroup/Application/DTOs/DeleteCustomerGroupRequest.php` and `app/core/CustomerGroup/Application/DTOs/ShowCustomerGroupRequest.php` as WHOLE FILES: 83% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `app/core/CustomerGroup/Application/DTOs/DeleteCustomerGroupRequest.php:15` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (14 lines × 2) app/core/InvoiceIn/Application/DTOs/ShowInvoiceInRequest.php:15— app/core/InvoiceIn/Application/DTOs/ShowInvoiceInRequest.php:15-28 | app/core/InvoiceOut/Application/DTOs/ShowInvoiceOutRequest.php:15-28 — before extracting anything, compare `app/core/InvoiceIn/Application/DTOs/ShowInvoiceInRequest.php` and `app/core/InvoiceOut/Application/DTOs/ShowInvoiceOutRequest.php` as WHOLE FILES: 83% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `app/core/InvoiceIn/Application/DTOs/ShowInvoiceInRequest.php:15` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (14 lines × 2) app/core/Notifications/Application/DTOs/DeleteNotificationRequest.php:15— app/core/Notifications/Application/DTOs/DeleteNotificationRequest.php:15-28 | app/core/Notifications/Application/DTOs/UpdateNotificationRequest.php:15-28 — before extracting anything, compare `app/core/Notifications/Application/DTOs/DeleteNotificationRequest.php` and `app/core/Notifications/Application/DTOs/UpdateNotificationRequest.php` as WHOLE FILES: 83% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `app/core/Notifications/Application/DTOs/DeleteNotificationRequest.php:15` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (14 lines × 2) app/core/Permission/Application/DTOs/CheckPermissionRequest.php:15— app/core/Permission/Application/DTOs/CheckPermissionRequest.php:15-28 | app/core/Permission/Application/DTOs/GetPermissionRequest.php:15-28 — before extracting anything, compare `app/core/Permission/Application/DTOs/CheckPermissionRequest.php` and `app/core/Permission/Application/DTOs/GetPermissionRequest.php` as WHOLE FILES: 83% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `app/core/Permission/Application/DTOs/CheckPermissionRequest.php:15` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (14 lines × 2) app/core/PermissionGroup/Application/DTOs/DeletePermissionGroupRequest.php:15— app/core/PermissionGroup/Application/DTOs/DeletePermissionGroupRequest.php:15-28 | app/core/PermissionGroup/Application/DTOs/ShowPermissionGroupRequest.php:15-28 — before extracting anything, compare `app/core/PermissionGroup/Application/DTOs/DeletePermissionGroupRequest.php` and `app/core/PermissionGroup/Application/DTOs/ShowPermissionGroupRequest.php` as WHOLE FILES: 83% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `app/core/PermissionGroup/Application/DTOs/DeletePermissionGroupRequest.php:15` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (14 lines × 2) extension-examples/StockOutExtras/Hooks/ShowHook.php:17— extension-examples/StockOutExtras/Hooks/ShowHook.php:17-30 | extension-examples/StockinExtras/Hooks/ShowHook.php:17-30 — 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 `extension-examples/StockOutExtras/Hooks/ShowHook.php:17` 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 first that the copies are not typed on the same thing: `StockinExtrasModel` names `Extensions\StockOutExtras\Models\StockinExtrasModel` in one and `Extensions\StockinExtras\Models\StockinExtrasModel` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Mutable entity: BusinessMemberShipModel app/app/Models/BusinessMemberShipModel.php:7— `BusinessMemberShipModel` exposes publicly writable state (table).
Mutable entity: BusinessModel app/app/Models/BusinessModel.php:7— `BusinessModel` exposes publicly writable state (table).
Mutable entity: ExtensionModel app/app/Models/ExtensionModel.php:7— `ExtensionModel` exposes publicly writable state (table).
Mutable entity: PermissionGroupModel app/app/Models/PermissionGroupModel.php:7— `PermissionGroupModel` exposes publicly writable state (table).
Mutable entity: PermissionGroupUserModel app/app/Models/PermissionGroupUserModel.php:7— `PermissionGroupUserModel` exposes publicly writable state (table).
Mutable entity: PermissionModel app/app/Models/PermissionModel.php:7— `PermissionModel` exposes publicly writable state (table).
Mutable entity: WarehouseModel app/app/Models/WarehouseModel.php:8— `WarehouseModel` exposes publicly writable state (table).
Mutable entity: SupplierFaxModel extension-examples/SupplierFax/Models/SupplierFaxModel.php:7— `SupplierFaxModel` exposes publicly writable state (table).
AC3 · Page structure· Heading level jumps from h4 to h6 · ×7
Heading level jumps from h4 to h6 app/resources/js/react/pages/report.jsx:92— Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
Heading level jumps from h4 to h6 app/resources/js/react/pages/report.jsx:100— Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
Heading level jumps from h4 to h6 app/resources/js/react/pages/report.jsx:112— Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
Heading level jumps from h4 to h6 app/resources/js/react/pages/report.jsx:120— Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
Heading level jumps from h4 to h6 extension-examples/Debt/Resources/views/index.blade.php:75— Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
Heading level jumps from h4 to h6 extension-examples/Debt/Resources/views/index.blade.php:88— Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
Heading level jumps from h4 to h6 extension-examples/Debt/Resources/views/index.blade.php:101— Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
TodoComment app/core/StockMovementOut/Infrastructure/Repositories/EloquentStockMovementOutRepository.php:14— // TODO: Add actual database logic — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment app/core/Shipping/Infrastructure/Repositories/EloquentShippingRepository.php:13— // TODO: Add actual database logic — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment app/core/Purchase/Infrastructure/Repositories/EloquentPurchaseRepository.php:14— // TODO: Add actual database logic — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment app/core/InvoiceOut/Infrastructure/Repositories/EloquentInvoiceOutRepository.php:14— // TODO: Add actual database logic — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment app/core/InvoiceIn/Infrastructure/Repositories/EloquentInvoiceInRepository.php:13— // TODO: Add actual database logic — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment app/core/Customer/Infrastructure/Repositories/EloquentCustomerRepository.php:46— // TODO: Add actual database logic — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment app/app/Console/Commands/MakeModule.php:152— // TODO: Add actual database logic — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
Duplicated block (10 lines × 2) app/app/Console/Commands/MakeBroadcastModule.php:31— app/app/Console/Commands/MakeBroadcastModule.php:31-40 | app/app/Console/Commands/MakeListenerModule.php:31-40 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `app/app/Console/Commands/MakeListenerModule.php:41` calls `exists`, `error` and `app/app/Console/Commands/MakeBroadcastModule.php:42` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (10 lines × 2) app/core/Extension/Infrastructure/Supports/ExtensionInstallImpl.php:13— app/core/Extension/Infrastructure/Supports/ExtensionInstallImpl.php:13-22 | app/core/Extension/Infrastructure/Supports/ExtensionInstallImpl.php:28-37 — 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/core/Extension/Infrastructure/Supports/ExtensionInstallImpl.php:13` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 2) app/core/Inventory/Application/Queries/IndexQuery.php:56— app/core/Inventory/Application/Queries/IndexQuery.php:56-86 | app/core/InventoryAdjustment/Application/Queries/IndexQuery.php:23-32 — 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/core/Inventory/Application/Queries/IndexQuery.php:56` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (10 lines × 2) app/core/InventoryAdjustment/Infrastructure/Repositories/EloquentInventoryAdjustmentRepository.php:23— app/core/InventoryAdjustment/Infrastructure/Repositories/EloquentInventoryAdjustmentRepository.php:23-32 | app/core/InvoiceOut/Infrastructure/Repositories/EloquentInvoiceOutRepository.php:42-51 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (10 lines × 2) app/core/StockMovementOut/Infrastructure/Repositories/EloquentStockMovementOutRepository.php:21— app/core/StockMovementOut/Infrastructure/Repositories/EloquentStockMovementOutRepository.php:21-30 | app/core/StockMovementOut/Infrastructure/Repositories/EloquentStockMovementOutRepository.php:34-43 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 2) app/core/User/Infrastructure/Repositories/EloquentUserRepository.php:13— app/core/User/Infrastructure/Repositories/EloquentUserRepository.php:13-22 | app/core/User/Infrastructure/Repositories/EloquentUserRepository.php:34-43 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (6 lines × 2) app/core/Notifications/Application/DTOs/CreateNotificationRequest.php:30— app/core/Notifications/Application/DTOs/CreateNotificationRequest.php:30-35 | app/core/Notifications/Application/DTOs/InsertManyNotificationRequest.php:31-36 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (6 lines × 2) app/core/PurchaseItem/Application/DTOs/CreatePurchaseItemRequest.php:31— app/core/PurchaseItem/Application/DTOs/CreatePurchaseItemRequest.php:31-36 | app/core/PurchaseItem/Domain/Entities/PurchaseItem.php:29-34 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (6 lines × 2) app/core/Extension/Application/DTOs/MakeExtensionCommand.php:57— app/core/Extension/Application/DTOs/MakeExtensionCommand.php:57-62 | app/core/Extension/Domain/Entities/Extension.php:60-65 — before extracting anything, compare `app/core/Extension/Application/DTOs/MakeExtensionCommand.php` and `app/core/Extension/Domain/Entities/Extension.php` as WHOLE FILES: 90% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (6 lines × 2) app/core/CustomInvoiceIn/Infrastructure/Services/CustomInvoiceInServiceImpl.php:16— app/core/CustomInvoiceIn/Infrastructure/Services/CustomInvoiceInServiceImpl.php:16-21 | app/core/CustomInvoiceOut/Infrastructure/Services/CustomInvoiceOutServiceImpl.php:16-21 — 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 (6 lines × 2) app/core/OrderShipping/Infrastructure/Services/OrderShippingServiceImpl.php:17— app/core/OrderShipping/Infrastructure/Services/OrderShippingServiceImpl.php:17-22 | app/core/Shipping/Infrastructure/Services/ShippingServiceImpl.php:16-21 — 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 (6 lines × 2) app/core/Customer/Infrastructure/Services/CustomerServiceImpl.php:48— app/core/Customer/Infrastructure/Services/CustomerServiceImpl.php:48-53 | app/core/Supplier/Infrastructure/Services/SupplierServiceImpl.php:34-39 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (5 lines × 2) app/core/InvoiceIn/Application/DTOs/CreateInvoiceInRequest.php:32— app/core/InvoiceIn/Application/DTOs/CreateInvoiceInRequest.php:32-36 | app/core/InvoiceIn/Domain/Entities/InvoiceIn.php:34-38 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (5 lines × 2) app/core/Order/Application/UseCases/CheckOrderCancelled.php:15— app/core/Order/Application/UseCases/CheckOrderCancelled.php:15-19 | app/core/Order/Application/UseCases/CheckUpdateShippingOrder.php:15-19 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. 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 (5 lines × 2) app/core/CustomInvoiceOut/Application/DTOs/DeleteCustomInvoiceOutRequest.php:15— app/core/CustomInvoiceOut/Application/DTOs/DeleteCustomInvoiceOutRequest.php:15-19 | app/core/PurchaseItem/Application/DTOs/DeletePurchaseItemRequest.php:15-19 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (5 lines × 2) app/core/OrderCancel/Infrastructure/Listeners/OrderCancelListeners.php:14— app/core/OrderCancel/Infrastructure/Listeners/OrderCancelListeners.php:14-18 | app/core/StockMovementOut/Infrastructure/Listeners/StockMovementOutListener.php:16-26 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Note 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 (5 lines × 2) app/core/InvoiceIn/Infrastructure/Services/InvoiceInServiceImpl.php:38— app/core/InvoiceIn/Infrastructure/Services/InvoiceInServiceImpl.php:38-42 | app/core/InvoiceOut/Infrastructure/Services/InvoiceOutServiceImpl.php:41-45 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (5 lines × 2) extension-examples/Hrm/Services/AttendanceService.php:48— extension-examples/Hrm/Services/AttendanceService.php:48-52 | extension-examples/Hrm/Services/ReportService.php:24-28 — 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 `extension-examples/Hrm/Services/AttendanceService.php:48` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 2) app/core/Customer/Application/UseCases/CreateCustomer.php:40— app/core/Customer/Application/UseCases/CreateCustomer.php:40-55 | app/core/Customer/Application/UseCases/CreateOrUpdateCustomer.php:40-55 — before extracting anything, compare `app/core/Customer/Application/UseCases/CreateCustomer.php` and `app/core/Customer/Application/UseCases/CreateOrUpdateCustomer.php` as WHOLE FILES: 90% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (16 lines × 2) app/core/Customer/Application/DTOs/IndexCustomerRequest.php:16— app/core/Customer/Application/DTOs/IndexCustomerRequest.php:16-32 | app/core/Supplier/Application/DTOs/IndexSupplierRequest.php:17-32 — 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/core/Customer/Application/DTOs/IndexCustomerRequest.php:16` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (16 lines × 2) app/core/CustomerGroup/Application/DTOs/IndexCustomerGroupRequest.php:16— app/core/CustomerGroup/Application/DTOs/IndexCustomerGroupRequest.php:16-31 | app/core/StockOut/Application/DTOs/IndexStockOutRequest.php:16-31 — 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/core/CustomerGroup/Application/DTOs/IndexCustomerGroupRequest.php:16` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (16 lines × 2) app/core/PurchaseTax/Application/DTOs/CreatePurchaseTaxRequest.php:17— app/core/PurchaseTax/Application/DTOs/CreatePurchaseTaxRequest.php:17-32 | app/core/PurchaseTax/Domain/Entities/PurchaseTax.php:16-31 — 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/core/PurchaseTax/Application/DTOs/CreatePurchaseTaxRequest.php:17` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (16 lines × 2) extension-examples/StockOutExtras/Hooks/CreateHook.php:16— extension-examples/StockOutExtras/Hooks/CreateHook.php:16-31 | extension-examples/StockinExtras/Hooks/CreateHook.php:16-31 — 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 `extension-examples/StockOutExtras/Hooks/CreateHook.php:16` 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 first that the copies are not typed on the same thing: `StockinExtrasModel` names `Extensions\StockOutExtras\Models\StockinExtrasModel` in one and `Extensions\StockinExtras\Models\StockinExtrasModel` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (9 lines × 2) app/core/Business/Application/DTOs/CreateBusinessRequest.php:27— app/core/Business/Application/DTOs/CreateBusinessRequest.php:27-35 | app/core/Business/Domain/Entities/Business.php:25-33 — before extracting anything, compare `app/core/Business/Application/DTOs/CreateBusinessRequest.php` and `app/core/Business/Domain/Entities/Business.php` as WHOLE FILES: 84% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `app/core/Business/Application/DTOs/CreateBusinessRequest.php:27` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) app/core/InventoryAdjustment/Infrastructure/Repositories/EloquentInventoryAdjustmentRepository.php:27— app/core/InventoryAdjustment/Infrastructure/Repositories/EloquentInventoryAdjustmentRepository.php:27-35 | extension-examples/Hrm/Services/AttendanceService.php:49-57 — 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 lines × 2) app/core/Extension/Http/Controllers/ExtensionController.php:19— app/core/Extension/Http/Controllers/ExtensionController.php:19-34 | app/core/Inventory/Http/Controllers/InventoryController.php:14-22 — 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/core/Extension/Http/Controllers/ExtensionController.php:19` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (9 lines × 2) app/core/InvoiceIn/Domain/Entities/InvoiceIn.php:102— app/core/InvoiceIn/Domain/Entities/InvoiceIn.php:102-110 | app/core/InvoiceOut/Domain/Entities/InvoiceOut.php:105-113 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 2) app/core/OrderShipping/Infrastructure/Repositories/EloquentOrderShippingRepository.php:36— app/core/OrderShipping/Infrastructure/Repositories/EloquentOrderShippingRepository.php:36-44 | app/core/OrderShipping/Infrastructure/Repositories/EloquentOrderShippingRepository.php:72-79 — 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/core/OrderShipping/Infrastructure/Repositories/EloquentOrderShippingRepository.php:36` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `app/core/OrderShipping/Infrastructure/Repositories/EloquentOrderShippingRepository.php:71` calls `join`, `where` and `app/core/OrderShipping/Infrastructure/Repositories/EloquentOrderShippingRepository.php:36` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (8 lines × 2) app/core/Shipping/Infrastructure/Services/ShippingServiceImpl.php:29— app/core/Shipping/Infrastructure/Services/ShippingServiceImpl.php:29-36 | app/core/Supplier/Infrastructure/Services/SupplierServiceImpl.php:25-32 — 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 (8 lines × 2) app/core/Supplier/Application/DTOs/CreateSupplierRequest.php:28— app/core/Supplier/Application/DTOs/CreateSupplierRequest.php:28-35 | app/core/Supplier/Domain/Entities/Supplier.php:51-58 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (8 lines × 2) extension-examples/Debt/Http/Controllers/DebtController.php:19— extension-examples/Debt/Http/Controllers/DebtController.php:19-26 | extension-examples/Debt/Http/Controllers/DebtController.php:28-35 — 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 `extension-examples/Debt/Http/Controllers/DebtController.php:19` 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 (29 lines × 2 locations) app/resources/js/react/components/Customer/ListCustomer.jsx:81— app/resources/js/react/components/Customer/ListCustomer.jsx:81 · app/resources/js/react/pages/suppliers.jsx:56 — 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 (29 lines × 2 locations) app/resources/js/react/components/Invoice/InvoiceOuts/InvoiceOutsDetail.jsx:370— app/resources/js/react/components/Invoice/InvoiceOuts/InvoiceOutsDetail.jsx:370 · app/resources/js/react/components/Stock/StockOutDetail.jsx:312 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases.
Duplicated block (29 lines × 2 locations) app/resources/js/react/components/Stock/StockInDetail.jsx:139— app/resources/js/react/components/Stock/StockInDetail.jsx:139 · app/resources/js/react/components/Stock/StockInDetail.jsx: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 (29 lines × 2 locations) app/resources/js/react/pages/suppliers.jsx:90— app/resources/js/react/pages/suppliers.jsx:90 · app/resources/js/react/pages/suppliers.jsx:130 — 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.
X24 · Document value interpolated into markup unescaped· Untrusted text written into markup unescaped · ×4
Untrusted text written into markup unescaped app/resources/js/react/components/AutoDataTable.jsx:90— `link.label` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` 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 app/resources/js/react/components/CommonDataTable.jsx:124— `item.label` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` 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 app/resources/js/react/components/CommonDataTableV2.jsx:259— `item.label` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` 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 app/resources/js/react/components/RenderFieldTableByList.jsx:21— `data` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` 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.
AC2 · Forms & labels· <TextArea> field component without a label · ×3
<TextArea> field component without a label app/resources/js/react/components/Invoice/IndexCustomInvoiceIns.jsx:301— This UI-library field component has no label / aria-label / aria-labelledby / id at this call site, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id, even one the component sets on what it renders, names nothing until a label points at it) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<TextArea> field component without a label app/resources/js/react/components/Invoice/IndexCustomInvoiceOuts.jsx:328— This UI-library field component has no label / aria-label / aria-labelledby / id at this call site, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id, even one the component sets on what it renders, names nothing until a label points at it) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<TextArea> field component without a label app/resources/js/react/components/Order/EditOrder.jsx:327— This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
AC2 · Forms & labels· <Select> field component without a label · ×3
<Select> field component without a label app/resources/js/react/components/Invoice/IndexCustomInvoiceIns.jsx:310— This UI-library field component has no label / aria-label / aria-labelledby / id at this call site, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id, even one the component sets on what it renders, names nothing until a label points at it) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<Select> field component without a label app/resources/js/react/components/Invoice/IndexCustomInvoiceOuts.jsx:337— This UI-library field component has no label / aria-label / aria-labelledby / id at this call site, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id, even one the component sets on what it renders, names nothing until a label points at it) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<Select> field component without a label app/resources/js/react/components/NotificationList.jsx:106— This UI-library field component has no label / aria-label / aria-labelledby / id at this call site, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id, even one the component sets on what it renders, names nothing until a label points at it) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
AC3 · Page structure· Data table has no header cells · ×3
Data table has no header cells app/resources/js/react/components/Business/BusinessListItem.jsx:43— A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
Data table has no header cells extension-examples/InvoiceInPDF/Views/index.blade.php:104— A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
Data table has no header cells extension-examples/InvoiceOutPDF/Views/index.blade.php:98— A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
AC3 · Page structure· Page without a main landmark · ×3
Page without a main landmark app/resources/views/admin/layouts/auth.blade.php:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark app/resources/views/admin/layouts/dashboard.blade.php:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark app/resources/views/home/layout.blade.php:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
MethodTooLong: MakeModule.handle app/app/Console/Commands/MakeModule.php:14— MethodTooLong — handle runs 196 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 96 over it, 1.96× 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: MakeExtension.createFiles app/app/Console/Commands/MakeExtension.php:78— MethodTooLong — createFiles runs 127 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 27 over it, 1.27× 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: IndexQuery.handle app/core/StockMovementIn/Application/Queries/IndexQuery.php:23— MethodTooLong — handle runs 115 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 15 over it, 1.15× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×3
Members sharing a duplicated core (4 members, 50+ identical tokens) app/core/CustomerGroup/Application/UseCases/DeleteCustomerGroup.php:25— app/core/CustomerGroup/Application/UseCases/DeleteCustomerGroup.php:25-66 | app/core/PermissionGroup/Application/UseCases/DeletePermissionGroup.php:26-70 | app/core/PurchaseItem/Application/UseCases/DeletePurchaseItem.php:26-57 | app/core/Warehouse/Application/UseCases/DeleteWarehouse.php:26-67 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) app/core/CustomerGroup/Application/UseCases/UpdateCustomerGroup.php:26— app/core/CustomerGroup/Application/UseCases/UpdateCustomerGroup.php:26-67 | app/core/PermissionGroup/Application/UseCases/UpdatePermissionGroup.php:26-70 | app/core/PurchaseItem/Application/UseCases/UpdatePurchaseItem.php:26-57 | app/core/Warehouse/Application/UseCases/UpdateWarehouse.php:26-67 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) extension-examples/CategoryProductThumbnail/Hooks/IndexHook.php:24— extension-examples/CategoryProductThumbnail/Hooks/IndexHook.php:24-34 | extension-examples/PriceListCountry/Hooks/IndexHook.php:24-35 | extension-examples/ShippingProviderFax/Hooks/IndexHook.php:24-33 | extension-examples/SupplierFax/Hooks/IndexHook.php:24-33 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Duplicated block (15 lines × 2) app/core/CustomInvoiceIn/Application/DTOs/CreateCustomInvoiceInRequest.php:25— app/core/CustomInvoiceIn/Application/DTOs/CreateCustomInvoiceInRequest.php:25-39 | app/core/CustomInvoiceIn/Domain/Entities/CustomInvoiceIn.php:25-39 — before extracting anything, compare `app/core/CustomInvoiceIn/Application/DTOs/CreateCustomInvoiceInRequest.php` and `app/core/CustomInvoiceIn/Domain/Entities/CustomInvoiceIn.php` as WHOLE FILES: 87% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (15 lines × 2) app/core/PurchaseItem/Http/Requests/CreatePurchaseItemRequest.php:41— app/core/PurchaseItem/Http/Requests/CreatePurchaseItemRequest.php:41-55 | app/core/PurchaseItem/Http/Requests/UpdatePurchaseItemRequest.php:39-53 — before extracting anything, compare `app/core/PurchaseItem/Http/Requests/CreatePurchaseItemRequest.php` and `app/core/PurchaseItem/Http/Requests/UpdatePurchaseItemRequest.php` as WHOLE FILES: 89% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (15 lines × 2) app/core/Product/Application/DTOs/IndexProductRequest.php:16— app/core/Product/Application/DTOs/IndexProductRequest.php:16-30 | app/core/StockIn/Application/DTOs/IndexStockInRequest.php:16-31 — 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/core/Product/Application/DTOs/IndexProductRequest.php:16` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (13 lines × 2) app/core/OrderItem/Http/Requests/CreateOrderItemRequest.php:45— app/core/OrderItem/Http/Requests/CreateOrderItemRequest.php:45-57 | app/core/OrderItem/Http/Requests/UpdateOrderItemRequest.php:45-57 — before extracting anything, compare `app/core/OrderItem/Http/Requests/CreateOrderItemRequest.php` and `app/core/OrderItem/Http/Requests/UpdateOrderItemRequest.php` as WHOLE FILES: 95% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 2) app/app/Exceptions/BadException.php:16— app/app/Exceptions/BadException.php:16-28 | app/app/Exceptions/ForbiddenBiddenException.php:16-28 — 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/app/Exceptions/BadException.php:16` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (13 lines × 2) app/core/Product/Application/DTOs/ShowProductRequest.php:15— app/core/Product/Application/DTOs/ShowProductRequest.php:15-27 | app/core/StockIn/Application/DTOs/CheckForStockMovementInRequest.php:15-28 — 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/core/Product/Application/DTOs/ShowProductRequest.php:15` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (7 lines × 2) app/core/InvoiceOut/Infrastructure/Repositories/EloquentInvoiceOutRepository.php:89— app/core/InvoiceOut/Infrastructure/Repositories/EloquentInvoiceOutRepository.php:89-95 | app/core/StockIn/Infrastructure/Repositories/EloquentStockInRepository.php:58-64 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (7 lines × 2) extension-examples/FastMode/ExtensionServiceProvider.php:25— extension-examples/FastMode/ExtensionServiceProvider.php:25-31 | extension-examples/InventoryTracking/ExtensionServiceProvider.php:24-30 — 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 (7 lines × 2) extension-examples/InvoiceInPDF/ExtensionServiceProvider.php:25— extension-examples/InvoiceInPDF/ExtensionServiceProvider.php:25-33 | extension-examples/InvoiceOutPDF/ExtensionServiceProvider.php:23-29 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (6 lines × 3) app/core/PurchaseItem/Infrastructure/Repositories/EloquentPurchaseItemRepository.php:47— app/core/PurchaseItem/Infrastructure/Repositories/EloquentPurchaseItemRepository.php:47-52 | app/core/User/Infrastructure/Repositories/EloquentUserRepository.php:14-19 | app/core/User/Infrastructure/Repositories/EloquentUserRepository.php:35-40 — 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/core/PurchaseItem/Infrastructure/Repositories/EloquentPurchaseItemRepository.php:47` 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 × 3) app/core/Customer/Application/DTOs/OrderShippingCustomerRequest.php:15— app/core/Customer/Application/DTOs/OrderShippingCustomerRequest.php:15-20 | app/core/OrderShipping/Application/DTOs/ShowOrderShippingRequest.php:16-21 | app/core/PermissionGroupUser/Application/DTOs/DeletePermissionGroupUserRequest.php:16-21 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (6 lines × 3) app/core/InvoiceOut/Infrastructure/Services/InvoiceOutServiceImpl.php:58— app/core/InvoiceOut/Infrastructure/Services/InvoiceOutServiceImpl.php:58-63 | app/core/Notifications/Infrastructure/Services/NotificationDBServiceImpl.php:29-34 | app/core/StockIn/Infrastructure/Services/StockInServiceImpl.php:40-45 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. 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.
AC3 · Page structure· Heading level jumps from h3 to h5 · ×2
Heading level jumps from h3 to h5 extension-examples/InvoiceInPDF/Views/index.blade.php:44— Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
Heading level jumps from h3 to h5 extension-examples/InvoiceOutPDF/Views/index.blade.php:37— Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
AC4 · Keyboard semantics· Anchor without href · ×2
Anchor without href app/resources/js/react/components/CommonDataTable.jsx:124— An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
Anchor without href app/resources/js/react/components/CommonDataTableV2.jsx:259— An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
AC6 · Visual & motion safety· Animation without a prefers-reduced-motion guard · ×2
Animation without a prefers-reduced-motion guard app/resources/css/app.css:120— `.menu-mobile-item` moves (`transition: transform 0.15s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard app/resources/css/popup.css:18— `.popup-card` moves (`animation: fadeIn 0.2s ease-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
D4 · Code Duplication· Members sharing a duplicated core (12 members, 50+ identical tokens) · ×2
Members sharing a duplicated core (12 members, 50+ identical tokens) app/core/CategoryProduct/Application/UseCases/ShowCategoryProduct.php:22— app/core/CategoryProduct/Application/UseCases/ShowCategoryProduct.php:22-51 | app/core/Customer/Application/UseCases/ShowCustomer.php:25-57 | app/core/CustomerGroup/Application/UseCases/ShowCustomerGroup.php:24-53 | app/core/InvoiceIn/Application/UseCases/ShowInvoiceIn.php:24-52 | app/core/InvoiceOut/Application/UseCases/ShowInvoiceOut.php:22-51 | app/core/Order/Application/UseCases/ShowOrder.php:23-53 | app/core/OrderShipping/Application/UseCases/ShowOrderShipping.php:22-49 | app/core/Permission/Application/UseCases/ShowPermission.php:26-55 | app/core/Product/Application/UseCases/ShowProduct.php:24-53 | app/core/StockIn/Application/UseCases/ShowStockIn.php:20-46 | app/core/StockOut/Application/UseCases/ShowStockOut.php:22-51 | app/core/Warehouse/Application/UseCases/ShowWarehouse.php:25-52 — These 12 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 12 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 12 times.
Members sharing a duplicated core (12 members, 50+ identical tokens) app/core/CategoryProduct/Application/UseCases/UpdateCategoryProduct.php:23— app/core/CategoryProduct/Application/UseCases/UpdateCategoryProduct.php:23-65 | app/core/CustomInvoiceIn/Application/UseCases/UpdateCustomInvoiceIn.php:24-66 | app/core/CustomInvoiceOut/Application/UseCases/UpdateCustomInvoiceOut.php:23-65 | app/core/Customer/Application/UseCases/UpdateCustomer.php:23-64 | app/core/Order/Application/UseCases/UpdateOrder.php:25-102 | app/core/PriceList/Application/UseCases/UpdatePriceList.php:23-66 | app/core/Product/Application/UseCases/UpdateProduct.php:24-65 | app/core/Purchase/Application/UseCases/UpdatePurchase.php:24-109 | app/core/StockIn/Application/UseCases/UpdateStockIn.php:25-99 | app/core/StockMovementIn/Application/UseCases/UpdateStockMovementIn.php:26-57 | app/core/StockOut/Application/UseCases/UpdateStockOut.php:25-109 | app/core/Supplier/Application/UseCases/UpdateSupplier.php:24-65 — These 12 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 12 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 12 times.
D4 · Code Duplication· Members sharing a duplicated core (7 members, 50+ identical tokens) · ×2
Members sharing a duplicated core (7 members, 50+ identical tokens) app/core/Business/Infrastructure/Repositories/EloquentBusinessRepository.php:31— app/core/Business/Infrastructure/Repositories/EloquentBusinessRepository.php:31-39 | app/core/Order/Infrastructure/Repositories/EloquentOrderRepository.php:40-64 | app/core/PurchaseItem/Infrastructure/Repositories/EloquentPurchaseItemRepository.php:46-55 | app/core/StockMovementOut/Infrastructure/Repositories/EloquentStockMovementOutRepository.php:21-30 | app/core/StockMovementOut/Infrastructure/Repositories/EloquentStockMovementOutRepository.php:34-43 | app/core/User/Infrastructure/Repositories/EloquentUserRepository.php:13-22 | app/core/User/Infrastructure/Repositories/EloquentUserRepository.php:34-43 — These 7 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 7 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 7 times.
Members sharing a duplicated core (7 members, 50+ identical tokens) app/core/OrderItem/Infrastructure/Repositories/EloquentOrderItemRepository.php:65— app/core/OrderItem/Infrastructure/Repositories/EloquentOrderItemRepository.php:65-74 | app/core/OrderShipping/Infrastructure/Repositories/EloquentOrderShippingRepository.php:19-28 | app/core/OrderShipping/Infrastructure/Repositories/EloquentOrderShippingRepository.php:32-44 | app/core/OrderShipping/Infrastructure/Repositories/EloquentOrderShippingRepository.php:67-79 | app/core/Permission/Infrastructure/Repositories/EloquentPermissionRepository.php:30-41 | app/core/PermissionGroupUser/Infrastructure/Repositories/EloquentPermissionGroupUserRepository.php:42-53 | app/core/StockOut/Infrastructure/Repositories/EloquentStockOutRepository.php:20-28 — These 7 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 7 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 7 times.
D4 · Code Duplication· Members sharing a duplicated core (6 members, 50+ identical tokens) · ×2
Members sharing a duplicated core (6 members, 50+ identical tokens) app/core/CustomerGroup/Application/UseCases/CreateCustomerGroup.php:24— app/core/CustomerGroup/Application/UseCases/CreateCustomerGroup.php:24-65 | app/core/Permission/Application/UseCases/CreateFullPermission.php:28-62 | app/core/Permission/Application/UseCases/CreatePermission.php:27-58 | app/core/PermissionGroup/Application/UseCases/CreatePermissionGroup.php:26-71 | app/core/PurchaseItem/Application/UseCases/CreatePurchaseItem.php:26-57 | app/core/Warehouse/Application/UseCases/CreateWarehouse.php:26-67 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
Members sharing a duplicated core (6 members, 50+ identical tokens) app/core/Inventory/Application/Queries/IndexQuery.php:26— app/core/Inventory/Application/Queries/IndexQuery.php:26-145 | app/core/Product/Application/Queries/IndexQuery.php:23-57 | app/core/StockMovementIn/Application/Queries/IndexQuery.php:25-182 | app/core/StockMovementOut/Application/Queries/IndexQuery.php:21-69 | app/core/User/Application/Queries/IndexQuery.php:24-57 | app/core/Warehouse/Application/Queries/IndexQuery.php:27-58 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
Duplicated block (31 lines × 2) app/app/Console/Commands/MakeEventModule.php:34— app/app/Console/Commands/MakeEventModule.php:34-64 | app/app/Console/Commands/MakeListenerModule.php:33-63 — 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 before the matched lines, `app/app/Console/Commands/MakeEventModule.php:33` calls `singular` and `app/app/Console/Commands/MakeListenerModule.php:32` 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 (31 lines × 2) app/core/PermissionGroupUser/Application/UseCases/CreatePermissionAdminGroupUser.php:24— app/core/PermissionGroupUser/Application/UseCases/CreatePermissionAdminGroupUser.php:24-54 | app/core/PermissionGroupUser/Application/UseCases/CreatePermissionGroupUser.php:26-56 — before extracting anything, compare `app/core/PermissionGroupUser/Application/UseCases/CreatePermissionAdminGroupUser.php` and `app/core/PermissionGroupUser/Application/UseCases/CreatePermissionGroupUser.php` as WHOLE FILES: 87% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `app/core/PermissionGroupUser/Application/UseCases/CreatePermissionGroupUser.php:58` calls `dispatch` and `app/core/PermissionGroupUser/Application/UseCases/CreatePermissionAdminGroupUser.php:55` 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 (25–27 lines × 4) app/core/CustomerGroup/Application/UseCases/DeleteCustomerGroup.php:27— app/core/CustomerGroup/Application/UseCases/DeleteCustomerGroup.php:27-51 | app/core/PermissionGroup/Application/UseCases/DeletePermissionGroup.php:29-55 | app/core/PurchaseItem/Application/UseCases/DeletePurchaseItem.php:28-52 | app/core/Warehouse/Application/UseCases/DeleteWarehouse.php:28-52 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 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 4 times.
Duplicated block (25–27 lines × 4) app/core/CustomerGroup/Application/UseCases/UpdateCustomerGroup.php:28— app/core/CustomerGroup/Application/UseCases/UpdateCustomerGroup.php:28-52 | app/core/PermissionGroup/Application/UseCases/UpdatePermissionGroup.php:29-55 | app/core/PurchaseItem/Application/UseCases/UpdatePurchaseItem.php:28-52 | app/core/Warehouse/Application/UseCases/UpdateWarehouse.php:28-52 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 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 4 times.
Duplicated block (15 lines × 4) app/core/Inventory/Application/Queries/IndexQuery.php:37— app/core/Inventory/Application/Queries/IndexQuery.php:37-51 | app/core/Overview/Infrastructure/Repositories/EloquentOverviewRepository.php:62-76 | app/core/StockMovementIn/Application/Queries/IndexQuery.php:36-50 | app/core/StockMovementIn/Infrastructure/Repositories/EloquentStockMovementInRepository.php:85-99 — before extracting anything, compare `app/core/Inventory/Application/Queries/IndexQuery.php` and `app/core/StockMovementIn/Application/Queries/IndexQuery.php` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 207 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (15 lines × 4) extension-examples/CustomerFax/Hooks/CreateHook.php:16— extension-examples/CustomerFax/Hooks/CreateHook.php:16-31 | extension-examples/InvoiceOutExtras/Hooks/CreateHook.php:16-31 | extension-examples/ProductRenew/Hooks/CreateHook.php:16-30 | extension-examples/TrackingNumberOrderShipping/Hooks/CreateHook.php:16-31 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 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 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `extension-examples/CustomerFax/Hooks/CreateHook.php:16` 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 first that the copies are not typed on the same thing: `ExampleModel` names `Extensions\CustomerFax\Models\ExampleModel` in one and `Extensions\InvoiceOutExtras\Models\ExampleModel` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (14 lines × 4) app/core/Inventory/Application/Queries/IndexQuery.php:123— app/core/Inventory/Application/Queries/IndexQuery.php:123-141 | app/core/Product/Application/Queries/IndexQuery.php:39-52 | app/core/StockMovementIn/Application/Queries/IndexQuery.php:160-178 | app/core/Warehouse/Application/Queries/IndexQuery.php:38-54 — before extracting anything, compare `app/core/Inventory/Application/Queries/IndexQuery.php` and `app/core/Product/Application/Queries/IndexQuery.php` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 81 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `app/core/Inventory/Application/Queries/IndexQuery.php:123` 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 (14 lines × 4) app/core/OrderItem/Application/DTOs/CancelledOrderItemRequest.php:18— app/core/OrderItem/Application/DTOs/CancelledOrderItemRequest.php:18-34 | app/core/OrderItem/Application/DTOs/GetSummaryOrderItemRequest.php:18-34 | app/core/OrderShipping/Application/DTOs/CheckReadyOrderShippingRequest.php:15-28 | app/core/OrderShipping/Application/DTOs/GetOrderShippingByOrderIdRequest.php:15-28 — before extracting anything, compare `app/core/OrderItem/Application/DTOs/CancelledOrderItemRequest.php` and `app/core/OrderItem/Application/DTOs/GetSummaryOrderItemRequest.php` as WHOLE FILES: 87% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `app/core/OrderItem/Application/DTOs/CancelledOrderItemRequest.php:18` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (10–11 lines × 2) app/core/Extension/Application/DTOs/MakeExtensionCommand.php:23— app/core/Extension/Application/DTOs/MakeExtensionCommand.php:23-33 | app/core/Extension/Domain/Entities/Extension.php:24-33 — before extracting anything, compare `app/core/Extension/Application/DTOs/MakeExtensionCommand.php` and `app/core/Extension/Domain/Entities/Extension.php` as WHOLE FILES: 90% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `app/core/Extension/Application/DTOs/MakeExtensionCommand.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. 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 (10–11 lines × 2) app/core/OrderShipping/Application/DTOs/CreateOrderShippingRequest.php:27— app/core/OrderShipping/Application/DTOs/CreateOrderShippingRequest.php:27-36 | app/core/OrderShipping/Domain/Entities/OrderShipping.php:29-39 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (9–10 lines × 2) app/core/Customer/Application/DTOs/CreateCustomerRequest.php:40— app/core/Customer/Application/DTOs/CreateCustomerRequest.php:40-48 | app/core/Customer/Domain/Entities/Customer.php:38-47 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (9–10 lines × 2) app/core/Order/Application/DTOs/CreateOrderRequest.php:24— app/core/Order/Application/DTOs/CreateOrderRequest.php:24-33 | app/core/Order/Application/DTOs/UpdateOrderRequest.php:25-33 — before extracting anything, compare `app/core/Order/Application/DTOs/CreateOrderRequest.php` and `app/core/Order/Application/DTOs/UpdateOrderRequest.php` as WHOLE FILES: 85% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `app/core/Order/Application/DTOs/CreateOrderRequest.php:24` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (5 lines × 6) app/core/Business/Infrastructure/Repositories/EloquentBusinessRepository.php:32— app/core/Business/Infrastructure/Repositories/EloquentBusinessRepository.php:32-36 | app/core/PurchaseItem/Infrastructure/Repositories/EloquentPurchaseItemRepository.php:47-52 | app/core/StockMovementOut/Infrastructure/Repositories/EloquentStockMovementOutRepository.php:22-27 | app/core/StockMovementOut/Infrastructure/Repositories/EloquentStockMovementOutRepository.php:35-40 | app/core/User/Infrastructure/Repositories/EloquentUserRepository.php:14-19 | app/core/User/Infrastructure/Repositories/EloquentUserRepository.php:35-40 — there are 6 copies across 4 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 6 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/core/Business/Infrastructure/Repositories/EloquentBusinessRepository.php:32` 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 × 6) app/core/Customer/Infrastructure/Services/CustomerServiceImpl.php:65— app/core/Customer/Infrastructure/Services/CustomerServiceImpl.php:65-69 | app/core/Extension/Infrastructure/Services/ExtensionServiceImpl.php:45-49 | app/core/OrderItem/Infrastructure/Services/OrderItemServiceImpl.php:69-73 | app/core/PermissionGroup/Infrastructure/Services/PermissionGroupServiceImpl.php:41-46 | app/core/PermissionGroupUser/Infrastructure/Services/PermissionGroupUserServiceImpl.php:27-32 | app/core/Warehouse/Infrastructure/Services/WarehouseServiceImpl.php:25-29 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 6 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 6 times. 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 (5 lines × 4) app/core/InvoiceOut/Infrastructure/Repositories/EloquentInvoiceOutRepository.php:89— app/core/InvoiceOut/Infrastructure/Repositories/EloquentInvoiceOutRepository.php:89-94 | app/core/OrderItem/Infrastructure/Repositories/EloquentOrderItemRepository.php:125-129 | app/core/OrderItem/Infrastructure/Repositories/EloquentOrderItemRepository.php:211-215 | app/core/StockIn/Infrastructure/Repositories/EloquentStockInRepository.php:58-63 — 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. 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/core/StockIn/Infrastructure/Repositories/EloquentStockInRepository.php:56` calls `leftJoin` and `app/core/OrderItem/Infrastructure/Repositories/EloquentOrderItemRepository.php:124` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (5 lines × 4) extension-examples/CategoryProductThumbnail/Hooks/IndexHook.php:24— extension-examples/CategoryProductThumbnail/Hooks/IndexHook.php:24-29 | extension-examples/PriceListCountry/Hooks/IndexHook.php:24-29 | extension-examples/ShippingProviderFax/Hooks/IndexHook.php:24-28 | extension-examples/SupplierFax/Hooks/IndexHook.php:24-28 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 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 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `extension-examples/CategoryProductThumbnail/Hooks/IndexHook.php:24` 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 × 3) app/core/InventoryAdjustment/Application/Queries/IndexQuery.php:25— app/core/InventoryAdjustment/Application/Queries/IndexQuery.php:25-32 | app/core/OrderItem/Application/Queries/IndexQuery.php:69-73 | app/core/StockMovementOut/Application/Queries/IndexQuery.php:43-47 — before extracting anything, compare `app/core/OrderItem/Application/Queries/IndexQuery.php` and `app/core/StockMovementOut/Application/Queries/IndexQuery.php` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 76 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `app/core/InventoryAdjustment/Application/Queries/IndexQuery.php:25` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (5 lines × 3) extension-examples/Debt/Resources/views/index.blade.php:7— extension-examples/Debt/Resources/views/index.blade.php:7-11 | extension-examples/InvoiceInPDF/Views/index.blade.php:6-10 | extension-examples/InvoiceOutPDF/Views/index.blade.php:6-11 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. 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 × 3) app/core/Customer/Application/DTOs/DeleteCustomerRequest.php:14— app/core/Customer/Application/DTOs/DeleteCustomerRequest.php:14-26 | app/core/Shipping/Application/DTOs/DeleteShippingRequest.php:15-28 | app/core/Supplier/Application/DTOs/DeleteSupplierRequest.php:15-26 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `app/core/Customer/Application/DTOs/DeleteCustomerRequest.php:14` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (12 lines × 3) app/core/Customer/Application/DTOs/ShowCustomerRequest.php:14— app/core/Customer/Application/DTOs/ShowCustomerRequest.php:14-26 | app/core/Purchase/Application/DTOs/ShowPurchaseRequest.php:16-29 | app/core/Warehouse/Application/DTOs/DeleteWarehouseRequest.php:13-24 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `app/core/Customer/Application/DTOs/ShowCustomerRequest.php:14` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (12 lines × 15) extension-examples/CategoryProductThumbnail/Hooks/ValidateCreateHook.php:18— extension-examples/CategoryProductThumbnail/Hooks/ValidateCreateHook.php:18-29 | extension-examples/CustomInvoiceIn/Hooks/ValidateCreateHook.php:15-26 | extension-examples/CustomInvoiceOut/Hooks/ValidateCreateHook.php:15-26 | extension-examples/CustomerFax/Hooks/ValidateCreateHook.php:15-26 | extension-examples/InvoiceInExtras/Hooks/ValidateCreateHook.php:15-26 | extension-examples/InvoiceOutExtras/Hooks/ValidateCreateHook.php:15-26 | extension-examples/OrderInformation/Hooks/ValidateCreateHook.php:15-26 | extension-examples/PriceListCountry/Hooks/ValidateCreateHook.php:18-29 | extension-examples/ProductRenew/Hooks/ValidateCreateHook.php:15-26 | extension-examples/PurchaseInformation/Hooks/ValidateCreateHook.php:15-26 | extension-examples/ShippingProviderFax/Hooks/ValidateCreateHook.php:18-29 | extension-examples/StockOutExtras/Hooks/ValidateCreateHook.php:15-26 | extension-examples/StockinExtras/Hooks/ValidateCreateHook.php:15-26 | extension-examples/SupplierFax/Hooks/ValidateCreateHook.php:18-29 | extension-examples/TrackingNumberOrderShipping/Hooks/ValidateCreateHook.php:15-26 — before extracting anything, compare `extension-examples/InvoiceInExtras/Hooks/ValidateCreateHook.php` and `extension-examples/InvoiceOutExtras/Hooks/ValidateCreateHook.php` as WHOLE FILES: 83% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `extension-examples/CategoryProductThumbnail/Hooks/ValidateCreateHook.php:18` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (12 lines × 15) extension-examples/CategoryProductThumbnail/Hooks/ValidateUpdateHook.php:18— extension-examples/CategoryProductThumbnail/Hooks/ValidateUpdateHook.php:18-29 | extension-examples/CustomInvoiceIn/Hooks/ValidateUpdateHook.php:15-26 | extension-examples/CustomInvoiceOut/Hooks/ValidateUpdateHook.php:15-26 | extension-examples/CustomerFax/Hooks/ValidateUpdateHook.php:15-26 | extension-examples/InvoiceInExtras/Hooks/ValidateUpdateHook.php:16-27 | extension-examples/InvoiceOutExtras/Hooks/ValidateUpdateHook.php:15-26 | extension-examples/OrderInformation/Hooks/ValidateUpdateHook.php:15-26 | extension-examples/PriceListCountry/Hooks/ValidateUpdateHook.php:18-29 | extension-examples/ProductRenew/Hooks/ValidateUpdateHook.php:15-26 | extension-examples/PurchaseInformation/Hooks/ValidateUpdateHook.php:15-26 | extension-examples/ShippingProviderFax/Hooks/ValidateUpdateHook.php:18-29 | extension-examples/StockOutExtras/Hooks/ValidateUpdateHook.php:15-26 | extension-examples/StockinExtras/Hooks/ValidateUpdateHook.php:15-26 | extension-examples/SupplierFax/Hooks/ValidateUpdateHook.php:18-29 | extension-examples/TrackingNumberOrderShipping/Hooks/ValidateUpdateHook.php:15-26 — before extracting anything, compare `extension-examples/OrderInformation/Hooks/ValidateUpdateHook.php` and `extension-examples/PurchaseInformation/Hooks/ValidateUpdateHook.php` as WHOLE FILES: 83% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `extension-examples/CategoryProductThumbnail/Hooks/ValidateUpdateHook.php:18` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (21 lines × 2) extension-examples/CustomInvoiceIn/Hooks/UpdateHook.php:17— extension-examples/CustomInvoiceIn/Hooks/UpdateHook.php:17-37 | extension-examples/CustomInvoiceOut/Hooks/UpdateHook.php:17-37 — 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 `extension-examples/CustomInvoiceIn/Hooks/UpdateHook.php:17` 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 first that the copies are not typed on the same thing: `ExampleModel` names `Extensions\CustomInvoiceIn\Models\ExampleModel` in one and `Extensions\CustomInvoiceOut\Models\ExampleModel` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (21 lines × 2) extension-examples/StockOutExtras/Hooks/UpdateHook.php:17— extension-examples/StockOutExtras/Hooks/UpdateHook.php:17-37 | extension-examples/StockinExtras/Hooks/UpdateHook.php:17-37 — 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 `extension-examples/StockOutExtras/Hooks/UpdateHook.php:17` 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 first that the copies are not typed on the same thing: `StockinExtrasModel` names `Extensions\StockOutExtras\Models\StockinExtrasModel` in one and `Extensions\StockinExtras\Models\StockinExtrasModel` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Wholesale file copy (185 identical lines × 2 files) extension-examples/Hrm/Resources/js/components/IndexLeave.jsx:1— extension-examples/Hrm/Resources/js/components/IndexLeave.jsx:1 · extension-examples/Hrm/Resources/js/components/LeaveApprovalList.jsx:1 — these 2 files are line-for-line copies of one another — 185 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Wholesale file copy (185 identical lines × 2 files) extension-examples/Hrm/Resources/js/components/IndexTimeAttendance.jsx:1— extension-examples/Hrm/Resources/js/components/IndexTimeAttendance.jsx:1 · extension-examples/Hrm/Resources/js/components/TimeAttendance.jsx:1 — these 2 files are line-for-line copies of one another — 185 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.
Dead file (~27 LoC) app/resources/js/react/components/Stock/StockInDetail/ProductTable.jsx— no import path from any entry point (7 application, 1 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~27 LoC) app/resources/js/react/components/Stock/StockOutDetail/ProductTable.jsx— no import path from any entry point (7 application, 1 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~15 LoC) app/resources/js/core/Extension.js— no import path from any entry point (7 application, 1 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~15 LoC) app/resources/js/react/components/Stock/StockOutDetail/TwoCol.jsx— no import path from any entry point (7 application, 1 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~11 LoC) app/resources/js/react/components/Stock/StockOutDetail/InfoBox.jsx— no import path from any entry point (7 application, 1 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~11 LoC) app/resources/js/react/services/StockMovementOut.js— no import path from any entry point (7 application, 1 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
AC3 · Page structure· Heading level jumps from h1 to h5 · ×1
Heading level jumps from h1 to h5 app/resources/views/welcome.blade.php:46— Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
AC3 · Page structure· Heading level jumps from h2 to h5 · ×1
Heading level jumps from h2 to h5 extension-examples/CustomHomePage/Resources/views/index.blade.php:50— Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
AC3 · Page structure· Heading level jumps from h3 to h6 · ×1
Heading level jumps from h3 to h6 extension-examples/Debt/Resources/views/index.blade.php:62— Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
AC4 · Keyboard semantics· Modal dialog does not manage focus · ×1
Modal dialog does not manage focus app/resources/js/react/layouts/PopupLayout.jsx:14— This <div role="dialog"> is a modal dialog, but nothing moves focus into it when it opens and nothing keeps focus inside it while it is open, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close.
AC6 · Visual & motion safety· Focus outline removed in CSS without a · ×1
Focus outline removed in CSS without a :focus replacement app/resources/css/topbar.css:21— `.erp-search-box input:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
AC7 · A11y enforcement· Accessibility enforcement below the top rung · ×1
Accessibility enforcement below the top rung package.json:2— No accessibility enforcement found — no a11y linter (eslint-plugin-jsx-a11y) and no axe/pa11y/Lighthouse in tests or CI. Start with the linter to catch issues at author time. What was searched, so you can tell an absence from a miss: the 197 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.
CommonDataTableV2.CommonDataTableV2 (cyclomatic 37) app/resources/js/react/components/CommonDataTableV2.jsx:11— CommonDataTableV2.CommonDataTableV2 has cyclomatic complexity 37 (threshold 15). Of this number, 21 points are the body's own statements and 16 belong to 5 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
EditOrder.EditOrder (cyclomatic 33) app/resources/js/react/components/Order/EditOrder.jsx:27— EditOrder.EditOrder has cyclomatic complexity 33 (threshold 15). Of this number, 17 points are the body's own statements and 16 belong to 9 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
EditPurchase.EditPurchase (cyclomatic 28) app/resources/js/react/components/Purchases/EditPurchase.jsx:27— EditPurchase.EditPurchase has cyclomatic complexity 28 (threshold 15). Of this number, 18 points are the body's own statements and 10 belong to 6 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
ListProduct.ListProducts (cyclomatic 22) app/resources/js/react/components/Purchases/AddProduct/ListProduct.jsx:20— ListProduct.ListProducts has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 10 of the 22 points are its own statements and the rest belongs to 9 function items inside it that branch (a function literal at line 81, a function literal at line 112, a function literal at line 139, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
StockInDetail.StockInDetail (cyclomatic 21) app/resources/js/react/components/Stock/StockInDetail.jsx:26— StockInDetail.StockInDetail has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 9 of the 21 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 84, 123, 155, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
AutoDataTable.AutoDataTable (cyclomatic 21) app/resources/js/react/components/AutoDataTable.jsx:3— AutoDataTable.AutoDataTable has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 6 of the 21 points are its own statements and the rest belongs to 4 function items inside it that branch (handleGoto, load, a function literal at line 80, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
Products.Products (cyclomatic 20) app/resources/js/react/components/Order/EditOrder/Products.jsx:14— Products.Products has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 5 of the 20 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 41, 83, 69, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
CommonDataTable.CommonDataTable (cyclomatic 19) app/resources/js/react/components/CommonDataTable.jsx:5— CommonDataTable.CommonDataTable has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 8 of the 19 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 59, 64, 117, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
PopupContext.PopupProvider (cyclomatic 18) app/resources/js/react/components/popups/PopupContext.jsx:12— PopupContext.PopupProvider has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 3 of the 18 points are its own statements and the rest belongs to 4 function items inside it that branch (a function literal at line 18, getIconStyle, popupTitle, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
SearchSelect.SearchSelect (cyclomatic 18) app/resources/js/react/components/UI/Input/SearchSelect.jsx:5— SearchSelect.SearchSelect has cyclomatic complexity 18 (threshold 15). Of this number, 9 points are the body's own statements and 9 belong to 4 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
StockOutDetail.StockOutDetail (cyclomatic 18) app/resources/js/react/components/Stock/StockOutDetail.jsx:29— StockOutDetail.StockOutDetail has cyclomatic complexity 18 (threshold 15). Of this number, 9 points are the body's own statements and 9 belong to 6 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.
EditOrder.EditOrder (cognitive 44) app/resources/js/react/components/Order/EditOrder.jsx:27— EditOrder.EditOrder has cognitive complexity 44 (threshold 15). Drivers by points: ternaries 12 (22 pts), if/else 16, boolean chains 6 (nesting depth added 10). Of this number, 26 points are the body's own statements and 18 belong to 9 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CommonDataTableV2.CommonDataTableV2 (cognitive 42) app/resources/js/react/components/CommonDataTableV2.jsx:11— CommonDataTableV2.CommonDataTableV2 has cognitive complexity 42 (threshold 15). Drivers by points: ternaries 13 (27 pts), boolean chains 11, if/else 3 (4 pts) (nesting depth added 15). Of this number, 20 points are the body's own statements and 22 belong to 5 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.
SearchSelect.SearchSelect (cognitive 26) app/resources/js/react/components/UI/Input/SearchSelect.jsx:5— SearchSelect.SearchSelect has cognitive complexity 26 (threshold 15). Drivers by points: ternaries 7 (15 pts), if/else 6 (9 pts), boolean chains 2 (nesting depth added 11). Of this number, 15 points are the body's own statements and 11 belong to 4 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CommonDataTable.CommonDataTable (cognitive 26) app/resources/js/react/components/CommonDataTable.jsx:5— CommonDataTable.CommonDataTable has cognitive complexity 26 (threshold 15). Drivers by points: ternaries 7 (16 pts), boolean chains 8, if/else 1 (2 pts) (nesting depth added 10). Most of this is not in the body itself: 8 of the 26 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 64, 59, 117, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
StockInDetail.StockInDetail (cognitive 23) app/resources/js/react/components/Stock/StockInDetail.jsx:26— StockInDetail.StockInDetail has cognitive complexity 23 (threshold 15). Drivers by points: if/else 11, ternaries 7 (10 pts), boolean chains 2 (nesting depth added 3). Most of this is not in the body itself: 11 of the 23 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 84, 123, 155, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
EditPurchase.EditPurchase (cognitive 23) app/resources/js/react/components/Purchases/EditPurchase.jsx:27— EditPurchase.EditPurchase has cognitive complexity 23 (threshold 15). Drivers by points: boolean chains 13, if/else 10. Most of this is not in the body itself: 11 of the 23 points are its own statements and the rest belongs to 6 function items inside it that branch (nextStep, a function literal at line 65, a function literal at line 87, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
ListProduct.ListProducts (cognitive 22) app/resources/js/react/components/Purchases/AddProduct/ListProduct.jsx:20— ListProduct.ListProducts has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 10 (11 pts), if/else 10, boolean chains 1 (nesting depth added 1). Most of this is not in the body itself: 10 of the 22 points are its own statements and the rest belongs to 9 function items inside it that branch (a function literal at line 81, a function literal at line 112, a function literal at line 139, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
activity-logs.ActivityLogs (cognitive 22) app/resources/js/react/pages/activity-logs.jsx:11— activity-logs.ActivityLogs has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 8 (19 pts), boolean chains 3 (nesting depth added 11). None of this is in the body itself: all 22 points belong to 3 function literals inside it that branch (lines 73, 89, 101). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
StockOutDetail.StockOutDetail (cognitive 21) app/resources/js/react/components/Stock/StockOutDetail.jsx:29— StockOutDetail.StockOutDetail has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10, ternaries 5 (8 pts), boolean chains 3 (nesting depth added 3). Of this number, 11 points are the body's own statements and 10 belong to 6 function literals inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
ExtensionCard.ExtensionCard (cognitive 19) app/resources/js/react/components/Extension/ExtensionCard.jsx:11— ExtensionCard.ExtensionCard has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 7 (13 pts), if/else 4 (6 pts) (nesting depth added 8). Most of this is not in the body itself: 9 of the 19 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 39, 46, 54, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
Products.Products (cognitive 18) app/resources/js/react/components/Order/EditOrder/Products.jsx:14— Products.Products has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9, ternaries 4 (7 pts), boolean chains 2 (nesting depth added 3). Most of this is not in the body itself: 7 of the 18 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 41, 69, 83, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
IndexCustomInvoiceOuts.IndexCustomInvoiceOuts (cognitive 16) app/resources/js/react/components/Invoice/IndexCustomInvoiceOuts.jsx:21— IndexCustomInvoiceOuts.IndexCustomInvoiceOuts has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9, ternaries 5 (7 pts) (nesting depth added 2). Most of this is not in the body itself: 5 of the 16 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 67, 95, 130, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
AutoDataTable.AutoDataTable (cognitive 16) app/resources/js/react/components/AutoDataTable.jsx:3— AutoDataTable.AutoDataTable has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 7, if/else 5, error handling 2 (3 pts), ternaries 1 (nesting depth added 1). Most of this is not in the body itself: 4 of the 16 points are its own statements and the rest belongs to 4 function items inside it that branch (handleGoto, load, a function literal at line 80, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
TooManyMethods: PermissionBuilder app/core/Permission/Infrastructure/Helpers/PermissionBuilder.php:8— TooManyMethods — 39 methods. The bar is 30 methods; this is 9 over it, 1.30× 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.
Change coupling: IndexInvoiceOuts.jsx ↔ InvoiceOutsDetail.jsx app/resources/js/react/components/Invoice/IndexInvoiceOuts.jsx:1— `app/resources/js/react/components/Invoice/IndexInvoiceOuts.jsx` and `app/resources/js/react/components/Invoice/InvoiceOuts/InvoiceOutsDetail.jsx` change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `bea18e7b` fix: fix router display for invoices detail. change key display total…; `fb327ccd` fix: add translate. refactor: implement label into input form (at that commit the file was still `app/resources/js/react/components/Invoice/InvoiceOuts.jsx`); `b6784414` Add amount paid, fix bug logic (at that commit the file was still `app/resources/js/react/components/Invoice/InvoiceOuts.jsx`) — run `git show` on any of them.
D4 · Code Duplication· Edited copy of a member (51 corresponding lines) · ×1
Edited copy of a member (51 corresponding lines) app/core/OrderItem/Application/Queries/IndexQuery.php:22— app/core/OrderItem/Application/Queries/IndexQuery.php:22-99 | app/core/OrderItem/Infrastructure/Repositories/EloquentOrderItemRepository.php:78-130 — These two members are one piece of code written twice and then edited apart: 51 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Members sharing a duplicated core (22 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (22 members, 50+ identical tokens) app/core/Business/Application/UseCases/ViewRender.php:18— app/core/Business/Application/UseCases/ViewRender.php:18-43 | app/core/CategoryProduct/Application/UseCases/ViewCategoryProduct.php:17-52 | app/core/CustomInvoiceIn/Application/UseCases/ViewCustomInvoiceIn.php:19-54 | app/core/CustomInvoiceOut/Application/UseCases/ViewCustomInvoiceOut.php:19-54 | app/core/Customer/Application/UseCases/ViewRender.php:19-54 | app/core/CustomerGroup/Application/UseCases/ViewCustomerGroup.php:19-54 | app/core/Inventory/Application/UseCases/ViewRender.php:18-53 | app/core/InventoryAdjustment/Application/UseCases/ViewRender.php:18-53 | app/core/InvoiceIn/Application/UseCases/ViewInvoiceIn.php:17-52 | app/core/InvoiceOut/Application/UseCases/ViewInvoiceOut.php:17-52 | app/core/Order/Application/UseCases/ViewRender.php:18-53 | app/core/OrderShipping/Application/UseCases/ViewRender.php:18-53 | app/core/PermissionGroup/Application/UseCases/ViewRender.php:18-53 | app/core/PriceList/Application/UseCases/ViewRender.php:18-53 | app/core/Product/Application/UseCases/ViewRender.php:18-53 | app/core/Purchase/Application/UseCases/ViewPurchase.php:17-52 | app/core/PurchaseItem/Application/UseCases/ViewPurchase.php:17-52 | app/core/Shipping/Application/UseCases/ViewShipping.php:17-54 | app/core/StockIn/Application/UseCases/ViewStockIn.php:17-52 | app/core/StockOut/Application/UseCases/ViewStockOut.php:17-52 | app/core/Supplier/Application/UseCases/ViewSupplier.php:15-50 | app/core/Warehouse/Application/UseCases/ViewWarehouse.php:17-54 — These 22 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 22 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 22 times.
Duplicated block (19–46 lines × 4) app/core/OrderItem/Application/Queries/IndexQuery.php:25— app/core/OrderItem/Application/Queries/IndexQuery.php:25-70 | app/core/OrderItem/Infrastructure/Repositories/EloquentOrderItemRepository.php:80-125 | app/core/PurchaseItem/Application/Queries/IndexQuery.php:26-44 | app/core/StockMovementOut/Application/Queries/IndexQuery.php:23-42 — before extracting anything, compare `app/core/OrderItem/Application/Queries/IndexQuery.php` and `app/core/PurchaseItem/Application/Queries/IndexQuery.php` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 83 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `app/core/OrderItem/Application/Queries/IndexQuery.php:25` 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/core/OrderItem/Application/Queries/IndexQuery.php:71` calls `join` and `app/core/PurchaseItem/Application/Queries/IndexQuery.php:45` 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 (12–37 lines × 3) app/core/Inventory/Application/Queries/IndexQuery.php:56— app/core/Inventory/Application/Queries/IndexQuery.php:56-91 | app/core/StockMovementIn/Application/Queries/IndexQuery.php:60-96 | app/core/StockOut/Infrastructure/Repositories/EloquentStockOutRepository.php:82-93 — before extracting anything, compare `app/core/Inventory/Application/Queries/IndexQuery.php` and `app/core/StockMovementIn/Application/Queries/IndexQuery.php` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 207 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `app/core/Inventory/Application/Queries/IndexQuery.php:56` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (32–34 lines × 21) app/core/CategoryProduct/Application/UseCases/ViewCategoryProduct.php:21— app/core/CategoryProduct/Application/UseCases/ViewCategoryProduct.php:21-52 | app/core/CustomInvoiceIn/Application/UseCases/ViewCustomInvoiceIn.php:23-54 | app/core/CustomInvoiceOut/Application/UseCases/ViewCustomInvoiceOut.php:23-54 | app/core/Customer/Application/UseCases/ViewRender.php:23-54 | app/core/CustomerGroup/Application/UseCases/ViewCustomerGroup.php:23-54 | app/core/Inventory/Application/UseCases/ViewRender.php:22-53 | app/core/InventoryAdjustment/Application/UseCases/ViewRender.php:22-53 | app/core/InvoiceIn/Application/UseCases/ViewInvoiceIn.php:21-52 | app/core/InvoiceOut/Application/UseCases/ViewInvoiceOut.php:21-52 | app/core/Order/Application/UseCases/ViewRender.php:22-53 | app/core/OrderShipping/Application/UseCases/ViewRender.php:22-53 | app/core/PermissionGroup/Application/UseCases/ViewRender.php:22-53 | app/core/PriceList/Application/UseCases/ViewRender.php:22-53 | app/core/Product/Application/UseCases/ViewRender.php:22-53 | app/core/Purchase/Application/UseCases/ViewPurchase.php:21-52 | app/core/PurchaseItem/Application/UseCases/ViewPurchase.php:21-52 | app/core/Shipping/Application/UseCases/ViewShipping.php:21-54 | app/core/StockIn/Application/UseCases/ViewStockIn.php:21-52 | app/core/StockOut/Application/UseCases/ViewStockOut.php:21-52 | app/core/Supplier/Application/UseCases/ViewSupplier.php:19-50 | app/core/Warehouse/Application/UseCases/ViewWarehouse.php:21-54 — before extracting anything, compare `app/core/CategoryProduct/Application/UseCases/ViewCategoryProduct.php` and `app/core/InvoiceIn/Application/UseCases/ViewInvoiceIn.php` as WHOLE FILES: 83% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `app/core/CategoryProduct/Application/UseCases/ViewCategoryProduct.php:21` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (31–32 lines × 2) app/core/Inventory/Application/Queries/IndexQuery.php:30— app/core/Inventory/Application/Queries/IndexQuery.php:30-61 | app/core/StockMovementIn/Application/Queries/IndexQuery.php:29-59 — before extracting anything, compare `app/core/Inventory/Application/Queries/IndexQuery.php` and `app/core/StockMovementIn/Application/Queries/IndexQuery.php` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 207 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `app/core/Inventory/Application/Queries/IndexQuery.php:30` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `app/core/Inventory/Application/Queries/IndexQuery.php:63` calls `join` and `app/core/StockMovementIn/Application/Queries/IndexQuery.php:59` 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 (25–28 lines × 6) app/core/CustomerGroup/Application/UseCases/CreateCustomerGroup.php:26— app/core/CustomerGroup/Application/UseCases/CreateCustomerGroup.php:26-50 | app/core/Permission/Application/UseCases/CreateFullPermission.php:31-57 | app/core/Permission/Application/UseCases/CreatePermission.php:29-53 | app/core/PermissionGroup/Application/UseCases/CreatePermissionGroup.php:29-56 | app/core/PurchaseItem/Application/UseCases/CreatePurchaseItem.php:28-52 | app/core/Warehouse/Application/UseCases/CreateWarehouse.php:28-52 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 6 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 6 times. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `app/core/Permission/Application/UseCases/CreateFullPermission.php:30` calls `addFull`, `buildListItem` and `app/core/CustomerGroup/Application/UseCases/CreateCustomerGroup.php:25` 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 (25–26 lines × 17) app/core/CategoryProduct/Application/UseCases/CreateCategoryProduct.php:27— app/core/CategoryProduct/Application/UseCases/CreateCategoryProduct.php:27-52 | app/core/CustomInvoiceIn/Application/UseCases/CreateCustomInvoiceIn.php:28-53 | app/core/CustomInvoiceOut/Application/UseCases/CreateCustomInvoiceOut.php:27-52 | app/core/Customer/Application/UseCases/CreateCustomer.php:27-51 | app/core/InvoiceIn/Application/UseCases/AutomaticCreateInvoice.php:28-52 | app/core/InvoiceIn/Application/UseCases/CreateInvoiceIn.php:25-49 | app/core/InvoiceOut/Application/UseCases/CreateInvoiceOut.php:27-52 | app/core/Order/Application/UseCases/CreateOrder.php:25-49 | app/core/OrderItem/Application/UseCases/CreateOrderItem.php:25-50 | app/core/OrderShipping/Application/UseCases/CreateOrderShipping.php:24-48 | app/core/PriceList/Application/UseCases/CreatePriceList.php:26-51 | app/core/Product/Application/UseCases/CreateProduct.php:26-50 | app/core/Purchase/Application/UseCases/CreatePurchase.php:27-51 | app/core/StockIn/Application/UseCases/CreateStockIn.php:26-50 | app/core/StockMovementIn/Application/UseCases/CreateStockMovementIn.php:27-51 | app/core/StockOut/Application/UseCases/CreateStockOut.php:25-49 | app/core/Supplier/Application/UseCases/CreateSupplier.php:24-48 — before extracting anything, compare `app/core/InvoiceIn/Application/UseCases/AutomaticCreateInvoice.php` and `app/core/InvoiceIn/Application/UseCases/CreateInvoiceIn.php` as WHOLE FILES: 85% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `app/core/InvoiceIn/Application/UseCases/AutomaticCreateInvoice.php:25` calls `getByPurchaseId`, `toArray` and `app/core/CategoryProduct/Application/UseCases/CreateCategoryProduct.php:26` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (25–26 lines × 11) app/core/CategoryProduct/Application/UseCases/ShowCategoryProduct.php:23— app/core/CategoryProduct/Application/UseCases/ShowCategoryProduct.php:23-47 | app/core/Customer/Application/UseCases/ShowCustomer.php:27-51 | app/core/CustomerGroup/Application/UseCases/ShowCustomerGroup.php:25-49 | app/core/InvoiceOut/Application/UseCases/ShowInvoiceOut.php:23-47 | app/core/Order/Application/UseCases/ShowOrder.php:24-49 | app/core/OrderShipping/Application/UseCases/ShowOrderShipping.php:23-47 | app/core/Permission/Application/UseCases/ShowPermission.php:27-52 | app/core/Product/Application/UseCases/ShowProduct.php:25-49 | app/core/StockIn/Application/UseCases/ShowStockIn.php:21-45 | app/core/StockOut/Application/UseCases/ShowStockOut.php:23-47 | app/core/Warehouse/Application/UseCases/ShowWarehouse.php:26-50 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 11 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 11 times. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `app/core/Permission/Application/UseCases/ShowPermission.php:53` calls `dispatch` and `app/core/CategoryProduct/Application/UseCases/ShowCategoryProduct.php:51` 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 (25 lines × 2) app/core/Purchase/Application/UseCases/ShowPurchase.php:25— app/core/Purchase/Application/UseCases/ShowPurchase.php:25-49 | app/core/PurchaseItem/Application/UseCases/ShowPurchaseItem.php:27-51 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `app/core/PurchaseItem/Application/UseCases/ShowPurchaseItem.php:55` calls `commit` and `app/core/Purchase/Application/UseCases/ShowPurchase.php:53` 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 (23–24 lines × 6) app/core/CategoryProduct/Application/UseCases/DeleteCategoryProduct.php:26— app/core/CategoryProduct/Application/UseCases/DeleteCategoryProduct.php:26-48 | app/core/CustomInvoiceIn/Application/UseCases/DeleteCustomInvoiceIn.php:25-48 | app/core/CustomInvoiceOut/Application/UseCases/DeleteCustomInvoiceOut.php:26-48 | app/core/Customer/Application/UseCases/DeleteCustomer.php:25-47 | app/core/Product/Application/UseCases/DeleteProduct.php:27-49 | app/core/Supplier/Application/UseCases/DeleteSupplier.php:26-48 — before extracting anything, compare `app/core/CategoryProduct/Application/UseCases/DeleteCategoryProduct.php` and `app/core/CustomInvoiceIn/Application/UseCases/DeleteCustomInvoiceIn.php` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 55 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `app/core/CategoryProduct/Application/UseCases/DeleteCategoryProduct.php:26` 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 (15–23 lines × 7) app/core/CategoryProduct/Application/Queries/IndexQuery.php:26— app/core/CategoryProduct/Application/Queries/IndexQuery.php:26-40 | app/core/CustomInvoiceIn/Application/Queries/IndexQuery.php:25-40 | app/core/CustomInvoiceOut/Application/Queries/IndexQuery.php:22-37 | app/core/InvoiceIn/Application/Queries/IndexQuery.php:37-51 | app/core/InvoiceOut/Application/Queries/IndexQuery.php:45-62 | app/core/OrderShipping/Application/Queries/IndexQuery.php:32-51 | app/core/PriceList/Application/Queries/IndexQuery.php:33-55 — before extracting anything, compare `app/core/CustomInvoiceIn/Application/Queries/IndexQuery.php` and `app/core/CustomInvoiceOut/Application/Queries/IndexQuery.php` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 99 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `app/core/CustomInvoiceIn/Application/Queries/IndexQuery.php:25` 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/core/InvoiceIn/Application/Queries/IndexQuery.php:36` calls `join` and `app/core/PriceList/Application/Queries/IndexQuery.php:33` 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 (16–23 lines × 3) app/core/Inventory/Application/Queries/IndexQuery.php:119— app/core/Inventory/Application/Queries/IndexQuery.php:119-141 | app/core/Product/Application/Queries/IndexQuery.php:37-52 | app/core/StockMovementIn/Application/Queries/IndexQuery.php:156-178 — before extracting anything, compare `app/core/Inventory/Application/Queries/IndexQuery.php` and `app/core/Product/Application/Queries/IndexQuery.php` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 81 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `app/core/Inventory/Application/Queries/IndexQuery.php:119` 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 (21–22 lines × 11) app/core/CategoryProduct/Application/UseCases/UpdateCategoryProduct.php:29— app/core/CategoryProduct/Application/UseCases/UpdateCategoryProduct.php:29-49 | app/core/CustomInvoiceIn/Application/UseCases/UpdateCustomInvoiceIn.php:30-51 | app/core/CustomInvoiceOut/Application/UseCases/UpdateCustomInvoiceOut.php:29-50 | app/core/Customer/Application/UseCases/UpdateCustomer.php:29-49 | app/core/Order/Application/UseCases/UpdateOrder.php:31-52 | app/core/PriceList/Application/UseCases/UpdatePriceList.php:29-50 | app/core/Product/Application/UseCases/UpdateProduct.php:30-50 | app/core/Purchase/Application/UseCases/UpdatePurchase.php:30-50 | app/core/StockMovementIn/Application/UseCases/UpdateStockMovementIn.php:32-52 | app/core/StockOut/Application/UseCases/UpdateStockOut.php:31-51 | app/core/Supplier/Application/UseCases/UpdateSupplier.php:30-50 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 11 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 11 times. Read the line range as the matched WINDOW rather than a finished unit: at `app/core/CategoryProduct/Application/UseCases/UpdateCategoryProduct.php:29` 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 after the matched lines, `app/core/StockOut/Application/UseCases/UpdateStockOut.php:52` calls `isCompleted` and `app/core/CategoryProduct/Application/UseCases/UpdateCategoryProduct.php:50` 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 (20–22 lines × 3) app/core/Inventory/Application/Queries/IndexQuery.php:30— app/core/Inventory/Application/Queries/IndexQuery.php:30-51 | app/core/Overview/Infrastructure/Repositories/EloquentOverviewRepository.php:57-76 | app/core/StockMovementIn/Application/Queries/IndexQuery.php:29-50 — before extracting anything, compare `app/core/Inventory/Application/Queries/IndexQuery.php` and `app/core/StockMovementIn/Application/Queries/IndexQuery.php` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 207 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (13–21 lines × 8) app/core/CustomInvoiceIn/Application/Queries/IndexQuery.php:33— app/core/CustomInvoiceIn/Application/Queries/IndexQuery.php:33-46 | app/core/CustomInvoiceOut/Application/Queries/IndexQuery.php:30-43 | app/core/InvoiceIn/Application/Queries/IndexQuery.php:44-57 | app/core/InvoiceOut/Application/Queries/IndexQuery.php:52-68 | app/core/Order/Application/Queries/IndexQuery.php:50-70 | app/core/OrderShipping/Application/Queries/IndexQuery.php:44-56 | app/core/PriceList/Application/Queries/IndexQuery.php:48-60 | app/core/StockIn/Application/Queries/IndexQuery.php:48-61 — before extracting anything, compare `app/core/CustomInvoiceIn/Application/Queries/IndexQuery.php` and `app/core/CustomInvoiceOut/Application/Queries/IndexQuery.php` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 99 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `app/core/CustomInvoiceIn/Application/Queries/IndexQuery.php:33` 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 (16–21 lines × 4) app/core/Inventory/Application/Queries/IndexQuery.php:121— app/core/Inventory/Application/Queries/IndexQuery.php:121-141 | app/core/Product/Application/Queries/IndexQuery.php:37-52 | app/core/StockMovementIn/Application/Queries/IndexQuery.php:158-178 | app/core/User/Application/Queries/IndexQuery.php:37-53 — before extracting anything, compare `app/core/Inventory/Application/Queries/IndexQuery.php` and `app/core/Product/Application/Queries/IndexQuery.php` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 81 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `app/core/Inventory/Application/Queries/IndexQuery.php:121` 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 after the matched lines, `app/core/User/Application/Queries/IndexQuery.php:54` calls `dispatch` and `app/core/Inventory/Application/Queries/IndexQuery.php:145` 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 (6–21 lines × 2) app/core/InventoryAdjustment/Application/Queries/IndexQuery.php:30— app/core/InventoryAdjustment/Application/Queries/IndexQuery.php:30-35 | app/core/PriceList/Application/Queries/IndexQuery.php:24-44 — 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/core/InventoryAdjustment/Application/Queries/IndexQuery.php:30` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (19–21 lines × 2) app/core/Purchase/Application/Queries/IndexQuery.php:26— app/core/Purchase/Application/Queries/IndexQuery.php:26-44 | app/core/Purchase/Infrastructure/Repositories/EloquentPurchaseRepository.php:32-52 — 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/core/Purchase/Application/Queries/IndexQuery.php:26` 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 (20 lines × 3) app/core/Inventory/Application/Queries/IndexQuery.php:37— app/core/Inventory/Application/Queries/IndexQuery.php:37-56 | app/core/StockMovementIn/Application/Queries/IndexQuery.php:36-55 | app/core/StockMovementIn/Infrastructure/Repositories/EloquentStockMovementInRepository.php:85-104 — before extracting anything, compare `app/core/Inventory/Application/Queries/IndexQuery.php` and `app/core/StockMovementIn/Application/Queries/IndexQuery.php` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 207 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `app/core/Inventory/Application/Queries/IndexQuery.php:37` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15–19 lines × 13) app/core/CustomInvoiceIn/Application/Queries/IndexQuery.php:28— app/core/CustomInvoiceIn/Application/Queries/IndexQuery.php:28-43 | app/core/CustomInvoiceOut/Application/Queries/IndexQuery.php:25-40 | app/core/InvoiceIn/Application/Queries/IndexQuery.php:39-54 | app/core/InvoiceOut/Application/Queries/IndexQuery.php:47-65 | app/core/Order/Application/Queries/IndexQuery.php:45-63 | app/core/OrderItem/Application/Queries/IndexQuery.php:75-92 | app/core/OrderShipping/Application/Queries/IndexQuery.php:39-53 | app/core/PermissionGroup/Application/Queries/IndexQuery.php:28-45 | app/core/PriceList/Application/Queries/IndexQuery.php:43-57 | app/core/PurchaseItem/Application/Queries/IndexQuery.php:47-64 | app/core/StockIn/Application/Queries/IndexQuery.php:43-58 | app/core/StockOut/Application/Queries/IndexQuery.php:53-68 | app/core/Supplier/Application/Queries/IndexQuery.php:28-46 — before extracting anything, compare `app/core/CustomInvoiceIn/Application/Queries/IndexQuery.php` and `app/core/CustomInvoiceOut/Application/Queries/IndexQuery.php` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 99 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `app/core/CustomInvoiceIn/Application/Queries/IndexQuery.php:28` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `app/core/OrderItem/Application/Queries/IndexQuery.php:73` calls `where` and `app/core/InvoiceIn/Application/Queries/IndexQuery.php:37` 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 (17–19 lines × 3) app/core/Product/Application/Queries/IndexQuery.php:41— app/core/Product/Application/Queries/IndexQuery.php:41-57 | app/core/StockMovementIn/Application/Queries/IndexQuery.php:164-182 | app/core/StockMovementOut/Application/Queries/IndexQuery.php:51-69 — before extracting anything, compare `app/core/Product/Application/Queries/IndexQuery.php` and `app/core/StockMovementIn/Application/Queries/IndexQuery.php` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 100 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `app/core/Product/Application/Queries/IndexQuery.php:41` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (18 lines × 22) app/core/Business/Application/UseCases/ViewRender.php:18— app/core/Business/Application/UseCases/ViewRender.php:18-35 | app/core/CategoryProduct/Application/UseCases/ViewCategoryProduct.php:17-34 | app/core/CustomInvoiceIn/Application/UseCases/ViewCustomInvoiceIn.php:19-36 | app/core/CustomInvoiceOut/Application/UseCases/ViewCustomInvoiceOut.php:19-36 | app/core/Customer/Application/UseCases/ViewRender.php:19-36 | app/core/CustomerGroup/Application/UseCases/ViewCustomerGroup.php:19-36 | app/core/Inventory/Application/UseCases/ViewRender.php:18-35 | app/core/InventoryAdjustment/Application/UseCases/ViewRender.php:18-35 | app/core/InvoiceIn/Application/UseCases/ViewInvoiceIn.php:17-34 | app/core/InvoiceOut/Application/UseCases/ViewInvoiceOut.php:17-34 | app/core/Order/Application/UseCases/ViewRender.php:18-35 | app/core/OrderShipping/Application/UseCases/ViewRender.php:18-35 | app/core/PermissionGroup/Application/UseCases/ViewRender.php:18-35 | app/core/PriceList/Application/UseCases/ViewRender.php:18-35 | app/core/Product/Application/UseCases/ViewRender.php:18-35 | app/core/Purchase/Application/UseCases/ViewPurchase.php:17-34 | app/core/PurchaseItem/Application/UseCases/ViewPurchase.php:17-34 | app/core/Shipping/Application/UseCases/ViewShipping.php:17-34 | app/core/StockIn/Application/UseCases/ViewStockIn.php:17-34 | app/core/StockOut/Application/UseCases/ViewStockOut.php:17-34 | app/core/Supplier/Application/UseCases/ViewSupplier.php:15-32 | app/core/Warehouse/Application/UseCases/ViewWarehouse.php:17-34 — before extracting anything, compare `app/core/Business/Application/UseCases/ViewRender.php` and `app/core/Inventory/Application/UseCases/ViewRender.php` as WHOLE FILES: 86% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (15–18 lines × 14) app/core/CustomInvoiceIn/Application/Queries/IndexQuery.php:28— app/core/CustomInvoiceIn/Application/Queries/IndexQuery.php:28-42 | app/core/CustomInvoiceOut/Application/Queries/IndexQuery.php:25-39 | app/core/InvoiceIn/Application/Queries/IndexQuery.php:39-53 | app/core/InvoiceOut/Application/Queries/IndexQuery.php:47-64 | app/core/Order/Application/Queries/IndexQuery.php:45-62 | app/core/OrderItem/Application/Queries/IndexQuery.php:75-92 | app/core/OrderShipping/Application/Queries/IndexQuery.php:39-53 | app/core/PermissionGroup/Application/Queries/IndexQuery.php:28-45 | app/core/PriceList/Application/Queries/IndexQuery.php:43-57 | app/core/Purchase/Application/Queries/IndexQuery.php:61-75 | app/core/PurchaseItem/Application/Queries/IndexQuery.php:47-64 | app/core/StockIn/Application/Queries/IndexQuery.php:43-57 | app/core/StockOut/Application/Queries/IndexQuery.php:53-67 | app/core/Supplier/Application/Queries/IndexQuery.php:28-45 — before extracting anything, compare `app/core/CustomInvoiceIn/Application/Queries/IndexQuery.php` and `app/core/CustomInvoiceOut/Application/Queries/IndexQuery.php` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 99 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `app/core/CustomInvoiceIn/Application/Queries/IndexQuery.php:28` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `app/core/OrderItem/Application/Queries/IndexQuery.php:73` calls `where` and `app/core/InvoiceIn/Application/Queries/IndexQuery.php:37` 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 (17–18 lines × 12) app/core/CategoryProduct/Application/UseCases/UpdateCategoryProduct.php:25— app/core/CategoryProduct/Application/UseCases/UpdateCategoryProduct.php:25-41 | app/core/CustomInvoiceIn/Application/UseCases/UpdateCustomInvoiceIn.php:26-43 | app/core/CustomInvoiceOut/Application/UseCases/UpdateCustomInvoiceOut.php:25-42 | app/core/Customer/Application/UseCases/UpdateCustomer.php:25-41 | app/core/Order/Application/UseCases/UpdateOrder.php:27-44 | app/core/PriceList/Application/UseCases/UpdatePriceList.php:25-42 | app/core/Product/Application/UseCases/UpdateProduct.php:26-42 | app/core/Purchase/Application/UseCases/UpdatePurchase.php:26-42 | app/core/StockIn/Application/UseCases/UpdateStockIn.php:27-43 | app/core/StockMovementIn/Application/UseCases/UpdateStockMovementIn.php:28-44 | app/core/StockOut/Application/UseCases/UpdateStockOut.php:27-43 | app/core/Supplier/Application/UseCases/UpdateSupplier.php:26-42 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 12 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 12 times. Read the line range as the matched WINDOW rather than a finished unit: at `app/core/CategoryProduct/Application/UseCases/UpdateCategoryProduct.php:25` 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 (15–18 lines × 11) app/core/CategoryProduct/Application/Queries/IndexQuery.php:27— app/core/CategoryProduct/Application/Queries/IndexQuery.php:27-41 | app/core/CustomInvoiceIn/Application/Queries/IndexQuery.php:27-41 | app/core/CustomInvoiceOut/Application/Queries/IndexQuery.php:24-38 | app/core/InvoiceIn/Application/Queries/IndexQuery.php:38-52 | app/core/InvoiceOut/Application/Queries/IndexQuery.php:46-63 | app/core/OrderShipping/Application/Queries/IndexQuery.php:37-52 | app/core/PriceList/Application/Queries/IndexQuery.php:41-56 | app/core/PurchaseItem/Application/Queries/IndexQuery.php:46-63 | app/core/StockIn/Application/Queries/IndexQuery.php:42-56 | app/core/StockOut/Application/Queries/IndexQuery.php:52-66 | app/core/Supplier/Application/Queries/IndexQuery.php:27-44 — before extracting anything, compare `app/core/CustomInvoiceIn/Application/Queries/IndexQuery.php` and `app/core/CustomInvoiceOut/Application/Queries/IndexQuery.php` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 99 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `app/core/OrderShipping/Application/Queries/IndexQuery.php:37` 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/core/InvoiceIn/Application/Queries/IndexQuery.php:36` calls `join`, `where` and `app/core/OrderShipping/Application/Queries/IndexQuery.php:37` 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 (17–18 lines × 4) app/core/Inventory/Application/Queries/IndexQuery.php:125— app/core/Inventory/Application/Queries/IndexQuery.php:125-141 | app/core/Product/Application/Queries/IndexQuery.php:39-56 | app/core/StockMovementIn/Application/Queries/IndexQuery.php:162-178 | app/core/StockMovementOut/Application/Queries/IndexQuery.php:49-65 — before extracting anything, compare `app/core/Inventory/Application/Queries/IndexQuery.php` and `app/core/Product/Application/Queries/IndexQuery.php` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 81 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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 (7–18 lines × 3) app/core/InventoryAdjustment/Application/Queries/IndexQuery.php:30— app/core/InventoryAdjustment/Application/Queries/IndexQuery.php:30-36 | app/core/InvoiceOut/Application/Queries/IndexQuery.php:42-49 | app/core/PriceList/Application/Queries/IndexQuery.php:28-45 — before extracting anything, compare `app/core/InvoiceOut/Application/Queries/IndexQuery.php` and `app/core/PriceList/Application/Queries/IndexQuery.php` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 117 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `app/core/InventoryAdjustment/Application/Queries/IndexQuery.php:30` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14–18 lines × 2) app/core/CustomerGroup/Application/Queries/IndexQuery.php:22— app/core/CustomerGroup/Application/Queries/IndexQuery.php:22-35 | app/core/InventoryAdjustment/Application/Queries/IndexQuery.php:33-50 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (16–17 lines × 7) app/core/CategoryProduct/Application/UseCases/DeleteCategoryProduct.php:35— app/core/CategoryProduct/Application/UseCases/DeleteCategoryProduct.php:35-50 | app/core/CustomInvoiceIn/Application/UseCases/DeleteCustomInvoiceIn.php:34-50 | app/core/CustomInvoiceOut/Application/UseCases/DeleteCustomInvoiceOut.php:35-50 | app/core/Customer/Application/UseCases/DeleteCustomer.php:34-49 | app/core/PriceList/Application/UseCases/DeletePriceList.php:31-46 | app/core/Product/Application/UseCases/DeleteProduct.php:36-51 | app/core/Supplier/Application/UseCases/DeleteSupplier.php:35-50 — before extracting anything, compare `app/core/CategoryProduct/Application/UseCases/DeleteCategoryProduct.php` and `app/core/CustomInvoiceIn/Application/UseCases/DeleteCustomInvoiceIn.php` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 55 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `app/core/CategoryProduct/Application/UseCases/DeleteCategoryProduct.php:35` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (10–17 lines × 2) app/core/Order/Application/Queries/IndexQuery.php:32— app/core/Order/Application/Queries/IndexQuery.php:32-41 | app/core/Purchase/Application/Queries/IndexQuery.php:31-47 — 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/core/Order/Application/Queries/IndexQuery.php:32` 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/core/Purchase/Application/Queries/IndexQuery.php:29` calls `raw` and `app/core/Order/Application/Queries/IndexQuery.php:31` 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 (15 lines × 10) app/core/CategoryProduct/Application/UseCases/ShowCategoryProduct.php:34— app/core/CategoryProduct/Application/UseCases/ShowCategoryProduct.php:34-51 | app/core/CustomerGroup/Application/UseCases/ShowCustomerGroup.php:36-53 | app/core/InvoiceIn/Application/UseCases/ShowInvoiceIn.php:38-52 | app/core/InvoiceOut/Application/UseCases/ShowInvoiceOut.php:34-51 | app/core/Order/Application/UseCases/ShowOrder.php:35-53 | app/core/OrderShipping/Application/UseCases/ShowOrderShipping.php:34-49 | app/core/Product/Application/UseCases/ShowProduct.php:36-53 | app/core/StockIn/Application/UseCases/ShowStockIn.php:32-46 | app/core/StockOut/Application/UseCases/ShowStockOut.php:34-51 | app/core/Warehouse/Application/UseCases/ShowWarehouse.php:37-52 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 10 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 10 times. Read the line range as the matched WINDOW rather than a finished unit: at `app/core/CategoryProduct/Application/UseCases/ShowCategoryProduct.php:34` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (13 lines × 17) app/core/CategoryProduct/Application/UseCases/CreateCategoryProduct.php:38— app/core/CategoryProduct/Application/UseCases/CreateCategoryProduct.php:38-52 | app/core/CustomInvoiceIn/Application/UseCases/CreateCustomInvoiceIn.php:39-53 | app/core/CustomInvoiceOut/Application/UseCases/CreateCustomInvoiceOut.php:38-52 | app/core/Customer/Application/UseCases/CreateCustomer.php:38-51 | app/core/InventoryAdjustment/Application/UseCases/CreateInventoryAdjustment.php:34-46 | app/core/InvoiceIn/Application/UseCases/AutomaticCreateInvoice.php:39-52 | app/core/InvoiceOut/Application/UseCases/CreateInvoiceOut.php:38-52 | app/core/Order/Application/UseCases/CreateOrder.php:36-49 | app/core/OrderItem/Application/UseCases/CreateOrderItem.php:36-50 | app/core/OrderShipping/Application/UseCases/CreateOrderShipping.php:35-48 | app/core/PriceList/Application/UseCases/CreatePriceList.php:37-51 | app/core/Product/Application/UseCases/CreateProduct.php:37-50 | app/core/Purchase/Application/UseCases/CreatePurchase.php:38-51 | app/core/StockIn/Application/UseCases/CreateStockIn.php:37-50 | app/core/StockMovementIn/Application/UseCases/CreateStockMovementIn.php:38-51 | app/core/StockOut/Application/UseCases/CreateStockOut.php:36-49 | app/core/Supplier/Application/UseCases/CreateSupplier.php:35-48 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 17 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 17 times. Read the line range as the matched WINDOW rather than a finished unit: at `app/core/CategoryProduct/Application/UseCases/CreateCategoryProduct.php:38` 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/core/InventoryAdjustment/Application/UseCases/CreateInventoryAdjustment.php:33` calls `fromArray`, `create`, `toArray` and `app/core/CategoryProduct/Application/UseCases/CreateCategoryProduct.php:38` 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 (13 lines × 7) app/core/CategoryProduct/Application/UseCases/DeleteCategoryProduct.php:26— app/core/CategoryProduct/Application/UseCases/DeleteCategoryProduct.php:26-38 | app/core/CustomInvoiceIn/Application/UseCases/DeleteCustomInvoiceIn.php:25-38 | app/core/CustomInvoiceOut/Application/UseCases/DeleteCustomInvoiceOut.php:26-38 | app/core/Customer/Application/UseCases/DeleteCustomer.php:25-37 | app/core/OrderItem/Application/UseCases/DeleteOrderItem.php:25-37 | app/core/Product/Application/UseCases/DeleteProduct.php:27-39 | app/core/Supplier/Application/UseCases/DeleteSupplier.php:26-38 — before extracting anything, compare `app/core/CategoryProduct/Application/UseCases/DeleteCategoryProduct.php` and `app/core/CustomInvoiceIn/Application/UseCases/DeleteCustomInvoiceIn.php` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 55 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (12–13 lines × 2) app/app/Http/Middleware/BusinessToken.php:37— app/app/Http/Middleware/BusinessToken.php:37-49 | app/core/AppToken/Application/UseCases/ParseAppToken.php:29-40 — 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/app/Http/Middleware/BusinessToken.php:37` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (11–12 lines × 2) app/core/Purchase/Application/DTOs/CreatePurchaseRequest.php:24— app/core/Purchase/Application/DTOs/CreatePurchaseRequest.php:24-35 | app/core/Purchase/Application/DTOs/UpdatePurchaseRequest.php:24-34 — before extracting anything, compare `app/core/Purchase/Application/DTOs/CreatePurchaseRequest.php` and `app/core/Purchase/Application/DTOs/UpdatePurchaseRequest.php` as WHOLE FILES: 85% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `app/core/Purchase/Application/DTOs/CreatePurchaseRequest.php:24` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (8–10 lines × 2) app/core/InvoiceIn/Infrastructure/Repositories/EloquentInvoiceInRepository.php:29— app/core/InvoiceIn/Infrastructure/Repositories/EloquentInvoiceInRepository.php:29-38 | app/core/PriceList/Infrastructure/Repositories/EloquentPriceListRepository.php:44-51 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `app/core/InvoiceIn/Infrastructure/Repositories/EloquentInvoiceInRepository.php:29` 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 (8–9 lines × 2) app/core/PurchaseItem/Infrastructure/Repositories/EloquentPurchaseItemRepository.php:23— app/core/PurchaseItem/Infrastructure/Repositories/EloquentPurchaseItemRepository.php:23-30 | app/core/PurchaseItem/Infrastructure/Repositories/EloquentPurchaseItemRepository.php:34-42 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7–8 lines × 5) app/core/Business/Infrastructure/Repositories/EloquentBusinessRepository.php:32— app/core/Business/Infrastructure/Repositories/EloquentBusinessRepository.php:32-38 | app/core/StockMovementOut/Infrastructure/Repositories/EloquentStockMovementOutRepository.php:22-29 | app/core/StockMovementOut/Infrastructure/Repositories/EloquentStockMovementOutRepository.php:35-42 | app/core/User/Infrastructure/Repositories/EloquentUserRepository.php:14-21 | app/core/User/Infrastructure/Repositories/EloquentUserRepository.php:35-42 — there are 5 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 5 sites; resolving a subset leaves the remainder to drift apart. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 6) app/core/OrderItem/Infrastructure/Repositories/EloquentOrderItemRepository.php:66— app/core/OrderItem/Infrastructure/Repositories/EloquentOrderItemRepository.php:66-73 | app/core/OrderShipping/Infrastructure/Repositories/EloquentOrderShippingRepository.php:20-27 | app/core/OrderShipping/Infrastructure/Repositories/EloquentOrderShippingRepository.php:71-78 | app/core/Permission/Infrastructure/Repositories/EloquentPermissionRepository.php:32-39 | app/core/PermissionGroupUser/Infrastructure/Repositories/EloquentPermissionGroupUserRepository.php:43-51 | app/core/StockOut/Infrastructure/Repositories/EloquentStockOutRepository.php:21-27 — there are 6 copies across 5 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 6 sites; resolving a subset leaves the remainder to drift apart. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (6 lines × 6) app/core/Business/Infrastructure/Repositories/EloquentBusinessRepository.php:33— app/core/Business/Infrastructure/Repositories/EloquentBusinessRepository.php:33-38 | app/core/Order/Infrastructure/Repositories/EloquentOrderRepository.php:56-63 | app/core/StockMovementOut/Infrastructure/Repositories/EloquentStockMovementOutRepository.php:23-29 | app/core/StockMovementOut/Infrastructure/Repositories/EloquentStockMovementOutRepository.php:36-42 | app/core/User/Infrastructure/Repositories/EloquentUserRepository.php:15-21 | app/core/User/Infrastructure/Repositories/EloquentUserRepository.php:36-42 — there are 6 copies across 4 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 6 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/core/Order/Infrastructure/Repositories/EloquentOrderRepository.php:56` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (6 lines × 4) app/core/OrderItem/Application/Queries/IndexQuery.php:49— app/core/OrderItem/Application/Queries/IndexQuery.php:49-70 | app/core/OrderItem/Infrastructure/Repositories/EloquentOrderItemRepository.php:104-125 | app/core/StockMovementOut/Application/Queries/IndexQuery.php:37-42 | app/core/StockOut/Application/Queries/IndexQuery.php:36-47 — before extracting anything, compare `app/core/OrderItem/Application/Queries/IndexQuery.php` and `app/core/StockMovementOut/Application/Queries/IndexQuery.php` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 76 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `app/core/OrderItem/Application/Queries/IndexQuery.php:49` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (12 lines × 4) app/core/CategoryProduct/Application/DTOs/ShowCategoryProductRequest.php:15— app/core/CategoryProduct/Application/DTOs/ShowCategoryProductRequest.php:15-26 | app/core/OrderItem/Application/DTOs/DeleteOrderItemRequest.php:18-34 | app/core/StockMovementIn/Application/DTOs/CheckStockMovementInRequest.php:15-26 | app/core/StockOut/Application/DTOs/ShowStockOutRequest.php:15-28 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 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 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `app/core/CategoryProduct/Application/DTOs/ShowCategoryProductRequest.php:15` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (16 lines × 17) app/core/CustomInvoiceIn/Http/Controllers/CustomInvoiceInController.php:18— app/core/CustomInvoiceIn/Http/Controllers/CustomInvoiceInController.php:18-39 | app/core/CustomInvoiceOut/Http/Controllers/CustomInvoiceOutController.php:18-39 | app/core/Customer/Http/Controllers/CustomerController.php:24-44 | app/core/CustomerGroup/Http/Controllers/CustomerGroupController.php:23-58 | app/core/InvoiceIn/Http/Controllers/InvoiceInController.php:19-34 | app/core/InvoiceOut/Http/Controllers/InvoiceOutController.php:23-47 | app/core/Order/Http/Controllers/OrderController.php:18-33 | app/core/OrderShipping/Http/Controllers/OrderShippingController.php:19-36 | app/core/PermissionGroup/Http/Controllers/PermissionGroupController.php:20-48 | app/core/PriceList/Http/Controllers/PriceListController.php:18-39 | app/core/Purchase/Http/Controllers/PurchaseController.php:18-33 | app/core/PurchaseItem/Http/Controllers/PurchaseItemController.php:20-53 | app/core/Shipping/Http/Controllers/ShippingController.php:21-43 | app/core/StockIn/Http/Controllers/StockInController.php:18-33 | app/core/StockOut/Http/Controllers/StockOutController.php:18-40 | app/core/Supplier/Http/Controllers/SupplierController.php:18-36 | app/core/Warehouse/Http/Controllers/WarehouseController.php:29-49 — before extracting anything, compare `app/core/Customer/Http/Controllers/CustomerController.php` and `app/core/CustomerGroup/Http/Controllers/CustomerGroupController.php` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 108 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `app/core/CustomInvoiceIn/Http/Controllers/CustomInvoiceInController.php:18` 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 first that the copies are not typed on the same thing: `IndexQuery` names `Core\CustomInvoiceIn\Application\Queries\IndexQuery` in one and `Core\CustomInvoiceOut\Application\Queries\IndexQuery` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (17 lines × 8) app/core/CustomInvoiceIn/Http/Requests/CreateCustomInvoiceInRequest.php:16— app/core/CustomInvoiceIn/Http/Requests/CreateCustomInvoiceInRequest.php:16-44 | app/core/CustomInvoiceOut/Http/Requests/CreateCustomInvoiceOutRequest.php:16-39 | app/core/Customer/Http/Requests/CreateCustomerRequest.php:16-50 | app/core/Inventory/Http/Requests/CreateInventoryRequest.php:15-31 | app/core/Order/Http/Requests/CreateOrderRequest.php:17-40 | app/core/OrderShipping/Http/Requests/CreateOrderShippingRequest.php:16-48 | app/core/PriceList/Http/Requests/CreatePriceListRequest.php:16-35 | app/core/Product/Http/Requests/CreateProductRequest.php:16-39 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 8 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 8 times. Read the line range as the matched WINDOW rather than a finished unit: at `app/core/CustomInvoiceIn/Http/Requests/CreateCustomInvoiceInRequest.php:16` 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 (17 lines × 5) app/core/CustomInvoiceIn/Http/Requests/DeleteCustomInvoiceInRequest.php:16— app/core/CustomInvoiceIn/Http/Requests/DeleteCustomInvoiceInRequest.php:16-32 | app/core/CustomInvoiceOut/Http/Requests/DeleteCustomInvoiceOutRequest.php:16-32 | app/core/Customer/Http/Requests/DeleteCustomerRequest.php:16-32 | app/core/PriceList/Http/Requests/DeletePriceListRequest.php:16-32 | app/core/Product/Http/Requests/DeleteProductRequest.php:16-32 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 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 5 times. Read the line range as the matched WINDOW rather than a finished unit: at `app/core/CustomInvoiceIn/Http/Requests/DeleteCustomInvoiceInRequest.php:16` 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 (19 lines × 6) app/core/CustomInvoiceIn/Http/Requests/IndexCustomInvoiceInRequest.php:16— app/core/CustomInvoiceIn/Http/Requests/IndexCustomInvoiceInRequest.php:16-34 | app/core/CustomInvoiceOut/Http/Requests/IndexCustomInvoiceOutRequest.php:16-35 | app/core/Customer/Http/Requests/IndexCustomerRequest.php:16-35 | app/core/Order/Http/Requests/IndexOrderRequest.php:16-36 | app/core/OrderShipping/Http/Requests/IndexOrderShippingRequest.php:16-35 | app/core/Product/Http/Requests/IndexProductRequest.php:16-34 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 6 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 6 times. Read the line range as the matched WINDOW rather than a finished unit: at `app/core/CustomInvoiceIn/Http/Requests/IndexCustomInvoiceInRequest.php:16` 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 (20 lines × 6) app/core/CustomInvoiceIn/Http/Requests/UpdateCustomInvoiceInRequest.php:16— app/core/CustomInvoiceIn/Http/Requests/UpdateCustomInvoiceInRequest.php:16-44 | app/core/CustomInvoiceOut/Http/Requests/UpdateCustomInvoiceOutRequest.php:16-39 | app/core/Customer/Http/Requests/UpdateCustomerRequest.php:16-50 | app/core/Order/Http/Requests/UpdateOrderRequest.php:17-42 | app/core/PriceList/Http/Requests/UpdatePriceListRequest.php:16-35 | app/core/Product/Http/Requests/UpdateProductRequest.php:16-35 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 6 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 6 times. Read the line range as the matched WINDOW rather than a finished unit: at `app/core/CustomInvoiceIn/Http/Requests/UpdateCustomInvoiceInRequest.php:16` 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 (21 lines × 6) app/core/Customer/Http/Controllers/CustomerController.php:24— app/core/Customer/Http/Controllers/CustomerController.php:24-44 | app/core/CustomerGroup/Http/Controllers/CustomerGroupController.php:23-58 | app/core/PermissionGroup/Http/Controllers/PermissionGroupController.php:20-48 | app/core/PurchaseItem/Http/Controllers/PurchaseItemController.php:20-53 | app/core/Shipping/Http/Controllers/ShippingController.php:21-43 | app/core/Warehouse/Http/Controllers/WarehouseController.php:29-49 — before extracting anything, compare `app/core/Customer/Http/Controllers/CustomerController.php` and `app/core/CustomerGroup/Http/Controllers/CustomerGroupController.php` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 108 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `app/core/Customer/Http/Controllers/CustomerController.php:24` 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 first that the copies are not typed on the same thing: `IndexQuery` names `Core\CustomerGroup\Application\Queries\IndexQuery` in one and `Core\Customer\Application\Queries\IndexQuery` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (17 lines × 4) app/core/Customer/Http/Requests/ShowCustomerRequest.php:16— app/core/Customer/Http/Requests/ShowCustomerRequest.php:16-32 | app/core/Order/Http/Requests/ShowOrderRequest.php:16-34 | app/core/OrderShipping/Http/Requests/ShowOrderShippingRequest.php:16-34 | app/core/Product/Http/Requests/ShowProductRequest.php:16-32 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 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 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `app/core/Customer/Http/Requests/ShowCustomerRequest.php:16` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (14 lines × 19) app/core/CustomInvoiceIn/Http/Controllers/CustomInvoiceInController.php:18— app/core/CustomInvoiceIn/Http/Controllers/CustomInvoiceInController.php:18-39 | app/core/CustomInvoiceOut/Http/Controllers/CustomInvoiceOutController.php:18-39 | app/core/Customer/Http/Controllers/CustomerController.php:24-44 | app/core/CustomerGroup/Http/Controllers/CustomerGroupController.php:23-58 | app/core/InvoiceIn/Http/Controllers/InvoiceInController.php:19-34 | app/core/InvoiceOut/Http/Controllers/InvoiceOutController.php:23-47 | app/core/Order/Http/Controllers/OrderController.php:18-33 | app/core/OrderShipping/Http/Controllers/OrderShippingController.php:19-36 | app/core/Permission/Http/Controllers/PermissionController.php:16-30 | app/core/PermissionGroup/Http/Controllers/PermissionGroupController.php:20-48 | app/core/PriceList/Http/Controllers/PriceListController.php:18-39 | app/core/Purchase/Http/Controllers/PurchaseController.php:18-33 | app/core/PurchaseItem/Http/Controllers/PurchaseItemController.php:20-53 | app/core/Shipping/Http/Controllers/ShippingController.php:21-43 | app/core/StockIn/Http/Controllers/StockInController.php:18-33 | app/core/StockMovementIn/Http/Controllers/StockMovementInController.php:15-28 | app/core/StockOut/Http/Controllers/StockOutController.php:18-40 | app/core/Supplier/Http/Controllers/SupplierController.php:18-36 | app/core/Warehouse/Http/Controllers/WarehouseController.php:29-49 — before extracting anything, compare `app/core/Customer/Http/Controllers/CustomerController.php` and `app/core/CustomerGroup/Http/Controllers/CustomerGroupController.php` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 108 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `app/core/CustomInvoiceIn/Http/Controllers/CustomInvoiceInController.php:18` 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 first that the copies are not typed on the same thing: `IndexQuery` names `Core\CustomInvoiceIn\Application\Queries\IndexQuery` in one and `Core\CustomInvoiceOut\Application\Queries\IndexQuery` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (7 lines × 38) app/core/ActivityLog/Infrastructure/Providers/ActivityLogServiceProvider.php:48— app/core/ActivityLog/Infrastructure/Providers/ActivityLogServiceProvider.php:48-54 | app/core/AppToken/Infrastructure/Providers/AppTokenServiceProvider.php:44-50 | app/core/Authencation/Infrastructure/Providers/AuthencationServiceProvider.php:47-53 | app/core/Business/Infrastructure/Providers/BusinessServiceProvider.php:44-50 | app/core/CategoryProduct/Infrastructure/Providers/CategoryProductServiceProvider.php:44-50 | app/core/CustomInvoiceIn/Infrastructure/Providers/CustomInvoiceInServiceProvider.php:44-50 | app/core/CustomInvoiceOut/Infrastructure/Providers/CustomInvoiceOutServiceProvider.php:44-50 | app/core/Customer/Infrastructure/Providers/CustomerServiceProvider.php:48-54 | app/core/CustomerGroup/Infrastructure/Providers/CustomerGroupServiceProvider.php:44-50 | app/core/Extension/Infrastructure/Providers/ExtensionServiceProvider.php:53-59 | app/core/ImageManager/Infrastructure/Providers/ImageManagerServiceProvider.php:44-50 | app/core/Inventory/Infrastructure/Providers/InventoryServiceProvider.php:45-51 | app/core/InventoryAdjustment/Infrastructure/Providers/InventoryAdjustmentServiceProvider.php:44-50 | app/core/InvoiceIn/Infrastructure/Providers/InvoiceInServiceProvider.php:48-54 | app/core/InvoiceOut/Infrastructure/Providers/InvoiceOutServiceProvider.php:49-55 | app/core/Notifications/Infrastructure/Providers/NotificationsServiceProvider.php:49-55 | app/core/Order/Infrastructure/Providers/OrderServiceProvider.php:52-58 | app/core/OrderCancel/Infrastructure/Providers/OrderCancelServiceProvider.php:47-53 | app/core/OrderItem/Infrastructure/Providers/OrderItemServiceProvider.php:46-52 | app/core/OrderShipping/Infrastructure/Providers/OrderShippingServiceProvider.php:52-58 | app/core/Overview/Infrastructure/Providers/OverviewServiceProvider.php:57-63 | app/core/Permission/Infrastructure/Providers/PermissionServiceProvider.php:46-52 | app/core/PermissionGroup/Infrastructure/Providers/PermissionGroupServiceProvider.php:46-52 | app/core/PermissionGroupUser/Infrastructure/Providers/PermissionGroupUserServiceProvider.php:46-52 | app/core/PriceList/Infrastructure/Providers/PriceListServiceProvider.php:44-50 | app/core/Product/Infrastructure/Providers/ProductServiceProvider.php:44-50 | app/core/Purchase/Infrastructure/Providers/PurchaseServiceProvider.php:46-52 | app/core/PurchaseCancel/Infrastructure/Providers/PurchaseCancelServiceProvider.php:47-53 | app/core/PurchaseItem/Infrastructure/Providers/PurchaseItemServiceProvider.php:48-54 | app/core/PurchaseTax/Infrastructure/Providers/PurchaseTaxServiceProvider.php:44-50 | app/core/Shipping/Infrastructure/Providers/ShippingServiceProvider.php:44-50 | app/core/StockIn/Infrastructure/Providers/StockInServiceProvider.php:46-52 | app/core/StockMovementIn/Infrastructure/Providers/StockMovementInServiceProvider.php:47-53 | app/core/StockMovementOut/Infrastructure/Providers/StockMovementOutServiceProvider.php:47-53 | app/core/StockOut/Infrastructure/Providers/StockOutServiceProvider.php:48-54 | app/core/Supplier/Infrastructure/Providers/SupplierServiceProvider.php:44-50 | app/core/User/Infrastructure/Providers/UserServiceProvider.php:46-52 | app/core/Warehouse/Infrastructure/Providers/WarehouseServiceProvider.php:50-56 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 38 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 38 times.
Duplicated block (5 lines × 14) app/core/CategoryProduct/Infrastructure/Services/CategoryProductServiceImpl.php:47— app/core/CategoryProduct/Infrastructure/Services/CategoryProductServiceImpl.php:47-51 | app/core/CustomInvoiceIn/Infrastructure/Services/CustomInvoiceInServiceImpl.php:45-50 | app/core/CustomInvoiceOut/Infrastructure/Services/CustomInvoiceOutServiceImpl.php:46-50 | app/core/Customer/Infrastructure/Services/CustomerServiceImpl.php:73-77 | app/core/CustomerGroup/Infrastructure/Services/CustomerGroupServiceImpl.php:38-42 | app/core/Extension/Infrastructure/Services/ExtensionServiceImpl.php:37-41 | app/core/Notifications/Infrastructure/Services/NotificationDBServiceImpl.php:38-42 | app/core/OrderItem/Infrastructure/Services/OrderItemServiceImpl.php:61-65 | app/core/PriceList/Infrastructure/Services/PriceListServiceImpl.php:42-46 | app/core/Product/Infrastructure/Services/ProductServiceImpl.php:52-56 | app/core/PurchaseItem/Infrastructure/Services/PurchaseItemServiceImpl.php:54-58 | app/core/Shipping/Infrastructure/Services/ShippingServiceImpl.php:45-49 | app/core/Supplier/Infrastructure/Services/SupplierServiceImpl.php:46-50 | app/core/Warehouse/Infrastructure/Services/WarehouseServiceImpl.php:49-53 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 14 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 14 times. 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 (15–20 lines × 3) extension-examples/Hrm/Http/Controllers/Api/AttendanceController.php:71— extension-examples/Hrm/Http/Controllers/Api/AttendanceController.php:71-90 | extension-examples/Hrm/Http/Controllers/Api/ExportExcelController.php:22-36 | extension-examples/Hrm/Http/Controllers/Api/ReportController.php:25-40 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
Duplicated block (8–9 lines × 3) extension-examples/PriceListCountry/Hooks/IndexHook.php:27— extension-examples/PriceListCountry/Hooks/IndexHook.php:27-35 | extension-examples/ShippingProviderFax/Hooks/IndexHook.php:26-33 | extension-examples/SupplierFax/Hooks/IndexHook.php:26-33 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `extension-examples/PriceListCountry/Hooks/IndexHook.php:27` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (19 lines × 13) extension-examples/CategoryProductThumbnail/Hooks/SearchIndexHook.php:20— extension-examples/CategoryProductThumbnail/Hooks/SearchIndexHook.php:20-38 | extension-examples/CustomInvoiceIn/Hooks/SearchIndexShowHook.php:20-43 | extension-examples/CustomInvoiceOut/Hooks/SearchIndexShowHook.php:20-43 | extension-examples/CustomerFax/Hooks/SearchIndexShowHook.php:20-43 | extension-examples/InvoiceInExtras/Hooks/SearchIndexShowHook.php:20-43 | extension-examples/InvoiceOutExtras/Hooks/SearchIndexShowHook.php:20-38 | extension-examples/OrderInformation/Hooks/SearchIndexShowHook.php:18-41 | extension-examples/PurchaseInformation/Hooks/SearchIndexShowHook.php:20-43 | extension-examples/ShippingProviderFax/Hooks/SearchIndexHook.php:20-38 | extension-examples/StockOutExtras/Hooks/SearchIndexShowHook.php:20-43 | extension-examples/StockinExtras/Hooks/SearchIndexShowHook.php:20-43 | extension-examples/SupplierFax/Hooks/SearchIndexHook.php:20-43 | extension-examples/TrackingNumberOrderShipping/Hooks/SearchIndexShowHook.php:20-43 — before extracting anything, compare `extension-examples/CustomInvoiceIn/Hooks/SearchIndexShowHook.php` and `extension-examples/CustomInvoiceOut/Hooks/SearchIndexShowHook.php` as WHOLE FILES: 90% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `extension-examples/CategoryProductThumbnail/Hooks/SearchIndexHook.php:20` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (19 lines × 2) extension-examples/CustomInvoiceIn/Hooks/CreateHook.php:16— extension-examples/CustomInvoiceIn/Hooks/CreateHook.php:16-34 | extension-examples/CustomInvoiceOut/Hooks/CreateHook.php:16-34 — 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 `extension-examples/CustomInvoiceIn/Hooks/CreateHook.php:16` 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 first that the copies are not typed on the same thing: `ExampleModel` names `Extensions\CustomInvoiceIn\Models\ExampleModel` in one and `Extensions\CustomInvoiceOut\Models\ExampleModel` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (7–16 lines × 11) extension-examples/CustomInvoiceIn/Hooks/IndexHook.php:19— extension-examples/CustomInvoiceIn/Hooks/IndexHook.php:19-35 | extension-examples/CustomInvoiceOut/Hooks/IndexHook.php:19-35 | extension-examples/CustomerFax/Hooks/IndexHook.php:19-34 | extension-examples/InvoiceInExtras/Hooks/IndexHook.php:19-34 | extension-examples/InvoiceOutExtras/Hooks/IndexHook.php:17-34 | extension-examples/OrderInformation/Hooks/IndexHook.php:18-34 | extension-examples/ProductRenew/Hooks/IndexHook.php:27-33 | extension-examples/PurchaseInformation/Hooks/IndexHook.php:18-33 | extension-examples/StockOutExtras/Hooks/IndexHook.php:18-35 | extension-examples/StockinExtras/Hooks/IndexHook.php:18-35 | extension-examples/TrackingNumberOrderShipping/Hooks/IndexHook.php:17-34 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 11 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 11 times. Read the line range as the matched WINDOW rather than a finished unit: at `extension-examples/CustomInvoiceIn/Hooks/IndexHook.php:19` 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 (17 lines × 13) extension-examples/CustomInvoiceIn/Hooks/IndexShowHook.php:18— extension-examples/CustomInvoiceIn/Hooks/IndexShowHook.php:18-34 | extension-examples/CustomInvoiceOut/Hooks/IndexShowHook.php:18-34 | extension-examples/CustomerFax/Hooks/IndexShowHook.php:18-34 | extension-examples/InvoiceInExtras/Hooks/IndexShowHook.php:18-34 | extension-examples/InvoiceOutExtras/Hooks/IndexShowHook.php:18-34 | extension-examples/OrderInformation/Hooks/IndexShowHook.php:18-34 | extension-examples/PriceListCountry/Hooks/IndexShowHook.php:18-34 | extension-examples/PurchaseInformation/Hooks/IndexShowHook.php:18-34 | extension-examples/ShippingProviderFax/Hooks/IndexShowHook.php:18-34 | extension-examples/StockOutExtras/Hooks/IndexShowHook.php:18-34 | extension-examples/StockinExtras/Hooks/IndexShowHook.php:18-34 | extension-examples/SupplierFax/Hooks/IndexShowHook.php:18-34 | extension-examples/TrackingNumberOrderShipping/Hooks/IndexShowHook.php:18-34 — before extracting anything, compare `extension-examples/CustomInvoiceIn/Hooks/IndexShowHook.php` and `extension-examples/CustomInvoiceOut/Hooks/IndexShowHook.php` as WHOLE FILES: 87% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `extension-examples/CustomInvoiceIn/Hooks/IndexShowHook.php:18` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (12 lines × 11) extension-examples/CustomInvoiceIn/Hooks/ValidateSearchHook.php:15— extension-examples/CustomInvoiceIn/Hooks/ValidateSearchHook.php:15-26 | extension-examples/CustomInvoiceOut/Hooks/ValidateSearchHook.php:15-26 | extension-examples/CustomerFax/Hooks/ValidateSearchHook.php:15-26 | extension-examples/InvoiceInExtras/Hooks/ValidateSearchHook.php:15-26 | extension-examples/InvoiceOutExtras/Hooks/ValidateSearchHook.php:15-26 | extension-examples/OrderInformation/Hooks/ValidateSearchHook.php:15-26 | extension-examples/ProductRenew/Hooks/ValidateSearchHook.php:15-26 | extension-examples/PurchaseInformation/Hooks/ValidateSearchHook.php:15-26 | extension-examples/StockOutExtras/Hooks/ValidateSearchHook.php:15-26 | extension-examples/StockinExtras/Hooks/ValidateSearchHook.php:15-26 | extension-examples/TrackingNumberOrderShipping/Hooks/ValidateSearchHook.php:15-26 — before extracting anything, compare `extension-examples/CustomInvoiceIn/Hooks/ValidateSearchHook.php` and `extension-examples/CustomInvoiceOut/Hooks/ValidateSearchHook.php` as WHOLE FILES: 83% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `extension-examples/CustomInvoiceIn/Hooks/ValidateSearchHook.php:15` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (18 lines × 11) extension-examples/CustomInvoiceIn/Hooks/ViewShowHook.php:18— extension-examples/CustomInvoiceIn/Hooks/ViewShowHook.php:18-35 | extension-examples/CustomInvoiceOut/Hooks/ViewShowHook.php:18-35 | extension-examples/CustomerFax/Hooks/ViewShowHook.php:18-35 | extension-examples/InvoiceOutExtras/Hooks/ViewShowHook.php:18-35 | extension-examples/OrderInformation/Hooks/ViewShowHook.php:18-35 | extension-examples/PurchaseInformation/Hooks/ViewShowHook.php:18-35 | extension-examples/ShippingProviderFax/Hooks/ViewShowHook.php:18-35 | extension-examples/StockOutExtras/Hooks/ViewShowHook.php:18-35 | extension-examples/StockinExtras/Hooks/ViewShowHook.php:18-35 | extension-examples/SupplierFax/Hooks/ViewShowHook.php:18-35 | extension-examples/TrackingNumberOrderShipping/Hooks/ViewShowHook.php:18-35 — before extracting anything, compare `extension-examples/CustomInvoiceIn/Hooks/ViewShowHook.php` and `extension-examples/CustomInvoiceOut/Hooks/ViewShowHook.php` as WHOLE FILES: 88% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `extension-examples/CustomInvoiceIn/Hooks/ViewShowHook.php:18` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (21 lines × 4) extension-examples/CustomerFax/Hooks/UpdateHook.php:17— extension-examples/CustomerFax/Hooks/UpdateHook.php:17-37 | extension-examples/InvoiceOutExtras/Hooks/UpdateHook.php:16-36 | extension-examples/ProductRenew/Hooks/UpdateHook.php:17-37 | extension-examples/TrackingNumberOrderShipping/Hooks/UpdateHook.php:17-37 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 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 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `extension-examples/CustomerFax/Hooks/UpdateHook.php:17` 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 first that the copies are not typed on the same thing: `ExampleModel` names `Extensions\CustomerFax\Models\ExampleModel` in one and `Extensions\InvoiceOutExtras\Models\ExampleModel` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (11 lines × 2) extension-examples/InvoiceInPDF/Hooks/IndexHook.php:18— extension-examples/InvoiceInPDF/Hooks/IndexHook.php:18-28 | extension-examples/InvoiceOutPDF/Hooks/IndexHook.php:17-28 — 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 `extension-examples/InvoiceInPDF/Hooks/IndexHook.php:18` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (17 lines × 2) extension-examples/InvoiceInPDF/Hooks/IndexShowHook.php:18— extension-examples/InvoiceInPDF/Hooks/IndexShowHook.php:18-34 | extension-examples/InvoiceOutPDF/Hooks/IndexShowHook.php:18-35 — 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 `extension-examples/InvoiceInPDF/Hooks/IndexShowHook.php:18` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (15 lines × 3) extension-examples/InvoiceOutExtras/Hooks/ShowHook.php:18— extension-examples/InvoiceOutExtras/Hooks/ShowHook.php:18-32 | extension-examples/TrackingNumberOrderShipping/Hooks/ShowHook.php:17-31 | extension-examples/TrackingNumberOrderShipping/Hooks/StockOutShipping.php:17-31 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `extension-examples/InvoiceOutExtras/Hooks/ShowHook.php:18` 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 first that the copies are not typed on the same thing: `ExampleModel` names `Extensions\InvoiceOutExtras\Models\ExampleModel` in one and `Extensions\TrackingNumberOrderShipping\Models\ExampleModel` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Low cohesion: EloquentExtensionRepository (LCOM4 5) app/core/Extension/Infrastructure/Repositories/EloquentExtensionRepository.php:15— EloquentExtensionRepository's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
M1 · Documentation (README)· README may be stale · ×1
README may be stale — 36 code files changed in the last 6 months but the README was not touched — it may no longer reflect the system.
P12 · CI test-gate honesty· Test suite runs only after the merge · ×1
Test suite runs only after the merge — `REDACTED`, `REDACTED` run(s) the test suite, but no workflow that runs tests is triggered by a pull request (or a merge queue) — so the suite reports on code that is already on the default branch. A red build there blocks nothing and the only remedy is a revert. Add the pull-request trigger to the workflow that runs your suite so the gate applies before the merge, not after it.
Duplication concentrated across 7 sibling directories (37 clone groups) app/resources/js/react/components/Order/ListOrder.jsx:15— 37 duplicated blocks under app/resources/js/react/components/ have copies in at least two of the sibling directories Customer, Inventory, Invoice, Order, Product, Purchases (+1 more sibling(s) not listed) — 27 of them are reported below, and 10 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 37 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 37 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 37 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 3 sibling directories (27 clone groups) app/resources/js/react/components/Inventory/IndexInventoryAdjustment.jsx:26— 27 duplicated blocks under app/resources/js/react/ have copies in at least two of the sibling directories components, layouts, pages — 20 of them are reported below, and 7 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 27 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 27 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 27 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 2 sibling directories (9 clone groups) app/resources/js/react/components/Invoice/InvoiceIns/InvoiceInDetail.jsx:32— 9 of the duplicated blocks reported below have copies in at least two of the sibling directories InvoiceIns, InvoiceOuts under app/resources/js/react/components/Invoice/. That concentration is one structural fact, not 9 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 9 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 2 sibling directories (5 clone groups) app/resources/js/react/components/Stock/StockInDetail/ProductTable.jsx:3— 5 duplicated blocks under app/resources/js/react/components/Stock/ have copies in at least two of the sibling directories StockInDetail, StockOutDetail — 4 of them are reported below, and 1 is counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 5 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 5 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 5 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.
Wholesale file copy (228 identical lines × 2 files) app/resources/js/react/components/Invoice/IndexCustomInvoiceIns.jsx:1— app/resources/js/react/components/Invoice/IndexCustomInvoiceIns.jsx:1 · app/resources/js/react/components/Invoice/IndexCustomInvoiceOuts.jsx:1 — these 2 files are line-for-line copies of one another — 228 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Wholesale file copy (158 identical lines × 2 files) extension-examples/Hrm/Resources/js/components/EndOfDayReportForm.jsx:1— extension-examples/Hrm/Resources/js/components/EndOfDayReportForm.jsx:1 · extension-examples/Hrm/Resources/js/components/IndexReport.jsx:1 — these 2 files are line-for-line copies of one another — 158 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Wholesale file copy (134 identical lines × 2 files) app/resources/js/react/components/Product/AddProduct.jsx:2— app/resources/js/react/components/Product/AddProduct.jsx:2 · app/resources/js/react/components/Product/UpdateProduct.jsx:2 — these 2 files are line-for-line copies of one another — 134 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 (114 matched lines × 2 locations) · ×1
Duplicated block with local edits (114 matched lines × 2 locations) app/resources/js/react/components/Stock/StockList/IndexStockIns.jsx:13— app/resources/js/react/components/Stock/StockList/IndexStockIns.jsx:13 · app/resources/js/react/components/Stock/StockList/IndexStockOuts.jsx:13 — the two spans are one implementation copied and then locally edited — 554 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 (98 matched lines × 2 locations) · ×1
Duplicated block with local edits (98 matched lines × 2 locations) app/resources/js/react/components/Order/ListOrder.jsx:15— app/resources/js/react/components/Order/ListOrder.jsx:15 · app/resources/js/react/components/Purchases/ListPurchases.jsx:17 — the two spans are one implementation copied and then locally edited — 517 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 (97 matched lines × 2 locations) · ×1
Duplicated block with local edits (97 matched lines × 2 locations) app/resources/js/react/components/CommonDataTable.jsx:26— app/resources/js/react/components/CommonDataTable.jsx:26 · app/resources/js/react/components/CommonDataTableV2.jsx:138 — the two spans are one implementation copied and then locally edited — 680 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 (88 matched lines × 2 locations) · ×1
Duplicated block with local edits (88 matched lines × 2 locations) app/resources/js/react/components/Customer/ListCustomer.jsx:47— app/resources/js/react/components/Customer/ListCustomer.jsx:47 · app/resources/js/react/components/Customer/ListGroup.jsx:45 — the two spans are one implementation copied and then locally edited — 477 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 (84 matched lines × 2 locations) · ×1
Duplicated block with local edits (84 matched lines × 2 locations) app/resources/js/react/components/Product/Category.jsx:179— app/resources/js/react/components/Product/Category.jsx:179 · app/resources/js/react/components/Product/IndexPriceList.jsx:144 — the two spans are one implementation copied and then locally edited — 444 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 (72 matched lines × 2 locations) · ×1
Duplicated block with local edits (72 matched lines × 2 locations) app/resources/js/react/components/Invoice/IndexInvoiceIns.jsx:64— app/resources/js/react/components/Invoice/IndexInvoiceIns.jsx:64 · app/resources/js/react/components/Invoice/IndexInvoiceOuts.jsx:65 — the two spans are one implementation copied and then locally edited — 403 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 (69 matched lines × 2 locations) · ×1
Duplicated block with local edits (69 matched lines × 2 locations) app/resources/js/react/components/Invoice/InvoiceIns/InvoiceInDetail.jsx:32— app/resources/js/react/components/Invoice/InvoiceIns/InvoiceInDetail.jsx:32 · app/resources/js/react/components/Invoice/InvoiceOuts/InvoiceOutsDetail.jsx:31 — 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.
R10 · Code Duplication· Duplicated block with local edits (53 matched lines × 2 locations) · ×1
Duplicated block with local edits (53 matched lines × 2 locations) app/resources/js/react/components/Order/AddOrder.jsx:32— app/resources/js/react/components/Order/AddOrder.jsx:32 · app/resources/js/react/components/Purchases/AddPurchase.jsx:33 — the two spans are one implementation copied and then locally edited — 294 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 (49 lines × 2 locations) extension-examples/Hrm/Resources/js/components/IndexMonthlyAttendanceSummary.jsx:7— extension-examples/Hrm/Resources/js/components/IndexMonthlyAttendanceSummary.jsx:7 · extension-examples/Hrm/Resources/js/components/MonthlyAttendanceSummary.jsx:7 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
Duplicated block (45 lines × 2 locations) app/resources/js/react/components/Invoice/InvoiceOuts/InvoiceOutsDetail.jsx:135— app/resources/js/react/components/Invoice/InvoiceOuts/InvoiceOutsDetail.jsx:135 · app/resources/js/react/components/Stock/StockOutDetail.jsx:171 — 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 (43 matched lines × 2 locations) · ×1
Duplicated block with local edits (43 matched lines × 2 locations) app/resources/js/react/components/Inventory/IndexInventory.jsx:11— app/resources/js/react/components/Inventory/IndexInventory.jsx:11 · app/resources/js/react/components/Inventory/IndexInventoryAdjustment.jsx:42 — the two spans are one implementation copied and then locally edited — 261 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 (43 lines × 2 locations) app/resources/js/react/components/Product/Category.jsx:48— app/resources/js/react/components/Product/Category.jsx:48 · app/resources/js/react/components/Product/Category.jsx:95 — 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 (41 matched lines × 2 locations) · ×1
Duplicated block with local edits (41 matched lines × 2 locations) app/resources/js/react/components/Stock/StockOutDetail/CustomerInfo.jsx:4— app/resources/js/react/components/Stock/StockOutDetail/CustomerInfo.jsx:4 · app/resources/js/react/components/Stock/StockOutDetail/ShippingInformation.jsx:6 — the two spans are one implementation copied and then locally edited — 291 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 (39 matched lines × 2 locations) · ×1
Duplicated block with local edits (39 matched lines × 2 locations) app/resources/js/react/components/Inventory/IndexInventoryAdjustment.jsx:26— app/resources/js/react/components/Inventory/IndexInventoryAdjustment.jsx:26 · app/resources/js/react/pages/warehouse.jsx:21 — the two spans are one implementation copied and then locally edited — 212 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 (38 matched lines × 2 locations) · ×1
Duplicated block with local edits (38 matched lines × 2 locations) app/resources/js/react/components/UI/Input/GalleryImage.jsx:5— app/resources/js/react/components/UI/Input/GalleryImage.jsx:5 · app/resources/js/react/components/UI/Input/UploadImage.jsx:4 — the two spans are one implementation copied and then locally edited — 230 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 (38 lines × 2 locations) app/resources/js/react/pages/suppliers.jsx:292— app/resources/js/react/pages/suppliers.jsx:292 · app/resources/js/react/pages/suppliers.jsx:334 — all 2 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Duplicated block (37 lines × 2 locations) app/resources/js/react/components/Invoice/InvoiceIns/InvoiceInDetail.jsx:173— app/resources/js/react/components/Invoice/InvoiceIns/InvoiceInDetail.jsx:173 · app/resources/js/react/components/Invoice/InvoiceOuts/InvoiceOutsDetail.jsx:191 — 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.
R10 · Code Duplication· Duplicated block with local edits (36 matched lines × 2 locations) · ×1
Duplicated block with local edits (36 matched lines × 2 locations) app/resources/js/react/pages/login.jsx:40— app/resources/js/react/pages/login.jsx:40 · app/resources/js/react/pages/register.jsx:45 — the two spans are one implementation copied and then locally edited — 233 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 (35 lines × 2 locations) app/resources/js/react/components/Invoice/InvoiceOuts/InvoiceOutsDetail.jsx:304— app/resources/js/react/components/Invoice/InvoiceOuts/InvoiceOutsDetail.jsx:304 · app/resources/js/react/components/Stock/StockOutDetail/ShippingInformation.jsx:54 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Duplicated block (34 lines × 2 locations) app/resources/js/react/pages/reset-password.jsx:6— app/resources/js/react/pages/reset-password.jsx:6 · app/resources/js/react/pages/verify-account.jsx:6 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
Duplicated block (30 lines × 2 locations) app/resources/js/react/components/Invoice/InvoiceIns/InvoiceInDetail.jsx:405— app/resources/js/react/components/Invoice/InvoiceIns/InvoiceInDetail.jsx:405 · app/resources/js/react/components/Invoice/InvoiceOuts/InvoiceOutsDetail.jsx:469 — 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.
R10 · Code Duplication· Duplicated block with local edits (30 matched lines × 2 locations) · ×1
Duplicated block with local edits (30 matched lines × 2 locations) app/resources/js/react/components/Order/DetailOrder/ProductAdded.jsx:12— app/resources/js/react/components/Order/DetailOrder/ProductAdded.jsx:12 · app/resources/js/react/components/Order/EditOrder/Products/ProductAdded.jsx:27 — the two spans are one implementation copied and then locally edited — 118 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 (29 matched lines × 2 locations) · ×1
Duplicated block with local edits (29 matched lines × 2 locations) app/resources/js/react/pages/forget-password.jsx:10— app/resources/js/react/pages/forget-password.jsx:10 · app/resources/js/react/pages/register.jsx:11 — the two spans are one implementation copied and then locally edited — 201 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 (28 lines × 3 locations) app/resources/js/react/pages/setting.jsx:85— app/resources/js/react/pages/setting.jsx:85 · app/resources/js/react/pages/setting.jsx:117 · app/resources/js/react/pages/setting.jsx:164 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (27 lines × 2 locations) app/resources/js/react/common/api-upload.js:9— app/resources/js/react/common/api-upload.js:9 · app/resources/js/react/common/api.js:9 — 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 (27 lines × 4 locations) app/resources/js/react/components/UI/PermissionButtons/ApproveButton.jsx:6— app/resources/js/react/components/UI/PermissionButtons/ApproveButton.jsx:6 · app/resources/js/react/components/UI/PermissionButtons/CancelButton.jsx:5 · app/resources/js/react/components/UI/PermissionButtons/DeleteButton.jsx:5 · app/resources/js/react/components/UI/PermissionButtons/UpdateButton.jsx:5 — the 4 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 4 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 (25 lines × 2 locations) app/resources/js/react/common/api-upload.js:1— app/resources/js/react/common/api-upload.js:1 · app/resources/js/react/common/authApi.js:1 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
Boundary violation [package:relative-cross-package] app/resources/css/app.css:2— app/resources/css/app.css:2 reaches into another package with a relative path (../../node_modules/bootstrap-icons/font/bootstrap-icons.css) — import the package by name instead.
Complex function CommonDataTableV2 (cyclomatic 21, cognitive 24) app/resources/js/react/components/CommonDataTableV2.jsx:11— CommonDataTableV2 has cyclomatic complexity 21 and cognitive complexity 24; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function EditPurchase (cyclomatic 19, cognitive 15) app/resources/js/react/components/Purchases/EditPurchase.jsx:27— EditPurchase has cyclomatic complexity 19 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function InvoiceOutDetail (cyclomatic 18, cognitive 17) app/resources/js/react/components/Invoice/InvoiceOuts/InvoiceOutsDetail.jsx:24— InvoiceOutDetail 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 EditOrder (cyclomatic 18, cognitive 17) app/resources/js/react/components/Order/EditOrder.jsx:27— EditOrder 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 StockInDetail (cyclomatic 14, cognitive 13) app/resources/js/react/components/Stock/StockInDetail.jsx:26— StockInDetail 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 StockOutDetail (cyclomatic 14, cognitive 13) app/resources/js/react/components/Stock/StockOutDetail.jsx:29— StockOutDetail 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 InvoiceInDetail (cyclomatic 13, cognitive 12) app/resources/js/react/components/Invoice/InvoiceIns/InvoiceInDetail.jsx:22— InvoiceInDetail 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 InputForm (cyclomatic 13, cognitive 12) app/resources/js/react/components/UI/Input/InputForm.jsx:2— InputForm 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 ListProducts (cyclomatic 11, cognitive 10) app/resources/js/react/components/Purchases/AddProduct/ListProduct.jsx:20— ListProducts 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.
Complex function (anonymous) (cyclomatic 11, cognitive 9) app/resources/js/react/components/CommonDataTableV2.jsx:175— (anonymous) has cyclomatic complexity 11 and cognitive complexity 9; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R3 · Large Files· app/resources/js/react/components/Invoice/InvoiceOuts/InvoiceOutsDetail.jsx · ×1
app/resources/js/react/components/Invoice/InvoiceOuts/InvoiceOutsDetail.jsx: 510 lines of code app/resources/js/react/components/Invoice/InvoiceOuts/InvoiceOutsDetail.jsx:1— app/resources/js/react/components/Invoice/InvoiceOuts/InvoiceOutsDetail.jsx has 510 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· app/resources/js/i18n/locales/en.js · ×1
app/resources/js/i18n/locales/en.js: 507 lines of code app/resources/js/i18n/locales/en.js:1— app/resources/js/i18n/locales/en.js 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· app/resources/js/react/components/Purchases/AddProduct/ListProduct.jsx · ×1
app/resources/js/react/components/Purchases/AddProduct/ListProduct.jsx: 493 lines of code app/resources/js/react/components/Purchases/AddProduct/ListProduct.jsx:1— app/resources/js/react/components/Purchases/AddProduct/ListProduct.jsx has 493 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· app/resources/js/react/components/Invoice/InvoiceIns/InvoiceInDetail.jsx · ×1
app/resources/js/react/components/Invoice/InvoiceIns/InvoiceInDetail.jsx: 442 lines of code app/resources/js/react/components/Invoice/InvoiceIns/InvoiceInDetail.jsx:1— app/resources/js/react/components/Invoice/InvoiceIns/InvoiceInDetail.jsx has 442 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· app/resources/js/react/components/Stock/StockInDetail.jsx · ×1
app/resources/js/react/components/Stock/StockInDetail.jsx: 413 lines of code app/resources/js/react/components/Stock/StockInDetail.jsx:1— app/resources/js/react/components/Stock/StockInDetail.jsx has 413 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· app/resources/js/react/components/Stock/StockOutDetail.jsx · ×1
app/resources/js/react/components/Stock/StockOutDetail.jsx: 407 lines of code app/resources/js/react/components/Stock/StockOutDetail.jsx:1— app/resources/js/react/components/Stock/StockOutDetail.jsx has 407 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
Test Coverage — 0% of 251 production file(s) reachable from 0 test file(s) via the import graph — 'production' here is the RESIDUE: every source file left once tests, tooling, generated output, config, declarations and declaration-only modules, fixture corpora, type fixtures, behaviour-free data modules, re-export barrels, registration/constant data modules and service workers are set aside, so the percentage is taken over a smaller denominator than the workspace's file count
R6 · Tooling· No test, lint or typecheck script · ×1
No test, lint or typecheck script — test ✗ · lint ✗ · typecheck ✗ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
Dead file (~187 LoC) app/resources/js/react/pages/report.jsx— no import path from any entry point (7 application, 1 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~162 LoC) app/resources/js/react/components/Order/DetailOrder/ShippingForm.jsx— no import path from any entry point (7 application, 1 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~105 LoC) app/resources/js/react/components/AutoDataTable.jsx— no import path from any entry point (7 application, 1 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~70 LoC) app/resources/js/react/components/Order/DetailOrder/ProductAdded.jsx— no import path from any entry point (7 application, 1 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~60 LoC) app/resources/js/react/layouts/ExtensionLayout.jsx— no import path from any entry point (7 application, 1 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~58 LoC) app/resources/js/react/components/UI/Input/Select2.jsx— no import path from any entry point (7 application, 1 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~48 LoC) app/resources/js/react/components/Order/DetailOrder/CustomerDetail.jsx— no import path from any entry point (7 application, 1 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~42 LoC) app/resources/js/react/components/Order/DetailOrder/ListProduct.jsx— no import path from any entry point (7 application, 1 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~29 LoC) app/resources/js/react/components/UI/Input/Input.jsx— no import path from any entry point (7 application, 1 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~28 LoC) app/resources/js/react/components/RenderTableSearch.jsx— no import path from any entry point (7 application, 1 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~25 LoC) app/resources/js/react/components/Stock/StockList.jsx— no import path from any entry point (7 application, 1 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~21 LoC) app/resources/js/react/components/UI/Input/SearchInput.jsx— no import path from any entry point (7 application, 1 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (app/resources/js/react/components/RenderTableSearch.jsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~10 LoC) app/resources/js/core/RegisterRoute.js— no import path from any entry point (7 application, 1 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~9 LoC) app/resources/js/react/components/Stock/StockOutDetail/SummaryRow.jsx— no import path from any entry point (7 application, 1 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~6 LoC) app/resources/js/react/components/Order/DetailOrder/OrderConfirm.jsx— no import path from any entry point (7 application, 1 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Unused dependency 'firebase' — Declared in app/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 'laravel-echo' — Declared in app/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 'react-to-print' — Declared in app/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.
Swallowed exception (caught, then discarded) app/core/Extension/Infrastructure/Repositories/EloquentExtensionRepository.php:118— `catch (\Throwable)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Duplicated predicate app/resources/js/react/pages/order.jsx:13— `searchParams.get('form') && searchParams.get('form') === 'add'` appears character-identically in 2 files — app/resources/js/react/pages/order.jsx, app/resources/js/react/pages/purchases.jsx. 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/resources/js/react/pages/order.jsx:14— `searchParams.get('form') && searchParams.get('form') === 'edit'` appears character-identically in 2 files — app/resources/js/react/pages/order.jsx, app/resources/js/react/pages/purchases.jsx. 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/resources/js/react/pages/Invoiceouts.jsx:13— `searchParams.get('form') && searchParams.get('id')` appears character-identically in 2 files — app/resources/js/react/pages/Invoiceouts.jsx, app/resources/js/react/pages/invoiceins.jsx. 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/core/OrderItem/Http/Requests/CreateOrderItemRequest.php:51— `$buy <= 0 && $gift <= 0 && $comp <= 0 && $conv <= 0` appears character-identically in 4 files — app/core/OrderItem/Http/Requests/CreateOrderItemRequest.php, app/core/OrderItem/Http/Requests/UpdateOrderItemRequest.php, app/core/PurchaseItem/Http/Requests/CreatePurchaseItemRequest.php, app/core/PurchaseItem/Http/Requests/UpdatePurchaseItemRequest.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 extension-examples/CategoryProductThumbnail/Hooks/CreateHook.php:17— `action === HookAction::CREATE && $context` appears character-identically in 34 files — extension-examples/CategoryProductThumbnail/Hooks/CreateHook.php, extension-examples/CategoryProductThumbnail/Hooks/ValidateCreateHook.php, extension-examples/CustomBusinessRole/Hooks/CreateHook.php, extension-examples/CustomInvoiceIn/Hooks/CreateHook.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 extension-examples/CategoryProductThumbnail/Hooks/IndexHook.php:16— `action === HookAction::INDEX && $context` appears character-identically in 52 files — extension-examples/CategoryProductThumbnail/Hooks/IndexHook.php, extension-examples/CategoryProductThumbnail/Hooks/IndexShowHook.php, extension-examples/CustomBusinessRole/Hooks/IndexShowHook.php, extension-examples/CustomHomePage/Hooks/CustomHomeHook.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 extension-examples/CategoryProductThumbnail/Hooks/SearchIndexHook.php:20— `action === HookAction::SEARCH && $context` appears character-identically in 15 files — extension-examples/CategoryProductThumbnail/Hooks/SearchIndexHook.php, extension-examples/CustomInvoiceIn/Hooks/SearchIndexShowHook.php, extension-examples/CustomInvoiceOut/Hooks/SearchIndexShowHook.php, extension-examples/CustomerFax/Hooks/SearchIndexShowHook.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 extension-examples/CategoryProductThumbnail/Hooks/UpdateHook.php:17— `action === HookAction::UPDATE && $context` appears character-identically in 32 files — extension-examples/CategoryProductThumbnail/Hooks/UpdateHook.php, extension-examples/CategoryProductThumbnail/Hooks/ValidateUpdateHook.php, extension-examples/CustomBusinessRole/Hooks/UpdateHook.php, extension-examples/CustomInvoiceIn/Hooks/UpdateHook.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/resources/views/admin/layouts/auth.blade.php:9— `file_exists(public_path('build/manifest.json')) || file_exists(public_path('hot'))` appears character-identically in 3 files — app/resources/views/admin/layouts/auth.blade.php, app/resources/views/admin/layouts/dashboard.blade.php, app/resources/views/home/layout.blade.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 extension-examples/CategoryProductThumbnail/Hooks/CreateHook.php:19— `module === 'CategoryProduct' && $context` appears character-identically in 8 files — extension-examples/CategoryProductThumbnail/Hooks/CreateHook.php, extension-examples/CategoryProductThumbnail/Hooks/IndexHook.php, extension-examples/CategoryProductThumbnail/Hooks/IndexShowHook.php, extension-examples/CategoryProductThumbnail/Hooks/SearchIndexHook.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 extension-examples/CustomInvoiceIn/Hooks/CreateHook.php:18— `module === 'CustomInvoiceIn' && $context` appears character-identically in 9 files — extension-examples/CustomInvoiceIn/Hooks/CreateHook.php, extension-examples/CustomInvoiceIn/Hooks/IndexHook.php, extension-examples/CustomInvoiceIn/Hooks/IndexShowHook.php, extension-examples/CustomInvoiceIn/Hooks/SearchIndexShowHook.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 extension-examples/CustomInvoiceOut/Hooks/CreateHook.php:18— `module === 'CustomInvoiceOut' && $context` appears character-identically in 9 files — extension-examples/CustomInvoiceOut/Hooks/CreateHook.php, extension-examples/CustomInvoiceOut/Hooks/IndexHook.php, extension-examples/CustomInvoiceOut/Hooks/IndexShowHook.php, extension-examples/CustomInvoiceOut/Hooks/SearchIndexShowHook.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 extension-examples/CategoryProductThumbnail/Hooks/CreateHook.php:18— `phase === HookPhase::RESPONSE && $context` appears character-identically in 49 files — extension-examples/CategoryProductThumbnail/Hooks/CreateHook.php, extension-examples/CategoryProductThumbnail/Hooks/UpdateHook.php, extension-examples/CustomBusinessRole/Hooks/CreateHook.php, extension-examples/CustomBusinessRole/Hooks/ShowHook.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 extension-examples/CategoryProductThumbnail/Hooks/ValidateCreateHook.php:19— `phase === HookPhase::VALIDATE && $context` appears character-identically in 41 files — extension-examples/CategoryProductThumbnail/Hooks/ValidateCreateHook.php, extension-examples/CategoryProductThumbnail/Hooks/ValidateUpdateHook.php, extension-examples/CustomInvoiceIn/Hooks/ValidateCreateHook.php, extension-examples/CustomInvoiceIn/Hooks/ValidateSearchHook.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 extension-examples/FastMode/Hooks/TriggerUpdateInvoiceHook.php:20— `timing === HookTiming::AFTER && $context` appears character-identically in 2 files — extension-examples/FastMode/Hooks/TriggerUpdateInvoiceHook.php, extension-examples/InventoryTracking/Hooks/TrackingHook.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 extension-examples/InventoryTracking/Hooks/AddMenuHook.php:21— `timing === HookTiming::BEFORE && $context` appears character-identically in 2 files — extension-examples/InventoryTracking/Hooks/AddMenuHook.php, extension-examples/Smtp/Hooks/UserNotify.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.
Interpolated log message defeats structured logging app/app/Providers/AppServiceProvider.php:79— `warning` at line 79 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/app/Providers/AppServiceProvider.php:88— `error` 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->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.
C2 · Access Controls· No named authorization policies · ×1
No named authorization policies — Authorization IS enforced here (by route guards, auth middleware or checks that refuse a caller) — this is NOT a claim that endpoints are unprotected. What's missing is a NAMED rule set: who may do what is encoded inline where it is checked, so the rules can't be listed, reviewed or tested apart from the code that applies them. Recommendation, not a defect.
No ADRs found — 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/`.
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion — 2 of 2 project(s) overshoot their size bounds, lowering Project Cohesion to 0.0/10. The most over is `app` (53353 LoC, 1072 module-visible types across 497 directories). Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
D28 · Secrets (history)· Rotate the exposed credentials · ×1
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.
No src/ separation — Production code isn't grouped under a src/ folder — it's spread across several top-level directories, so there's no one place that says 'this is the product'.
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) as a CI step. What was searched, so you can tell an absence from a miss: the 2348 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:2— `package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`.
P4 · Deployment & Rollback· No rollback/health safety · ×1
No rollback/health safety — Deployment is orchestrated by compose, but no service declares a `healthcheck:` and nothing pins a previous image to fall back to — the runtime can tell that the container is up, not that it is serving, so a bad release is harder to detect and reverse.
R7 · Dead Code· Unused export 'capitalizeFirstLetter' · ×1
Unused export 'capitalizeFirstLetter' app/resources/js/react/libraries/common.js:21— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'resetNotificationCount' · ×1
Unused export 'resetNotificationCount' app/resources/js/react/redux/NotificationSlice.js:29— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'clearBusinessInfo' · ×1
Unused export 'clearBusinessInfo' app/resources/js/react/redux/businessInfoSlice.js:33— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'setOrderDetail' · ×1
Unused export 'setOrderDetail' app/resources/js/react/redux/order/detailSlice.js:17— Nothing imports this binding — it is safe to review for removal.
No security response headers detected docker-config/host.conf:1— None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. This is reported because `host.conf` is committed to this repository and declares the server that serves it, so the configuration that would carry these headers is in this repository and was read in full. (−2.0 on this card.)
X5 · Nullable reference types· 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.
X7 · Silent fallback defaults· Pending state with no failure state · ×1
Pending state with no failure state app/resources/js/react/components/AutoDataTable.jsx:62— The view draws `Loading...` under `loading`, but `loading` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
Silent fallback default in catch app/core/Extension/Infrastructure/Repositories/EloquentExtensionRepository.php:118— `all` 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.
Outdated (npm): @reduxjs/toolkit — @reduxjs/toolkit is pinned at 2.10.1; registry.npmjs.org publishes 2.14.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @tinymce/tinymce-react — @tinymce/tinymce-react is pinned at 6.3.0; registry.npmjs.org publishes 6.3.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): bootstrap-icons — bootstrap-icons is pinned at 1.13.1; registry.npmjs.org publishes 1.13.2 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): firebase — firebase is pinned at 12.12.1; registry.npmjs.org publishes 13.2.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): react — react is pinned at 19.2.0; registry.npmjs.org publishes 19.3.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): react-dom — react-dom is pinned at 19.2.0; registry.npmjs.org publishes 19.3.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): react-redux — react-redux is pinned at 9.2.0; registry.npmjs.org publishes 9.3.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): react-router-dom — react-router-dom is pinned at 7.9.5; registry.npmjs.org publishes 7.18.5 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): react-to-print — react-to-print is pinned at 3.2.0; registry.npmjs.org publishes 3.3.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): recharts — recharts is pinned at 3.3.0; registry.npmjs.org publishes 3.10.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 2 file(s) — `app/app/Supports/Hooks/HookContext.php`, `app/core/StockMovementOut/Application/DTOs/CreateManyStockMovementOutRequest.php` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
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 01a1be72-86ce-72d7-b32e-a4567b2d9986 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 99 · Warnings: 473 · Recommendations: 44 · Info: 10 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 09-11-2026 @ 03:55 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.