Public report of alchemy-fr/phrasea, published 16 November 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 16 November 2026, 15:57 UTC · Survey ID cd_afa2d86dc7ce4bcd84adda82e86af2c6
alchemy-fr/phrasea
Measured 16 November 2026, 15:56 UTC, at code version f141016
Code coverage is not measured: JavaScript/TypeScript suite (CouldNotMeasureNoCollector).
CAI scoreAt risk
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A large codebase: 293,156 lines of product code in 36 projects, tests not counted · Estimated rebuild effort: about 2.9 person-years · Weakest lens: Production Readiness, 28.1
Findings by how serious they are
221 critical1720 serious292 minor
13 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
16 November 2026, 15:56 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 ▸
91of 91 dimensions measured by tools.
2125of 2233 findings point to an exact file and line, so you can open each one in the code. The other 108 concern the repository as a whole, such as missing documentation.
91dimensions across 8 lenses, read from 293,156 lines of product code in 36 projects.
alchemy-fr/phrasea is rated At risk because critical security findings are open, most of them in the build pipeline. Its score is held back because two passwords or keys sit in the current code and it has packages under a licence on your banned list. It scores 38.5 out of 100, which the At risk rating leaves unchanged.
Production Readiness, at 28.1, is the weakest lens and counts most in the score. The best first steps are replacing the two exposed passwords or keys and switching the old ones off and replacing the 14 packages under a banned licence, each worth about 8.8 points. Raising Production Readiness to 70 would lift the score to about 47.2.
Forty pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Thirty-four passwords or keys in the code's history and two in the code are open to anyone who can read the repository, and thirty-two secrets can leak from the build pipeline. Pinning each tool to an exact version, replacing each exposed password or key and limiting each secret to its own step would close these risks. Updating the vulnerable packages would fix the ten packages with a known security hole, and the 15 unsafe settings in infrastructure or container files need changing to safe values. Referring to the other business object by its identifier would take care of the 40 business objects holding another business object directly.
The product code is 293,156 lines, about €420,000 to rebuild.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
If Production Readiness rose from 28.1 to 70, the lowest score rated Strong, the score would rise from 38.5 to about 47.2.
Code composition: what the lines of code are
Product code 74%Tests 26%
Rebuild cost: about €420,000 · Estimate
Cost to rebuild
€140,000 to €700,000, for 2,322 to 7,367 hours of work, about 2.9 person-years for 1 to 6 engineers
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.7 at a score of 38. 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
Large: 293,156 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 2 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2).
Raises the score by about 8.8 points · Low effort · REDACTED Scanning
2
Resolve the 14 Banned license finding(s) in License Compliance — start with REDACTED (14).
Raises the score by about 8.8 points · Medium effort · License Compliance
3
Resolve the 28 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (28).
Raises the score by about 8.4 points · Medium effort · Dependency Hygiene
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 €420,000 to build again, about 2.9 person-years of work. Its weakest lens is Production Readiness, at 28.1 (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 16 Domain Modelling findings · Common cause
16 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. Identifiers, such as order numbers and customer numbers, are passed around as plain numbers or text, so nothing stops the code from using one kind where another belongs. 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 (7 findings) · Rich vs anemic model (5 findings) · Strongly-typed ids (4 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 2 Leaked secret finding(s) in REDACTED Scanning. Of all the actions in this report, it raises the score most for the work it takes: about 8.8 points for low effort, because it clears the 2 REDACTED Scanning findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 7.4 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 2% to 5% on every change. The history of the code shows how much it changes: about 479,881 lines over the last 90 days, which is about 1,946,184 lines a year. At that pace, the extra work comes to an estimated 97.3 to 648.7 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of our own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Code Duplication · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.
Architecture — module dependency graph
Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.
Architecture: which parts of the code depend on which
The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.
837 modules, with 1264 dependencies between them. 5 loops run through 89 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 797 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.
Alchemy.Workflow.Model uses Alchemy.Workflow.State, so a change to Alchemy.Workflow.State can break Alchemy.Workflow.Model, while a change to Alchemy.Workflow.Model can't break Alchemy.Workflow.State.
Position
Below the diagonal: Alchemy.Workflow.Model uses a module listed above it, which is the healthy direction.
App.Model uses Alchemy.RenditionFactory.DTO, so a change to Alchemy.RenditionFactory.DTO can break App.Model, while a change to App.Model can't break Alchemy.RenditionFactory.DTO.
Position
Below the diagonal: App.Model uses a module listed above it, which is the healthy direction.
App.Repository.Core uses App.Entity.Core, so a change to App.Entity.Core can break App.Repository.Core, while a change to App.Repository.Core can't break App.Entity.Core.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
App.Service.Storage uses Alchemy.MessengerBundle.Listener, so a change to Alchemy.MessengerBundle.Listener can break App.Service.Storage, while a change to App.Service.Storage can't break Alchemy.MessengerBundle.Listener.
Position
Below the diagonal: App.Service.Storage uses a module listed above it, which is the healthy direction.
App.Service.Storage uses Alchemy.StorageBundle.Storage, so a change to Alchemy.StorageBundle.Storage can break App.Service.Storage, while a change to App.Service.Storage can't break Alchemy.StorageBundle.Storage.
Position
Below the diagonal: App.Service.Storage uses a module listed above it, which is the healthy direction.
App.Service.Storage uses Alchemy.StorageBundle.Upload, so a change to Alchemy.StorageBundle.Upload can break App.Service.Storage, while a change to App.Service.Storage can't break Alchemy.StorageBundle.Upload.
Position
Below the diagonal: App.Service.Storage uses a module listed above it, which is the healthy direction.
13→25 App.Service.Storage uses App.Service.Assetpart of a loop✕
Connections
2 pairs of types, where a type in App.Service.Storage uses a type in App.Service.Asset.
App.Service.Storage uses App.Service.Asset, so a change to App.Service.Asset can break App.Service.Storage, while a change to App.Service.Storage can't break App.Service.Asset.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→28 App.Service.Storage uses App.Entity.Corepart of a loop✕
Connections
7 pairs of types, where a type in App.Service.Storage uses a type in App.Entity.Core.
App.Service.Storage uses App.Entity.Core, so a change to App.Entity.Core can break App.Service.Storage, while a change to App.Service.Storage can't break App.Entity.Core.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
Alchemy.Workflow uses Alchemy.Workflow.State, so a change to Alchemy.Workflow.State can break Alchemy.Workflow, while a change to Alchemy.Workflow can't break Alchemy.Workflow.State.
Position
Below the diagonal: Alchemy.Workflow uses a module listed above it, which is the healthy direction.
Alchemy.Workflow uses Alchemy.Workflow.Model, so a change to Alchemy.Workflow.Model can break Alchemy.Workflow, while a change to Alchemy.Workflow can't break Alchemy.Workflow.Model.
Position
Below the diagonal: Alchemy.Workflow uses a module listed above it, which is the healthy direction.
Alchemy.Workflow.Executor uses Alchemy.Workflow.State, so a change to Alchemy.Workflow.State can break Alchemy.Workflow.Executor, while a change to Alchemy.Workflow.Executor can't break Alchemy.Workflow.State.
Position
Below the diagonal: Alchemy.Workflow.Executor uses a module listed above it, which is the healthy direction.
Alchemy.Workflow.Executor uses Alchemy.Workflow.Model, so a change to Alchemy.Workflow.Model can break Alchemy.Workflow.Executor, while a change to Alchemy.Workflow.Executor can't break Alchemy.Workflow.Model.
Position
Below the diagonal: Alchemy.Workflow.Executor uses a module listed above it, which is the healthy direction.
App.Entity uses Alchemy.CoreBundle.Entity, so a change to Alchemy.CoreBundle.Entity can break App.Entity, while a change to App.Entity can't break Alchemy.CoreBundle.Entity.
Position
Below the diagonal: App.Entity uses a module listed above it, which is the healthy direction.
App.Service.Asset.Attribute uses App.Repository.Core, so a change to App.Repository.Core can break App.Service.Asset.Attribute, while a change to App.Service.Asset.Attribute can't break App.Repository.Core.
Position
Below the diagonal: App.Service.Asset.Attribute uses a module listed above it, which is the healthy direction.
17→28 App.Service.Asset.Attribute uses App.Entity.Corepart of a loop✕
Connections
16 pairs of types, where a type in App.Service.Asset.Attribute uses a type in App.Entity.Core.
App.Service.Asset.Attribute uses App.Entity.Core, so a change to App.Entity.Core can break App.Service.Asset.Attribute, while a change to App.Service.Asset.Attribute can't break App.Entity.Core.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→29 App.Service.Asset.Attribute uses App.Attributepart of a loop✕
Connections
6 pairs of types, where a type in App.Service.Asset.Attribute uses a type in App.Attribute.
App.Service.Asset.Attribute uses App.Attribute, so a change to App.Attribute can break App.Service.Asset.Attribute, while a change to App.Service.Asset.Attribute can't break App.Attribute.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
App.Service.Image uses Alchemy.MessengerBundle.Listener, so a change to Alchemy.MessengerBundle.Listener can break App.Service.Image, while a change to App.Service.Image can't break Alchemy.MessengerBundle.Listener.
Position
Below the diagonal: App.Service.Image uses a module listed above it, which is the healthy direction.
App.Service.Image uses Alchemy.StorageBundle.Storage, so a change to Alchemy.StorageBundle.Storage can break App.Service.Image, while a change to App.Service.Image can't break Alchemy.StorageBundle.Storage.
Position
Below the diagonal: App.Service.Image uses a module listed above it, which is the healthy direction.
App.Service.Image uses App.Service.Storage, so a change to App.Service.Storage can break App.Service.Image, while a change to App.Service.Image can't break App.Service.Storage.
Position
Below the diagonal: App.Service.Image uses a module listed above it, which is the healthy direction.
18→25 App.Service.Image uses App.Service.Assetpart of a loop✕
Connections
1 pair of types, where a type in App.Service.Image uses a type in App.Service.Asset.
App.Service.Image uses App.Service.Asset, so a change to App.Service.Asset can break App.Service.Image, while a change to App.Service.Image can't break App.Service.Asset.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→28 App.Service.Image uses App.Entity.Corepart of a loop✕
Connections
3 pairs of types, where a type in App.Service.Image uses a type in App.Entity.Core.
App.Service.Image uses App.Entity.Core, so a change to App.Entity.Core can break App.Service.Image, while a change to App.Service.Image can't break App.Entity.Core.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
App.Service.Log uses App.Entity.Core, so a change to App.Entity.Core can break App.Service.Log, while a change to App.Service.Log can't break App.Entity.Core.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
App.Entity.Integration uses Alchemy.CoreBundle.Entity, so a change to Alchemy.CoreBundle.Entity can break App.Entity.Integration, while a change to App.Entity.Integration can't break Alchemy.CoreBundle.Entity.
Position
Below the diagonal: App.Entity.Integration uses a module listed above it, which is the healthy direction.
App.Entity.Integration uses App.Entity, so a change to App.Entity can break App.Entity.Integration, while a change to App.Entity.Integration can't break App.Entity.
Position
Below the diagonal: App.Entity.Integration uses a module listed above it, which is the healthy direction.
20→28 App.Entity.Integration uses App.Entity.Corepart of a loop✕
Connections
1 pair of types, where a type in App.Entity.Integration uses a type in App.Entity.Core.
App.Entity.Integration uses App.Entity.Core, so a change to App.Entity.Core can break App.Entity.Integration, while a change to App.Entity.Integration can't break App.Entity.Core.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
App.Security uses Alchemy.AuthBundle.Security, so a change to Alchemy.AuthBundle.Security can break App.Security, while a change to App.Security can't break Alchemy.AuthBundle.Security.
Position
Below the diagonal: App.Security uses a module listed above it, which is the healthy direction.
App.Security uses Alchemy.StorageBundle.Storage, so a change to Alchemy.StorageBundle.Storage can break App.Security, while a change to App.Security can't break Alchemy.StorageBundle.Storage.
Position
Below the diagonal: App.Security uses a module listed above it, which is the healthy direction.
App.Security uses App.Repository.Core, so a change to App.Repository.Core can break App.Security, while a change to App.Security can't break App.Repository.Core.
Position
Below the diagonal: App.Security uses a module listed above it, which is the healthy direction.
App.Service.Workspace uses Alchemy.StorageBundle.Storage, so a change to Alchemy.StorageBundle.Storage can break App.Service.Workspace, while a change to App.Service.Workspace can't break Alchemy.StorageBundle.Storage.
Position
Below the diagonal: App.Service.Workspace uses a module listed above it, which is the healthy direction.
App.Service.Workspace uses App.Repository.Core, so a change to App.Repository.Core can break App.Service.Workspace, while a change to App.Service.Workspace can't break App.Repository.Core.
Position
Below the diagonal: App.Service.Workspace uses a module listed above it, which is the healthy direction.
App.Service.Workspace uses App.Service.Image, so a change to App.Service.Image can break App.Service.Workspace, while a change to App.Service.Workspace can't break App.Service.Image.
Position
Below the diagonal: App.Service.Workspace uses a module listed above it, which is the healthy direction.
22→28 App.Service.Workspace uses App.Entity.Corepart of a loop✕
Connections
12 pairs of types, where a type in App.Service.Workspace uses a type in App.Entity.Core.
App.Service.Workspace uses App.Entity.Core, so a change to App.Entity.Core can break App.Service.Workspace, while a change to App.Service.Workspace can't break App.Entity.Core.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
App.Elasticsearch uses Alchemy.CoreBundle.Entity, so a change to Alchemy.CoreBundle.Entity can break App.Elasticsearch, while a change to App.Elasticsearch can't break Alchemy.CoreBundle.Entity.
Position
Below the diagonal: App.Elasticsearch uses a module listed above it, which is the healthy direction.
App.Elasticsearch uses App.Repository.Core, so a change to App.Repository.Core can break App.Elasticsearch, while a change to App.Elasticsearch can't break App.Repository.Core.
Position
Below the diagonal: App.Elasticsearch uses a module listed above it, which is the healthy direction.
App.Elasticsearch uses App.Service.Asset.Attribute, so a change to App.Service.Asset.Attribute can break App.Elasticsearch, while a change to App.Elasticsearch can't break App.Service.Asset.Attribute.
Position
Below the diagonal: App.Elasticsearch uses a module listed above it, which is the healthy direction.
App.Elasticsearch uses App.Security, so a change to App.Security can break App.Elasticsearch, while a change to App.Elasticsearch can't break App.Security.
Position
Below the diagonal: App.Elasticsearch uses a module listed above it, which is the healthy direction.
23→25 App.Elasticsearch uses App.Service.Assetpart of a loop✕
Connections
1 pair of types, where a type in App.Elasticsearch uses a type in App.Service.Asset.
App.Elasticsearch uses App.Service.Asset, so a change to App.Service.Asset can break App.Elasticsearch, while a change to App.Elasticsearch can't break App.Service.Asset.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
23→28 App.Elasticsearch uses App.Entity.Corepart of a loop✕
Connections
6 pairs of types, where a type in App.Elasticsearch uses a type in App.Entity.Core.
App.Elasticsearch uses App.Entity.Core, so a change to App.Entity.Core can break App.Elasticsearch, while a change to App.Elasticsearch can't break App.Entity.Core.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
23→29 App.Elasticsearch uses App.Attributepart of a loop✕
Connections
3 pairs of types, where a type in App.Elasticsearch uses a type in App.Attribute.
App.Elasticsearch uses App.Attribute, so a change to App.Attribute can break App.Elasticsearch, while a change to App.Elasticsearch can't break App.Attribute.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
App.Consumer.Handler.Asset uses Alchemy.NotifierBundle.Manager, so a change to Alchemy.NotifierBundle.Manager can break App.Consumer.Handler.Asset, while a change to App.Consumer.Handler.Asset can't break Alchemy.NotifierBundle.Manager.
Position
Below the diagonal: App.Consumer.Handler.Asset uses a module listed above it, which is the healthy direction.
App.Consumer.Handler.Asset uses Alchemy.StorageBundle.Storage, so a change to Alchemy.StorageBundle.Storage can break App.Consumer.Handler.Asset, while a change to App.Consumer.Handler.Asset can't break Alchemy.StorageBundle.Storage.
Position
Below the diagonal: App.Consumer.Handler.Asset uses a module listed above it, which is the healthy direction.
App.Consumer.Handler.Asset uses App.Model, so a change to App.Model can break App.Consumer.Handler.Asset, while a change to App.Consumer.Handler.Asset can't break App.Model.
Position
Below the diagonal: App.Consumer.Handler.Asset uses a module listed above it, which is the healthy direction.
App.Consumer.Handler.Asset uses App.Repository.Core, so a change to App.Repository.Core can break App.Consumer.Handler.Asset, while a change to App.Consumer.Handler.Asset can't break App.Repository.Core.
Position
Below the diagonal: App.Consumer.Handler.Asset uses a module listed above it, which is the healthy direction.
App.Consumer.Handler.Asset uses Alchemy.Workflow, so a change to Alchemy.Workflow can break App.Consumer.Handler.Asset, while a change to App.Consumer.Handler.Asset can't break Alchemy.Workflow.
Position
Below the diagonal: App.Consumer.Handler.Asset uses a module listed above it, which is the healthy direction.
App.Consumer.Handler.Asset uses App.Service.Asset.Attribute, so a change to App.Service.Asset.Attribute can break App.Consumer.Handler.Asset, while a change to App.Consumer.Handler.Asset can't break App.Service.Asset.Attribute.
Position
Below the diagonal: App.Consumer.Handler.Asset uses a module listed above it, which is the healthy direction.
App.Consumer.Handler.Asset uses App.Service.Log, so a change to App.Service.Log can break App.Consumer.Handler.Asset, while a change to App.Consumer.Handler.Asset can't break App.Service.Log.
Position
Below the diagonal: App.Consumer.Handler.Asset uses a module listed above it, which is the healthy direction.
App.Consumer.Handler.Asset uses App.Service.Workspace, so a change to App.Service.Workspace can break App.Consumer.Handler.Asset, while a change to App.Consumer.Handler.Asset can't break App.Service.Workspace.
Position
Below the diagonal: App.Consumer.Handler.Asset uses a module listed above it, which is the healthy direction.
App.Consumer.Handler.Asset uses App.Elasticsearch, so a change to App.Elasticsearch can break App.Consumer.Handler.Asset, while a change to App.Consumer.Handler.Asset can't break App.Elasticsearch.
Position
Below the diagonal: App.Consumer.Handler.Asset uses a module listed above it, which is the healthy direction.
24→25 App.Consumer.Handler.Asset uses App.Service.Assetpart of a loop✕
Connections
4 pairs of types, where a type in App.Consumer.Handler.Asset uses a type in App.Service.Asset.
App.Consumer.Handler.Asset uses App.Service.Asset, so a change to App.Service.Asset can break App.Consumer.Handler.Asset, while a change to App.Consumer.Handler.Asset can't break App.Service.Asset.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
24→28 App.Consumer.Handler.Asset uses App.Entity.Corepart of a loop✕
Connections
1 pair of types, where a type in App.Consumer.Handler.Asset uses a type in App.Entity.Core.
App.Consumer.Handler.Asset uses App.Entity.Core, so a change to App.Entity.Core can break App.Consumer.Handler.Asset, while a change to App.Consumer.Handler.Asset can't break App.Entity.Core.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
App.Service.Asset uses Alchemy.MessengerBundle.Listener, so a change to Alchemy.MessengerBundle.Listener can break App.Service.Asset, while a change to App.Service.Asset can't break Alchemy.MessengerBundle.Listener.
Position
Below the diagonal: App.Service.Asset uses a module listed above it, which is the healthy direction.
App.Service.Asset uses Alchemy.RenditionFactory.DTO, so a change to Alchemy.RenditionFactory.DTO can break App.Service.Asset, while a change to App.Service.Asset can't break Alchemy.RenditionFactory.DTO.
Position
Below the diagonal: App.Service.Asset uses a module listed above it, which is the healthy direction.
App.Service.Asset uses Alchemy.StorageBundle.Storage, so a change to Alchemy.StorageBundle.Storage can break App.Service.Asset, while a change to App.Service.Asset can't break Alchemy.StorageBundle.Storage.
Position
Below the diagonal: App.Service.Asset uses a module listed above it, which is the healthy direction.
App.Service.Asset uses Alchemy.StorageBundle.Upload, so a change to Alchemy.StorageBundle.Upload can break App.Service.Asset, while a change to App.Service.Asset can't break Alchemy.StorageBundle.Upload.
Position
Below the diagonal: App.Service.Asset uses a module listed above it, which is the healthy direction.
App.Service.Asset uses App.Repository.Core, so a change to App.Repository.Core can break App.Service.Asset, while a change to App.Service.Asset can't break App.Repository.Core.
Position
Below the diagonal: App.Service.Asset uses a module listed above it, which is the healthy direction.
App.Service.Asset uses App.Service.Storage, so a change to App.Service.Storage can break App.Service.Asset, while a change to App.Service.Asset can't break App.Service.Storage.
Position
Below the diagonal: App.Service.Asset uses a module listed above it, which is the healthy direction.
App.Service.Asset uses Alchemy.Workflow, so a change to Alchemy.Workflow can break App.Service.Asset, while a change to App.Service.Asset can't break Alchemy.Workflow.
Position
Below the diagonal: App.Service.Asset uses a module listed above it, which is the healthy direction.
App.Service.Asset uses App.Service.Asset.Attribute, so a change to App.Service.Asset.Attribute can break App.Service.Asset, while a change to App.Service.Asset can't break App.Service.Asset.Attribute.
Position
Below the diagonal: App.Service.Asset uses a module listed above it, which is the healthy direction.
App.Service.Asset uses App.Service.Image, so a change to App.Service.Image can break App.Service.Asset, while a change to App.Service.Asset can't break App.Service.Image.
Position
Below the diagonal: App.Service.Asset uses a module listed above it, which is the healthy direction.
App.Service.Asset uses App.Consumer.Handler.Asset, so a change to App.Consumer.Handler.Asset can break App.Service.Asset, while a change to App.Service.Asset can't break App.Consumer.Handler.Asset.
Position
Below the diagonal: App.Service.Asset uses a module listed above it, which is the healthy direction.
25→28 App.Service.Asset uses App.Entity.Corepart of a loop✕
Connections
29 pairs of types, where a type in App.Service.Asset uses a type in App.Entity.Core. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
App.Service.Asset uses App.Entity.Core, so a change to App.Entity.Core can break App.Service.Asset, while a change to App.Service.Asset can't break App.Entity.Core.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
25→29 App.Service.Asset uses App.Attributepart of a loop✕
Connections
1 pair of types, where a type in App.Service.Asset uses a type in App.Attribute.
App.Service.Asset uses App.Attribute, so a change to App.Attribute can break App.Service.Asset, while a change to App.Service.Asset can't break App.Attribute.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
App.Service.Discussion uses Alchemy.CoreBundle.Entity, so a change to Alchemy.CoreBundle.Entity can break App.Service.Discussion, while a change to App.Service.Discussion can't break Alchemy.CoreBundle.Entity.
Position
Below the diagonal: App.Service.Discussion uses a module listed above it, which is the healthy direction.
App.Service.Discussion uses Alchemy.StorageBundle.Upload, so a change to Alchemy.StorageBundle.Upload can break App.Service.Discussion, while a change to App.Service.Discussion can't break Alchemy.StorageBundle.Upload.
Position
Below the diagonal: App.Service.Discussion uses a module listed above it, which is the healthy direction.
App.Service.Discussion uses App.Service.Asset, so a change to App.Service.Asset can break App.Service.Discussion, while a change to App.Service.Discussion can't break App.Service.Asset.
Position
Below the diagonal: App.Service.Discussion uses a module listed above it, which is the healthy direction.
26→28 App.Service.Discussion uses App.Entity.Corepart of a loop✕
Connections
1 pair of types, where a type in App.Service.Discussion uses a type in App.Entity.Core.
App.Service.Discussion uses App.Entity.Core, so a change to App.Entity.Core can break App.Service.Discussion, while a change to App.Service.Discussion can't break App.Entity.Core.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
App.Doctrine.Listener uses Alchemy.MessengerBundle.Listener, so a change to Alchemy.MessengerBundle.Listener can break App.Doctrine.Listener, while a change to App.Doctrine.Listener can't break Alchemy.MessengerBundle.Listener.
Position
Below the diagonal: App.Doctrine.Listener uses a module listed above it, which is the healthy direction.
App.Doctrine.Listener uses App.Repository.Core, so a change to App.Repository.Core can break App.Doctrine.Listener, while a change to App.Doctrine.Listener can't break App.Repository.Core.
Position
Below the diagonal: App.Doctrine.Listener uses a module listed above it, which is the healthy direction.
App.Doctrine.Listener uses App.Entity, so a change to App.Entity can break App.Doctrine.Listener, while a change to App.Doctrine.Listener can't break App.Entity.
Position
Below the diagonal: App.Doctrine.Listener uses a module listed above it, which is the healthy direction.
App.Doctrine.Listener uses App.Service.Asset.Attribute, so a change to App.Service.Asset.Attribute can break App.Doctrine.Listener, while a change to App.Doctrine.Listener can't break App.Service.Asset.Attribute.
Position
Below the diagonal: App.Doctrine.Listener uses a module listed above it, which is the healthy direction.
App.Doctrine.Listener uses App.Service.Log, so a change to App.Service.Log can break App.Doctrine.Listener, while a change to App.Doctrine.Listener can't break App.Service.Log.
Position
Below the diagonal: App.Doctrine.Listener uses a module listed above it, which is the healthy direction.
App.Doctrine.Listener uses App.Security, so a change to App.Security can break App.Doctrine.Listener, while a change to App.Doctrine.Listener can't break App.Security.
Position
Below the diagonal: App.Doctrine.Listener uses a module listed above it, which is the healthy direction.
App.Doctrine.Listener uses App.Service.Asset, so a change to App.Service.Asset can break App.Doctrine.Listener, while a change to App.Doctrine.Listener can't break App.Service.Asset.
Position
Below the diagonal: App.Doctrine.Listener uses a module listed above it, which is the healthy direction.
App.Doctrine.Listener uses App.Service.Discussion, so a change to App.Service.Discussion can break App.Doctrine.Listener, while a change to App.Doctrine.Listener can't break App.Service.Discussion.
Position
Below the diagonal: App.Doctrine.Listener uses a module listed above it, which is the healthy direction.
27→28 App.Doctrine.Listener uses App.Entity.Corepart of a loop✕
Connections
3 pairs of types, where a type in App.Doctrine.Listener uses a type in App.Entity.Core.
App.Doctrine.Listener uses App.Entity.Core, so a change to App.Entity.Core can break App.Doctrine.Listener, while a change to App.Doctrine.Listener can't break App.Entity.Core.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
33 pairs of types, where a type in App.Entity.Core uses a type in Alchemy.CoreBundle.Entity. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
App.Entity.Core uses Alchemy.CoreBundle.Entity, so a change to Alchemy.CoreBundle.Entity can break App.Entity.Core, while a change to App.Entity.Core can't break Alchemy.CoreBundle.Entity.
Position
Below the diagonal: App.Entity.Core uses a module listed above it, which is the healthy direction.
App.Entity.Core uses App.Entity.Integration, so a change to App.Entity.Integration can break App.Entity.Core, while a change to App.Entity.Core can't break App.Entity.Integration.
Position
Below the diagonal: App.Entity.Core uses a module listed above it, which is the healthy direction.
App.Entity.Core uses App.Doctrine.Listener, so a change to App.Doctrine.Listener can break App.Entity.Core, while a change to App.Entity.Core can't break App.Doctrine.Listener.
Position
Below the diagonal: App.Entity.Core uses a module listed above it, which is the healthy direction.
App.Attribute uses Alchemy.AuthBundle.Security, so a change to Alchemy.AuthBundle.Security can break App.Attribute, while a change to App.Attribute can't break Alchemy.AuthBundle.Security.
Position
Below the diagonal: App.Attribute uses a module listed above it, which is the healthy direction.
App.Attribute uses Alchemy.MessengerBundle.Listener, so a change to Alchemy.MessengerBundle.Listener can break App.Attribute, while a change to App.Attribute can't break Alchemy.MessengerBundle.Listener.
Position
Below the diagonal: App.Attribute uses a module listed above it, which is the healthy direction.
App.Attribute uses App.Repository.Core, so a change to App.Repository.Core can break App.Attribute, while a change to App.Attribute can't break App.Repository.Core.
Position
Below the diagonal: App.Attribute uses a module listed above it, which is the healthy direction.
App.Attribute uses App.Service.Asset.Attribute, so a change to App.Service.Asset.Attribute can break App.Attribute, while a change to App.Attribute can't break App.Service.Asset.Attribute.
Position
Below the diagonal: App.Attribute uses a module listed above it, which is the healthy direction.
App.Attribute uses App.Service.Log, so a change to App.Service.Log can break App.Attribute, while a change to App.Attribute can't break App.Service.Log.
Position
Below the diagonal: App.Attribute uses a module listed above it, which is the healthy direction.
App.Attribute uses App.Entity.Core, so a change to App.Entity.Core can break App.Attribute, while a change to App.Attribute can't break App.Entity.Core.
Position
Below the diagonal: App.Attribute uses a module listed above it, which is the healthy direction.
App.Integration uses Alchemy.CoreBundle.Entity, so a change to Alchemy.CoreBundle.Entity can break App.Integration, while a change to App.Integration can't break Alchemy.CoreBundle.Entity.
Position
Below the diagonal: App.Integration uses a module listed above it, which is the healthy direction.
App.Integration uses Alchemy.Workflow.Model, so a change to Alchemy.Workflow.Model can break App.Integration, while a change to App.Integration can't break Alchemy.Workflow.Model.
Position
Below the diagonal: App.Integration uses a module listed above it, which is the healthy direction.
App.Integration uses Alchemy.Workflow.Executor, so a change to Alchemy.Workflow.Executor can break App.Integration, while a change to App.Integration can't break Alchemy.Workflow.Executor.
Position
Below the diagonal: App.Integration uses a module listed above it, which is the healthy direction.
App.Integration uses App.Entity.Integration, so a change to App.Entity.Integration can break App.Integration, while a change to App.Integration can't break App.Entity.Integration.
Position
Below the diagonal: App.Integration uses a module listed above it, which is the healthy direction.
App.Integration uses App.Entity.Core, so a change to App.Entity.Core can break App.Integration, while a change to App.Integration can't break App.Entity.Core.
Position
Below the diagonal: App.Integration uses a module listed above it, which is the healthy direction.
App.Api.Provider uses Alchemy.MessengerBundle.Listener, so a change to Alchemy.MessengerBundle.Listener can break App.Api.Provider, while a change to App.Api.Provider can't break Alchemy.MessengerBundle.Listener.
Position
Below the diagonal: App.Api.Provider uses a module listed above it, which is the healthy direction.
App.Api.Provider uses App.Repository.Core, so a change to App.Repository.Core can break App.Api.Provider, while a change to App.Api.Provider can't break App.Repository.Core.
Position
Below the diagonal: App.Api.Provider uses a module listed above it, which is the healthy direction.
App.Api.Provider uses App.Service.Storage, so a change to App.Service.Storage can break App.Api.Provider, while a change to App.Api.Provider can't break App.Service.Storage.
Position
Below the diagonal: App.Api.Provider uses a module listed above it, which is the healthy direction.
App.Api.Provider uses App.Service.Asset.Attribute, so a change to App.Service.Asset.Attribute can break App.Api.Provider, while a change to App.Api.Provider can't break App.Service.Asset.Attribute.
Position
Below the diagonal: App.Api.Provider uses a module listed above it, which is the healthy direction.
App.Api.Provider uses App.Service.Image, so a change to App.Service.Image can break App.Api.Provider, while a change to App.Api.Provider can't break App.Service.Image.
Position
Below the diagonal: App.Api.Provider uses a module listed above it, which is the healthy direction.
App.Api.Provider uses App.Service.Log, so a change to App.Service.Log can break App.Api.Provider, while a change to App.Api.Provider can't break App.Service.Log.
Position
Below the diagonal: App.Api.Provider uses a module listed above it, which is the healthy direction.
App.Api.Provider uses App.Security, so a change to App.Security can break App.Api.Provider, while a change to App.Api.Provider can't break App.Security.
Position
Below the diagonal: App.Api.Provider uses a module listed above it, which is the healthy direction.
App.Api.Provider uses App.Service.Workspace, so a change to App.Service.Workspace can break App.Api.Provider, while a change to App.Api.Provider can't break App.Service.Workspace.
Position
Below the diagonal: App.Api.Provider uses a module listed above it, which is the healthy direction.
App.Api.Provider uses App.Elasticsearch, so a change to App.Elasticsearch can break App.Api.Provider, while a change to App.Api.Provider can't break App.Elasticsearch.
Position
Below the diagonal: App.Api.Provider uses a module listed above it, which is the healthy direction.
App.Api.Provider uses App.Service.Asset, so a change to App.Service.Asset can break App.Api.Provider, while a change to App.Api.Provider can't break App.Service.Asset.
Position
Below the diagonal: App.Api.Provider uses a module listed above it, which is the healthy direction.
App.Api.Provider uses App.Entity.Core, so a change to App.Entity.Core can break App.Api.Provider, while a change to App.Api.Provider can't break App.Entity.Core.
Position
Below the diagonal: App.Api.Provider uses a module listed above it, which is the healthy direction.
App.Api.Provider uses App.Attribute, so a change to App.Attribute can break App.Api.Provider, while a change to App.Api.Provider can't break App.Attribute.
Position
Below the diagonal: App.Api.Provider uses a module listed above it, which is the healthy direction.
App.Api.Provider uses App.Integration, so a change to App.Integration can break App.Api.Provider, while a change to App.Api.Provider can't break App.Integration.
Position
Below the diagonal: App.Api.Provider uses a module listed above it, which is the healthy direction.
App.Controller.Admin uses Alchemy.Workflow, so a change to Alchemy.Workflow can break App.Controller.Admin, while a change to App.Controller.Admin can't break Alchemy.Workflow.
Position
Below the diagonal: App.Controller.Admin uses a module listed above it, which is the healthy direction.
App.Controller.Admin uses App.Service.Workspace, so a change to App.Service.Workspace can break App.Controller.Admin, while a change to App.Controller.Admin can't break App.Service.Workspace.
Position
Below the diagonal: App.Controller.Admin uses a module listed above it, which is the healthy direction.
App.Controller.Admin uses App.Elasticsearch, so a change to App.Elasticsearch can break App.Controller.Admin, while a change to App.Controller.Admin can't break App.Elasticsearch.
Position
Below the diagonal: App.Controller.Admin uses a module listed above it, which is the healthy direction.
App.Controller.Admin uses App.Entity.Core, so a change to App.Entity.Core can break App.Controller.Admin, while a change to App.Controller.Admin can't break App.Entity.Core.
Position
Below the diagonal: App.Controller.Admin uses a module listed above it, which is the healthy direction.
App.Controller.Admin uses App.Attribute, so a change to App.Attribute can break App.Controller.Admin, while a change to App.Controller.Admin can't break App.Attribute.
Position
Below the diagonal: App.Controller.Admin uses a module listed above it, which is the healthy direction.
App.Controller.Admin uses App.Integration, so a change to App.Integration can break App.Controller.Admin, while a change to App.Controller.Admin can't break App.Integration.
Position
Below the diagonal: App.Controller.Admin uses a module listed above it, which is the healthy direction.
App.Integration.Core.FaceRecognition uses Alchemy.MessengerBundle.Listener, so a change to Alchemy.MessengerBundle.Listener can break App.Integration.Core.FaceRecognition, while a change to App.Integration.Core.FaceRecognition can't break Alchemy.MessengerBundle.Listener.
Position
Below the diagonal: App.Integration.Core.FaceRecognition uses a module listed above it, which is the healthy direction.
App.Integration.Core.FaceRecognition uses Alchemy.Workflow.Model, so a change to Alchemy.Workflow.Model can break App.Integration.Core.FaceRecognition, while a change to App.Integration.Core.FaceRecognition can't break Alchemy.Workflow.Model.
Position
Below the diagonal: App.Integration.Core.FaceRecognition uses a module listed above it, which is the healthy direction.
App.Integration.Core.FaceRecognition uses App.Repository.Core, so a change to App.Repository.Core can break App.Integration.Core.FaceRecognition, while a change to App.Integration.Core.FaceRecognition can't break App.Repository.Core.
Position
Below the diagonal: App.Integration.Core.FaceRecognition uses a module listed above it, which is the healthy direction.
App.Integration.Core.FaceRecognition uses App.Service.Storage, so a change to App.Service.Storage can break App.Integration.Core.FaceRecognition, while a change to App.Integration.Core.FaceRecognition can't break App.Service.Storage.
Position
Below the diagonal: App.Integration.Core.FaceRecognition uses a module listed above it, which is the healthy direction.
App.Integration.Core.FaceRecognition uses Alchemy.Workflow.Executor, so a change to Alchemy.Workflow.Executor can break App.Integration.Core.FaceRecognition, while a change to App.Integration.Core.FaceRecognition can't break Alchemy.Workflow.Executor.
Position
Below the diagonal: App.Integration.Core.FaceRecognition uses a module listed above it, which is the healthy direction.
App.Integration.Core.FaceRecognition uses App.Service.Image, so a change to App.Service.Image can break App.Integration.Core.FaceRecognition, while a change to App.Integration.Core.FaceRecognition can't break App.Service.Image.
Position
Below the diagonal: App.Integration.Core.FaceRecognition uses a module listed above it, which is the healthy direction.
App.Integration.Core.FaceRecognition uses App.Entity.Integration, so a change to App.Entity.Integration can break App.Integration.Core.FaceRecognition, while a change to App.Integration.Core.FaceRecognition can't break App.Entity.Integration.
Position
Below the diagonal: App.Integration.Core.FaceRecognition uses a module listed above it, which is the healthy direction.
App.Integration.Core.FaceRecognition uses App.Service.Asset, so a change to App.Service.Asset can break App.Integration.Core.FaceRecognition, while a change to App.Integration.Core.FaceRecognition can't break App.Service.Asset.
Position
Below the diagonal: App.Integration.Core.FaceRecognition uses a module listed above it, which is the healthy direction.
App.Integration.Core.FaceRecognition uses App.Entity.Core, so a change to App.Entity.Core can break App.Integration.Core.FaceRecognition, while a change to App.Integration.Core.FaceRecognition can't break App.Entity.Core.
Position
Below the diagonal: App.Integration.Core.FaceRecognition uses a module listed above it, which is the healthy direction.
App.Integration.Core.FaceRecognition uses App.Attribute, so a change to App.Attribute can break App.Integration.Core.FaceRecognition, while a change to App.Integration.Core.FaceRecognition can't break App.Attribute.
Position
Below the diagonal: App.Integration.Core.FaceRecognition uses a module listed above it, which is the healthy direction.
App.Integration.Core.FaceRecognition uses App.Integration, so a change to App.Integration can break App.Integration.Core.FaceRecognition, while a change to App.Integration.Core.FaceRecognition can't break App.Integration.
Position
Below the diagonal: App.Integration.Core.FaceRecognition uses a module listed above it, which is the healthy direction.
App.Integration.Phrasea.Expose uses App.Model, so a change to App.Model can break App.Integration.Phrasea.Expose, while a change to App.Integration.Phrasea.Expose can't break App.Model.
Position
Below the diagonal: App.Integration.Phrasea.Expose uses a module listed above it, which is the healthy direction.
App.Integration.Phrasea.Expose uses App.Service.Storage, so a change to App.Service.Storage can break App.Integration.Phrasea.Expose, while a change to App.Integration.Phrasea.Expose can't break App.Service.Storage.
Position
Below the diagonal: App.Integration.Phrasea.Expose uses a module listed above it, which is the healthy direction.
App.Integration.Phrasea.Expose uses App.Service.Asset.Attribute, so a change to App.Service.Asset.Attribute can break App.Integration.Phrasea.Expose, while a change to App.Integration.Phrasea.Expose can't break App.Service.Asset.Attribute.
Position
Below the diagonal: App.Integration.Phrasea.Expose uses a module listed above it, which is the healthy direction.
App.Integration.Phrasea.Expose uses App.Entity.Integration, so a change to App.Entity.Integration can break App.Integration.Phrasea.Expose, while a change to App.Integration.Phrasea.Expose can't break App.Entity.Integration.
Position
Below the diagonal: App.Integration.Phrasea.Expose uses a module listed above it, which is the healthy direction.
App.Integration.Phrasea.Expose uses App.Service.Asset, so a change to App.Service.Asset can break App.Integration.Phrasea.Expose, while a change to App.Integration.Phrasea.Expose can't break App.Service.Asset.
Position
Below the diagonal: App.Integration.Phrasea.Expose uses a module listed above it, which is the healthy direction.
App.Integration.Phrasea.Expose uses App.Entity.Core, so a change to App.Entity.Core can break App.Integration.Phrasea.Expose, while a change to App.Integration.Phrasea.Expose can't break App.Entity.Core.
Position
Below the diagonal: App.Integration.Phrasea.Expose uses a module listed above it, which is the healthy direction.
App.Integration.Phrasea.Expose uses App.Attribute, so a change to App.Attribute can break App.Integration.Phrasea.Expose, while a change to App.Integration.Phrasea.Expose can't break App.Attribute.
Position
Below the diagonal: App.Integration.Phrasea.Expose uses a module listed above it, which is the healthy direction.
App.Integration.Phrasea.Expose uses App.Integration, so a change to App.Integration can break App.Integration.Phrasea.Expose, while a change to App.Integration.Phrasea.Expose can't break App.Integration.
Position
Below the diagonal: App.Integration.Phrasea.Expose uses a module listed above it, which is the healthy direction.
App.Automation.Action uses Alchemy.NotifierBundle.Manager, so a change to Alchemy.NotifierBundle.Manager can break App.Automation.Action, while a change to App.Automation.Action can't break Alchemy.NotifierBundle.Manager.
Position
Below the diagonal: App.Automation.Action uses a module listed above it, which is the healthy direction.
App.Automation.Action uses App.Model, so a change to App.Model can break App.Automation.Action, while a change to App.Automation.Action can't break App.Model.
Position
Below the diagonal: App.Automation.Action uses a module listed above it, which is the healthy direction.
App.Automation.Action uses App.Service.Asset.Attribute, so a change to App.Service.Asset.Attribute can break App.Automation.Action, while a change to App.Automation.Action can't break App.Service.Asset.Attribute.
Position
Below the diagonal: App.Automation.Action uses a module listed above it, which is the healthy direction.
App.Automation.Action uses App.Entity.Integration, so a change to App.Entity.Integration can break App.Automation.Action, while a change to App.Automation.Action can't break App.Entity.Integration.
Position
Below the diagonal: App.Automation.Action uses a module listed above it, which is the healthy direction.
App.Automation.Action uses App.Security, so a change to App.Security can break App.Automation.Action, while a change to App.Automation.Action can't break App.Security.
Position
Below the diagonal: App.Automation.Action uses a module listed above it, which is the healthy direction.
App.Automation.Action uses App.Service.Asset, so a change to App.Service.Asset can break App.Automation.Action, while a change to App.Automation.Action can't break App.Service.Asset.
Position
Below the diagonal: App.Automation.Action uses a module listed above it, which is the healthy direction.
App.Automation.Action uses App.Entity.Core, so a change to App.Entity.Core can break App.Automation.Action, while a change to App.Automation.Action can't break App.Entity.Core.
Position
Below the diagonal: App.Automation.Action uses a module listed above it, which is the healthy direction.
App.Automation.Action uses App.Attribute, so a change to App.Attribute can break App.Automation.Action, while a change to App.Automation.Action can't break App.Attribute.
Position
Below the diagonal: App.Automation.Action uses a module listed above it, which is the healthy direction.
App.Automation.Action uses App.Integration, so a change to App.Integration can break App.Automation.Action, while a change to App.Automation.Action can't break App.Integration.
Position
Below the diagonal: App.Automation.Action uses a module listed above it, which is the healthy direction.
App.Automation.Action uses App.Integration.Phrasea.Expose, so a change to App.Integration.Phrasea.Expose can break App.Automation.Action, while a change to App.Automation.Action can't break App.Integration.Phrasea.Expose.
Position
Below the diagonal: App.Automation.Action uses a module listed above it, which is the healthy direction.
35→37 App.Automation.Action uses App.Automationpart of a loop✕
Connections
27 pairs of types, where a type in App.Automation.Action uses a type in App.Automation. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
App.Automation.Action uses App.Automation, so a change to App.Automation can break App.Automation.Action, while a change to App.Automation.Action can't break App.Automation.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
App.Command uses App.Repository.Core, so a change to App.Repository.Core can break App.Command, while a change to App.Command can't break App.Repository.Core.
Position
Below the diagonal: App.Command uses a module listed above it, which is the healthy direction.
App.Command uses App.Service.Workspace, so a change to App.Service.Workspace can break App.Command, while a change to App.Command can't break App.Service.Workspace.
Position
Below the diagonal: App.Command uses a module listed above it, which is the healthy direction.
App.Command uses App.Elasticsearch, so a change to App.Elasticsearch can break App.Command, while a change to App.Command can't break App.Elasticsearch.
Position
Below the diagonal: App.Command uses a module listed above it, which is the healthy direction.
App.Command uses App.Service.Asset, so a change to App.Service.Asset can break App.Command, while a change to App.Command can't break App.Service.Asset.
Position
Below the diagonal: App.Command uses a module listed above it, which is the healthy direction.
App.Command uses App.Integration.Core.FaceRecognition, so a change to App.Integration.Core.FaceRecognition can break App.Command, while a change to App.Command can't break App.Integration.Core.FaceRecognition.
Position
Below the diagonal: App.Command uses a module listed above it, which is the healthy direction.
App.Automation uses Alchemy.AuthBundle.Security, so a change to Alchemy.AuthBundle.Security can break App.Automation, while a change to App.Automation can't break Alchemy.AuthBundle.Security.
Position
Below the diagonal: App.Automation uses a module listed above it, which is the healthy direction.
App.Automation uses App.Repository.Core, so a change to App.Repository.Core can break App.Automation, while a change to App.Automation can't break App.Repository.Core.
Position
Below the diagonal: App.Automation uses a module listed above it, which is the healthy direction.
App.Automation uses App.Elasticsearch, so a change to App.Elasticsearch can break App.Automation, while a change to App.Automation can't break App.Elasticsearch.
Position
Below the diagonal: App.Automation uses a module listed above it, which is the healthy direction.
App.Automation uses App.Automation.Action, so a change to App.Automation.Action can break App.Automation, while a change to App.Automation can't break App.Automation.Action.
Position
Below the diagonal: App.Automation uses a module listed above it, which is the healthy direction.
App.Api.Mapper.Input uses Alchemy.MessengerBundle.Listener, so a change to Alchemy.MessengerBundle.Listener can break App.Api.Mapper.Input, while a change to App.Api.Mapper.Input can't break Alchemy.MessengerBundle.Listener.
Position
Below the diagonal: App.Api.Mapper.Input uses a module listed above it, which is the healthy direction.
App.Api.Mapper.Input uses Alchemy.StorageBundle.Upload, so a change to Alchemy.StorageBundle.Upload can break App.Api.Mapper.Input, while a change to App.Api.Mapper.Input can't break Alchemy.StorageBundle.Upload.
Position
Below the diagonal: App.Api.Mapper.Input uses a module listed above it, which is the healthy direction.
App.Api.Mapper.Input uses App.Repository.Core, so a change to App.Repository.Core can break App.Api.Mapper.Input, while a change to App.Api.Mapper.Input can't break App.Repository.Core.
Position
Below the diagonal: App.Api.Mapper.Input uses a module listed above it, which is the healthy direction.
App.Api.Mapper.Input uses App.Service.Storage, so a change to App.Service.Storage can break App.Api.Mapper.Input, while a change to App.Api.Mapper.Input can't break App.Service.Storage.
Position
Below the diagonal: App.Api.Mapper.Input uses a module listed above it, which is the healthy direction.
App.Api.Mapper.Input uses App.Service.Asset.Attribute, so a change to App.Service.Asset.Attribute can break App.Api.Mapper.Input, while a change to App.Api.Mapper.Input can't break App.Service.Asset.Attribute.
Position
Below the diagonal: App.Api.Mapper.Input uses a module listed above it, which is the healthy direction.
App.Api.Mapper.Input uses App.Entity.Integration, so a change to App.Entity.Integration can break App.Api.Mapper.Input, while a change to App.Api.Mapper.Input can't break App.Entity.Integration.
Position
Below the diagonal: App.Api.Mapper.Input uses a module listed above it, which is the healthy direction.
App.Api.Mapper.Input uses App.Service.Workspace, so a change to App.Service.Workspace can break App.Api.Mapper.Input, while a change to App.Api.Mapper.Input can't break App.Service.Workspace.
Position
Below the diagonal: App.Api.Mapper.Input uses a module listed above it, which is the healthy direction.
App.Api.Mapper.Input uses App.Service.Asset, so a change to App.Service.Asset can break App.Api.Mapper.Input, while a change to App.Api.Mapper.Input can't break App.Service.Asset.
Position
Below the diagonal: App.Api.Mapper.Input uses a module listed above it, which is the healthy direction.
App.Api.Mapper.Input uses App.Entity.Core, so a change to App.Entity.Core can break App.Api.Mapper.Input, while a change to App.Api.Mapper.Input can't break App.Entity.Core.
Position
Below the diagonal: App.Api.Mapper.Input uses a module listed above it, which is the healthy direction.
App.Api.Mapper.Input uses App.Attribute, so a change to App.Attribute can break App.Api.Mapper.Input, while a change to App.Api.Mapper.Input can't break App.Attribute.
Position
Below the diagonal: App.Api.Mapper.Input uses a module listed above it, which is the healthy direction.
App.Api.Mapper.Input uses App.Integration, so a change to App.Integration can break App.Api.Mapper.Input, while a change to App.Api.Mapper.Input can't break App.Integration.
Position
Below the diagonal: App.Api.Mapper.Input uses a module listed above it, which is the healthy direction.
App.Api.Mapper.Input uses App.Automation, so a change to App.Automation can break App.Api.Mapper.Input, while a change to App.Api.Mapper.Input can't break App.Automation.
Position
Below the diagonal: App.Api.Mapper.Input uses a module listed above it, which is the healthy direction.
App.Api.Mapper.Output uses Alchemy.NotifierBundle.Manager, so a change to Alchemy.NotifierBundle.Manager can break App.Api.Mapper.Output, while a change to App.Api.Mapper.Output can't break Alchemy.NotifierBundle.Manager.
Position
Below the diagonal: App.Api.Mapper.Output uses a module listed above it, which is the healthy direction.
App.Api.Mapper.Output uses App.Service.Asset.Attribute, so a change to App.Service.Asset.Attribute can break App.Api.Mapper.Output, while a change to App.Api.Mapper.Output can't break App.Service.Asset.Attribute.
Position
Below the diagonal: App.Api.Mapper.Output uses a module listed above it, which is the healthy direction.
App.Api.Mapper.Output uses App.Service.Log, so a change to App.Service.Log can break App.Api.Mapper.Output, while a change to App.Api.Mapper.Output can't break App.Service.Log.
Position
Below the diagonal: App.Api.Mapper.Output uses a module listed above it, which is the healthy direction.
App.Api.Mapper.Output uses App.Security, so a change to App.Security can break App.Api.Mapper.Output, while a change to App.Api.Mapper.Output can't break App.Security.
Position
Below the diagonal: App.Api.Mapper.Output uses a module listed above it, which is the healthy direction.
App.Api.Mapper.Output uses App.Service.Workspace, so a change to App.Service.Workspace can break App.Api.Mapper.Output, while a change to App.Api.Mapper.Output can't break App.Service.Workspace.
Position
Below the diagonal: App.Api.Mapper.Output uses a module listed above it, which is the healthy direction.
App.Api.Mapper.Output uses App.Elasticsearch, so a change to App.Elasticsearch can break App.Api.Mapper.Output, while a change to App.Api.Mapper.Output can't break App.Elasticsearch.
Position
Below the diagonal: App.Api.Mapper.Output uses a module listed above it, which is the healthy direction.
App.Api.Mapper.Output uses App.Service.Asset, so a change to App.Service.Asset can break App.Api.Mapper.Output, while a change to App.Api.Mapper.Output can't break App.Service.Asset.
Position
Below the diagonal: App.Api.Mapper.Output uses a module listed above it, which is the healthy direction.
App.Api.Mapper.Output uses App.Service.Discussion, so a change to App.Service.Discussion can break App.Api.Mapper.Output, while a change to App.Api.Mapper.Output can't break App.Service.Discussion.
Position
Below the diagonal: App.Api.Mapper.Output uses a module listed above it, which is the healthy direction.
App.Api.Mapper.Output uses App.Entity.Core, so a change to App.Entity.Core can break App.Api.Mapper.Output, while a change to App.Api.Mapper.Output can't break App.Entity.Core.
Position
Below the diagonal: App.Api.Mapper.Output uses a module listed above it, which is the healthy direction.
App.Api.Mapper.Output uses App.Attribute, so a change to App.Attribute can break App.Api.Mapper.Output, while a change to App.Api.Mapper.Output can't break App.Attribute.
Position
Below the diagonal: App.Api.Mapper.Output uses a module listed above it, which is the healthy direction.
App.Api.Mapper.Output uses App.Integration, so a change to App.Integration can break App.Api.Mapper.Output, while a change to App.Api.Mapper.Output can't break App.Integration.
Position
Below the diagonal: App.Api.Mapper.Output uses a module listed above it, which is the healthy direction.
App.Api.Mapper.Output uses App.Automation, so a change to App.Automation can break App.Api.Mapper.Output, while a change to App.Api.Mapper.Output can't break App.Automation.
Position
Below the diagonal: App.Api.Mapper.Output uses a module listed above it, which is the healthy direction.
App.Api.Processor uses Alchemy.MessengerBundle.Listener, so a change to Alchemy.MessengerBundle.Listener can break App.Api.Processor, while a change to App.Api.Processor can't break Alchemy.MessengerBundle.Listener.
Position
Below the diagonal: App.Api.Processor uses a module listed above it, which is the healthy direction.
App.Api.Processor uses Alchemy.NotifierBundle.Manager, so a change to Alchemy.NotifierBundle.Manager can break App.Api.Processor, while a change to App.Api.Processor can't break Alchemy.NotifierBundle.Manager.
Position
Below the diagonal: App.Api.Processor uses a module listed above it, which is the healthy direction.
App.Api.Processor uses App.Repository.Core, so a change to App.Repository.Core can break App.Api.Processor, while a change to App.Api.Processor can't break App.Repository.Core.
Position
Below the diagonal: App.Api.Processor uses a module listed above it, which is the healthy direction.
App.Api.Processor uses App.Service.Storage, so a change to App.Service.Storage can break App.Api.Processor, while a change to App.Api.Processor can't break App.Service.Storage.
Position
Below the diagonal: App.Api.Processor uses a module listed above it, which is the healthy direction.
App.Api.Processor uses Alchemy.Workflow, so a change to Alchemy.Workflow can break App.Api.Processor, while a change to App.Api.Processor can't break Alchemy.Workflow.
Position
Below the diagonal: App.Api.Processor uses a module listed above it, which is the healthy direction.
App.Api.Processor uses App.Service.Image, so a change to App.Service.Image can break App.Api.Processor, while a change to App.Api.Processor can't break App.Service.Image.
Position
Below the diagonal: App.Api.Processor uses a module listed above it, which is the healthy direction.
App.Api.Processor uses App.Service.Log, so a change to App.Service.Log can break App.Api.Processor, while a change to App.Api.Processor can't break App.Service.Log.
Position
Below the diagonal: App.Api.Processor uses a module listed above it, which is the healthy direction.
App.Api.Processor uses App.Entity.Integration, so a change to App.Entity.Integration can break App.Api.Processor, while a change to App.Api.Processor can't break App.Entity.Integration.
Position
Below the diagonal: App.Api.Processor uses a module listed above it, which is the healthy direction.
App.Api.Processor uses App.Service.Workspace, so a change to App.Service.Workspace can break App.Api.Processor, while a change to App.Api.Processor can't break App.Service.Workspace.
Position
Below the diagonal: App.Api.Processor uses a module listed above it, which is the healthy direction.
App.Api.Processor uses App.Service.Asset, so a change to App.Service.Asset can break App.Api.Processor, while a change to App.Api.Processor can't break App.Service.Asset.
Position
Below the diagonal: App.Api.Processor uses a module listed above it, which is the healthy direction.
App.Api.Processor uses App.Service.Discussion, so a change to App.Service.Discussion can break App.Api.Processor, while a change to App.Api.Processor can't break App.Service.Discussion.
Position
Below the diagonal: App.Api.Processor uses a module listed above it, which is the healthy direction.
App.Api.Processor uses App.Doctrine.Listener, so a change to App.Doctrine.Listener can break App.Api.Processor, while a change to App.Api.Processor can't break App.Doctrine.Listener.
Position
Below the diagonal: App.Api.Processor uses a module listed above it, which is the healthy direction.
App.Api.Processor uses App.Entity.Core, so a change to App.Entity.Core can break App.Api.Processor, while a change to App.Api.Processor can't break App.Entity.Core.
Position
Below the diagonal: App.Api.Processor uses a module listed above it, which is the healthy direction.
App.Api.Processor uses App.Attribute, so a change to App.Attribute can break App.Api.Processor, while a change to App.Api.Processor can't break App.Attribute.
Position
Below the diagonal: App.Api.Processor uses a module listed above it, which is the healthy direction.
App.Api.Processor uses App.Integration, so a change to App.Integration can break App.Api.Processor, while a change to App.Api.Processor can't break App.Integration.
Position
Below the diagonal: App.Api.Processor uses a module listed above it, which is the healthy direction.
App.Api.Processor uses App.Api.Provider, so a change to App.Api.Provider can break App.Api.Processor, while a change to App.Api.Processor can't break App.Api.Provider.
Position
Below the diagonal: App.Api.Processor uses a module listed above it, which is the healthy direction.
App.Api.Processor uses App.Automation, so a change to App.Automation can break App.Api.Processor, while a change to App.Api.Processor can't break App.Automation.
Position
Below the diagonal: App.Api.Processor uses a module listed above it, which is the healthy direction.
App.Api.Processor uses App.Api.Mapper.Input, so a change to App.Api.Mapper.Input can break App.Api.Processor, while a change to App.Api.Processor can't break App.Api.Mapper.Input.
Position
Below the diagonal: App.Api.Processor uses a module listed above it, which is the healthy direction.
App.Api.Processor uses App.Api.Mapper.Output, so a change to App.Api.Mapper.Output can break App.Api.Processor, while a change to App.Api.Processor can't break App.Api.Mapper.Output.
Position
Below the diagonal: App.Api.Processor uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 50.9 · Adequate · gated by 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
A05:2025 — Injection
110
High / Critical
A02:2025 — Security Misconfiguration
64
High / Critical
A07:2025 — Authentication Failures
37
High / Critical
A03:2025 — Software Supply Chain Failures
36
High / Critical
Roadmap
Top priorities: Resolve the 2 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2); Resolve the 14 Banned license finding(s) in License Compliance — start with REDACTED (14); Resolve the 28 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (28).
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 2 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (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.
Give every client an explicit bound: `new Client(['timeout' => 10, 'connect_timeout' => 3])` for Guzzle (whose default is to wait forever), `CURLOPT_TIMEOUT`/`CURLOPT_CONNECTTIMEOUT` before `curl_exec`, `timeout`/`max_duration` on Symfony HttpClient (or `framework.http_client.default_options`), and a stream-context `timeout` or `connection_timeout` for `file_get_contents`/`SoapClient`. In Drupal, use the `http_client` service, which carries core's site-wide timeout, rather than `new Client()`. Add retries with back-off (Guzzle `Middleware::retry`, Symfony `RetryableHttpClient`, Laravel `->retry()`) around dependencies that fail.
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 — 221
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 — 1720
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 — 292
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 13
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 91 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 — 91 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, 2125 of 2233 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.
D10 Test Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 115 test(s) behind this row are the ones the code-model census could read, and this repository also carries at least 311 test source file(s) (.ts, .tsx, .js) that it cannot: it reads the test types the .php frontend declared, so a suite in any other language is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability NOT MEASURED: the JavaScript/TypeScript suite could not be re-run in the analyzer sandbox — the dependency install for dashboard/client/ failed in the analyzer sandbox (ERR_PNPM_BROKEN_LOCKFILE The lockfile at "REDACTED" is broken: expected a single document in the stream, but found more), so the suite never ran. This is OUR limitation, not a defect in the repo — it is excluded from the score.
D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the vitest suite in dashboard/client/ was NOT MEASURED: the dependency install for dashboard/client/ failed in the analyzer sandbox (ERR_PNPM_BROKEN_LOCKFILE The lockfile at "REDACTED" is broken: expected a single document in the stream, but found more), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the vitest suite in databox/client/ was NOT MEASURED: the dependency install for databox/client/ failed in the analyzer sandbox (ERR_PNPM_BROKEN_LOCKFILE The lockfile at "REDACTED" is broken: expected a single document in the stream, but found more), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the vitest suite in databox/indexer/ was NOT MEASURED: the dependency install for databox/indexer/ failed in the analyzer sandbox (ERR_PNPM_BROKEN_LOCKFILE The lockfile at "REDACTED" is broken: expected a single document in the stream, but found more), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the vitest suite in expose/client/ was NOT MEASURED: the dependency install for expose/client/ failed in the analyzer sandbox (ERR_PNPM_BROKEN_LOCKFILE The lockfile at "REDACTED" is broken: expected a single document in the stream, but found more), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the vitest suite in lib/js/api/ was NOT MEASURED: the dependency install for lib/js/api/ failed in the analyzer sandbox (ERR_PNPM_BROKEN_LOCKFILE The lockfile at "REDACTED" is broken: expected a single document in the stream, but found more), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the vitest suite in lib/js/auth/ was NOT MEASURED: the dependency install for lib/js/auth/ failed in the analyzer sandbox (ERR_PNPM_BROKEN_LOCKFILE The lockfile at "REDACTED" is broken: expected a single document in the stream, but found more), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the vitest suite in lib/js/next-core/ was NOT MEASURED: the dependency install for lib/js/next-core/ failed in the analyzer sandbox (ERR_PNPM_BROKEN_LOCKFILE The lockfile at "REDACTED" is broken: expected a single document in the stream, but found more), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the vitest suite in lib/js/next-i18n/ was NOT MEASURED: the dependency install for lib/js/next-i18n/ failed in the analyzer sandbox (ERR_PNPM_BROKEN_LOCKFILE The lockfile at "REDACTED" is broken: expected a single document in the stream, but found more), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the vitest suite in lib/js/next-theme/ was NOT MEASURED: the dependency install for lib/js/next-theme/ failed in the analyzer sandbox (ERR_PNPM_BROKEN_LOCKFILE The lockfile at "REDACTED" is broken: expected a single document in the stream, but found more), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the vitest suite in lib/js/next-ui/ was NOT MEASURED: the dependency install for lib/js/next-ui/ failed in the analyzer sandbox (ERR_PNPM_BROKEN_LOCKFILE The lockfile at "REDACTED" is broken: expected a single document in the stream, but found more), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the vitest suite in uploader/client/ was NOT MEASURED: the dependency install for uploader/client/ failed in the analyzer sandbox (ERR_PNPM_BROKEN_LOCKFILE The lockfile at "REDACTED" is broken: expected a single document in the stream, but found more), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
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.
D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. D21's naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
D24 Comment Value — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
D27 Navigability — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Tracing effort is measured over resolved call sites, and all 987 sampled here came from .php files. This repository's .tsx source is a material share of its production lines and contributed none, so the score above is a verdict about the part that was read. Not a finding that the unread half navigates well — it is unmeasured.
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. `configurator/src/Command/ConfigureCommand.php`, `configurator/src/Command/Migration20230807Command.php`, `configurator/src/Command/SynchronizeCommand.php`, `configurator/src/Configurator/Configurator.php`, `configurator/src/Configurator/Vendor/Database/DatabaseConfigurator.php`, … (+1380 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
D44 Platform End-of-Life — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a REDACTED) is simply not read here yet.
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. 31 further occurrence(s) are not listed individually; the score already reflects all 71.
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 Symfony DependencyInjection and a PSR-11 container (Psr\Container) and an unrecognised PHP 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.
AX7 Slice cohesion — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 433 further occurrence(s) are not listed individually; the score already reflects all 473.
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 (docker-compose.dev.yml). compose up failed (exit 15 — the compose project is invalid) — service "uploader-scheduler" has neither an image nor a build context specified: invalid compose project; runtime evidence skipped.
C1 Data Protection — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
C2 Access Controls — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
C3 Audit Trail — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
C4 Data Retention — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
DM1 Aggregate boundaries — 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. 61 further occurrence(s) are not listed individually; the score already reflects all 101.
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, Scala, Rust and Java 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, Scala and Rust 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.
M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
P7 Outbound HTTP resilience — 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. 14 further occurrence(s) are not listed individually; the score already reflects all 54.
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. 178 further occurrence(s) are not listed individually; the score already reflects all 218.
R2 Cyclomatic Complexity — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 140 further occurrence(s) are not listed individually; the score already reflects all 180.
R3 Large Files — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 26 further occurrence(s) are not listed individually; the score already reflects all 66.
R4 Test Coverage — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 310 further occurrence(s) are not listed individually; the score already reflects all 350.
R7 Dead Code — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 1 further occurrence(s) are not listed individually; the score already reflects all 41.
X1 Async correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X10 Duplicated predicate — 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. 15 further occurrence(s) are not listed individually; the score already reflects all 55.
X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X17 Uncapped recursion over a caller-supplied document — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X27 Collection changed while being enumerated — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
X29 Per-element action decided by a fixed element — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X3 Exception handling — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 15 further occurrence(s) are not listed individually; the score already reflects all 55.
X4 Structured logging — 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. 26 further occurrence(s) are not listed individually; the score already reflects all 66.
Repo exclusion declarations: 1 pattern(s) declared (.gitattributes linguist-generated/vendored, .editorconfig generated_code) excluded 0 source file(s) from code-quality scoring. Declarations are the repo's own visible statement that a tree is machine-written or vendored — auditable in any diff, honored by GitHub the same way.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
D22 Internal API Consistency: API consistency compares the call shapes of members that play the same role on the exposed C# surface: whether the API suits its callers is not measured, and surfaces in other languages are not measured.
D23 Boundary Type-Coupling: Boundary leakage is detected from type references across detected contexts — leaks that flow through primitives, serialization or shared infrastructure may not surface as a typed reference.
D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
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.
AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
C3 Audit Trail: This control is scored from in-repo evidence only — a working control configured outside the repository leaves no signal a static scan can credit.
C4 Data Retention: This control is scored from in-repo evidence only — its real-world effectiveness, exercised only at runtime, is outside a static scan.
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.
M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
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.
227 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was AssetMap.MapView at 98. A further 1 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being GlobalToasts.GlobalToasts at 16 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: databox/client/src/features/upload/GlobalToasts.tsx (GlobalToasts.GlobalToasts at 16). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
+ 219 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 8 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with AssetMap.MapView (cyclomatic 98), CollectionVoter.doVote (cyclomatic 90), AttributeBatchEditorRoute.AttributeBatchEditorRoute (cyclomatic 90). — 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 8 together lifts Cyclomatic Complexity from 6.0 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
+ 321 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 1 body over 120 down to 120 or less in Cognitive Complexity — start with AQLGrammar.match_operator (cognitive 246). — Refactoring it lifts Cognitive Complexity from 4.9 to about 5.7/10.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes7.3 / 10Strong✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 146 FunctionTooLong finding(s) in God Classes — start with ConfigForm.tsx (4), CollectionsPanel.tsx (3), ConditionBuilder.tsx (3). — One of this dimension's main actionable groups (146 warning-level).
Resolve the 30 FileTooLong finding(s) in God Classes — start with ConfigForm.tsx (2), AQLGrammar.php, AttributeBatchEditorRoute.tsx. — One of this dimension's main actionable groups (30 warning-level).
Resolve the 16 TooManyMethods finding(s) in God Classes — start with Asset.php (2), AttributeDefinition.php, Publication.php. — One of this dimension's main actionable groups (16 warning-level).
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How much of the production code is copy-pasted: the share of production lines inside a reported copy (every copy of a duplicated block or of an edited member, each line once), 10 at none and 0 at a quarter of the lines.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), scored on the share of production lines inside a reported copy (each line once; 10 at none, 0 at a quarter). Deterministic.
178 duplicated block group(s) detected. 2.8 % of the production lines (8,215 of 293,156) are in a reported copy. A further 109 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. Measured on part of this repository only: .tsx (32% of production source) was not exposed to THIS dimension's token comparison and is not in this count; duplication there is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream.
Edited copy of a member (6 corresponding lines) · ×12lib/php/rendition-factory/src/Transformer/Video/VideoTransformer.php:170
Edited copy of a member (4 corresponding lines) · ×7expose/api/src/Controller/ClientLogAction.php:75
+ 136 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 12 Edited copy of a member (6 corresponding lines) finding(s) in Code Duplication — start with VideoTransformer.php, TargetDataProcessor.php, RekognitionAnalyzeHandler.php. — One of this dimension's main actionable groups (12 warning-level).
Resolve the 12 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with FollowProcessor.php, ShareAttachmentProvider.php, FileAnalyzer.php. — One of this dimension's main actionable groups (12 warning-level).
Resolve the 11 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with AQLGrammar.php (3), AutomationRunCrudController.php, CollectionDelete.php. — One of this dimension's main actionable groups (11 warning-level).
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling5.4 / 10Adequate✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
35 production modules (npm+Composer), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 20 module(s) off the main sequence.
Off the main sequence: @alchemy/core · ×20
What to do
Resolve the 20 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (20 warning-level).
Detailed fixes: d5_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 2 Low cohesion finding(s) in Cohesion (LCOM4) — start with AwsRekognitionIntegration.php, FaceRecognitionIntegration.php. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D10 · Test 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.
1 skipped (1 with a documented reason), 2 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 115 tests. Measured on the .php suite only — at least 311 test source file(s) (.ts, .tsx, .js) went unread, so its test quality is unmeasured and is not in these counts.
No assertions (declared): testAcceptedCouple · ×2lib/php/storage-bundle/Tests/FileValidatorTest.php:20
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.
31 outdated direct production npm dependency(ies) of 62 graded, 1 pinning defect(s), across 14 package.json (14 of them the product) and 1 committed lockfile(s). Development dependencies are deliberately not graded for currency: that grade is about what SHIPS. 4 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.
Resolve the 28 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (28). — One of this dimension's main actionable groups (28 recommendation-level).
Resolve the 5 Deprecated finding(s) in Dependency Hygiene — start with package.json (5). — One of this dimension's main actionable groups (5 warning-level).
Resolve the 1 One package at two majors across the workspace finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (1 warning-level).
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.
2 secret(s) detected. 12 detection(s) were excluded as holding no minted credential in material that runs: a name, reference or comparison rather than a value, a readable phrase or pattern, a value that declares itself fake, or development, test, example, mock or demo material.
REDACTED
What to do
Resolve the 2 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
Detailed fixes: d13_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
14 of 731 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 731 package(s) this repository's committed lockfile installs for a consumer — its 62 production, optional and peer dependency(ies), across 14 product package.json manifest(s), and everything those install in turn. Its 183 `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. 1 of them publish no licence this pass can read on registry.npmjs.org — an absent field, `UNLICENSED`, or a `SEE LICENSE IN <file>` pointer into a tarball this pass does not download; that is missing data, not a violation, and none of them is charged. Third-party code that ships WITHOUT a manifest entry was read too: 0 component(s) whose licence travels in the tree (vendored or copied-in directories, licence comments preserved in committed bundles, compiled wasm modules) and 0 bundled package(s) named only by a bundle's module path, graded on the registry; 0 use a banned licence. 5 vendored, copied-in or compiled component(s) state no licence this pass can read — missing data, not charged. This repository publishes itself under MIT, which is its own choice and is not judged here. ★ 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.
Resolve the 14 Banned license finding(s) in License Compliance — start with REDACTED (14). — One of this dimension's main actionable groups (14 issue-level).
Detailed fixes: d14_recommendation.md · top locations in Appendix A, every location in findings.md.
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: databox/client/src/features/assets/view/AssetViewRoute.tsx (21×84=1764); databox/client/src/features/attributes/batch/AttributeBatchEditorRoute.tsx (12×90=1080); databox/client/src/features/workspaces/manage/DefinitionManager.tsx (14×74=1036) Repeated repair below the complexity floor: expose/api/src/Entity/Asset.php (8 of 11 changes were fixes); expose/api/src/Entity/Publication.php (6 of 11 changes were fixes); databox/api/src/Service/Asset/AssetCopier.php (6 of 7 changes were fixes)
Resolve the 110 Hotspot finding(s) in Churn × Complexity Hotspots — start with AssetViewRoute.tsx, AttributeBatchEditorRoute.tsx, DefinitionManager.tsx. — One of this dimension's main actionable groups (110 warning-level).
Resolve the 28 Repeated repair finding(s) in Churn × Complexity Hotspots — start with Asset.php, Publication.php, AssetCopier.php. — One of this dimension's main actionable groups (28 warning-level).
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D16 · Bus Factor6.9 / 10Adequate✓ Tool-verified
What it measures: Whether knowledge is concentrated in too few people (the "bus factor").
Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.
350 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is lib/js/core/src/mimeTypes.ts. Counted over 1097 of the 3043 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Off-boarding risk: anonymized user #1
Further sole-owners (lower concentration)
What to do
Resolve the 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d16_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.
14 deducted task-comment markers across 293156 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 14 TodoComment finding(s) in Explicit Debt — start with StructureImporter.ts (3), PdfToImageTransformerModule.php (2), VideoToAnimationTransformerModule.php. — One of this dimension's main actionable groups (14 warning-level).
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.
2 of 2 documentation facets pass in full. 94 document(s) read across 14 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.
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with composer.json. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d20_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether names — types, methods, variables — are clear and consistent.
Method: Seven vocabulary-free rules (N1-N7) mine each naming convention from the repository and flag a name that breaks a convention its structural peers in the same unit follow; production C# and TypeScript, each its own population. Deterministic, no model, no sample. Advisory.
2 naming inconsistencies among 57 declarations measured against a convention their peers follow.
`baseURL` spells `URL` where 55 names in the project spell it `Url` · ×2databox/indexer/src/databox/client.ts:27
What to do
Resolve the 2 `baseURL` spells `URL` where 55 names in the project spell it `Url` finding(s) in Naming Consistency — start with client.ts, httpClient.ts. — One of this dimension's main actionable groups (2 recommendation-level).
Detailed fixes: d21_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D22 · Internal API Consistency10.0 / 10Exemplary○ Nothing flagged
What it measures: Whether the internal API surface is consistent and coherent.
Method: Call-shape rules (A1-A9) over the structured code model of the intentionally exposed C# surface: members of one type, overloads of one name and the same slot across sibling types are compared, and a member that makes a caller use a different convention for the same kind of operation is flagged. Deterministic, no model. Advisory.
What it measures: Whether domain types (IDs, enums, value objects) leak across bounded-context boundaries.
Method: Cross-context domain-type leakage via Roslyn structural classification (strongly-typed IDs / value objects) over every public surface. Exhaustive, deterministic, type-level aggregate-boundary check.
Coverage: Bounded contexts derived from NAMESPACE prefix (or graph-inferred where available); cross-boundary domain-type leakage then checked exhaustively over every public member of every type.
What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).
Method: Every inline C# comment compared word by word with the identifiers, literals and constructs of the code it annotates (taken from the syntax); a comment whose words that code already contains is redundant, as are closing-brace labels and generator template text. Comments giving a reason or a reference are kept; other scripts and languages are not judged. Deterministic, exhaustive, advisory.
7 of 36 build units (Composer, npm) flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesion · ×7databox/api/composer.json:1
What to do
Resolve the 7 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with composer.json (4), package.json (3). — One of this dimension's main actionable groups (7 recommendation-level).
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
18 % of calls cross a namespace and 0 % go through an interface, but 94 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated. Measured over the .php source only — this repository's .tsx was not sampled for call sites, so this score covers part of the tree, not all of it.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: REDACTED scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
34 finding(s): 0 critical, 34 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
REDACTED
REDACTED
REDACTED
What to do
Resolve the 26 REDACTED finding(s) in Secrets (history) — start with REDACTED (15), REDACTED (7), REDACTED. — One of this dimension's main actionable groups (26 issue-level).
Resolve the 8 High secret finding(s) in Secrets (history) — start with REDACTED (5), REDACTED (3). — One of this dimension's main actionable groups (8 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).
110 finding(s): 0 critical, 81 high, 18 medium, 11 low. 40 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 1409 file(s) — `bin/dev/multipart-upload.sh` (line 20, line 23), `configurator/src/Command/ConfigureCommand.php` (line 18), `configurator/src/Command/Migration20230807Command.php` (line 19, line 20, line 21, …), `configurator/src/Command/SynchronizeCommand.php` (line 19, line 20), `configurator/src/Configurator/Configurator.php` (line 13), … (+1404 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 4 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 16 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 15 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4), REDACTED (3), REDACTED (3). — One of this dimension's main actionable groups (15 issue-level).
Resolve the 14 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (13), REDACTED. — One of this dimension's main actionable groups (14 issue-level).
No action in Static Analysis (SAST) — all 40 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 (40 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 12 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (12). — One of this dimension's main actionable groups (12 warning-level).
Resolve the 6 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (6). — One of this dimension's main actionable groups (6 issue-level).
Resolve the 4 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (4). — One of this dimension's main actionable groups (4 issue-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
Resolve the 37 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (30), REDACTED (7). — One of this dimension's main actionable groups (37 warning-level).
Resolve the 15 High IaC finding(s) in IaC & Container Security — start with REDACTED (13), REDACTED (2). — One of this dimension's main actionable groups (15 issue-level).
Resolve the 12 Low IaC finding(s) in IaC & Container Security — start with REDACTED (12). — One of this dimension's main actionable groups (12 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.
18 of 1097 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is lib/php/rendition-factory/src/Image/ColorspaceDetector.php. Counted over 1097 of the 3043 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 AssetInputMapper.php. — 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.
+ 4 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 4 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (4 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 — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
No dependency in any ecosystem this repository declares is published as malicious.
✓ On the Gold path — maintain.
Detailed fixes: d43_recommendation.md.
Do you agree with this assessment?
Frontend & cross-cutting dimensions
R = React/JS · M = Maturity · P = Readiness.
AC1 · Text alternatives5.3 / 10Adequate✓ Tool-verified
Other · Accessibility — Whether non-text content carries a text alternative — img/area/input[type=image] have alt, a meaningful svg has a title or aria-label, video has a captions track, and object/embed/canvas have a name or fallback content. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: every img/area/input[type=image] checked for alt, svg[role=img] for a title/aria-label, video for a captions <track>. Components skipped, spreads suppressed. Deterministic, hard fact per element.
Coverage: Population: image/media elements — img, area, input[type=image], svg, video, object, embed, canvas — across the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and dynamic-attribute elements are skipped. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is NOT read by any producer, so it contributes no element to this population; where such a frontend is present the card discloses it as an analyzer gap rather than scoring around it.
Video with no captions <track> offers no captions. This player's source is set at runtime, so there is no caption file to author here: give the player a way to carry captions — accept a track/captions URL alongside the media and render a <track kind="captions"> when one is supplied — and capture that asset wherever the media enters the product (upload, import or generation). — databox/client/src/features/clip/ClipEditorDialog.tsx:279
A <canvas> with no aria-label/title and no inner fallback content can't be described by assistive tech. Add a name or fallback content. (×3) — databox/client/src/features/clip/TimelineParts.tsx:107, databox/client/src/features/clip/VideoFilmstrip.tsx:176, databox/client/src/features/clip/frameCanvas.ts:77
What to do
Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
Do you agree with this assessment?
AC2 · Forms & labels4.6 / 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). (×2) — databox/client/src/components/form/CollectionTreePicker.tsx:264, databox/client/src/components/form/CollectionTreePicker.tsx:432
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. (×18) — databox/client/src/components/form/CollectionTreePicker.tsx:577, databox/client/src/components/form/FileOrUrlInput.tsx:101, databox/client/src/features/attributes/widgets/AttributeWidget.tsx:147, …
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. (×15) — databox/client/src/components/form/PrivacyField.tsx:86, databox/client/src/features/annotations/AnnotationToolbar.tsx:373, databox/client/src/features/attributes/widgets/AttributeWidget.tsx:285, …
This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label. (×2) — databox/client/src/components/form/TagsInput.tsx:142, databox/client/src/features/search/SearchBar.tsx:119
A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label. — databox/client/src/features/baskets/manage/BasketIntegrations.tsx:254
This UI-library field component has no label / aria-label / aria-labelledby / id, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id alone, wherever it is set, names nothing until a label points at it). The text inside it does not stand in for one: these compound APIs render a trigger with role="combobox" (or role="button"), and those roles take their name from the AUTHOR, not from their content — so the words on screen never reach the accessibility tree as a name. 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. (×2) — databox/client/src/features/profiles/manage/ProfileFiltersTab.tsx:160, databox/client/src/features/saved-searches/SavedSearchPrivacyField.tsx:50
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.
Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one. (×2) — databox/api/templates/admin/integration_help.html.twig:27, REDACTED:225
A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>. — databox/api/templates/terms/terms_pdf.html.twig:2
No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. (×3) — databox/api/templates/terms/terms_pdf.html.twig:2, expose/api/templates/base.html.twig:2, REDACTED:2
The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). (×3) — expose/api/templates/base.html.twig:2, expose/iframe.html:1, REDACTED:2
An iframe with no title (or an empty one) is announced only as "frame". Add a non-empty title describing its content, or an aria-label. — expose/iframe.html:12
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".
This <div> binds mousedown, touchstart and double-click — pointer gestures with no keyboard form, a double-click among them. No click, no key handler, and no tabIndex={0}, so it cannot even take focus. Nothing synthesises a double-click from the keyboard: Enter and Space fire a single click, and only on a native <button> or <a href>. So this behaviour has no keyboard path at all. Expose the same action on a real control, or add role + tabIndex={0} + a key handler alongside the double-click. — databox/client/src/components/ui/data-table/DataTable.tsx:520
A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler. (×3) — databox/client/src/features/annotations/AnnotationLayer.tsx:708, expose/client/src/features/player/AssetPlayer.tsx:132, expose/client/src/features/player/ZoomableImage.tsx:190
This <div> announces itself as a role="separator" and is operated by pointerdown, but nothing can put focus on it: no tabIndex={0}, no key handler, and nothing in its scripts moves focus. A keyboard cannot produce a pointer drag, so the control cannot be operated at all (WCAG 2.1.1). Give it tabIndex={0}="0" and move it with the arrow keys in a key handler (with aria-valuenow for the position it holds). — databox/client/src/features/attributes/batch/AttributeBatchEditorRoute.tsx:1236
A click handler on a plain element with no role and no tabindex: even where another element's key handler can reach it, assistive tech can neither focus it nor announce what it is. Use a <button>, or add role + tabIndex={0}. — expose/client/src/features/player/PdfViewer.tsx:302
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. — expose/client/src/features/publication/Lightbox.tsx:57
This <span> announces itself as a role="button" and binds a click, but nothing can put focus on it: no tabIndex={0} in any spelling, no key handler, and nothing in this file moves focus or sets aria-activedescendant. The role tells assistive tech what the control IS; it does not make the control reachable, so a keyboard user cannot operate it at all (WCAG 2.1.1). Give it tabIndex={0}="0" and an Enter/Space key handler, or make it a native <button>. If a parent widget owns the keyboard model, that parent must move focus onto the active role="button" or point aria-activedescendant at it. — lib/js/next-ui/src/form/AsyncCombobox.tsx:260
A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler. — lib/php/admin-bundle/Resources/views/list/id.html.twig:2
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.
<a> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2). — dashboard/client/src/features/dashboard/ServiceCardView.tsx:136
<textarea> takes keyboard focus, and outline:none/0 in its inline style removes the focus ring with no chance of a :focus replacement (an inline style outranks every stylesheet rule). Keep a visible focus indicator. — databox/client/src/features/annotations/TextEditor.tsx:73
<button> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2). (×2) — databox/client/src/features/integrations/config/pickers/SecretReferencePicker.tsx:230, databox/client/src/features/share/ShareGallery.tsx:229
<input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2). — databox/client/src/features/theme/ThemeEditorScreen.tsx:804
<span> moves — its `animate-ping` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:. — databox/client/src/features/workflows/jobStatus.tsx:85
What to do
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether 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.
Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').
Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.
`AttributeTypeInterface` declares 24 methods: `getElasticSearchType`, `getElasticSearchTextSubField`, `getElasticSearchSearchType`, `getAdditionalSubFields`, `getElasticSearchRawField`, `getElasticSearchSortSubField`, `supportsElasticSearchFuzziness`, `getFacetType`, `supportsAggregation`, `getElasticSearchMapping`, `normalizeValue`, `convertToDbValue`, `denormalizeValue`, `normalizeElasticsearchValue`, `getStringValue`, `getGroupValueLabel`, `isMappingLocaleAware`, `isLocaleAware`, `supportsSuggest`, `supportsTranslations`, `validate`, `getAggregationField`, `normalizeBuckets`, `isListed`. Counted over its public instance methods, once per name; constants and static methods are not counted. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — databox/api/src/Attribute/Type/AttributeTypeInterface.php:10
What to do
Split fat interfaces into focused role-interfaces so clients depend only on what they use.
Other · Architecture — Whether feature slices stay independent (no direct cross-slice references) — the discipline that makes vertical-slice architecture pay off.
Method: Roslyn scan (vertical-slice gated): feature slices resolved from namespaces (.Features.*, .Slices.*) or project names; cross-slice type references detected. Deterministic, traceable.
`DashboardScreen` (slice 'dashboard') depends on `useServiceStatuses` from slice 'status'. — dashboard/client/src/features/dashboard/DashboardScreen.tsx:34
`StatusIndicator` (slice 'dashboard') depends on `ServiceStatus` from slice 'status'. — dashboard/client/src/features/dashboard/ServiceCardView.tsx:63
`labelAttributeAnnotations` (slice 'annotations') depends on `FormatContext` from slice 'attributes'. — databox/client/src/features/annotations/assetAnnotations.ts:21
`labelAttributeAnnotations` (slice 'annotations') depends on `formatAttributeString` from slice 'attributes'. — databox/client/src/features/annotations/assetAnnotations.ts:29
`ExportDialog` (slice 'assets') depends on `hasClip` from slice 'clip'. — databox/client/src/features/assets/actions/ExportDialog.tsx:54
`ExportDialog` (slice 'assets') depends on `effectiveClip` from slice 'clip'. — databox/client/src/features/assets/actions/ExportDialog.tsx:54
`ExportDialog` (slice 'assets') depends on `useCollectionStore` from slice 'collections'. — databox/client/src/features/assets/actions/ExportDialog.tsx:104
`ExportDialog` (slice 'assets') depends on `TermsContent` from slice 'share'. — databox/client/src/features/assets/actions/ExportDialog.tsx:214
`RestoreAssetsDialog` (slice 'assets') depends on `RestoreCollectionDialog` from slice 'collections'. — databox/client/src/features/assets/actions/RestoreAssetsDialog.tsx:117
`useAssetActions` (slice 'assets') depends on `useAddToCurrentBasket` from slice 'baskets'. — databox/client/src/features/assets/actions/useAssetActions.tsx:147
`useAssetActions` (slice 'assets') depends on `useOptionalResults` from slice 'search'. — databox/client/src/features/assets/actions/useAssetActions.tsx:149
`useAssetActions` (slice 'assets') depends on `usePinnedStoriesStore` from slice 'stories'. — databox/client/src/features/assets/actions/useAssetActions.tsx:151
`useAssetActions` (slice 'assets') depends on `useSimilarSearch` from slice 'search'. — databox/client/src/features/assets/actions/useAssetActions.tsx:153
`useAssetActions` (slice 'assets') depends on `ShareDialog` from slice 'share'. — databox/client/src/features/assets/actions/useAssetActions.tsx:373
`useAssetActions` (slice 'assets') depends on `isClipApplicable` from slice 'clip'. — databox/client/src/features/assets/actions/useAssetActions.tsx:452
`AssetListProps` (slice 'assets') depends on `LayoutMode` from slice 'preferences'. — databox/client/src/features/assets/list/AssetList.tsx:30
`AssetList` (slice 'assets') depends on `DragScopeProvider` from slice 'dnd'. — databox/client/src/features/assets/list/AssetList.tsx:134
`AssetThumb` (slice 'assets') depends on `useDisplayPreferences` from slice 'preferences'. — databox/client/src/features/assets/list/AssetThumb.tsx:72
`AssetThumb` (slice 'assets') depends on `clipForFile` from slice 'clip'. — databox/client/src/features/assets/list/AssetThumb.tsx:86
`AssetThumb` (slice 'assets') depends on `effectiveClip` from slice 'clip'. — databox/client/src/features/assets/list/AssetThumb.tsx:86
`AssetThumb` (slice 'assets') depends on `useClipPlayback` from slice 'clip'. — databox/client/src/features/assets/list/AssetThumb.tsx:105
`AssetThumb` (slice 'assets') depends on `cropAspect` from slice 'clip'. — databox/client/src/features/assets/list/AssetThumb.tsx:127
`AssetThumb` (slice 'assets') depends on `ClipFrame` from slice 'clip'. — databox/client/src/features/assets/list/AssetThumb.tsx:243
`SelectableCard` (slice 'assets') depends on `useAssetDrag` from slice 'dnd'. — databox/client/src/features/assets/list/SelectableCard.tsx:44
`GroupLabel` (slice 'assets') depends on `useFormatContext` from slice 'attributes'. — databox/client/src/features/assets/list/layouts/Dividers.tsx:91
`GroupLabel` (slice 'assets') depends on `useAttributeFormats` from slice 'attributes'. — databox/client/src/features/assets/list/layouts/Dividers.tsx:92
`GroupLabel` (slice 'assets') depends on `useDefinitionBySearchSlug` from slice 'attributes'. — databox/client/src/features/assets/list/layouts/Dividers.tsx:93
`GroupLabel` (slice 'assets') depends on `getAttributeType` from slice 'attributes'. — databox/client/src/features/assets/list/layouts/Dividers.tsx:94
`useGridProfileItems` (slice 'assets') depends on `useProfileStore` from slice 'profiles'. — databox/client/src/features/assets/list/layouts/GridCardZones.tsx:47
`GridCardZones` (slice 'assets') depends on `useDefinitionsById` from slice 'attributes'. — databox/client/src/features/assets/list/layouts/GridCardZones.tsx:104
`GridCardZones` (slice 'assets') depends on `useAttributeFormats` from slice 'attributes'. — databox/client/src/features/assets/list/layouts/GridCardZones.tsx:105
`GridCardZones` (slice 'assets') depends on `groupAttributes` from slice 'attributes'. — databox/client/src/features/assets/list/layouts/GridCardZones.tsx:108
`GridCardZones` (slice 'assets') depends on `builtInValueResolvers` from slice 'attributes'. — databox/client/src/features/assets/list/layouts/GridCardZones.tsx:129
`GridCardZones` (slice 'assets') depends on `BuiltInAttribute` from slice 'search'. — databox/client/src/features/assets/list/layouts/GridCardZones.tsx:129
`GridCardZones` (slice 'assets') depends on `builtInTypes` from slice 'attributes'. — databox/client/src/features/assets/list/layouts/GridCardZones.tsx:142
`GridCardZones` (slice 'assets') depends on `getAttributeType` from slice 'attributes'. — databox/client/src/features/assets/list/layouts/GridCardZones.tsx:145
`GridItem` (slice 'assets') depends on `useOptionalSearch` from slice 'search'. — databox/client/src/features/assets/list/layouts/GridLayout.tsx:107
`ListItem` (slice 'assets') depends on `AttributeList` from slice 'attributes'. — databox/client/src/features/assets/list/layouts/ListLayout.tsx:272
`AssetPreview` (slice 'assets') depends on `useDisplayPreferences` from slice 'preferences'. — databox/client/src/features/assets/list/preview/AssetPreview.tsx:24
`AssetPreview` (slice 'assets') depends on `effectiveClip` from slice 'clip'. — databox/client/src/features/assets/list/preview/AssetPreview.tsx:47
What to do
Keep slices independent: share cross-slice needs via an explicit contract/shared-kernel, not direct references between slices.
Do you agree with this assessment?
AX8 · Test isolation7.5 / 10Strong✓ Tool-verified
Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.
Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.
`api (databox/api)` (production) references the test project `alchemy/test-bundle`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
What to do
Remove every production → test project reference: extract any shared test helper into a production support library (which the tests reference), or invert the dependency so the test project depends on production — not the reverse.
Do you agree with this assessment?
C1 · Data Protection6.5 / 10Adequate✓ 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.
No in-app HTTPS enforcement, but trusted proxies are configured (TrustProxies $proxies / trustProxies(at: …) / setTrustedProxies) — a reverse-proxy topology, where forcing HTTPS in the app would be wrong. Verify the reverse proxy enforces TLS. — databox/api/public/index.php:19
What to do
Strengthen data-at-rest protection: vault your keys (AWS KMS / Secrets Manager, GCP KMS / REDACTED Manager, HashiCorp Vault — not only APP_KEY in REDACTED) and encrypt the most sensitive columns (Eloquent 'encrypted' casts, CipherSweet) — partial coverage still leaves gaps.
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.
Do you agree with this assessment?
C3 · Audit Trail10.0 / 10Exemplary✓ Tool-verified
Other · Security — Whether changes to sensitive data are recorded (who, what, when) for compliance + incident response.
C4 · Data Retention10.0 / 10Exemplary✓ Tool-verified
Other · Security — Whether data has a defined lifetime — retention periods, TTLs, cleanup jobs (storage limitation).
Method: Roslyn scan: retention/TTL configuration presence in schema; CascadeDelete detected but not scored as retention control. Deterministic, gated by PII presence.
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.
`AssetOutput` references the aggregate root `Thread` directly (via `thread`) — hold its `ThreadId` instead.
`AssetOutput` references the aggregate root `Collection` directly (via `storyCollection`) — hold its `CollectionId` instead.
`AssetOutput` references the aggregate root `File` directly (via `source`) — hold its `FileId` instead.
`AssetOutput` references the aggregate root `AssetRendition` directly (via `main`) — hold its `AssetRenditionId` instead.
`AssetOutput` references the aggregate root `AssetRendition` directly (via `preview`) — hold its `AssetRenditionId` instead.
`AssetOutput` references the aggregate root `AssetRendition` directly (via `thumbnail`) — hold its `AssetRenditionId` instead.
`AssetOutput` references the aggregate root `AssetRendition` directly (via `animatedThumbnail`) — hold its `AssetRenditionId` instead.
`AutomationRun` references the aggregate root `SavedSearchAutomation` directly (via `automation`) — hold its `SavedSearchAutomationId` instead.
`AutomationSeenAsset` references the aggregate root `SavedSearchAutomation` directly (via `automation`) — hold its `SavedSearchAutomationId` instead.
`AutomationSeenAsset` references the aggregate root `Asset` directly (via `asset`) — hold its `AssetId` instead.
`AutomationShare` references the aggregate root `SavedSearchAutomation` directly (via `automation`) — hold its `SavedSearchAutomationId` instead.
`AutomationShare` references the aggregate root `Workspace` directly (via `workspace`) — hold its `WorkspaceId` instead.
`AutomationShare` references the aggregate root `Share` directly (via `share`) — hold its `ShareId` instead.
`SavedSearchAutomation` references the aggregate root `SavedSearch` directly (via `savedSearch`) — hold its `SavedSearchId` instead.
`SavedSearchAutomation` references the aggregate root `Workspace` directly (via `workspace`) — hold its `WorkspaceId` instead.
`BasketAsset` references the aggregate root `Basket` directly (via `basket`) — hold its `BasketId` instead.
`BasketAsset` references the aggregate root `Asset` directly (via `asset`) — hold its `AssetId` instead.
`Asset` references the aggregate root `Collection` directly (via `storyCollection`) — hold its `CollectionId` instead.
`Asset` references the aggregate root `Collection` directly (via `referenceCollection`) — hold its `CollectionId` instead.
`Asset` references the aggregate root `File` directly (via `source`) — hold its `FileId` instead.
`AssetAttachment` references the aggregate root `Asset` directly (via `asset`) — hold its `AssetId` instead.
`AssetAttachment` references the aggregate root `Asset` directly (via `attachment`) — hold its `AssetId` instead.
`AssetEmbedding` references the aggregate root `Asset` directly (via `asset`) — hold its `AssetId` instead.
`AssetFileVersion` references the aggregate root `Asset` directly (via `asset`) — hold its `AssetId` instead.
`AssetFileVersion` references the aggregate root `File` directly (via `file`) — hold its `FileId` instead.
`AssetImport` references the aggregate root `Workspace` directly (via `workspace`) — hold its `WorkspaceId` instead.
`AssetImport` references the aggregate root `Collection` directly (via `collection`) — hold its `CollectionId` instead.
`AssetImport` references the aggregate root `WorkspaceIntegration` directly (via `integration`) — hold its `WorkspaceIntegrationId` instead.
`AssetImportError` references the aggregate root `AssetImport` directly (via `import`) — hold its `AssetImportId` instead.
`AssetPolicyDependency` references the aggregate root `AssetPolicy` directly (via `policy`) — hold its `AssetPolicyId` instead.
`AssetPolicyUser` references the aggregate root `AssetPolicy` directly (via `policy`) — hold its `AssetPolicyId` instead.
`AssetRelationship` references the aggregate root `Asset` directly (via `source`) — hold its `AssetId` instead.
`AssetRelationship` references the aggregate root `File` directly (via `sourceFile`) — hold its `FileId` instead.
`AssetRelationship` references the aggregate root `WorkspaceIntegration` directly (via `integration`) — hold its `WorkspaceIntegrationId` instead.
`AssetRelationship` references the aggregate root `Asset` directly (via `target`) — hold its `AssetId` instead.
`AssetRendition` references the aggregate root `RenditionDefinition` directly (via `definition`) — hold its `RenditionDefinitionId` instead.
`AssetRendition` references the aggregate root `Asset` directly (via `asset`) — hold its `AssetId` instead.
`AssetRendition` references the aggregate root `File` directly (via `file`) — hold its `FileId` instead.
`Attribute` references the aggregate root `Asset` directly (via `asset`) — hold its `AssetId` instead.
`Attribute` references the aggregate root `AttributeDefinition` directly (via `definition`) — hold its `AttributeDefinitionId` instead.
What to do
Reference other aggregates by their strongly-typed id, never by object reference, so each aggregate stays an independent consistency boundary.
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.
`AutomationSeenAsset`'s public constructor takes `runId` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `AutomationSeenAsset` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — databox/api/src/Entity/Automation/AutomationSeenAsset.php:38
`Asset`'s public constructor takes `now`, `sequence` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `Asset` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — databox/api/src/Entity/Core/Asset.php:619
`AssetImportError`'s public constructor takes `line`, `key`, `message` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `AssetImportError` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — databox/api/src/Entity/Core/AssetImportError.php:73
`FileAnalysis`'s public constructor takes `status` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `FileAnalysis` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — databox/api/src/Entity/Core/FileAnalysis.php:46
`Broadcast`'s public constructor takes `topic`, `directory` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `Broadcast` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — lib/php/notifier-bundle/src/Entity/Broadcast.php:86
`Notification`'s public constructor takes `topic` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `Notification` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — lib/php/notifier-bundle/src/Entity/Notification.php:47
`NotificationPreference`'s public constructor takes `topic` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `NotificationPreference` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — lib/php/notifier-bundle/src/Entity/NotificationPreference.php:38
`Subscriber`'s public constructor takes `userId` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `Subscriber` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — lib/php/notifier-bundle/src/Entity/Subscriber.php:41
`JobState`'s public constructor takes `id`, `jobId` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `JobState` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — lib/php/workflow-bundle/Entity/JobState.php:41
`WorkflowState`'s public constructor takes `id` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `WorkflowState` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — lib/php/workflow-bundle/Entity/WorkflowState.php:39
`Job`'s public constructor takes `id` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `Job` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — lib/php/workflow/src/Model/Job.php:26
`Step`'s public constructor takes `id`, `name` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `Step` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — lib/php/workflow/src/Model/Step.php:16
What to do
Give each aggregate one way in that can refuse — a guarded constructor, value-object parameters that validate themselves, or a private constructor behind a factory that returns a failure.
Other · Domain Modelling — How much of the domain uses strongly-typed ids vs raw Guid/string/int — adoption curve, not all-or-nothing.
Method: Roslyn (DDD-gated): strongly-typed id adoption on domain entities/events; raw Guid/int/string ids counted versus wrapped types. An id wrapper is recognised by VALUE SEMANTICS, not by being a struct — a record struct, a record class (`record ApartmentId(Guid Value)`) or a class declared by a typed-id base (`class MemberId : TypedIdValueBase`) all count, while a plain mutable class (reference equality) and a verb-phrase query record (`GetCustomerById`) do not. Deterministic, adoption percentage.
Coverage: Population: id-like members by *Id/*Key NAME suffix; strongly-typed-ID shape then checked semantically — non-suffixed identifiers are not seen.
`AssetOutput.threadKey` is a raw `string` — give it a strongly-typed id: a dedicated single-field type wrapping the `string`, in whatever form your language spells that.
`AssetOutput.trackingId` is a raw `string` — give it a strongly-typed id: a dedicated single-field type wrapping the `string`, in whatever form your language spells that.
`AssetOutput.externalId` is a raw `string` — give it a strongly-typed id: a dedicated single-field type wrapping the `string`, in whatever form your language spells that.
`AssetOutput.resolvedTrackingId` is a raw `string` — give it a strongly-typed id: a dedicated single-field type wrapping the `string`, in whatever form your language spells that.
What to do
Adopt strongly-typed ids across the domain — finish the migration or document the boundary; primitive ids invite transposed-argument bugs.
Do you agree with this assessment?
DM4 · Rich vs anemic model9.6 / 10Exemplary✓ 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.
`AutomationSeenAsset` 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. — databox/api/src/Entity/Automation/AutomationSeenAsset.php:18
`AutomationShare` 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. — databox/api/src/Entity/Automation/AutomationShare.php:19
`AssetImportError` 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. — databox/api/src/Entity/Core/AssetImportError.php:21
`NotificationDigest` is an aggregate/entity with 7 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — lib/php/notifier-bundle/src/Entity/NotificationDigest.php:22
`Subscription` 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. — lib/php/notifier-bundle/src/Entity/Subscription.php:16
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.
`AssetOutput` exposes publicly writable state (attachments, thread, threadKey, deleted, storyCollection, owner, and 10 more). — databox/api/src/Api/Model/Output/AssetOutput.php:25
`OperationTask` exposes publicly writable state (owner). — databox/api/src/Entity/Admin/OperationTask.php:27
`Asset` exposes publicly writable state (name, groupValue, attributesIndex). — databox/api/src/Entity/Core/Asset.php:102
`AssetExport` exposes publicly writable state (downloadUrl, owner). — databox/api/src/Entity/Core/AssetExport.php:25
`Attribute` exposes publicly writable state (batchUpdate). — databox/api/src/Entity/Core/Attribute.php:32
`File` exposes publicly writable state (localTmpPath). — databox/api/src/Entity/Core/File.php:23
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 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 repository and its projects have a README, and whether it is substantive.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
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.
`README.md` draws the system's parts, and the drawing no longer matches the code: it leaves out `dashboard-client`, `dev`, which the repository has beside the units it does draw. A diagram of a system that no longer exists misleads the reader it was drawn for, so it is not credited as documenting the shape. — README.md:83
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.
Update README.md so it draws the parts the code has today: add dashboard-client, dev.
Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.
Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.
Readiness · Readiness — Whether an automated pipeline builds and tests every change.
Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.
Do you agree with this assessment?
P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged
Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.
Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language's code model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.
Do you agree with this assessment?
P2 · Observability6.1 / 10Adequate✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
Only 16/23 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `dashboard/client`, `databox/client`, `expose/client`, `lib/js/next-core`, `lib/js/next-theme` and 2 more.
`databox/indexer/src/configLoader.ts` reports through `console.*` at line 110 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — databox/indexer/src/configLoader.ts:110
`databox/indexer/src/env.ts` reports through `console.*` at line 5 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — databox/indexer/src/env.ts:5
`databox/indexer/src/eventHandler.ts` reports through `console.*` at line 28 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — databox/indexer/src/eventHandler.ts:28
`databox/indexer/src/eventHandler.ts` reports through `console.*` at line 45 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — databox/indexer/src/eventHandler.ts:45
`databox/indexer/src/init.ts` reports through `console.*` at line 8 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — databox/indexer/src/init.ts:8
`databox/indexer/src/init.ts` reports through `console.*` at line 11 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — databox/indexer/src/init.ts:11
`databox/indexer/src/shutdown.ts` reports through `console.*` at line 40 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — databox/indexer/src/shutdown.ts:40
`databox/indexer/src/shutdown.ts` reports through `console.*` at line 47 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — databox/indexer/src/shutdown.ts:47
`databox/indexer/src/shutdown.ts` reports through `console.*` at line 56 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — databox/indexer/src/shutdown.ts:56
`databox/indexer/src/shutdown.ts` reports through `console.*` at line 64 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — databox/indexer/src/shutdown.ts:64
`databox/indexer/src/command/list.ts` reports through `console.*` at line 9 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — databox/indexer/src/command/list.ts:9
`databox/indexer/src/command/list.ts` reports through `console.*` at line 11 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — databox/indexer/src/command/list.ts:11
What to do
Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
Route service-code `console.*` output through the module's structured logger (with named fields), so delivery outcomes and failures reach the log pipeline with a level.
Add a health-check endpoint (Laravel's /up health route or a /health route) so orchestrators and load balancers can probe liveness/readiness.
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 8 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:9
`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:16
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.
What to do
Add an approval/environment gate (required reviewers / protection rules) before production promotion.
Do you agree with this assessment?
P5 · DR & Backup7.0 / 10Strong✓ Tool-verified
Readiness · Readiness — Whether disaster recovery is planned and codified — backups, geo-recovery, RTO/RPO, persistence guarantees — from IaC + container manifests + docs, never the live cloud.
Method: Filesystem scan: disaster recovery, backup, geo-recovery, RTO/RPO, persistence guarantees from IaC, manifests, and docs. Exhaustive, deterministic, never a live environment.
What to do
Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery).
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.
No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
Readiness · Readiness — Whether outbound HTTP calls are wrapped in resilience (retry/timeout/circuit-breaker) so a failing dependency doesn't cascade.
Method: Source scan: outbound HTTP clients and what bounds them — resilience handlers (Polly, AddStandardResilienceHandler) on .NET; on Go, the JVM, Python, JavaScript/TypeScript, Ruby, PHP, Rust, Elixir, Swift, Dart and Erlang, a timeout, deadline, retry or breaker beside each call, or a process-wide client default (a framework-wide deadline such as Drupal core's, Laravel's or actix's awc counts). Exhaustive, deterministic.
`->request(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. (×40) — databox/api/src/Border/UploaderClient.php:28, databox/api/src/Border/UploaderClient.php:39, databox/api/src/Border/UriDownloader.php:34, …
What to do
Give every client an explicit bound: `new Client(['timeout' => 10, 'connect_timeout' => 3])` for Guzzle (whose default is to wait forever), `CURLOPT_TIMEOUT`/`CURLOPT_CONNECTTIMEOUT` before `curl_exec`, `timeout`/`max_duration` on Symfony HttpClient (or `framework.http_client.default_options`), and a stream-context `timeout` or `connection_timeout` for `file_get_contents`/`SoapClient`. In Drupal, use the `http_client` service, which carries core's site-wide timeout, rather than `new Client()`. Add retries with back-off (Guzzle `Middleware::retry`, Symfony `RetryableHttpClient`, Laravel `->retry()`) around dependencies that fail.
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.
`fs.existsSync` in `anonymous function` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — databox/indexer/src/handlers/fs/server.ts:16
`fs.readFileSync` in `anonymous function` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — databox/indexer/src/handlers/phraseanet/indexer.ts:219
`fs.writeFileSync` in `anonymous function` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — databox/indexer/src/handlers/phraseanet/indexer.ts:283, databox/indexer/src/handlers/phraseanet/indexer.ts:444
What to do
TypeScript/JavaScript: use the promise APIs (fs/promises, a promisified child_process.execFile, the async zlib/crypto functions) and await them instead of the *Sync variants.
Do you agree with this assessment?
R1 · Type Safety9.5 / 10Exemplary✓ Tool-verified
React / JS · Code Health — How much of the frontend is typed TypeScript vs untyped JavaScript.
Method: Frontend file inventory: the share of typed TypeScript vs untyped JavaScript across the source tree. Deterministic, exhaustive over frontend files.
React / JS · Code Health — The share of the scored frontend lines inside a near-exact copy-pasted block of substantial extent (the D4 clone algorithm over JS/TS tokens, D-386; each line once, 10 at none and 0 at a quarter of the lines, as D4): a block is reported only where its copies still agree on most of their own identifiers and literals, or were renamed as they were pasted but kept most of their constants, and where the copies carry enough code to stand on their own or the copied extent reaches 30 lines — so a re-implementation sharing neither names nor values, and a small pasted declaration, are both found and deliberately not reported, and a clean R10 is not a claim that nothing was copied.
Method: Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm run over JS/TS tokens). Masking finds the candidates; a block is reported when its copies still agree on most of their own identifiers and literals, or when a renamed copy still agrees on most of its constants, AND the copies carry enough code to stand on their own — or when the copied extent reaches 30 lines. So a re-implementation sharing neither names nor values, and a small pasted declaration, are deliberately not counted. Scored on the share of the scored frontend lines inside a reported copy, on the same curve as D4. Deterministic.
84 duplicated blocks under the repository root have copies in at least two of the sibling directories dashboard, databox, expose, lib, uploader — 57 of them are reported below, and 27 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 84 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 84 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 84 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. — databox/client/src/lib/api/http.ts:1
82 duplicated blocks under databox/client/src/features/ have copies in at least two of the sibling directories attributes, audit-log, baskets, clip, collections, discussion (+19 more sibling(s) not listed) — 37 of them are reported below, and 45 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 82 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 82 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 82 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. — databox/client/src/features/baskets/manage/BasketManageRoute.tsx:117
14 duplicated blocks under databox/client/src/ have copies in at least two of the sibling directories components, features, hooks, lib — 5 of them are reported below, and 9 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 14 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 14 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 14 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. — databox/client/src/features/annotations/AnnotationsProvider.tsx:221
8 duplicated blocks under databox/client/src/features/workspaces/manage/ have copies in at least two of the sibling directories entities, tabs — 3 of them are reported below, and 5 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 8 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 8 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 8 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. — databox/client/src/features/workspaces/manage/entities/EntityListsTab.tsx:26
databox/client/src/features/workspaces/manage/tabs/AttributeDefinitionsTab.tsx:41 · databox/client/src/features/workspaces/manage/tabs/RenditionDefinitionsTab.tsx:35 — the two spans are one implementation copied and then locally edited — 1363 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. — databox/client/src/features/workspaces/manage/tabs/AttributeDefinitionsTab.tsx:41
databox/client/src/lib/api/http.ts:1 · expose/client/src/lib/api/http.ts:1 · uploader/client/src/lib/api/http.ts:1 — these 3 files are line-for-line copies of one another — 160 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. — databox/client/src/lib/api/http.ts:1
databox/client/src/features/collections/tree/CollectionsPanel.tsx:275 · databox/client/src/features/collections/tree/CollectionsPanel.tsx:508 — the two spans are one implementation copied and then locally edited — 720 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — databox/client/src/features/collections/tree/CollectionsPanel.tsx:275
databox/client/src/components/form/code/CodeEditor.tsx:15 · uploader/client/src/components/form/code/CodeEditor.tsx:10 — the two spans are one implementation copied and then locally edited — 590 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. — databox/client/src/components/form/code/CodeEditor.tsx:15
databox/client/src/features/integrations/config/pickers/CreateSecretDialog.tsx:100 · databox/client/src/features/integrations/config/pickers/VariableDialog.tsx:52 — the two spans are one implementation copied and then locally edited — 774 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. — databox/client/src/features/integrations/config/pickers/CreateSecretDialog.tsx:100
databox/client/src/features/baskets/manage/BasketManageRoute.tsx:117 · databox/client/src/features/saved-searches/manage/SavedSearchManageRoute.tsx:94 — the two spans are one implementation copied and then locally edited — 586 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. — databox/client/src/features/baskets/manage/BasketManageRoute.tsx:117
databox/client/src/features/integrations/config/pickers/AttributePicker.tsx:24 · databox/client/src/features/integrations/config/pickers/RenditionPicker.tsx:13 — the two spans are one implementation copied and then locally edited — 406 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — databox/client/src/features/integrations/config/pickers/AttributePicker.tsx:24
databox/client/src/lib/utils/format.ts:2 · expose/client/src/lib/utils/format.ts:2 — these 2 files are line-for-line copies of one another — 82 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. — databox/client/src/lib/utils/format.ts:2
dashboard/client/src/lib/auth/AuthProvider.tsx:11 · expose/client/src/lib/auth/AuthProvider.tsx:11 · uploader/client/src/lib/auth/AuthProvider.tsx:11 — these 3 files are line-for-line copies of one another — 80 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. — dashboard/client/src/lib/auth/AuthProvider.tsx:11
databox/client/src/lib/auth/AuthProvider.tsx:61 · expose/client/src/lib/auth/AuthProvider.tsx:32 — the two spans are one implementation copied and then locally edited — 449 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. — databox/client/src/lib/auth/AuthProvider.tsx:61
databox/client/src/features/workspaces/manage/tabs/RenditionDefinitionsTab.tsx:53 · databox/client/src/features/workspaces/manage/tabs/TagManagerTab.tsx:35 — the two spans are one implementation copied and then locally edited — 384 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. — databox/client/src/features/workspaces/manage/tabs/RenditionDefinitionsTab.tsx:53
databox/client/src/features/workspaces/manage/tabs/AssetPoliciesTab.tsx:335 · databox/client/src/features/workspaces/manage/tabs/AssetPoliciesTab.tsx:447 — the two spans are one implementation copied and then locally edited — 300 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — databox/client/src/features/workspaces/manage/tabs/AssetPoliciesTab.tsx:335
expose/client/src/features/admin/AdminPublicationList.tsx:41 · expose/client/src/features/publications/PublicationList.tsx:32 — the two spans are one implementation copied and then locally edited — 334 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. — expose/client/src/features/admin/AdminPublicationList.tsx:41
expose/client/src/features/admin/ProfileEditScreen.tsx:47 · expose/client/src/features/admin/PublicationEditScreen.tsx:69 — the two spans are one implementation copied and then locally edited — 359 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. — expose/client/src/features/admin/ProfileEditScreen.tsx:47
databox/client/src/app/providers.tsx:3 · expose/client/src/app/providers.tsx:3 — these 2 files are line-for-line copies of one another — 59 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. — databox/client/src/app/providers.tsx:3
databox/client/src/app/providers.tsx:3 · uploader/client/src/app/providers.tsx:3 — these 2 files are line-for-line copies of one another — 59 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. — databox/client/src/app/providers.tsx:3
expose/client/src/app/providers.tsx:3 · uploader/client/src/app/providers.tsx:3 — these 2 files are line-for-line copies of one another — 59 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. — expose/client/src/app/providers.tsx:3
databox/client/src/lib/api/metadata.ts:231 · databox/client/src/lib/api/metadata.ts:363 — the two spans are one implementation copied and then locally edited — 301 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — databox/client/src/lib/api/metadata.ts:231
databox/client/src/lib/utils/locale.ts:7 · expose/client/src/lib/utils/locale.ts:7 · uploader/client/src/lib/utils/locale.ts:7 — the 3 copies are spread across 3 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — databox/client/src/lib/utils/locale.ts:7
dashboard/client/src/app/layout.tsx:18 · uploader/client/src/app/layout.tsx:17 — 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. — dashboard/client/src/app/layout.tsx:18
databox/client/src/app/layout.tsx:1 · expose/client/src/app/layout.tsx:1 — these 2 files are line-for-line copies of one another — 54 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. — databox/client/src/app/layout.tsx:1
uploader/client/src/features/admin/FormScreens.tsx:18 · uploader/client/src/features/admin/TargetDataScreens.tsx:17 — 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. — uploader/client/src/features/admin/FormScreens.tsx:18
dashboard/client/src/app/providers.tsx:3 · expose/client/src/app/providers.tsx:3 — these 2 files are line-for-line copies of one another — 51 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. — dashboard/client/src/app/providers.tsx:3
dashboard/client/src/app/providers.tsx:3 · uploader/client/src/app/providers.tsx:3 — these 2 files are line-for-line copies of one another — 51 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. — dashboard/client/src/app/providers.tsx:3
databox/client/src/lib/analytics/useContentTracking.ts:13 · expose/client/src/lib/analytics/useContentTracking.ts:13 — 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. — databox/client/src/lib/analytics/useContentTracking.ts:13
databox/client/src/lib/api/upload.ts:38 · uploader/client/src/lib/api/upload.ts:29 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — databox/client/src/lib/api/upload.ts:38
dashboard/client/src/lib/config/server.ts:74 · uploader/client/src/lib/config/server.ts:92 — the two spans are one implementation copied and then locally edited — 202 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. — dashboard/client/src/lib/config/server.ts:74
databox/client/src/components/form/CollectionTreePicker.tsx:267 · databox/client/src/components/form/CollectionTreePicker.tsx:439 — the two spans are one implementation copied and then locally edited — 152 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — databox/client/src/components/form/CollectionTreePicker.tsx:267
databox/client/src/features/workspaces/manage/PolicyForm.tsx:65 · databox/client/src/features/workspaces/manage/tabs/TagManagerTab.tsx:78 — the two spans are one implementation copied and then locally edited — 281 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. — databox/client/src/features/workspaces/manage/PolicyForm.tsx:65
databox/client/src/features/saved-searches/automations/actions/RemoteExportForm.tsx:136 · databox/client/src/features/saved-searches/automations/actions/ShareExportForm.tsx:260 — 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. — databox/client/src/features/saved-searches/automations/actions/RemoteExportForm.tsx:136
databox/client/src/features/workspaces/manage/tabs/AttributePoliciesTab.tsx:20 · databox/client/src/features/workspaces/manage/tabs/RenditionPoliciesTab.tsx:20 — 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. — databox/client/src/features/workspaces/manage/tabs/AttributePoliciesTab.tsx:20
dashboard/client/src/lib/auth/loginWindow.ts:26 · expose/client/src/lib/auth/loginWindow.ts:36 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — dashboard/client/src/lib/auth/loginWindow.ts:26
databox/client/src/lib/config/server.ts:5 · expose/client/src/lib/config/server.ts:5 — 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. — databox/client/src/lib/config/server.ts:5
lib/js/next-ui/src/ui/menu.tsx:108 · lib/js/next-ui/src/ui/menu.tsx:219 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — lib/js/next-ui/src/ui/menu.tsx:108
databox/client/src/lib/api/metadata.ts:73 · databox/client/src/lib/api/misc.ts:316 — 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. — databox/client/src/lib/api/metadata.ts:73
expose/client/src/features/admin/AdminPublicationList.tsx:66 · expose/client/src/features/admin/ProfileList.tsx:66 — 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. — expose/client/src/features/admin/AdminPublicationList.tsx:66
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.
expose/client/src/features/player/AudioPlayer.tsx:7 imports wavesurfer.js/dist/plugins/timeline.esm.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — expose/client/src/features/player/AudioPlayer.tsx:7
expose/client/src/features/player/AudioPlayer.tsx:8 imports wavesurfer.js/dist/plugins/zoom.esm.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — expose/client/src/features/player/AudioPlayer.tsx:8
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.
DefinitionManager has cyclomatic complexity 58 and cognitive complexity 45; 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. — databox/client/src/features/workspaces/manage/DefinitionManager.tsx:134
AttributeWidget has cyclomatic complexity 48 and cognitive complexity 45; 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. — databox/client/src/features/attributes/widgets/AttributeWidget.tsx:51
ClipEditorDialog has cyclomatic complexity 45 and cognitive complexity 43; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — databox/client/src/features/clip/ClipEditorDialog.tsx:81
IntegrationForm has cyclomatic complexity 44 and cognitive complexity 42; 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. — databox/client/src/features/integrations/manage/IntegrationManager.tsx:149
UploadDialog has cyclomatic complexity 43 and cognitive complexity 39; 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. — databox/client/src/features/upload/UploadDialog.tsx:89
DefinitionForm has cyclomatic complexity 42 and cognitive complexity 41; 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. — databox/client/src/features/workspaces/manage/tabs/AttributeDefinitionsTab.tsx:139
phraseanetIndexer has cyclomatic complexity 40 and cognitive complexity 103; 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. — databox/indexer/src/handlers/phraseanet/indexer.ts:41
AnnotationLayer has cyclomatic complexity 40 and cognitive complexity 33; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — databox/client/src/features/annotations/AnnotationLayer.tsx:105
onKeyDown has cyclomatic complexity 38 and cognitive complexity 32; 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. — databox/client/src/components/ui/data-table/DataTable.tsx:305
SecretReferencePicker has cyclomatic complexity 37 and cognitive complexity 29; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — databox/client/src/features/integrations/config/pickers/SecretReferencePicker.tsx:66
importSubdefsStructure has cyclomatic complexity 35 and cognitive complexity 74; 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. — databox/indexer/src/handlers/phraseanet/StructureImporter.ts:236
normalizeClientTheme has cyclomatic complexity 34 and cognitive complexity 43; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — lib/js/next-theme/src/customTheme.ts:409
UploadScreen has cyclomatic complexity 34 and cognitive complexity 31; 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. — uploader/client/src/features/upload/UploadScreen.tsx:114
criteria has cyclomatic complexity 33 and cognitive complexity 47; 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. — databox/client/src/features/search/aql/parser.ts:270
getOperatorLabel has cyclomatic complexity 33 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — databox/client/src/features/search/aql/operatorLabel.ts:11
tokenize has cyclomatic complexity 30 and cognitive complexity 55; 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. — databox/client/src/features/search/aql/parser.ts:55
ShareDialog has cyclomatic complexity 29 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 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. — databox/client/src/features/share/ShareDialog.tsx:116
computeBatchActions has cyclomatic complexity 28 and cognitive complexity 78; 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. — databox/client/src/features/attributes/editor/attributeEditorModel.ts:104
AutomationFormDialog has cyclomatic complexity 28 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — databox/client/src/features/saved-searches/automations/AutomationForm.tsx:94
onPointerDown has cyclomatic complexity 27 and cognitive complexity 30; 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. — databox/client/src/features/annotations/AnnotationLayer.tsx:311
ThemeEditorScreen has cyclomatic complexity 27 and cognitive complexity 26; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — databox/client/src/features/theme/ThemeEditorScreen.tsx:194
canDropAssets has cyclomatic complexity 26 and cognitive complexity 39; 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. — databox/client/src/features/dnd/canDrop.ts:71
AsyncCombobox has cyclomatic complexity 25 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — lib/js/next-ui/src/form/AsyncCombobox.tsx:91
MessageComposer has cyclomatic complexity 25 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — databox/client/src/features/discussion/MessageComposer.tsx:150
(anonymous) has cyclomatic complexity 25 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — lib/js/api/src/useRequestErrorHandler.ts:17
importStory has cyclomatic complexity 24 and cognitive complexity 41; 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. — databox/indexer/src/handlers/phraseanet/indexer.ts:488
validateValues has cyclomatic complexity 23 and cognitive complexity 47; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:369
TopBar has cyclomatic complexity 23 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — databox/client/src/components/layout/TopBar.tsx:65
ClipTimeline has cyclomatic complexity 23 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — databox/client/src/features/clip/ClipTimeline.tsx:75
FormBuilderEditor has cyclomatic complexity 23 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — uploader/client/src/features/admin/FormBuilderEditor.tsx:62
normalizeFonts has cyclomatic complexity 22 and cognitive complexity 32; 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. — lib/js/next-theme/src/customTheme.ts:512
HumanizedValue has cyclomatic complexity 22 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. — databox/client/src/features/search/conditions/SearchConditionChip.tsx:373
AttributeRow has cyclomatic complexity 22 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — databox/client/src/features/attributes/AttributeList.tsx:233
CollectionItem has cyclomatic complexity 22 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — databox/client/src/features/collections/tree/CollectionsPanel.tsx:502
InputFieldInspector has cyclomatic complexity 22 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — uploader/client/src/features/form-builder/editor/FieldInspector.tsx:107
FileTile has cyclomatic complexity 22 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — uploader/client/src/features/upload/FileTile.tsx:36
(anonymous) has cyclomatic complexity 21 and cognitive complexity 28; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — databox/client/src/features/attributes/AttributeList.tsx:89
useSearchSuggestions has cyclomatic complexity 21 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — databox/client/src/features/search/suggest/useSearchSuggestions.ts:36
importMetadataStructure has cyclomatic complexity 20 and cognitive complexity 37; 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. — databox/indexer/src/handlers/phraseanet/StructureImporter.ts:429
createAsset has cyclomatic complexity 20 and cognitive complexity 37; 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. — databox/indexer/src/handlers/phraseanet/shared.ts:140
Do you agree with this assessment?
R3 · Large Files7.0 / 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.
lib/js/core/src/mimeTypes.ts has 2089 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — lib/js/core/src/mimeTypes.ts:1
databox/client/src/features/attributes/batch/AttributeBatchEditorRoute.tsx has 1567 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — databox/client/src/features/attributes/batch/AttributeBatchEditorRoute.tsx:1
databox/client/src/types/api.ts has 1250 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — databox/client/src/types/api.ts:1
databox/client/src/features/map/AssetMap.tsx has 1194 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — databox/client/src/features/map/AssetMap.tsx:1
uploader/client/src/features/upload/UploadScreen.tsx has 1016 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — uploader/client/src/features/upload/UploadScreen.tsx:1
databox/client/src/features/search/conditions/ConditionBuilder.tsx has 931 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — databox/client/src/features/search/conditions/ConditionBuilder.tsx:1
databox/client/src/features/upload/UploadDialog.tsx has 922 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — databox/client/src/features/upload/UploadDialog.tsx:1
databox/client/src/features/annotations/AnnotationLayer.tsx has 876 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — databox/client/src/features/annotations/AnnotationLayer.tsx:1
databox/client/src/features/integrations/config/ConfigForm.tsx has 869 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — databox/client/src/features/integrations/config/ConfigForm.tsx:1
databox/client/src/features/share/ShareDialog.tsx has 866 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — databox/client/src/features/share/ShareDialog.tsx:1
databox/client/src/features/theme/ThemeEditorScreen.tsx has 846 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — databox/client/src/features/theme/ThemeEditorScreen.tsx:1
databox/indexer/src/handlers/phraseanet/StructureImporter.ts has 820 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — databox/indexer/src/handlers/phraseanet/StructureImporter.ts:1
databox/client/src/features/collections/tree/CollectionsPanel.tsx has 795 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — databox/client/src/features/collections/tree/CollectionsPanel.tsx:1
databox/client/src/components/form/selects.tsx has 765 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — databox/client/src/components/form/selects.tsx:1
databox/client/src/features/workspaces/manage/entities/EntityGrid.tsx has 756 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — databox/client/src/features/workspaces/manage/entities/EntityGrid.tsx:1
expose/client/src/features/admin/config/ConfigForm.tsx has 733 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — expose/client/src/features/admin/config/ConfigForm.tsx:1
databox/client/src/features/annotations/shapes.tsx has 722 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — databox/client/src/features/annotations/shapes.tsx:1
databox/client/src/features/operation-tasks/OperationTasksScreen.tsx has 721 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — databox/client/src/features/operation-tasks/OperationTasksScreen.tsx:1
databox/client/src/features/profiles/manage/ProfileGridTab.tsx has 712 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — databox/client/src/features/profiles/manage/ProfileGridTab.tsx:1
REDACTED has 698 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
databox/client/src/features/workspaces/manage/DefinitionManager.tsx has 692 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — databox/client/src/features/workspaces/manage/DefinitionManager.tsx:1
databox/indexer/src/handlers/phraseanet/indexer.ts has 690 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — databox/indexer/src/handlers/phraseanet/indexer.ts:1
databox/client/src/features/discussion/MessageComposer.tsx has 684 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — databox/client/src/features/discussion/MessageComposer.tsx:1
databox/client/src/lib/api/misc.ts has 674 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — databox/client/src/lib/api/misc.ts:1
databox/client/src/components/ui/data-table/DataTable.tsx has 669 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — databox/client/src/components/ui/data-table/DataTable.tsx:1
databox/client/src/features/clip/ClipEditorDialog.tsx has 653 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — databox/client/src/features/clip/ClipEditorDialog.tsx:1
lib/js/next-core/src/auth/oidc.ts has 642 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — lib/js/next-core/src/auth/oidc.ts:1
databox/client/src/features/search/pinned/PinnedFilters.tsx has 631 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — databox/client/src/features/search/pinned/PinnedFilters.tsx:1
databox/client/src/features/profiles/manage/ProfileAttributesTab.tsx has 594 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — databox/client/src/features/profiles/manage/ProfileAttributesTab.tsx:1
databox/client/src/features/saved-searches/automations/AutomationForm.tsx has 592 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — databox/client/src/features/saved-searches/automations/AutomationForm.tsx:1
databox/client/src/features/audit-log/AuditLogScreen.tsx has 580 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — databox/client/src/features/audit-log/AuditLogScreen.tsx:1
databox/client/src/lib/api/assets.ts has 578 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — databox/client/src/lib/api/assets.ts:1
databox/client/src/components/form/CollectionTreePicker.tsx has 577 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — databox/client/src/components/form/CollectionTreePicker.tsx:1
databox/client/src/features/workspaces/manage/tabs/AttributeDefinitionsTab.tsx has 577 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — databox/client/src/features/workspaces/manage/tabs/AttributeDefinitionsTab.tsx:1
databox/client/src/features/baskets/manage/BasketIntegrations.tsx has 576 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — databox/client/src/features/baskets/manage/BasketIntegrations.tsx:1
databox/client/src/features/workspaces/manage/tabs/AssetPoliciesTab.tsx has 574 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — databox/client/src/features/workspaces/manage/tabs/AssetPoliciesTab.tsx:1
lib/js/auth/src/client/OAuthClient.ts has 564 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — lib/js/auth/src/client/OAuthClient.ts:1
databox/client/src/features/search/aql/parser.ts has 554 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — databox/client/src/features/search/aql/parser.ts:1
lib/js/next-theme/src/customTheme.ts has 554 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — lib/js/next-theme/src/customTheme.ts:1
expose/client/src/features/player/PdfViewer.tsx has 550 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — expose/client/src/features/player/PdfViewer.tsx: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 Coverage5.9 / 10Adequate✓ Tool-verified
React / JS · Readiness — Static test reachability (D-386): the share of production files reachable from any test via the import graph — measured without running anything.
Method: Static test reachability: the share of production files reachable from any test via the import graph — measured without running anything. Deterministic.
No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×40) — databox/client/src/features/attributes/batch/AttributeBatchEditorRoute.tsx:1, databox/client/src/features/map/AssetMap.tsx:1, uploader/client/src/features/upload/UploadScreen.tsx:1, …
What to do
Add tests that import the unreached modules (directly or through their public entry).
Do you agree with this assessment?
R6 · Tooling10.0 / 10Exemplary✓ Tool-verified
React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each package.json script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.
Method: package.json scanned for test/lint/typecheck script wiring. Deterministic presence check.
`lib/js/auth` is TypeScript, but a type error in it cannot fail anything this repository runs: its `format` script (`prettier --ignore-path .gitignore --write "**/*.+(js|ts|json|cjs|tsx|jsx)"`) compiles TypeScript with a transpile-only tool that strips types without checking them, and no script, config or CI step of the package runs `tsc --noEmit` or another type checker over it. Add a type check that can fail — a `typecheck` script running `tsc --noEmit` (or `vue-tsc`/`svelte-check`) that CI or the workspace pipeline runs, or a build step that checks before it bundles. — lib/js/auth/package.json:16
The package in `dashboard/client` declares the lint script `lint` (`eslint src`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `dashboard/client` (or the workspace's task runner). — dashboard/client/package.json:11
The package in `databox/client` declares the lint script `lint` (`eslint src`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `databox/client` (or the workspace's task runner). — databox/client/package.json:11
The package in `databox/indexer` declares the lint script `lint` (`eslint src tests`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `databox/indexer` (or the workspace's task runner). — databox/indexer/package.json:20
The package in `expose/client` declares the lint script `lint` (`eslint src`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `expose/client` (or the workspace's task runner). — expose/client/package.json:11
The package in `uploader/client` declares the lint script `lint` (`eslint src`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `uploader/client` (or the workspace's task runner). — uploader/client/package.json:11
The package in `lib/js/api` declares the lint script `lint` (`eslint src`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `lib/js/api` (or the workspace's task runner). — lib/js/api/package.json:11
The package in `lib/js/auth` declares the lint script `lint` (`eslint src`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `lib/js/auth` (or the workspace's task runner). — lib/js/auth/package.json:14
The package in `lib/js/core` declares the lint script `lint` (`eslint src`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `lib/js/core` (or the workspace's task runner). — lib/js/core/package.json:12
The package in `lib/js/next-core` declares the lint script `lint` (`eslint src`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `lib/js/next-core` (or the workspace's task runner). — lib/js/next-core/package.json:31
The package in `lib/js/next-i18n` declares the lint script `lint` (`eslint src`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `lib/js/next-i18n` (or the workspace's task runner). — lib/js/next-i18n/package.json:19
The package in `lib/js/next-theme` declares the lint script `lint` (`eslint src`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `lib/js/next-theme` (or the workspace's task runner). — lib/js/next-theme/package.json:25
The package in `lib/js/next-ui` declares the lint script `lint` (`eslint src`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `lib/js/next-ui` (or the workspace's task runner). — lib/js/next-ui/package.json:26
The package in `lib/js/storage` declares the lint script `lint` (`eslint src`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `lib/js/storage` (or the workspace's task runner). — lib/js/storage/package.json:7
Do you agree with this assessment?
R7 · Dead Code8.1 / 10Strong✓ Tool-verified
React / JS · Code Health — Files unreachable from every application/tooling/test entry point, and exports nothing imports (module-graph reachability, D-386).
Method: Dead code: files unreachable from every application/tooling/test entry point plus exports nothing imports, via module-graph reachability. Deterministic, exhaustive over the import graph.
Unreachable from the 199 application, 95 tooling and 302 test entry point(s) detected in this repo. Gate removals on `pnpm run build` — an undetected custom entry would make these reachable.
no import path from any entry point (199 application, 95 tooling, 302 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 (×7) — databox/client/src/features/discussion/Discussion.tsx, databox/client/src/features/baskets/BasketSwitcher.tsx, databox/client/src/features/annotations/useAnnotationLayer.tsx, …
no import path from any entry point (199 application, 95 tooling, 302 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (databox/client/src/features/annotations/useAnnotationLayer.tsx) — 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 — databox/client/src/features/annotations/AnnotationToolbar.tsx
no import path from any entry point (199 application, 95 tooling, 302 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (databox/client/src/features/dnd/useAssetDrag.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — databox/client/src/features/dnd/DragScope.tsx
Nothing imports this binding — it is safe to review for removal. (×30) — databox/client/src/features/annotations/common.ts:50, databox/client/src/features/annotations/geometry.ts:56, databox/client/src/features/annotations/geometry.ts:60, …
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. — eslint.config.cjs:6
Declared in dashboard/client/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. — dashboard/client/package.json:41
Declared in databox/client/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) — databox/client/package.json:29, databox/client/package.json:40, databox/client/package.json:66
Declared in databox/indexer/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. — databox/indexer/package.json:40
Declared in expose/client/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. — expose/client/package.json:41
Declared in lib/js/auth/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. — lib/js/auth/package.json:24
Declared in lib/js/next-i18n/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. — lib/js/next-i18n/package.json:33
Declared in lib/js/next-theme/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. — lib/js/next-theme/package.json:46
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 — markup this repository SHIPS is scored for third-party script integrity whether or not the repository serves it itself, since a page handed to a consumer runs in that consumer’s origin — 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.
`https://cdnjs.cloudflare.com/ajax/libs/highlight.js/11.7.0/highlight.min.js` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. 3 such include(s) across the repository's markup. — databox/api/templates/admin/integration_help.html.twig:12
Set: Content-Security-Policy, Referrer-Policy, Strict-Transport-Security, X-Content-Type-Options. Missing: X-Frame-Options — the four headers that carry the points of this card's security-headers term (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options), 0.5 each. (−0.5 on this card.) — infra/docker/nginx-fpm-base/tpl/default.conf:8
What to do
Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-…"` hash alongside `crossorigin="anonymous"` (both are required — an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the app’s own origin, so no consumer inherits a third-party dependency they did not choose.
Add X-Frame-Options beside the headers already set; Content-Security-Policy is the one that pays for itself first, then Strict-Transport-Security, then nosniff and a frame policy.
Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.
Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.
Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether 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 async functions that make a cancellable request accept or pass on an AbortSignal (adoption curve).
Method: Roslyn scan: every async method (excluding framework-fixed overrides/Blazor handlers) checked for CancellationToken parameter presence. Deterministic, adoption percentage. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same question: every named async function that itself makes a request an AbortSignal can cancel (global `fetch`, axios and its file-local instances, ky, ofetch) counts, and it is compliant when its parameters or body name a signal or it hands one of its own parameters to the request as options; signatures a framework fixes (JSX event handlers, route and lifecycle exports, request-first handlers, `override`, `'use server'` modules, TanStack `mutationFn`) are exempt unless they take a signal. Deterministic, adoption percentage.
Only 11/19 async functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
`saveUrlAs` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — lib/js/next-ui/src/utils/misc.ts:91
`refresh` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — lib/js/next-core/src/auth/oidc.ts:383
`doHandleCallback` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — lib/js/next-core/src/auth/oidc.ts:638
`createJiraIssue` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — databox/client/src/lib/ticketing/jira.ts:56
`attachScreenshot` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — databox/client/src/lib/ticketing/jira.ts:106
`resolveSession` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — databox/client/src/lib/ticketing/session.ts:54
`fetchRemoteValues` holds an AbortSignal but calls `getTags(…)` without it, so its caller's cancellation never reaches that call and it runs to its end after whatever wanted it has given up. Hand the signal on: `getTags(…, { signal })`. — databox/client/src/features/search/suggest/remoteValues.ts:39
`fetchStatuses` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — dashboard/client/src/features/status/useServiceStatuses.ts:8
What to do
Thread an AbortSignal through async functions that make requests, so the work stops when its caller gives up.
Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.
Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether the work a diagnostic log line costs is paid only when that line is wanted — C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.
Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` — outside any arrow or function passed as an argument, which the logger calls only when the level is on — with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. Deterministic, provable per finding. Advisory.
`debug` at line 113 is called with an argument built by `implode('", "', $ids)` (line 113), whose cost grows with the collection it walks. PHP evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isHandling` test, no debug flag, and no placeholder context array that lets the logger build the text only when the level is on. — lib/php/es-bundle/Indexer/SearchIndexer.php:113
`debug` at line 86 is called with an argument built by `JSON.stringify(error.response.data)` (line 89), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — databox/indexer/src/lib/axios.ts:86
`debug` at line 116 is called with an argument built by `JSON.stringify(error.response.headers, undefined, 2)` (line 118), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — databox/indexer/src/lib/axios.ts:116
`debug` at line 169 is called with an argument built by `obfuscate(JSON.stringify(config.headers, null, 2))` (line 170), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — databox/indexer/src/lib/axios.ts:169
`debug` at line 584 is called with an argument built by `Object.keys(phraseanetDatabox.collections)` (line 585), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — databox/indexer/src/handlers/phraseanet/indexer.ts:584
`debug` at line 587 is called with an argument built by `JSON.stringify(phraseanetDatabox.collections[story.base_id])` (line 588), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — databox/indexer/src/handlers/phraseanet/indexer.ts:587
`debug` at line 63 is called with an argument built by `json_encode($data, JSON_THROW_ON_ERROR)` (line 63), whose cost grows with the collection it walks. PHP evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isHandling` test, no debug flag, and no placeholder context array that lets the logger build the text only when the level is on. — databox/api/src/Integration/Phraseanet/PhraseanetGenerateAssetRenditionsAction.php:63
`debug` at line 52 is called with an argument built by `json_encode($data, JSON_THROW_ON_ERROR)` (line 52), whose cost grows with the collection it walks. PHP evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isHandling` test, no debug flag, and no placeholder context array that lets the logger build the text only when the level is on. — databox/api/src/Integration/Phraseanet/PhraseanetGenerateAssetRenditionsEnqueueMethodAction.php:52
What to do
Each finding names the diagnostic call and the expression inside its argument whose cost scales with a collection. Confirm from the two that the argument is built before the call — that is JavaScript's evaluation order, not a guess — then put the construction behind the level check the logger offers (`if (logger.isLevelEnabled('debug'))` for pino and winston, `isDebugEnabled()` for log4js, the repository's own debug flag where it has one), or hand the logger the object and a format string (`logger.debug({ payload }, 'raw request')`) so the serialising happens only when the line is written. Moving the call is not the fix: it is the join/projection/stringify in the argument that is paid, wherever the call sits. In PHP, put the construction behind the logger's own check (`if ($logger->isHandling(Logger::DEBUG))` for Monolog, a debug flag for a line only a debug build needs), or pass the collection through the PSR-3 context array with a `{placeholder}` (`$logger->debug('rows: {rows}', ['rows' => $rows])`) so the handler renders it only when the record is written. Concatenating or interpolating the value into the message is not the fix: PHP builds the string, and every `array_map`, `implode` or `json_encode` inside it, before the call is entered.
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?
X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a `foreach` leaves the array or collection it is walking alone — PHP raises nothing, but the loop's view and the collection part: an array walked by value (and a Doctrine or Laravel collection) is walked as the snapshot taken when the loop began, so an element added in the body is never visited and one removed is visited anyway; an array walked by reference (`as &$v`) and an SPL container (`SplObjectStorage`, `ArrayObject`, `SplQueue`) are walked live, so an added element is walked too and a removal skips the next one; and after an `array_splice`, `array_shift` or sort every later key names a different element.
Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. 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.
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.
An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×31) — uploader/client/src/features/upload/engine/resumeStorage.ts:89, lib/js/next-ui/src/utils/misc.ts:111, lib/js/next-theme/src/themeScript.ts:24, …
`catch (\Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×4) — lib/php/workflow-bundle/Entity/WorkflowState.php:83, lib/php/workflow-bundle/Entity/WorkflowState.php:92, lib/php/workflow-bundle/Entity/WorkflowState.php:101, …
`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. (×2) — lib/php/rendition-factory/src/Image/ColorspaceDetector.php:93, expose/api/src/Security/PasswordTokenExtractor.php:25
`.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. — databox/client/src/features/workspaces/terms/WorkspaceTermsGate.tsx:55
`catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included. (×2) — databox/client/src/features/stories/useStoryRenditionRefresh.ts:59, databox/client/src/features/integrations/rekognition/RekognitionPanel.tsx:79
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.
`error` at line 32 is handed a template literal with `${…}` substitutions 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 the values beside a constant message instead: `logger.error({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.error('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — databox/indexer/src/amqp.ts:32
`info` at line 33 is handed a template literal with `${…}` substitutions 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 the values beside a constant message instead: `logger.info({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.info('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — databox/indexer/src/amqp.ts:33
`debug` at line 11 is handed a template literal with `${…}` substitutions 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 the values beside a constant message instead: `logger.debug({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.debug('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — databox/indexer/src/pathFilter.ts:11
`debug` at line 15 is handed a template literal with `${…}` substitutions 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 the values beside a constant message instead: `logger.debug({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.debug('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — databox/indexer/src/pathFilter.ts:15
`info` at line 84 is handed a template literal with `${…}` substitutions 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 the values beside a constant message instead: `logger.info({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.info('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — databox/indexer/src/server.ts:84
`warn` at line 104 is handed a template literal with `${…}` substitutions 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 the values beside a constant message instead: `logger.warn({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.warn('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — databox/indexer/src/server.ts:104
`warn` at line 114 is handed a template literal with `${…}` substitutions 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 the values beside a constant message instead: `logger.warn({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.warn('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — databox/indexer/src/server.ts:114
`warn` at line 79 is handed a template literal with `${…}` substitutions 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 the values beside a constant message instead: `logger.warn({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.warn('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — databox/indexer/src/lib/axios.ts:79
`debug` at line 86 is handed a template literal with `${…}` substitutions 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 the values beside a constant message instead: `logger.debug({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.debug('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — databox/indexer/src/lib/axios.ts:86
`debug` at line 169 is handed a template literal with `${…}` substitutions 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 the values beside a constant message instead: `logger.debug({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.debug('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — databox/indexer/src/lib/axios.ts:169
`info` at line 25 is handed a template literal with `${…}` substitutions 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 the values beside a constant message instead: `logger.info({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.info('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — databox/indexer/src/handlers/s3_amqp/indexer.ts:25
`error` at line 308 is handed a template literal with `${…}` substitutions 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 the values beside a constant message instead: `logger.error({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.error('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — databox/indexer/src/handlers/phraseanet/StructureImporter.ts:308
`error` at line 323 is handed a template literal with `${…}` substitutions 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 the values beside a constant message instead: `logger.error({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.error('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — databox/indexer/src/handlers/phraseanet/StructureImporter.ts:323
`error` at line 327 is handed a template literal with `${…}` substitutions 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 the values beside a constant message instead: `logger.error({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.error('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — databox/indexer/src/handlers/phraseanet/StructureImporter.ts:327
`info` at line 348 is handed a template literal with `${…}` substitutions 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 the values beside a constant message instead: `logger.info({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.info('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — databox/indexer/src/handlers/phraseanet/StructureImporter.ts:348
`info` at line 364 is handed a template literal with `${…}` substitutions 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 the values beside a constant message instead: `logger.info({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.info('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — databox/indexer/src/handlers/phraseanet/StructureImporter.ts:364
`info` at line 371 is handed a template literal with `${…}` substitutions 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 the values beside a constant message instead: `logger.info({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.info('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — databox/indexer/src/handlers/phraseanet/StructureImporter.ts:371
`info` at line 380 is handed a template literal with `${…}` substitutions 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 the values beside a constant message instead: `logger.info({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.info('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — databox/indexer/src/handlers/phraseanet/StructureImporter.ts:380
`error` at line 397 is handed a template literal with `${…}` substitutions 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 the values beside a constant message instead: `logger.error({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.error('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — databox/indexer/src/handlers/phraseanet/StructureImporter.ts:397
`info` at line 508 is handed a template literal with `${…}` substitutions 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 the values beside a constant message instead: `logger.info({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.info('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — databox/indexer/src/handlers/phraseanet/StructureImporter.ts:508
`info` at line 534 is handed a template literal with `${…}` substitutions 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 the values beside a constant message instead: `logger.info({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.info('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — databox/indexer/src/handlers/phraseanet/StructureImporter.ts:534
`info` at line 540 is handed a template literal with `${…}` substitutions 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 the values beside a constant message instead: `logger.info({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.info('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — databox/indexer/src/handlers/phraseanet/StructureImporter.ts:540
`info` at line 71 is handed a template literal with `${…}` substitutions 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 the values beside a constant message instead: `logger.info({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.info('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — databox/indexer/src/handlers/phraseanet/indexer.ts:71
`info` at line 85 is handed a template literal with `${…}` substitutions 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 the values beside a constant message instead: `logger.info({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.info('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — databox/indexer/src/handlers/phraseanet/indexer.ts:85
`info` at line 120 is handed a template literal with `${…}` substitutions 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 the values beside a constant message instead: `logger.info({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.info('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — databox/indexer/src/handlers/phraseanet/indexer.ts:120
`info` at line 239 is handed a template literal with `${…}` substitutions 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 the values beside a constant message instead: `logger.info({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.info('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — databox/indexer/src/handlers/phraseanet/indexer.ts:239
`info` at line 271 is handed a template literal with `${…}` substitutions 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 the values beside a constant message instead: `logger.info({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.info('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — databox/indexer/src/handlers/phraseanet/indexer.ts:271
`info` at line 291 is handed a template literal with `${…}` substitutions 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 the values beside a constant message instead: `logger.info({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.info('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — databox/indexer/src/handlers/phraseanet/indexer.ts:291
`info` at line 311 is handed a template literal with `${…}` substitutions 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 the values beside a constant message instead: `logger.info({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.info('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — databox/indexer/src/handlers/phraseanet/indexer.ts:311
`info` at line 320 is handed a template literal with `${…}` substitutions 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 the values beside a constant message instead: `logger.info({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.info('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — databox/indexer/src/handlers/phraseanet/indexer.ts:320
`info` at line 449 is handed a template literal with `${…}` substitutions 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 the values beside a constant message instead: `logger.info({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.info('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — databox/indexer/src/handlers/phraseanet/indexer.ts:449
`info` at line 465 is handed a template literal with `${…}` substitutions 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 the values beside a constant message instead: `logger.info({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.info('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — databox/indexer/src/handlers/phraseanet/indexer.ts:465
`info` at line 475 is handed a template literal with `${…}` substitutions 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 the values beside a constant message instead: `logger.info({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.info('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — databox/indexer/src/handlers/phraseanet/indexer.ts:475
`warn` at line 510 is handed a template literal with `${…}` substitutions 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 the values beside a constant message instead: `logger.warn({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.warn('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — databox/indexer/src/handlers/phraseanet/indexer.ts:510
`debug` at line 584 is handed a template literal with `${…}` substitutions 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 the values beside a constant message instead: `logger.debug({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.debug('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — databox/indexer/src/handlers/phraseanet/indexer.ts:584
`debug` at line 587 is handed a template literal with `${…}` substitutions 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 the values beside a constant message instead: `logger.debug({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.debug('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — databox/indexer/src/handlers/phraseanet/indexer.ts:587
`error` at line 600 is handed a template literal with `${…}` substitutions 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 the values beside a constant message instead: `logger.error({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.error('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — databox/indexer/src/handlers/phraseanet/indexer.ts:600
`error` at line 626 is handed a template literal with `${…}` substitutions 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 the values beside a constant message instead: `logger.error({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.error('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — databox/indexer/src/handlers/phraseanet/indexer.ts:626
`info` at line 642 is handed a template literal with `${…}` substitutions 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 the values beside a constant message instead: `logger.info({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.info('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — databox/indexer/src/handlers/phraseanet/indexer.ts:642
`warn` at line 662 is handed a template literal with `${…}` substitutions 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 the values beside a constant message instead: `logger.warn({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.warn('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — databox/indexer/src/handlers/phraseanet/indexer.ts:662
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.
0/3 of this repository's PHPStan/Psalm configuration(s) run at a level that checks null — PHPStan level 8 or above (`max` included), or Psalm `errorLevel` 3 or below (Psalm's default, with none stated, is 1). A PHPStan level written neither in the file nor in an include inside the repository is 0, PHPStan's own default. Below those levels the checker removes `null` from a union before any rule looks, so `$order->customer()->name()` on a `?Customer` passes, and the first null reaching it is an `Error: Call to a member function name() on null` in production.
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 — 2 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
X10 Duplicated predicate — 40 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 24 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
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.
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.
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).
AX4 Dependency direction — not applicable to a vertical-slice architecture (the inward-dependency rule is for layered/clean styles)
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — compose up failed (exit 15 — the compose project is invalid) — service "uploader-scheduler" has neither an image nor a build context specified: invalid compose project; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
D11 Test Reliability — Test reliability not measured — JavaScript/TypeScript suite did not run
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
D25 ADR Conformance — no ADRs to check
D32 Data Compliance (PII/GDPR) — 1385 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
D8 Code Coverage — Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — dashboard/client/ runs vitest but declares no coverage provider, so the suite can run and still produce no lcov — add `@vitest/coverage-v8` (or `@vitest/coverage-istanbul`) as a devDependency. Coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan.
DM10 One transaction, one aggregate — no repository writes detected — no operation to judge against the one-aggregate rule
DM12 Ambient inputs in the domain — no domain-layer types detected — ambient-input check not applicable
DM3 Integration-event coupling — no integration events detected — coupling check not applicable
DM6 Domain ↔ infrastructure boundary — no domain-layer types detected — domain↔infrastructure boundary 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, Scala, Rust and Java, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for 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.
R5 Dependency Freshness — uses a pnpm lockfile — dependency freshness not measured here; JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X1 Async correctness — X1 reached only 45% of this repository's production lines — php (160,204 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X12 Unreachable branch — X12 reached only 45% of this repository's production lines — php (160,204 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X17 Uncapped recursion over a caller-supplied document — X17 reached only 45% of this repository's production lines — php (160,204 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X24 Document value interpolated into markup unescaped — X24 reached only 45% of this repository's production lines — php (160,204 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
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.
X29 Per-element action decided by a fixed element — X29 reached only 45% of this repository's production lines — php (160,204 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
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.
DM1 · Aggregate boundaries· Aggregate holds a reference to another aggregate · ×40
Aggregate holds a reference to another aggregate: AssetOutput.thread — `AssetOutput` references the aggregate root `Thread` directly (via `thread`) — hold its `ThreadId` instead.
Aggregate holds a reference to another aggregate: AssetOutput.storyCollection — `AssetOutput` references the aggregate root `Collection` directly (via `storyCollection`) — hold its `CollectionId` instead.
Aggregate holds a reference to another aggregate: AssetOutput.source — `AssetOutput` references the aggregate root `File` directly (via `source`) — hold its `FileId` instead.
Aggregate holds a reference to another aggregate: AssetOutput.main — `AssetOutput` references the aggregate root `AssetRendition` directly (via `main`) — hold its `AssetRenditionId` instead.
Aggregate holds a reference to another aggregate: AssetOutput.preview — `AssetOutput` references the aggregate root `AssetRendition` directly (via `preview`) — hold its `AssetRenditionId` instead.
Aggregate holds a reference to another aggregate: AssetOutput.thumbnail — `AssetOutput` references the aggregate root `AssetRendition` directly (via `thumbnail`) — hold its `AssetRenditionId` instead.
Aggregate holds a reference to another aggregate: AssetOutput.animatedThumbnail — `AssetOutput` references the aggregate root `AssetRendition` directly (via `animatedThumbnail`) — hold its `AssetRenditionId` instead.
Aggregate holds a reference to another aggregate: AutomationRun.automation — `AutomationRun` references the aggregate root `SavedSearchAutomation` directly (via `automation`) — hold its `SavedSearchAutomationId` instead.
Aggregate holds a reference to another aggregate: AutomationSeenAsset.automation — `AutomationSeenAsset` references the aggregate root `SavedSearchAutomation` directly (via `automation`) — hold its `SavedSearchAutomationId` instead.
Aggregate holds a reference to another aggregate: AutomationSeenAsset.asset — `AutomationSeenAsset` references the aggregate root `Asset` directly (via `asset`) — hold its `AssetId` instead.
Aggregate holds a reference to another aggregate: AutomationShare.automation — `AutomationShare` references the aggregate root `SavedSearchAutomation` directly (via `automation`) — hold its `SavedSearchAutomationId` instead.
Aggregate holds a reference to another aggregate: AutomationShare.workspace — `AutomationShare` references the aggregate root `Workspace` directly (via `workspace`) — hold its `WorkspaceId` instead.
Aggregate holds a reference to another aggregate: AutomationShare.share — `AutomationShare` references the aggregate root `Share` directly (via `share`) — hold its `ShareId` instead.
Aggregate holds a reference to another aggregate: SavedSearchAutomation.savedSearch — `SavedSearchAutomation` references the aggregate root `SavedSearch` directly (via `savedSearch`) — hold its `SavedSearchId` instead.
Aggregate holds a reference to another aggregate: SavedSearchAutomation.workspace — `SavedSearchAutomation` references the aggregate root `Workspace` directly (via `workspace`) — hold its `WorkspaceId` instead.
Aggregate holds a reference to another aggregate: BasketAsset.basket — `BasketAsset` references the aggregate root `Basket` directly (via `basket`) — hold its `BasketId` instead.
Aggregate holds a reference to another aggregate: BasketAsset.asset — `BasketAsset` references the aggregate root `Asset` directly (via `asset`) — hold its `AssetId` instead.
Aggregate holds a reference to another aggregate: Asset.storyCollection — `Asset` references the aggregate root `Collection` directly (via `storyCollection`) — hold its `CollectionId` instead.
Aggregate holds a reference to another aggregate: Asset.referenceCollection — `Asset` references the aggregate root `Collection` directly (via `referenceCollection`) — hold its `CollectionId` instead.
Aggregate holds a reference to another aggregate: Asset.source — `Asset` references the aggregate root `File` directly (via `source`) — hold its `FileId` instead.
Aggregate holds a reference to another aggregate: AssetAttachment.asset — `AssetAttachment` references the aggregate root `Asset` directly (via `asset`) — hold its `AssetId` instead.
Aggregate holds a reference to another aggregate: AssetAttachment.attachment — `AssetAttachment` references the aggregate root `Asset` directly (via `attachment`) — hold its `AssetId` instead.
Aggregate holds a reference to another aggregate: AssetEmbedding.asset — `AssetEmbedding` references the aggregate root `Asset` directly (via `asset`) — hold its `AssetId` instead.
Aggregate holds a reference to another aggregate: AssetFileVersion.asset — `AssetFileVersion` references the aggregate root `Asset` directly (via `asset`) — hold its `AssetId` instead.
Aggregate holds a reference to another aggregate: AssetFileVersion.file — `AssetFileVersion` references the aggregate root `File` directly (via `file`) — hold its `FileId` instead.
Banned license: @img/sharp-libvips-darwin-arm64 REDACTED:1857— `@img/sharp-libvips-darwin-arm64` 1.3.4 is published on registry.npmjs.org under `LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
Banned license: @img/sharp-libvips-darwin-x64 REDACTED:1862— `@img/sharp-libvips-darwin-x64` 1.3.4 is published on registry.npmjs.org under `LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
Banned license: @img/sharp-libvips-linux-arm REDACTED:1873— `@img/sharp-libvips-linux-arm` 1.3.4 is published on registry.npmjs.org under `LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
Banned license: @img/sharp-libvips-linux-arm64 REDACTED:1867— `@img/sharp-libvips-linux-arm64` 1.3.4 is published on registry.npmjs.org under `LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
Banned license: @img/sharp-libvips-linux-ppc64 REDACTED:1879— `@img/sharp-libvips-linux-ppc64` 1.3.4 is published on registry.npmjs.org under `LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
Banned license: @img/sharp-libvips-linux-riscv64 REDACTED:1885— `@img/sharp-libvips-linux-riscv64` 1.3.4 is published on registry.npmjs.org under `LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
Banned license: @img/sharp-libvips-linux-s390x REDACTED:1891— `@img/sharp-libvips-linux-s390x` 1.3.4 is published on registry.npmjs.org under `LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
Banned license: @img/sharp-libvips-linux-x64 REDACTED:1897— `@img/sharp-libvips-linux-x64` 1.3.4 is published on registry.npmjs.org under `LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
Banned license: @img/sharp-libvips-linuxmusl-arm64 REDACTED:1903— `@img/sharp-libvips-linuxmusl-arm64` 1.3.4 is published on registry.npmjs.org under `LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
Banned license: @img/sharp-libvips-linuxmusl-x64 REDACTED:1909— `@img/sharp-libvips-linuxmusl-x64` 1.3.4 is published on registry.npmjs.org under `LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
Banned license: @img/sharp-wasm32 REDACTED:1971— `@img/sharp-wasm32` 0.35.5 is published on registry.npmjs.org under `Apache-2.0 AND LGPL-3.0-or-later AND MIT`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
Banned license: @img/sharp-win32-arm64 REDACTED:1980— `@img/sharp-win32-arm64` 0.35.5 is published on registry.npmjs.org under `Apache-2.0 AND LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
Banned license: @img/sharp-win32-ia32 REDACTED:1986— `@img/sharp-win32-ia32` 0.35.5 is published on registry.npmjs.org under `Apache-2.0 AND LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
Banned license: @img/sharp-win32-x64 REDACTED:1992— `@img/sharp-win32-x64` 0.35.5 is published on registry.npmjs.org under `Apache-2.0 AND LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
<html> without a lang expose/api/templates/base.html.twig:2— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang expose/iframe.html:1— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang REDACTED:2— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
AC2 · Forms & labels· <button> with no accessible text · ×2
<button> with no accessible text databox/client/src/components/form/CollectionTreePicker.tsx:264— 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 databox/client/src/components/form/CollectionTreePicker.tsx:432— A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
AC2 · Forms & labels· <input> without a programmatic label · ×2
<input> without a programmatic label databox/client/src/components/form/TagsInput.tsx:142— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
<input> without a programmatic label databox/client/src/features/search/SearchBar.tsx:119— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
AC4 · Keyboard semantics· Click handler on a non-interactive <div> · ×2
Click handler on a non-interactive <div> expose/client/src/features/player/PdfViewer.tsx:302— A click handler on a plain element with no role and no tabindex: even where another element's key handler can reach it, assistive tech can neither focus it nor announce what it is. Use a <button>, or add role + tabIndex={0}.
Click handler on a non-interactive <div> expose/client/src/features/player/ZoomableImage.tsx:190— 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· Link with no accessible name · ×1
Link with no accessible name databox/client/src/features/baskets/manage/BasketIntegrations.tsx:254— A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label.
AC3 · Page structure· Document without a <title> · ×1
Document without a <title> databox/api/templates/terms/terms_pdf.html.twig:2— A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>.
AC3 · Page structure· <iframe> without a title · ×1
<iframe> without a title expose/iframe.html:12— An iframe with no title (or an empty one) is announced only as "frame". Add a non-empty title describing its content, or an aria-label.
AC4 · Keyboard semantics· Double-click handler on a non-interactive <div> · ×1
Double-click handler on a non-interactive <div> databox/client/src/components/ui/data-table/DataTable.tsx:520— This <div> binds mousedown, touchstart and double-click — pointer gestures with no keyboard form, a double-click among them. No click, no key handler, and no tabIndex={0}, so it cannot even take focus. Nothing synthesises a double-click from the keyboard: Enter and Space fire a single click, and only on a native <button> or <a href>. So this behaviour has no keyboard path at all. Expose the same action on a real control, or add role + tabIndex={0} + a key handler alongside the double-click.
AC4 · Keyboard semantics· Click handler on a non-interactive <svg> · ×1
Click handler on a non-interactive <svg> databox/client/src/features/annotations/AnnotationLayer.tsx:708— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
AC4 · Keyboard semantics· Clickable role="separator" that no keyboard user can reach · ×1
Clickable role="separator" that no keyboard user can reach databox/client/src/features/attributes/batch/AttributeBatchEditorRoute.tsx:1236— This <div> announces itself as a role="separator" and is operated by pointerdown, but nothing can put focus on it: no tabIndex={0}, no key handler, and nothing in its scripts moves focus. A keyboard cannot produce a pointer drag, so the control cannot be operated at all (WCAG 2.1.1). Give it tabIndex={0}="0" and move it with the arrow keys in a key handler (with aria-valuenow for the position it holds).
AC4 · Keyboard semantics· Click handler on a non-interactive <img> · ×1
Click handler on a non-interactive <img> expose/client/src/features/player/AssetPlayer.tsx:132— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
AC4 · Keyboard semantics· Clickable role="button" that no keyboard user can reach · ×1
Clickable role="button" that no keyboard user can reach lib/js/next-ui/src/form/AsyncCombobox.tsx:260— This <span> announces itself as a role="button" and binds a click, but nothing can put focus on it: no tabIndex={0} in any spelling, no key handler, and nothing in this file moves focus or sets aria-activedescendant. The role tells assistive tech what the control IS; it does not make the control reachable, so a keyboard user cannot operate it at all (WCAG 2.1.1). Give it tabIndex={0}="0" and an Enter/Space key handler, or make it a native <button>. If a parent widget owns the keyboard model, that parent must move focus onto the active role="button" or point aria-activedescendant at it.
AC4 · Keyboard semantics· Click handler on a non-interactive <span> · ×1
Click handler on a non-interactive <span> lib/php/admin-bundle/Resources/views/list/id.html.twig:2— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
AX8 · Test isolation· Production project references a test project · ×1
Production project references a test project: api (databox/api) → alchemy/test-bundle — `api (databox/api)` (production) references the test project `alchemy/test-bundle`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
FunctionTooLong: AttributeBatchEditorRoute.AttributeBatchEditorRoute databox/client/src/features/attributes/batch/AttributeBatchEditorRoute.tsx:143— FunctionTooLong — AttributeBatchEditorRoute runs 860 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 760 over it, 8.60× 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: AssetMap.MapView databox/client/src/features/map/AssetMap.tsx:193— FunctionTooLong — MapView runs 709 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 609 over it, 7.09× 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: UploadDialog.UploadDialog databox/client/src/features/upload/UploadDialog.tsx:89— FunctionTooLong — UploadDialog runs 643 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 543 over it, 6.43× 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: AnnotationLayer.AnnotationLayer databox/client/src/features/annotations/AnnotationLayer.tsx:105— FunctionTooLong — AnnotationLayer runs 601 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 501 over it, 6.01× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: EntityGrid.EntityGrid databox/client/src/features/workspaces/manage/entities/EntityGrid.tsx:116— FunctionTooLong — EntityGrid runs 500 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 400 over it, 5.00× 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: DataTable.DataTable databox/client/src/components/ui/data-table/DataTable.tsx:90— FunctionTooLong — DataTable runs 460 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 360 over it, 4.60× 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: UploadScreen.UploadScreen uploader/client/src/features/upload/UploadScreen.tsx:114— FunctionTooLong — UploadScreen runs 447 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 347 over it, 4.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: MessageComposer.MessageComposer databox/client/src/features/discussion/MessageComposer.tsx:150— FunctionTooLong — MessageComposer runs 446 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 346 over it, 4.46× 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: ClipEditorDialog.ClipEditorDialog databox/client/src/features/clip/ClipEditorDialog.tsx:81— FunctionTooLong — ClipEditorDialog runs 432 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 332 over it, 4.32× 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: AutomationForm.AutomationFormDialog databox/client/src/features/saved-searches/automations/AutomationForm.tsx:94— FunctionTooLong — AutomationFormDialog runs 432 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 332 over it, 4.32× 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: ThemeEditorScreen.ThemeEditorScreen databox/client/src/features/theme/ThemeEditorScreen.tsx:194— FunctionTooLong — ThemeEditorScreen runs 420 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 320 over it, 4.20× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: AttributeDefinitionsTab.DefinitionForm databox/client/src/features/workspaces/manage/tabs/AttributeDefinitionsTab.tsx:139— FunctionTooLong — DefinitionForm runs 378 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 278 over it, 3.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: DefinitionManager.DefinitionManager databox/client/src/features/workspaces/manage/DefinitionManager.tsx:134— FunctionTooLong — DefinitionManager runs 352 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 252 over it, 3.52× 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: PdfViewer.PdfDocumentViewer expose/client/src/features/player/PdfViewer.tsx:101— FunctionTooLong — PdfDocumentViewer runs 341 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 241 over it, 3.41× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: IntegrationManager.IntegrationForm databox/client/src/features/integrations/manage/IntegrationManager.tsx:149— FunctionTooLong — IntegrationForm runs 340 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 240 over it, 3.40× 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: BasketIntegrations.ExposeIntegration databox/client/src/features/baskets/manage/BasketIntegrations.tsx:126— FunctionTooLong — ExposeIntegration runs 335 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 235 over it, 3.35× 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: ClipTimeline.ClipTimeline databox/client/src/features/clip/ClipTimeline.tsx:75— FunctionTooLong — ClipTimeline runs 331 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 231 over it, 3.31× 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: AclEditor.AclEditor databox/client/src/features/permissions/AclEditor.tsx:54— FunctionTooLong — AclEditor runs 328 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 228 over it, 3.28× 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: ShareDialog.ShareDialog databox/client/src/features/share/ShareDialog.tsx:116— FunctionTooLong — ShareDialog runs 326 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 226 over it, 3.26× 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: Discussion.Discussion databox/client/src/features/discussion/Discussion.tsx:67— FunctionTooLong — Discussion runs 324 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 224 over it, 3.24× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: AuditLogScreen.AuditLogScreen databox/client/src/features/audit-log/AuditLogScreen.tsx:113— FunctionTooLong — AuditLogScreen runs 303 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 203 over it, 3.03× 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: entityColumns.buildEntityColumns databox/client/src/features/workspaces/manage/entities/entityColumns.tsx:196— FunctionTooLong — buildEntityColumns runs 295 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 195 over it, 2.95× 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: AnnotationToolbar.AnnotationToolbar databox/client/src/features/annotations/AnnotationToolbar.tsx:71— FunctionTooLong — AnnotationToolbar runs 275 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 175 over it, 2.75× 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: collectionStore.useCollectionStore databox/client/src/features/collections/collectionStore.ts:151— FunctionTooLong — useCollectionStore runs 275 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 175 over it, 2.75× 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: FieldInspector.InputFieldInspector uploader/client/src/features/form-builder/editor/FieldInspector.tsx:107— FunctionTooLong — InputFieldInspector runs 266 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 166 over it, 2.66× 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.
Hotspot: databox/client/src/features/assets/view/AssetViewRoute.tsx databox/client/src/features/assets/view/AssetViewRoute.tsx:110— databox/client/src/features/assets/view/AssetViewRoute.tsx changed 21 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 84 in AssetViewRoute.AssetViewRoute at line 110. 4 of those changes were fix/bug commits, and the other 17 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 11:29:16 +01:00' --until='2026-11-16 11:29:16 +01:00' --full-history --no-merges -- databox/client/src/features/assets/view/AssetViewRoute.tsx`: 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: databox/client/src/features/attributes/batch/AttributeBatchEditorRoute.tsx databox/client/src/features/attributes/batch/AttributeBatchEditorRoute.tsx:143— databox/client/src/features/attributes/batch/AttributeBatchEditorRoute.tsx changed 12 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 90 in AttributeBatchEditorRoute.AttributeBatchEditorRoute at line 143. 2 of those changes were fix/bug commits, and the other 10 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 11:29:16 +01:00' --until='2026-11-16 11:29:16 +01:00' --full-history --no-merges -- databox/client/src/features/attributes/batch/AttributeBatchEditorRoute.tsx`: 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: databox/client/src/features/workspaces/manage/DefinitionManager.tsx databox/client/src/features/workspaces/manage/DefinitionManager.tsx:134— databox/client/src/features/workspaces/manage/DefinitionManager.tsx changed 14 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 74 in DefinitionManager.DefinitionManager at line 134. 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-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 11:29:16 +01:00' --until='2026-11-16 11:29:16 +01:00' --full-history --no-merges -- databox/client/src/features/workspaces/manage/DefinitionManager.tsx`: 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: databox/client/src/features/upload/UploadDialog.tsx databox/client/src/features/upload/UploadDialog.tsx:89— databox/client/src/features/upload/UploadDialog.tsx changed 11 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 76 in UploadDialog.UploadDialog at line 89. 1 of those changes was a fix/bug commit, and the other 10 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 11:29:16 +01:00' --until='2026-11-16 11:29:16 +01:00' --full-history --no-merges -- databox/client/src/features/upload/UploadDialog.tsx`: 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: databox/client/src/features/annotations/AnnotationLayer.tsx databox/client/src/features/annotations/AnnotationLayer.tsx:105— databox/client/src/features/annotations/AnnotationLayer.tsx changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 166 in AnnotationLayer.AnnotationLayer at line 105. 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-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 11:29:16 +01:00' --until='2026-11-16 11:29:16 +01:00' --full-history --no-merges -- databox/client/src/features/annotations/AnnotationLayer.tsx`: 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: databox/client/src/features/assets/list/AssetThumb.tsx databox/client/src/features/assets/list/AssetThumb.tsx:52— databox/client/src/features/assets/list/AssetThumb.tsx changed 12 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 62 in AssetThumb.AssetThumb at line 52. 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-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 11:29:16 +01:00' --until='2026-11-16 11:29:16 +01:00' --full-history --no-merges -- databox/client/src/features/assets/list/AssetThumb.tsx`: 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: databox/client/src/features/assets/actions/useAssetActions.tsx databox/client/src/features/assets/actions/useAssetActions.tsx:139— databox/client/src/features/assets/actions/useAssetActions.tsx changed 12 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 53 in useAssetActions.useAssetActions at line 139. 2 of those changes were fix/bug commits, and the other 10 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 11:29:16 +01:00' --until='2026-11-16 11:29:16 +01:00' --full-history --no-merges -- databox/client/src/features/assets/actions/useAssetActions.tsx`: 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: databox/client/src/features/discussion/Discussion.tsx databox/client/src/features/discussion/Discussion.tsx:67— databox/client/src/features/discussion/Discussion.tsx changed 12 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 45 in Discussion.Discussion at line 67. 1 of those changes was a fix/bug commit, and the other 11 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 11:29:16 +01:00' --until='2026-11-16 11:29:16 +01:00' --full-history --no-merges -- databox/client/src/features/discussion/Discussion.tsx`: 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: databox/api/src/Security/Voter/CollectionVoter.php databox/api/src/Security/Voter/CollectionVoter.php:47— databox/api/src/Security/Voter/CollectionVoter.php changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 90 in CollectionVoter.doVote at line 47. 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-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 11:29:16 +01:00' --until='2026-11-16 11:29:16 +01:00' --full-history --no-merges -- databox/api/src/Security/Voter/CollectionVoter.php`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: databox/client/src/features/search/SearchProvider.tsx databox/client/src/features/search/SearchProvider.tsx:100— databox/client/src/features/search/SearchProvider.tsx changed 11 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 40 in SearchProvider.SearchProvider at line 100. 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-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 11:29:16 +01:00' --until='2026-11-16 11:29:16 +01:00' --full-history --no-merges -- databox/client/src/features/search/SearchProvider.tsx`: 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: databox/client/src/components/layout/TopBar.tsx databox/client/src/components/layout/TopBar.tsx:65— databox/client/src/components/layout/TopBar.tsx changed 19 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 23 in TopBar.TopBar at line 65. 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-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 11:29:16 +01:00' --until='2026-11-16 11:29:16 +01:00' --full-history --no-merges -- databox/client/src/components/layout/TopBar.tsx`: 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: databox/api/src/Elasticsearch/AssetSearch.php databox/api/src/Elasticsearch/AssetSearch.php:308— databox/api/src/Elasticsearch/AssetSearch.php changed 15 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 29 in AssetSearch.buildQuery at line 308. 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-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 11:29:16 +01:00' --until='2026-11-16 11:29:16 +01:00' --full-history --no-merges -- databox/api/src/Elasticsearch/AssetSearch.php`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: databox/client/src/features/collections/tree/CollectionsPanel.tsx databox/client/src/features/collections/tree/CollectionsPanel.tsx:275— databox/client/src/features/collections/tree/CollectionsPanel.tsx changed 15 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 29 in CollectionsPanel.WorkspaceItem at line 275. 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-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 11:29:16 +01:00' --until='2026-11-16 11:29:16 +01:00' --full-history --no-merges -- databox/client/src/features/collections/tree/CollectionsPanel.tsx`: 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: uploader/client/src/features/upload/UploadScreen.tsx uploader/client/src/features/upload/UploadScreen.tsx:114— uploader/client/src/features/upload/UploadScreen.tsx changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 54 in UploadScreen.UploadScreen at line 114. 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-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 11:29:16 +01:00' --until='2026-11-16 11:29:16 +01:00' --full-history --no-merges -- uploader/client/src/features/upload/UploadScreen.tsx`: 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: databox/client/src/features/integrations/manage/IntegrationManager.tsx databox/client/src/features/integrations/manage/IntegrationManager.tsx:149— databox/client/src/features/integrations/manage/IntegrationManager.tsx changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 47 in IntegrationManager.IntegrationForm at line 149. 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-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 11:29:16 +01:00' --until='2026-11-16 11:29:16 +01:00' --full-history --no-merges -- databox/client/src/features/integrations/manage/IntegrationManager.tsx`: 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: databox/client/src/features/assets/player/AudioPlayer.tsx databox/client/src/features/assets/player/AudioPlayer.tsx:76— databox/client/src/features/assets/player/AudioPlayer.tsx changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 53 in AudioPlayer.AudioPlayer at line 76. 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-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 11:29:16 +01:00' --until='2026-11-16 11:29:16 +01:00' --full-history --no-merges -- databox/client/src/features/assets/player/AudioPlayer.tsx`: 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: databox/client/src/features/baskets/manage/BasketIntegrations.tsx databox/client/src/features/baskets/manage/BasketIntegrations.tsx:126— databox/client/src/features/baskets/manage/BasketIntegrations.tsx changed 11 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 30 in BasketIntegrations.ExposeIntegration at line 126. 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-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 11:29:16 +01:00' --until='2026-11-16 11:29:16 +01:00' --full-history --no-merges -- databox/client/src/features/baskets/manage/BasketIntegrations.tsx`: 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: databox/client/src/features/workspaces/manage/tabs/AttributeDefinitionsTab.tsx databox/client/src/features/workspaces/manage/tabs/AttributeDefinitionsTab.tsx:139— databox/client/src/features/workspaces/manage/tabs/AttributeDefinitionsTab.tsx changed 11 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 30 in AttributeDefinitionsTab.DefinitionForm at line 139. 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-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 11:29:16 +01:00' --until='2026-11-16 11:29:16 +01:00' --full-history --no-merges -- databox/client/src/features/workspaces/manage/tabs/AttributeDefinitionsTab.tsx`: 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: databox/client/src/features/share/ShareDialog.tsx databox/client/src/features/share/ShareDialog.tsx:116— databox/client/src/features/share/ShareDialog.tsx changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 41 in ShareDialog.ShareDialog at line 116. 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-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 11:29:16 +01:00' --until='2026-11-16 11:29:16 +01:00' --full-history --no-merges -- databox/client/src/features/share/ShareDialog.tsx`: 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: databox/client/src/features/assets/player/ZoomableImage.tsx databox/client/src/features/assets/player/ZoomableImage.tsx:44— databox/client/src/features/assets/player/ZoomableImage.tsx changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 44 in ZoomableImage.ZoomableImage at line 44. 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-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 11:29:16 +01:00' --until='2026-11-16 11:29:16 +01:00' --full-history --no-merges -- databox/client/src/features/assets/player/ZoomableImage.tsx`: 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: databox/client/src/components/ui/data-table/DataTable.tsx databox/client/src/components/ui/data-table/DataTable.tsx:90— databox/client/src/components/ui/data-table/DataTable.tsx changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 102 in DataTable.DataTable at line 90. 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-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 11:29:16 +01:00' --until='2026-11-16 11:29:16 +01:00' --full-history --no-merges -- databox/client/src/components/ui/data-table/DataTable.tsx`: 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: databox/client/src/features/clip/ClipEditorDialog.tsx databox/client/src/features/clip/ClipEditorDialog.tsx:81— databox/client/src/features/clip/ClipEditorDialog.tsx changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 71 in ClipEditorDialog.ClipEditorDialog at line 81. 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-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 11:29:16 +01:00' --until='2026-11-16 11:29:16 +01:00' --full-history --no-merges -- databox/client/src/features/clip/ClipEditorDialog.tsx`: 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: databox/client/src/features/discussion/MessageComposer.tsx databox/client/src/features/discussion/MessageComposer.tsx:150— databox/client/src/features/discussion/MessageComposer.tsx changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 55 in MessageComposer.MessageComposer at line 150. 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-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 11:29:16 +01:00' --until='2026-11-16 11:29:16 +01:00' --full-history --no-merges -- databox/client/src/features/discussion/MessageComposer.tsx`: 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: databox/client/src/features/permissions/AclEditor.tsx databox/client/src/features/permissions/AclEditor.tsx:54— databox/client/src/features/permissions/AclEditor.tsx changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 34 in AclEditor.AclEditor at line 54. 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-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 11:29:16 +01:00' --until='2026-11-16 11:29:16 +01:00' --full-history --no-merges -- databox/client/src/features/permissions/AclEditor.tsx`: 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: databox/client/src/features/attributes/editor/AttributesEditor.tsx databox/client/src/features/attributes/editor/AttributesEditor.tsx:52— databox/client/src/features/attributes/editor/AttributesEditor.tsx changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 38 in AttributesEditor.AttributesEditor at line 52. 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-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 11:29:16 +01:00' --until='2026-11-16 11:29:16 +01:00' --full-history --no-merges -- databox/client/src/features/attributes/editor/AttributesEditor.tsx`: 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.
Cross-slice coupling: dashboard → status dashboard/client/src/features/dashboard/DashboardScreen.tsx:34— `DashboardScreen` (slice 'dashboard') depends on `useServiceStatuses` from slice 'status'.
Cross-slice coupling: dashboard → status dashboard/client/src/features/dashboard/ServiceCardView.tsx:63— `StatusIndicator` (slice 'dashboard') depends on `ServiceStatus` from slice 'status'.
Cross-slice coupling: annotations → attributes databox/client/src/features/annotations/assetAnnotations.ts:21— `labelAttributeAnnotations` (slice 'annotations') depends on `FormatContext` from slice 'attributes'.
Cross-slice coupling: annotations → attributes databox/client/src/features/annotations/assetAnnotations.ts:29— `labelAttributeAnnotations` (slice 'annotations') depends on `formatAttributeString` from slice 'attributes'.
Cross-slice coupling: assets → clip databox/client/src/features/assets/actions/ExportDialog.tsx:54— `ExportDialog` (slice 'assets') depends on `hasClip` from slice 'clip'.
Cross-slice coupling: assets → clip databox/client/src/features/assets/actions/ExportDialog.tsx:54— `ExportDialog` (slice 'assets') depends on `effectiveClip` from slice 'clip'.
Cross-slice coupling: assets → collections databox/client/src/features/assets/actions/ExportDialog.tsx:104— `ExportDialog` (slice 'assets') depends on `useCollectionStore` from slice 'collections'.
Cross-slice coupling: assets → share databox/client/src/features/assets/actions/ExportDialog.tsx:214— `ExportDialog` (slice 'assets') depends on `TermsContent` from slice 'share'.
Cross-slice coupling: assets → collections databox/client/src/features/assets/actions/RestoreAssetsDialog.tsx:117— `RestoreAssetsDialog` (slice 'assets') depends on `RestoreCollectionDialog` from slice 'collections'.
Cross-slice coupling: assets → baskets databox/client/src/features/assets/actions/useAssetActions.tsx:147— `useAssetActions` (slice 'assets') depends on `useAddToCurrentBasket` from slice 'baskets'.
Cross-slice coupling: assets → search databox/client/src/features/assets/actions/useAssetActions.tsx:149— `useAssetActions` (slice 'assets') depends on `useOptionalResults` from slice 'search'.
Cross-slice coupling: assets → stories databox/client/src/features/assets/actions/useAssetActions.tsx:151— `useAssetActions` (slice 'assets') depends on `usePinnedStoriesStore` from slice 'stories'.
Cross-slice coupling: assets → search databox/client/src/features/assets/actions/useAssetActions.tsx:153— `useAssetActions` (slice 'assets') depends on `useSimilarSearch` from slice 'search'.
Cross-slice coupling: assets → share databox/client/src/features/assets/actions/useAssetActions.tsx:373— `useAssetActions` (slice 'assets') depends on `ShareDialog` from slice 'share'.
Cross-slice coupling: assets → clip databox/client/src/features/assets/actions/useAssetActions.tsx:452— `useAssetActions` (slice 'assets') depends on `isClipApplicable` from slice 'clip'.
Cross-slice coupling: assets → preferences databox/client/src/features/assets/list/AssetList.tsx:30— `AssetListProps` (slice 'assets') depends on `LayoutMode` from slice 'preferences'.
Cross-slice coupling: assets → dnd databox/client/src/features/assets/list/AssetList.tsx:134— `AssetList` (slice 'assets') depends on `DragScopeProvider` from slice 'dnd'.
Cross-slice coupling: assets → preferences databox/client/src/features/assets/list/AssetThumb.tsx:72— `AssetThumb` (slice 'assets') depends on `useDisplayPreferences` from slice 'preferences'.
Cross-slice coupling: assets → clip databox/client/src/features/assets/list/AssetThumb.tsx:86— `AssetThumb` (slice 'assets') depends on `clipForFile` from slice 'clip'.
Cross-slice coupling: assets → clip databox/client/src/features/assets/list/AssetThumb.tsx:86— `AssetThumb` (slice 'assets') depends on `effectiveClip` from slice 'clip'.
Cross-slice coupling: assets → clip databox/client/src/features/assets/list/AssetThumb.tsx:105— `AssetThumb` (slice 'assets') depends on `useClipPlayback` from slice 'clip'.
Cross-slice coupling: assets → clip databox/client/src/features/assets/list/AssetThumb.tsx:127— `AssetThumb` (slice 'assets') depends on `cropAspect` from slice 'clip'.
Cross-slice coupling: assets → clip databox/client/src/features/assets/list/AssetThumb.tsx:243— `AssetThumb` (slice 'assets') depends on `ClipFrame` from slice 'clip'.
Cross-slice coupling: assets → dnd databox/client/src/features/assets/list/SelectableCard.tsx:44— `SelectableCard` (slice 'assets') depends on `useAssetDrag` from slice 'dnd'.
Cross-slice coupling: assets → attributes databox/client/src/features/assets/list/layouts/Dividers.tsx:91— `GroupLabel` (slice 'assets') depends on `useFormatContext` from slice 'attributes'.
Outbound HTTP without resilience databox/api/src/Border/UploaderClient.php:28— `->request(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience databox/api/src/Border/UploaderClient.php:39— `->request(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience databox/api/src/Border/UriDownloader.php:34— `->request(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience databox/api/src/Border/UriDownloader.php:57— `->request(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience databox/api/src/Controller/Integration/ExposeIntegrationController.php:113— `->request(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience databox/api/src/Controller/Integration/IntegrationAuthController.php:67— `->request(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience databox/api/src/Integration/Aws/Transcribe/Consumer/ConfirmSnsSubscriptionHandler.php:19— `->request(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience databox/api/src/Integration/Core/Webhook/WebhookAction.php:59— `->request(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience databox/api/src/Integration/Happyscribe/Consumer/CreateExportMessageHandler.php:34— `->request(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience databox/api/src/Integration/Happyscribe/Consumer/ExportTranscriptionMessageHandler.php:49— `->request(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience databox/api/src/Integration/Happyscribe/Consumer/ExportTranscriptionMessageHandler.php:82— `->request(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience databox/api/src/Integration/Happyscribe/Consumer/TranscriptionHappyscribeMessageHandler.php:48— `->request(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience databox/api/src/Integration/Happyscribe/Consumer/TranscriptionHappyscribeMessageHandler.php:114— `->request(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience databox/api/src/Integration/Happyscribe/Consumer/TranslateTranscriptionMessageHandler.php:37— `->request(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience databox/api/src/Integration/Happyscribe/HappyscribeAction.php:78— `->request(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience databox/api/src/Integration/Happyscribe/HappyscribeAction.php:94— `->request(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience databox/api/src/Integration/Happyscribe/HappyscribeAction.php:123— `->request(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience databox/api/src/Integration/Phrasea/Expose/ExposeClient.php:69— `->request(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience databox/api/src/Integration/Phrasea/Expose/ExposeClient.php:173— `->request(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience databox/api/src/Integration/Phrasea/Expose/ExposeClient.php:179— `->request(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience databox/api/src/Integration/Phrasea/Expose/ExposeClient.php:316— `->request(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience databox/api/src/Integration/Phrasea/Expose/ExposeClient.php:354— `->request(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience databox/api/src/Integration/Phrasea/Expose/ExposeClient.php:379— `->request(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience databox/api/src/Integration/Phrasea/Expose/ExposeClient.php:396— `->request(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience databox/api/src/Integration/Phrasea/Expose/ExposeClient.php:414— `->request(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
+ 15 more in this group — see findings.md.
R4 · Test Coverage· No test reaches this file · ×40
No test reaches this file databox/client/src/features/attributes/batch/AttributeBatchEditorRoute.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file databox/client/src/features/map/AssetMap.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file uploader/client/src/features/upload/UploadScreen.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file databox/client/src/features/upload/UploadDialog.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file databox/client/src/features/theme/ThemeEditorScreen.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file databox/client/src/features/collections/tree/CollectionsPanel.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file expose/client/src/features/admin/config/ConfigForm.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file databox/client/src/features/operation-tasks/OperationTasksScreen.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file databox/client/src/features/profiles/manage/ProfileGridTab.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file databox/client/src/features/search/pinned/PinnedFilters.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file databox/client/src/features/profiles/manage/ProfileAttributesTab.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file databox/client/src/features/saved-searches/automations/AutomationForm.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file databox/client/src/features/workspaces/manage/tabs/AssetPoliciesTab.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file databox/client/src/features/baskets/manage/BasketIntegrations.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file databox/client/src/features/workspaces/manage/tabs/AttributeDefinitionsTab.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file expose/client/src/features/player/PdfViewer.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file databox/client/src/features/discussion/Discussion.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file uploader/client/src/features/form-builder/editor/FieldInspector.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file databox/client/src/features/integrations/manage/IntegrationManager.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file uploader/client/src/features/admin/UploadLinksScreen.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file databox/client/src/features/workspaces/manage/tabs/WorkspaceEditTab.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file databox/client/src/features/profiles/manage/AttributePalette.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file databox/client/src/features/annotations/AnnotationToolbar.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file databox/client/src/features/permissions/InstancePermissionsScreen.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file expose/client/src/features/player/ZoomableImage.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
Swallowed exception (empty catch) uploader/client/src/features/upload/engine/resumeStorage.ts:89— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) lib/js/next-ui/src/utils/misc.ts:111— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) lib/js/next-theme/src/themeScript.ts:24— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) lib/js/next-theme/src/themeStore.ts:39— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) lib/js/auth/src/stateNonce.ts:59— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) lib/js/auth/src/stateNonce.ts:77— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) expose/client/src/lib/auth/loggedOut.ts:11— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) expose/client/src/lib/auth/loggedOut.ts:19— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) expose/client/src/hooks/useStoredState.ts:22— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) expose/client/src/hooks/useStoredState.ts:33— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) expose/client/src/features/player/subtitles.ts:28— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) databox/client/src/lib/ticketing/jira.ts:49— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) databox/client/src/lib/auth/impersonation.ts:56— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) databox/client/src/lib/auth/impersonation.ts:74— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) databox/client/src/lib/auth/impersonation.ts:88— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) databox/client/src/hooks/useResizablePanel.ts:119— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) databox/client/src/hooks/useResizablePanel.ts:135— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) databox/client/src/hooks/useResizablePanel.ts:170— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) databox/client/src/features/workspaces/terms/WorkspaceTermsGate.tsx:55— `.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) databox/client/src/features/stories/pinnedStoriesStore.ts:36— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) databox/client/src/features/share/shareDisplayStore.ts:43— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) databox/client/src/features/share/ShareDialog.tsx:552— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) databox/client/src/features/share/ShareTerms.tsx:132— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) databox/client/src/features/search/aql/serializer.ts:212— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) databox/client/src/features/saved-searches/automations/actions/WebhookForm.tsx:251— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
FileTooLong: AQL/AQLGrammar.php databox/api/src/Elasticsearch/AQL/AQLGrammar.php— FileTooLong — 1622 significant lines (blank, comment-only and punctuation-only lines excluded), about 100% of them inside a single declaration: AQLGrammar (7-2021). The bar is 500 significant lines; this is 1122 over it, 3.24× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: batch/AttributeBatchEditorRoute.tsx databox/client/src/features/attributes/batch/AttributeBatchEditorRoute.tsx— FileTooLong — 1316 significant lines (blank, comment-only and punctuation-only lines excluded), about 65% of them inside a single declaration: AttributeBatchEditorRoute (143-1220). The bar is 500 significant lines; this is 816 over it, 2.63× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: types/api.ts databox/client/src/types/api.ts— FileTooLong — 967 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 467 over it, 1.93× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: map/AssetMap.tsx databox/client/src/features/map/AssetMap.tsx— FileTooLong — 947 significant lines (blank, comment-only and punctuation-only lines excluded), about 75% of them inside a single declaration: MapView (193-1159). The bar is 500 significant lines; this is 447 over it, 1.89× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: upload/UploadScreen.tsx uploader/client/src/features/upload/UploadScreen.tsx— FileTooLong — 865 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 365 over it, 1.73× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: upload/UploadDialog.tsx databox/client/src/features/upload/UploadDialog.tsx— FileTooLong — 791 significant lines (blank, comment-only and punctuation-only lines excluded), about 81% of them inside a single declaration: UploadDialog (89-867). The bar is 500 significant lines; this is 291 over it, 1.58× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: conditions/ConditionBuilder.tsx databox/client/src/features/search/conditions/ConditionBuilder.tsx— FileTooLong — 772 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 272 over it, 1.54× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: share/ShareDialog.tsx databox/client/src/features/share/ShareDialog.tsx— FileTooLong — 737 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 237 over it, 1.47× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: config/ConfigForm.tsx databox/client/src/features/integrations/config/ConfigForm.tsx— FileTooLong — 736 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 236 over it, 1.47× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: theme/ThemeEditorScreen.tsx databox/client/src/features/theme/ThemeEditorScreen.tsx— FileTooLong — 732 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 232 over it, 1.46× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: tree/CollectionsPanel.tsx databox/client/src/features/collections/tree/CollectionsPanel.tsx— FileTooLong — 706 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 206 over it, 1.41× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: annotations/AnnotationLayer.tsx databox/client/src/features/annotations/AnnotationLayer.tsx— FileTooLong — 670 significant lines (blank, comment-only and punctuation-only lines excluded), about 90% of them inside a single declaration: AnnotationLayer (105-926). The bar is 500 significant lines; this is 170 over it, 1.34× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: entities/EntityGrid.tsx databox/client/src/features/workspaces/manage/entities/EntityGrid.tsx— FileTooLong — 625 significant lines (blank, comment-only and punctuation-only lines excluded), about 80% of them inside a single declaration: EntityGrid (116-752). The bar is 500 significant lines; this is 125 over it, 1.25× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: config/ConfigForm.tsx expose/client/src/features/admin/config/ConfigForm.tsx— FileTooLong — 624 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 124 over it, 1.25× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Core/Asset.php databox/api/src/Entity/Core/Asset.php— FileTooLong — 623 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 123 over it, 1.25× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: form/selects.tsx databox/client/src/components/form/selects.tsx— FileTooLong — 611 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 111 over it, 1.22× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: phraseanet/StructureImporter.ts databox/indexer/src/handlers/phraseanet/StructureImporter.ts— FileTooLong — 600 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 100 over it, 1.20× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: operation-tasks/OperationTasksScreen.tsx databox/client/src/features/operation-tasks/OperationTasksScreen.tsx— FileTooLong — 596 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 96 over it, 1.19× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: manage/ProfileGridTab.tsx databox/client/src/features/profiles/manage/ProfileGridTab.tsx— FileTooLong — 592 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 92 over it, 1.18× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: manage/DefinitionManager.tsx databox/client/src/features/workspaces/manage/DefinitionManager.tsx— FileTooLong — 579 significant lines (blank, comment-only and punctuation-only lines excluded), about 61% of them inside a single declaration: DefinitionManager (134-557). The bar is 500 significant lines; this is 79 over it, 1.16× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: annotations/shapes.tsx databox/client/src/features/annotations/shapes.tsx— FileTooLong — 574 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 74 over it, 1.15× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: clip/ClipEditorDialog.tsx databox/client/src/features/clip/ClipEditorDialog.tsx— FileTooLong — 551 significant lines (blank, comment-only and punctuation-only lines excluded), about 78% of them inside a single declaration: ClipEditorDialog (81-606). The bar is 500 significant lines; this is 51 over it, 1.10× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: data-table/DataTable.tsx databox/client/src/components/ui/data-table/DataTable.tsx— FileTooLong — 546 significant lines (blank, comment-only and punctuation-only lines excluded), about 84% of them inside a single declaration: DataTable (90-680). The bar is 500 significant lines; this is 46 over it, 1.09× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: phraseanet/indexer.ts databox/indexer/src/handlers/phraseanet/indexer.ts— FileTooLong — 545 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 45 over it, 1.09× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: discussion/MessageComposer.tsx databox/client/src/features/discussion/MessageComposer.tsx— FileTooLong — 544 significant lines (blank, comment-only and punctuation-only lines excluded), about 82% of them inside a single declaration: MessageComposer (150-715). The bar is 500 significant lines; this is 44 over it, 1.09× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
Repeated repair: expose/api/src/Entity/Asset.php expose/api/src/Entity/Asset.php:674— expose/api/src/Entity/Asset.php changed 11 times in last 90 days and 8 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 Asset.getPreviewDefinition at line 674), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “PS-1354 fix(expose): inherited visibility, private WebVTT cache, asynchronous archive build”; “PS-1354 fix(expose): enforce download settings and download terms server-side”; “Revert "Merge branch 'mcp' into next"”; “fix(validation): re-enable attribute constraints in expose”. 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-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 11:29:16 +01:00' --until='2026-11-16 11:29:16 +01:00' --full-history --no-merges -- expose/api/src/Entity/Asset.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: expose/api/src/Entity/Publication.php expose/api/src/Entity/Publication.php:692— expose/api/src/Entity/Publication.php changed 11 times in last 90 days and 6 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 7 (its worst body is Publication.isVisible at line 692), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “PS-1354 fix: send the access token to the API origin only, filter publication children without changing the entity”; “PS-1354 fix(expose): inherited visibility, private WebVTT cache, asynchronous archive build”; “PS-1354 fix(expose): rate-limit password checks and download requests, hash publication passwords”; “Revert "Merge branch 'mcp' into next"”. 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-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 11:29:16 +01:00' --until='2026-11-16 11:29:16 +01:00' --full-history --no-merges -- expose/api/src/Entity/Publication.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: databox/api/src/Service/Asset/AssetCopier.php databox/api/src/Service/Asset/AssetCopier.php:84— databox/api/src/Service/Asset/AssetCopier.php changed 7 times in last 90 days and 6 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 9 (its worst body is AssetCopier.doCopyAsset at line 84), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(AssetCopier): return file directly if already in the target workspace”; “fix(databox): keep the relation extra metadata when copying an asset”; “fix(databox): set the destination collection as reference of a copied asset”; “fix(databox): reset asset copier file cache when a copy fails”. 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-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 11:29:16 +01:00' --until='2026-11-16 11:29:16 +01:00' --full-history --no-merges -- databox/api/src/Service/Asset/AssetCopier.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: expose/api/src/Controller/PostPublicationArchiveRequestAction.php expose/api/src/Controller/PostPublicationArchiveRequestAction.php:36— expose/api/src/Controller/PostPublicationArchiveRequestAction.php 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 3 (its worst body is PostPublicationArchiveRequestAction.__invoke at line 36), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “PS-1354 fix(expose): inherited visibility, private WebVTT cache, asynchronous archive build”; “PS-1354 fix(expose): rate-limit password checks and download requests, hash publication passwords”; “PS-1354 fix(expose): enforce download settings and download terms server-side”; “Revert "Merge branch 'mcp' into next"”. 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-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 11:29:16 +01:00' --until='2026-11-16 11:29:16 +01:00' --full-history --no-merges -- expose/api/src/Controller/PostPublicationArchiveRequestAction.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: expose/api/src/Entity/SubDefinition.php expose/api/src/Entity/SubDefinition.php:235— expose/api/src/Entity/SubDefinition.php changed 7 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 1 (its worst body is SubDefinition.__construct at line 235), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “PS-1354 fix(expose): enforce download settings and download terms server-side”; “Revert "Merge branch 'mcp' into next"”; “fix(validation): re-enable attribute constraints in expose”; “fix(expose): check the asset read right on sub-definitions”. 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-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 11:29:16 +01:00' --until='2026-11-16 11:29:16 +01:00' --full-history --no-merges -- expose/api/src/Entity/SubDefinition.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: expose/api/src/Controller/PostDownloadAssetViaEmailAction.php expose/api/src/Controller/PostDownloadAssetViaEmailAction.php:19— expose/api/src/Controller/PostDownloadAssetViaEmailAction.php changed 5 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 1 (its worst body is PostDownloadAssetViaEmailAction.__invoke at line 19), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “PS-1354 fix(expose): rate-limit password checks and download requests, hash publication passwords”; “PS-1354 fix(expose): enforce download settings and download terms server-side”; “Revert "Merge branch 'mcp' into next"”; “fix(validation): re-enable attribute constraints in expose”. 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-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 11:29:16 +01:00' --until='2026-11-16 11:29:16 +01:00' --full-history --no-merges -- expose/api/src/Controller/PostDownloadAssetViaEmailAction.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: expose/api/src/Controller/PostDownloadSubDefViaEmailAction.php expose/api/src/Controller/PostDownloadSubDefViaEmailAction.php:19— expose/api/src/Controller/PostDownloadSubDefViaEmailAction.php changed 5 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 1 (its worst body is PostDownloadSubDefViaEmailAction.__invoke at line 19), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “PS-1354 fix(expose): rate-limit password checks and download requests, hash publication passwords”; “PS-1354 fix(expose): enforce download settings and download terms server-side”; “Revert "Merge branch 'mcp' into next"”; “fix(validation): re-enable attribute constraints in expose”. 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-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 11:29:16 +01:00' --until='2026-11-16 11:29:16 +01:00' --full-history --no-merges -- expose/api/src/Controller/PostDownloadSubDefViaEmailAction.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: uploader/api/src/Api/Processor/CreateAssetProcessor.php uploader/api/src/Api/Processor/CreateAssetProcessor.php:47— uploader/api/src/Api/Processor/CreateAssetProcessor.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 10 (its worst body is CreateAssetProcessor.process at line 47), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “PS-1354 fix(storage): check the real type of the files and apply the allowed types everywhere”; “PS-1354 fix(storage): check the owner and the real size of multipart uploads”; “fix(uploader): check the target upload permission on multipart uploads and commits”. 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-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 11:29:16 +01:00' --until='2026-11-16 11:29:16 +01:00' --full-history --no-merges -- uploader/api/src/Api/Processor/CreateAssetProcessor.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: expose/api/src/Entity/PublicationConfig.php expose/api/src/Entity/PublicationConfig.php:204— expose/api/src/Entity/PublicationConfig.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 PublicationConfig.setSecurityOptions at line 204), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “PS-1354 fix(expose): rate-limit password checks and download requests, hash publication passwords”; “Revert "Merge branch 'mcp' into next"”; “fix(validation): re-enable attribute constraints in expose”. 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-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 11:29:16 +01:00' --until='2026-11-16 11:29:16 +01:00' --full-history --no-merges -- expose/api/src/Entity/PublicationConfig.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: databox/api/src/Controller/Integration/PhraseanetIntegrationController.php databox/api/src/Controller/Integration/PhraseanetIntegrationController.php:38— databox/api/src/Controller/Integration/PhraseanetIntegrationController.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 9 (its worst body is PhraseanetIntegrationController.incomingRenditionAction at line 38), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “PS-1354 fix(storage): check the real type of the files and apply the allowed types everywhere”; “fix(databox): only fetch Phraseanet permalinks on the integration port”; “fix(databox): only fetch Phraseanet permalinks from the integration host”. 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-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 11:29:16 +01:00' --until='2026-11-16 11:29:16 +01:00' --full-history --no-merges -- databox/api/src/Controller/Integration/PhraseanetIntegrationController.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: expose/api/src/Api/Upload/UploadRequestResolver.php expose/api/src/Api/Upload/UploadRequestResolver.php:39— expose/api/src/Api/Upload/UploadRequestResolver.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 9 (its worst body is UploadRequestResolver.resolve at line 39), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “PS-1354 fix(storage): check the real type of the files and apply the allowed types everywhere”; “PS-1354 fix(storage): validate type/extension couples on upload, force response headers on signed URLs”; “PS-1354 fix(storage): check the owner and the real size of multipart uploads”. 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-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 11:29:16 +01:00' --until='2026-11-16 11:29:16 +01:00' --full-history --no-merges -- expose/api/src/Api/Upload/UploadRequestResolver.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: uploader/api/src/Consumer/Handler/DownloadHandler.php uploader/api/src/Consumer/Handler/DownloadHandler.php:50— uploader/api/src/Consumer/Handler/DownloadHandler.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 10 (its worst body is DownloadHandler.__invoke at line 50), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “PS-1354 fix(storage): check the real type of the files and apply the allowed types everywhere”; “PS-1354 fix(storage): check the owner and the real size of multipart uploads”; “fix(uploader): refuse private network URLs in the upload from URL”. 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-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 11:29:16 +01:00' --until='2026-11-16 11:29:16 +01:00' --full-history --no-merges -- uploader/api/src/Consumer/Handler/DownloadHandler.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: expose/api/src/Serializer/Normalizer/PublicationNormalizer.php expose/api/src/Serializer/Normalizer/PublicationNormalizer.php:23— expose/api/src/Serializer/Normalizer/PublicationNormalizer.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 8 (its worst body is PublicationNormalizer.normalize at line 23), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “PS-1354 fix: send the access token to the API origin only, filter publication children without changing the entity”; “PS-1354 fix(expose): rate-limit password checks and download requests, hash publication passwords”; “PS-1354 fix(expose): enforce download settings and download terms server-side”. 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-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 11:29:16 +01:00' --until='2026-11-16 11:29:16 +01:00' --full-history --no-merges -- expose/api/src/Serializer/Normalizer/PublicationNormalizer.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: expose/client/src/lib/api/publications.ts expose/client/src/lib/api/publications.ts:64— expose/client/src/lib/api/publications.ts changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 5 (its worst body is publications.listQuery at line 64), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “PS-1354 fix(expose): inherited visibility, private WebVTT cache, asynchronous archive build”; “PS-1354 fix(expose): rate-limit password checks and download requests, hash publication passwords”; “PS-1354 fix(expose): enforce download settings and download terms server-side”. 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-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 11:29:16 +01:00' --until='2026-11-16 11:29:16 +01:00' --full-history --no-merges -- expose/client/src/lib/api/publications.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: lib/php/storage-bundle/Upload/UploadManager.php lib/php/storage-bundle/Upload/UploadManager.php:68— lib/php/storage-bundle/Upload/UploadManager.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 4 (its worst body is UploadManager.getSignedUrls at line 68), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “PS-1354 fix(storage): validate type/extension couples on upload, force response headers on signed URLs”; “PS-1354 fix(storage): check the owner and the real size of multipart uploads”; “Fixes (#909)”. 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-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 11:29:16 +01:00' --until='2026-11-16 11:29:16 +01:00' --full-history --no-merges -- lib/php/storage-bundle/Upload/UploadManager.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: expose/api/src/Controller/AbstractAssetAction.php expose/api/src/Controller/AbstractAssetAction.php:43— expose/api/src/Controller/AbstractAssetAction.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 AbstractAssetAction.getAssetOfPublication at line 43), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “PS-1354 fix(expose): enforce download settings and download terms server-side”; “Revert "Merge branch 'mcp' into next"”; “fix(validation): re-enable attribute constraints in expose”. 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-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 11:29:16 +01:00' --until='2026-11-16 11:29:16 +01:00' --full-history --no-merges -- expose/api/src/Controller/AbstractAssetAction.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: expose/api/src/Storage/AssetManager.php expose/api/src/Storage/AssetManager.php:27— expose/api/src/Storage/AssetManager.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 15 (its worst body is AssetManager.createAsset at line 27), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Revert "Merge branch 'mcp' into next"”; “fix(validation): re-enable attribute constraints in expose”; “fix(expose): check the delete right in the delete by asset ID operation”. 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-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 11:29:16 +01:00' --until='2026-11-16 11:29:16 +01:00' --full-history --no-merges -- expose/api/src/Storage/AssetManager.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: databox/api/src/Repository/Core/RenditionDefinitionRepository.php databox/api/src/Repository/Core/RenditionDefinitionRepository.php:31— databox/api/src/Repository/Core/RenditionDefinitionRepository.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 5 (its worst body is RenditionDefinitionRepository.addAclConditions at line 31), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “PS-1196 fix: harden CORS, hide the Sentry DSN, hide the rendition definitions of deleted workspaces”; “fix(databox): list rendition definitions with VIEW or CHILD_VIEW on their policy”; “fix(databox): PS-1312 list renditions of private policies in export dialog”. 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-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 11:29:16 +01:00' --until='2026-11-16 11:29:16 +01:00' --full-history --no-merges -- databox/api/src/Repository/Core/RenditionDefinitionRepository.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: databox/api/src/Security/Voter/RenditionDefinitionVoter.php databox/api/src/Security/Voter/RenditionDefinitionVoter.php:31— databox/api/src/Security/Voter/RenditionDefinitionVoter.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 12 (its worst body is RenditionDefinitionVoter.voteOnAttribute at line 31), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “PS-1196 fix: harden CORS, hide the Sentry DSN, hide the rendition definitions of deleted workspaces”; “fix(databox): remove commented code for clarity in voter classes”; “fix(databox): apply the collection ACL to rendition definition READ”. 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-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 11:29:16 +01:00' --until='2026-11-16 11:29:16 +01:00' --full-history --no-merges -- databox/api/src/Security/Voter/RenditionDefinitionVoter.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: databox/api/src/Elasticsearch/Listener/PopulateListener.php databox/api/src/Elasticsearch/Listener/PopulateListener.php:32— databox/api/src/Elasticsearch/Listener/PopulateListener.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 PopulateListener.preIndexPopulate at line 32), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “PS-1089 fix(databox): trace the memory of each populate page and lighten it”; “PS-1356 fix(databox): populate without forcemerge nor refresh_interval”; “PS-1089 fix(databox): bound the memory of the Elasticsearch populate”. 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-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 11:29:16 +01:00' --until='2026-11-16 11:29:16 +01:00' --full-history --no-merges -- databox/api/src/Elasticsearch/Listener/PopulateListener.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: databox/api/src/Service/Asset/FileFetcher.php databox/api/src/Service/Asset/FileFetcher.php:101— databox/api/src/Service/Asset/FileFetcher.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 9 (its worst body is FileFetcher.getHead at line 101), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(databox): delete the temporary copies created by FileFetcher”; “PS-1354 fix(storage): check the real type of the files and apply the allowed types everywhere”; “Fixes (#909)”. 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-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 11:29:16 +01:00' --until='2026-11-16 11:29:16 +01:00' --full-history --no-merges -- databox/api/src/Service/Asset/FileFetcher.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: databox/api/src/Border/UriDownloader.php databox/api/src/Border/UriDownloader.php:75— databox/api/src/Border/UriDownloader.php changed 3 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 5 (its worst body is UriDownloader.createClient at line 75), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “PS-1354 fix(storage): check the real type of the files and apply the allowed types everywhere”; “fix(databox): refuse private network URLs for user-supplied files”; “fix: address the Sentry issues triaged as "to fix" (#907)”. 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-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 11:29:16 +01:00' --until='2026-11-16 11:29:16 +01:00' --full-history --no-merges -- databox/api/src/Border/UriDownloader.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: lib/php/storage-bundle/Upload/FileValidator.php lib/php/storage-bundle/Upload/FileValidator.php:48— lib/php/storage-bundle/Upload/FileValidator.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 6 (its worst body is FileValidator.normalizeTypes at line 48), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “PS-1354 fix(storage): check the real type of the files and apply the allowed types everywhere”; “PS-1354 fix(storage): validate type/extension couples on upload, force response headers on signed URLs”; “fix: address the Sentry issues triaged as "to fix" (#907)”. 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-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 11:29:16 +01:00' --until='2026-11-16 11:29:16 +01:00' --full-history --no-merges -- lib/php/storage-bundle/Upload/FileValidator.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: lib/php/auth-bundle/Security/UriJwtManager.php lib/php/auth-bundle/Security/UriJwtManager.php:73— lib/php/auth-bundle/Security/UriJwtManager.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 3 (its worst body is UriJwtManager.validateJWT at line 73), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “PS-1354 fix(expose): enforce download settings and download terms server-side”; “fix(auth-bundle): verify the signature of URI JWTs”; “fix: address the Sentry issues triaged as "to fix" (#907)”. 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-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 11:29:16 +01:00' --until='2026-11-16 11:29:16 +01:00' --full-history --no-merges -- lib/php/auth-bundle/Security/UriJwtManager.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: expose/api/src/DataPersister/ExposeDataPersister.php expose/api/src/DataPersister/ExposeDataPersister.php:32— expose/api/src/DataPersister/ExposeDataPersister.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 13 (its worst body is ExposeDataPersister.process at line 32), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(expose): check the profile read right when a publication changes profile”; “fix(expose): check the parent, cover, package and profile of a publication”; “Fixes (#909)”. 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-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 11:29:16 +01:00' --until='2026-11-16 11:29:16 +01:00' --full-history --no-merges -- expose/api/src/DataPersister/ExposeDataPersister.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.
Off the main sequence: @alchemy/core — @alchemy/core: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: @alchemy/next-i18n — @alchemy/next-i18n: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 4 project(s), so it's rigid to change.
Off the main sequence: @alchemy/next-ui — @alchemy/next-ui: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 6 project(s), so it's rigid to change.
Off the main sequence: @alchemy/storage — @alchemy/storage: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 2 project(s), so it's rigid to change.
Off the main sequence: alchemy/metadata-manipulator-bundle — alchemy/metadata-manipulator-bundle: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: alchemy/rendition-factory-bundle — alchemy/rendition-factory-bundle: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: alchemy/storage-bundle — alchemy/storage-bundle: abstractness 0.04, instability 0.00, distance 0.96 — zone of pain — concrete and depended on by 3 project(s), so it's rigid to change.
Off the main sequence: alchemy/messenger-bundle — alchemy/messenger-bundle: abstractness 0.07, instability 0.00, distance 0.93 — zone of pain — concrete and depended on by 3 project(s), so it's rigid to change.
Off the main sequence: alchemy/webhook-bundle — alchemy/webhook-bundle: abstractness 0.08, instability 0.00, distance 0.92 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: alchemy/rendition-factory — alchemy/rendition-factory: abstractness 0.13, instability 0.00, distance 0.87 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: alchemy/auth-bundle — alchemy/auth-bundle: abstractness 0.14, instability 0.00, distance 0.86 — zone of pain — concrete and depended on by 5 project(s), so it's rigid to change.
Off the main sequence: alchemy/es-bundle — alchemy/es-bundle: abstractness 0.16, instability 0.00, distance 0.84 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: alchemy/core-bundle — alchemy/core-bundle: abstractness 0.17, instability 0.00, distance 0.83 — zone of pain — concrete and depended on by 7 project(s), so it's rigid to change.
Off the main sequence: alchemy/workflow — alchemy/workflow: abstractness 0.19, instability 0.00, distance 0.81 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: @alchemy/api — @alchemy/api: abstractness 0.00, instability 0.20, distance 0.80 — zone of pain — concrete and depended on by 4 project(s), so it's rigid to change.
Off the main sequence: @alchemy/next-core — @alchemy/next-core: abstractness 0.00, instability 0.20, distance 0.80 — zone of pain — concrete and depended on by 4 project(s), so it's rigid to change.
Off the main sequence: @alchemy/next-theme — @alchemy/next-theme: abstractness 0.00, instability 0.20, distance 0.80 — zone of pain — concrete and depended on by 4 project(s), so it's rigid to change.
Off the main sequence: alchemy/report-sdk — alchemy/report-sdk: abstractness 0.20, instability 0.00, distance 0.80 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: alchemy/mcp-bundle — alchemy/mcp-bundle: abstractness 0.00, instability 0.25, distance 0.75 — zone of pain — concrete and depended on by 3 project(s), so it's rigid to change.
Off the main sequence: alchemy/configurator-bundle — alchemy/configurator-bundle: abstractness 0.09, instability 0.20, distance 0.71 — zone of pain — concrete and depended on by 4 project(s), so it's rigid to change.
TooManyMethods: AttributeDefinition databox/api/src/Entity/Core/AttributeDefinition.php:53— TooManyMethods — 84 methods. The bar is 30 methods; this is 54 over it, 2.80× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Publication expose/api/src/Entity/Publication.php:42— TooManyMethods — 75 methods. The bar is 30 methods; this is 45 over it, 2.50× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: AQLGrammar databox/api/src/Elasticsearch/AQL/AQLGrammar.php:7— TooManyMethods — 67 methods. The bar is 30 methods; this is 37 over it, 2.23× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Asset expose/api/src/Entity/Asset.php:34— TooManyMethods — 65 methods. The bar is 30 methods; this is 35 over it, 2.17× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Asset databox/api/src/Entity/Core/Asset.php:102— TooManyMethods — 60 methods. The bar is 30 methods; this is 30 over it, 2.00× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: File databox/api/src/Entity/Core/File.php:23— TooManyMethods — 53 methods. The bar is 30 methods; this is 23 over it, 1.77× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: ProfileItem databox/api/src/Entity/Profile/ProfileItem.php:23— TooManyMethods — 40 methods. The bar is 30 methods; this is 10 over it, 1.33× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Collection databox/api/src/Entity/Core/Collection.php:70— TooManyMethods — 38 methods. The bar is 30 methods; this is 8 over it, 1.27× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: RenditionDefinition databox/api/src/Entity/Core/RenditionDefinition.php:44— TooManyMethods — 38 methods. The bar is 30 methods; this is 8 over it, 1.27× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: PublicationConfig expose/api/src/Entity/PublicationConfig.php:17— TooManyMethods — 38 methods. The bar is 30 methods; this is 8 over it, 1.27× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Target uploader/api/src/Entity/Target.php:35— TooManyMethods — 33 methods. The bar is 30 methods; this is 3 over it, 1.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Commit uploader/api/src/Entity/Commit.php:31— TooManyMethods — 32 methods. The bar is 30 methods; this is 2 over it, 1.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: SavedSearchAutomation databox/api/src/Entity/Automation/SavedSearchAutomation.php:42— TooManyMethods — 31 methods. The bar is 30 methods; this is 1 over it, 1.03× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Attribute databox/api/src/Entity/Core/Attribute.php:32— TooManyMethods — 31 methods. The bar is 30 methods; this is 1 over it, 1.03× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: AttributeEntity databox/api/src/Entity/Core/AttributeEntity.php:47— TooManyMethods — 31 methods. The bar is 30 methods; this is 1 over it, 1.03× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: KeycloakClient lib/php/auth-bundle/Client/KeycloakClient.php:21— TooManyMethods — 31 methods. The bar is 30 methods; this is 1 over it, 1.03× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TodoComment lib/php/rendition-factory/src/Transformer/Video/VideoToAnimationTransformerModule.php:95— // todo: implement other modes — 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 lib/php/rendition-factory/src/Transformer/Image/Imagine/ImagineTransformerModule.php:402— // TODO implement projection — 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 lib/php/rendition-factory/src/Transformer/Document/DocumentToPdfTransformerModule.php:103— // TODO implement projection — 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 lib/php/rendition-factory/src/Transformer/Document/PdfToImageTransformerModule.php:112— // TODO implement projection — 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 lib/php/rendition-factory/src/Transformer/Document/PdfToImageTransformerModule.php:80— // TODO normalize file to PDF — 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 lib/php/es-bundle/Listener/DeferredIndexListener.php:30— // #[AsDoctrineListener(Events::postFlush)] TODO break tests — 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 lib/php/core-bundle/Health/Checker/RabbitMQConnectionChecker.php:18— // TODO — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment expose/api/src/DataPersister/ExposeDataPersister.php:35— // TODO remove after deprecation cycle — 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 databox/indexer/src/handlers/phraseanet/StructureImporter.ts:337— // todo: check conflicts — 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 databox/indexer/src/handlers/phraseanet/StructureImporter.ts:598— // todo: extension ? — 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 databox/indexer/src/handlers/phraseanet/StructureImporter.ts:665— // todo : gop — 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 databox/indexer/src/handlers/phraseanet/shared.ts:193— // todo: better handle of mono/multi/object — 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 databox/api/src/Security/Voter/WorkspaceVoter.php:101— // TODO implement UI to add/remove users/groups on client — 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 databox/api/src/Consumer/Handler/Basket/BasketUpdateHandler.php:28— // TODO cache whether there are basket integrations — 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.
AC2 · Forms & labels· <Input> field component without a label · ×13
<Input> field component without a label databox/client/src/components/form/CollectionTreePicker.tsx:577— 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.
<Input> field component without a label databox/client/src/components/form/FileOrUrlInput.tsx:101— 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.
<Input> field component without a label databox/client/src/features/annotations/AnnotationToolbar.tsx:373— 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.
<Input> field component without a label databox/client/src/features/collections/tree/CollectionsPanel.tsx:116— 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.
<Input> field component without a label databox/client/src/features/integrations/manage/IntegrationCatalog.tsx:115— 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.
<Input> field component without a label databox/client/src/features/integrations/tui/PhotoEditorDialog.tsx:145— 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.
<Input> field component without a label databox/client/src/features/operation-tasks/OperationTasksScreen.tsx:553— 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.
<Input> field component without a label databox/client/src/features/profiles/manage/AttributePalette.tsx:336— 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.
<Input> field component without a label databox/client/src/features/saved-searches/automations/AutomationForm.tsx:369— 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.
<Input> field component without a label databox/client/src/features/saved-searches/automations/AutomationForm.tsx:382— 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.
<Input> field component without a label databox/client/src/features/saved-searches/automations/actions/RemoteDestinationFields.tsx:60— 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.
<Input> field component without a label databox/client/src/features/saved-searches/automations/actions/WebhookForm.tsx:167— 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.
<Input> field component without a label databox/client/src/features/saved-searches/automations/actions/WebhookForm.tsx:183— 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· <SimpleSelect> field component without a label · ×13
<SimpleSelect> field component without a label databox/client/src/components/form/PrivacyField.tsx:86— 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.
<SimpleSelect> field component without a label databox/client/src/features/attributes/widgets/AttributeWidget.tsx:147— 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.
<SimpleSelect> field component without a label databox/client/src/features/attributes/widgets/AttributeWidget.tsx:285— 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.
<SimpleSelect> field component without a label databox/client/src/features/clip/ClipEditorDialog.tsx:570— 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.
<SimpleSelect> field component without a label databox/client/src/features/map/AssetMap.tsx:970— 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.
<SimpleSelect> field component without a label databox/client/src/features/operation-tasks/OperationTasksScreen.tsx:535— 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.
<SimpleSelect> field component without a label databox/client/src/features/profiles/manage/ProfileGridTab.tsx:623— 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.
<SimpleSelect> field component without a label databox/client/src/features/profiles/manage/ProfileGridTab.tsx:658— 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.
<SimpleSelect> field component without a label databox/client/src/features/profiles/manage/ProfileGridTab.tsx:680— 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.
<SimpleSelect> field component without a label databox/client/src/features/saved-searches/automations/AutomationForm.tsx:321— 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.
<SimpleSelect> field component without a label databox/client/src/features/saved-searches/automations/AutomationForm.tsx:356— 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.
<SimpleSelect> field component without a label databox/client/src/features/search/conditions/ConditionBuilder.tsx:185— 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.
<SimpleSelect> field component without a label databox/client/src/features/search/conditions/ConditionBuilder.tsx:358— 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.
MethodTooLong: ImagineTransformerModule.buildConfiguration lib/php/rendition-factory/src/Transformer/Image/Imagine/ImagineTransformerModule.php:51— MethodTooLong — buildConfiguration runs 307 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 207 over it, 3.07× 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: Migration20230807Command.execute configurator/src/Command/Migration20230807Command.php:27— MethodTooLong — execute runs 199 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 99 over it, 1.99× 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: FFMpegTransformerModule.getExtraConfigurationBuilders lib/php/rendition-factory/src/Transformer/Video/FFMpegTransformerModule.php:183— MethodTooLong — getExtraConfigurationBuilders runs 180 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 80 over it, 1.80× 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: AQLGrammar.match_operator databox/api/src/Elasticsearch/AQL/AQLGrammar.php:527— MethodTooLong — match_operator runs 167 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 67 over it, 1.67× 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: BatchAttributeManager.handleBatch databox/api/src/Attribute/BatchAttributeManager.php:92— MethodTooLong — handleBatch runs 162 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 62 over it, 1.62× 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: AssetExportProcessHandler.__invoke databox/api/src/Consumer/Handler/Asset/AssetExportProcessHandler.php:66— MethodTooLong — __invoke runs 138 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 38 over it, 1.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.
MethodTooLong: CollectionVoter.doVote databox/api/src/Security/Voter/CollectionVoter.php:47— MethodTooLong — doVote runs 135 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 35 over it, 1.35× 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: Parser.criteria databox/client/src/features/search/aql/parser.ts:270— MethodTooLong — criteria runs 125 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 25 over it, 1.25× 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: Version20260610134844.up databox/api/migrations/Version20260610134844.php:21— MethodTooLong — up runs 123 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 23 over it, 1.23× 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: WorkspaceCreator.createWorkspace databox/api/src/Service/Workspace/WorkspaceCreator.php:28— MethodTooLong — createWorkspace runs 111 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 11 over it, 1.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.
MethodTooLong: AttributeEntityMergeHandler.__invoke databox/api/src/Consumer/Handler/Search/AttributeEntityMergeHandler.php:37— MethodTooLong — __invoke runs 107 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 7 over it, 1.07× 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: VideoSummaryTransformerModule.transform lib/php/rendition-factory/src/Transformer/Video/VideoSummaryTransformerModule.php:127— MethodTooLong — transform runs 103 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 3 over it, 1.03× 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: AQLGrammar.match_value databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1801— MethodTooLong — match_value runs 102 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 2 over it, 1.02× 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.
R6 · Tooling· This package's lint script runs in no CI job · ×13
This package's lint script runs in no CI job dashboard/client/package.json:11— The package in `dashboard/client` declares the lint script `lint` (`eslint src`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `dashboard/client` (or the workspace's task runner).
This package's lint script runs in no CI job databox/client/package.json:11— The package in `databox/client` declares the lint script `lint` (`eslint src`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `databox/client` (or the workspace's task runner).
This package's lint script runs in no CI job databox/indexer/package.json:20— The package in `databox/indexer` declares the lint script `lint` (`eslint src tests`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `databox/indexer` (or the workspace's task runner).
This package's lint script runs in no CI job expose/client/package.json:11— The package in `expose/client` declares the lint script `lint` (`eslint src`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `expose/client` (or the workspace's task runner).
This package's lint script runs in no CI job uploader/client/package.json:11— The package in `uploader/client` declares the lint script `lint` (`eslint src`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `uploader/client` (or the workspace's task runner).
This package's lint script runs in no CI job lib/js/api/package.json:11— The package in `lib/js/api` declares the lint script `lint` (`eslint src`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `lib/js/api` (or the workspace's task runner).
This package's lint script runs in no CI job lib/js/auth/package.json:14— The package in `lib/js/auth` declares the lint script `lint` (`eslint src`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `lib/js/auth` (or the workspace's task runner).
This package's lint script runs in no CI job lib/js/core/package.json:12— The package in `lib/js/core` declares the lint script `lint` (`eslint src`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `lib/js/core` (or the workspace's task runner).
This package's lint script runs in no CI job lib/js/next-core/package.json:31— The package in `lib/js/next-core` declares the lint script `lint` (`eslint src`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `lib/js/next-core` (or the workspace's task runner).
This package's lint script runs in no CI job lib/js/next-i18n/package.json:19— The package in `lib/js/next-i18n` declares the lint script `lint` (`eslint src`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `lib/js/next-i18n` (or the workspace's task runner).
This package's lint script runs in no CI job lib/js/next-theme/package.json:25— The package in `lib/js/next-theme` declares the lint script `lint` (`eslint src`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `lib/js/next-theme` (or the workspace's task runner).
This package's lint script runs in no CI job lib/js/next-ui/package.json:26— The package in `lib/js/next-ui` declares the lint script `lint` (`eslint src`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `lib/js/next-ui` (or the workspace's task runner).
This package's lint script runs in no CI job lib/js/storage/package.json:7— The package in `lib/js/storage` declares the lint script `lint` (`eslint src`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `lib/js/storage` (or the workspace's task runner).
D30 · Dependency Vulnerabilities· Medium CVE · ×12
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
D4 · Code Duplication· Edited copy of a member (6 corresponding lines) · ×12
Edited copy of a member (6 corresponding lines) lib/php/rendition-factory/src/Transformer/Video/VideoTransformer.php:170— lib/php/rendition-factory/src/Transformer/Video/VideoTransformer.php:170-175 | lib/php/rendition-factory/src/Transformer/Video/AudioTransformer.php:126-131 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) uploader/api/src/Api/Processor/TargetDataProcessor.php:27— uploader/api/src/Api/Processor/TargetDataProcessor.php:27-32 | uploader/api/src/Api/Processor/TargetFormProcessor.php:27-32 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) databox/api/src/Integration/Aws/Rekognition/Message/RekognitionAnalyzeHandler.php:25— databox/api/src/Integration/Aws/Rekognition/Message/RekognitionAnalyzeHandler.php:25-32 | databox/api/src/Integration/RemoveBg/Message/RemoveBgCallHandler.php:25-30 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) databox/api/src/Controller/Admin/AssetDataTemplateCrudController.php:50— databox/api/src/Controller/Admin/AssetDataTemplateCrudController.php:50-55 | databox/api/src/Controller/Admin/CollectionCrudController.php:64-69 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) expose/api/src/Storage/AssetManager.php:107— expose/api/src/Storage/AssetManager.php:107-118 | uploader/api/src/Storage/AssetManager.php:61-66 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) databox/api/src/Controller/Admin/BasketCrudController.php:53— databox/api/src/Controller/Admin/BasketCrudController.php:53-59 | databox/api/src/Controller/Admin/ThreadCrudController.php:31-36 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) databox/api/src/Integration/AbstractIntegrationAction.php:42— databox/api/src/Integration/AbstractIntegrationAction.php:42-49 | expose/api/src/Storage/AssetManager.php:183-188 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) databox/api/src/Admin/Field/PrivacyField.php:19— databox/api/src/Admin/Field/PrivacyField.php:19-24 | lib/php/admin-bundle/Field/Acl/UserTypeChoiceField.php:12-19 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) databox/api/src/Elasticsearch/FilteredPager.php:22— databox/api/src/Elasticsearch/FilteredPager.php:22-27 | databox/api/src/Elasticsearch/MappedPager.php:30-35 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) lib/php/storage-bundle/Storage/FileStorageManager.php:40— lib/php/storage-bundle/Storage/FileStorageManager.php:40-45 | lib/php/workflow/src/WorkflowOrchestrator.php:295-300 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) databox/api/src/Controller/Admin/AttributeDefinitionCrudController.php:148— databox/api/src/Controller/Admin/AttributeDefinitionCrudController.php:148-153 | databox/api/src/Form/Type/AttributeTypeChoiceType.php:20-28 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) lib/php/configurator-bundle/src/Field/FileField.php:19— lib/php/configurator-bundle/src/Field/FileField.php:19-25 | lib/php/webhook-bundle/Field/EventsChoiceField.php:17-22 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (8 lines × 2) databox/api/src/Api/Processor/FollowProcessor.php:32— databox/api/src/Api/Processor/FollowProcessor.php:32-39 | databox/api/src/Api/Processor/UnfollowProcessor.php:32-39 — before extracting anything, compare `databox/api/src/Api/Processor/FollowProcessor.php` and `databox/api/src/Api/Processor/UnfollowProcessor.php` as WHOLE FILES: 93% 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 `databox/api/src/Api/Processor/FollowProcessor.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 (8 lines × 2) databox/api/src/Api/Provider/ShareAttachmentProvider.php:34— databox/api/src/Api/Provider/ShareAttachmentProvider.php:34-41 | databox/api/src/Api/Provider/ShareRenditionProvider.php:47-54 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. 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) databox/api/src/Border/FileAnalyzer.php:79— databox/api/src/Border/FileAnalyzer.php:79-86 | databox/api/src/Border/FileAnalyzer.php:123-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. Read the line range as the matched WINDOW rather than a finished unit: at `databox/api/src/Border/FileAnalyzer.php:79` 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 lines × 2) databox/api/src/Consumer/Handler/Asset/AssetsDeleteHandler.php:58— databox/api/src/Consumer/Handler/Asset/AssetsDeleteHandler.php:58-65 | databox/api/src/Consumer/Handler/Asset/AssetsRestoreHandler.php:35-42 — 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 `databox/api/src/Consumer/Handler/Asset/AssetsDeleteHandler.php:58` 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, `databox/api/src/Consumer/Handler/Asset/AssetsRestoreHandler.php:34` calls `disable` and `databox/api/src/Consumer/Handler/Asset/AssetsDeleteHandler.php:57` 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) databox/api/src/Doctrine/Delete/CollectionDelete.php:63— databox/api/src/Doctrine/Delete/CollectionDelete.php:63-70 | databox/api/src/Doctrine/Delete/WorkspaceDelete.php:84-91 — 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 `databox/api/src/Doctrine/Delete/CollectionDelete.php:63` 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, `databox/api/src/Doctrine/Delete/WorkspaceDelete.php:92` calls `enable` and `databox/api/src/Doctrine/Delete/CollectionDelete.php:71` 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) databox/api/src/Repository/Core/FileRepository.php:32— databox/api/src/Repository/Core/FileRepository.php:32-39 | databox/api/src/Repository/Core/FileRepository.php:61-68 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) databox/api/src/Service/Asset/RenditionBuilder.php:116— databox/api/src/Service/Asset/RenditionBuilder.php:116-123 | databox/api/src/Service/Asset/RenditionBuilder.php:280-287 — 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 `databox/api/src/Service/Asset/RenditionBuilder.php:116` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) uploader/api/src/Api/Provider/FormFieldOptionsProvider.php:40— uploader/api/src/Api/Provider/FormFieldOptionsProvider.php:40-47 | uploader/api/src/Api/Provider/TargetFormProvider.php:30-37 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (8 lines × 2) databox/api/src/Api/Mapper/Input/AbstractFileInputMapper.php:72— databox/api/src/Api/Mapper/Input/AbstractFileInputMapper.php:72-79 | databox/api/src/Service/Discussion/MessageAttachmentManager.php:70-77 — 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) expose/api/src/Kernel.php:34— expose/api/src/Kernel.php:34-41 | uploader/api/src/Kernel.php:43-50 — before extracting anything, compare `expose/api/src/Kernel.php` and `uploader/api/src/Kernel.php` as WHOLE FILES: 92% 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.
Duplicated block (8 lines × 2) databox/api/src/Entity/Core/FileMetadata.php:48— databox/api/src/Entity/Core/FileMetadata.php:48-55 | databox/api/src/Entity/Core/FileOverriddenMetadata.php:62-69 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (8 lines × 2) databox/api/src/Repository/Core/AttributeDefinitionRepository.php:261— databox/api/src/Repository/Core/AttributeDefinitionRepository.php:261-268 | databox/api/src/Repository/Core/CollectionRepository.php:36-43 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
DM11 · Constructible invalid state· Constructible in an invalid state · ×12
Constructible in an invalid state: AutomationSeenAsset databox/api/src/Entity/Automation/AutomationSeenAsset.php:38— `AutomationSeenAsset`'s public constructor takes `runId` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `AutomationSeenAsset` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
Constructible in an invalid state: Asset databox/api/src/Entity/Core/Asset.php:619— `Asset`'s public constructor takes `now`, `sequence` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `Asset` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
Constructible in an invalid state: AssetImportError databox/api/src/Entity/Core/AssetImportError.php:73— `AssetImportError`'s public constructor takes `line`, `key`, `message` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `AssetImportError` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
Constructible in an invalid state: FileAnalysis databox/api/src/Entity/Core/FileAnalysis.php:46— `FileAnalysis`'s public constructor takes `status` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `FileAnalysis` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
Constructible in an invalid state: Broadcast lib/php/notifier-bundle/src/Entity/Broadcast.php:86— `Broadcast`'s public constructor takes `topic`, `directory` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `Broadcast` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
Constructible in an invalid state: Notification lib/php/notifier-bundle/src/Entity/Notification.php:47— `Notification`'s public constructor takes `topic` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `Notification` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
Constructible in an invalid state: NotificationPreference lib/php/notifier-bundle/src/Entity/NotificationPreference.php:38— `NotificationPreference`'s public constructor takes `topic` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `NotificationPreference` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
Constructible in an invalid state: Subscriber lib/php/notifier-bundle/src/Entity/Subscriber.php:41— `Subscriber`'s public constructor takes `userId` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `Subscriber` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
Constructible in an invalid state: JobState lib/php/workflow-bundle/Entity/JobState.php:41— `JobState`'s public constructor takes `id`, `jobId` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `JobState` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
Constructible in an invalid state: WorkflowState lib/php/workflow-bundle/Entity/WorkflowState.php:39— `WorkflowState`'s public constructor takes `id` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `WorkflowState` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
Constructible in an invalid state: Job lib/php/workflow/src/Model/Job.php:26— `Job`'s public constructor takes `id` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `Job` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
Constructible in an invalid state: Step lib/php/workflow/src/Model/Step.php:16— `Step`'s public constructor takes `id`, `name` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `Step` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
Duplicated block (7 lines × 2) databox/api/src/Controller/Admin/AutomationRunCrudController.php:43— databox/api/src/Controller/Admin/AutomationRunCrudController.php:43-49 | databox/api/src/Controller/Admin/SavedSearchAutomationCrudController.php:47-53 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 2) databox/api/src/Doctrine/Delete/CollectionDelete.php:53— databox/api/src/Doctrine/Delete/CollectionDelete.php:53-59 | databox/api/src/Doctrine/Delete/WorkspaceDelete.php:74-81 — 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 `databox/api/src/Doctrine/Delete/CollectionDelete.php:53` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) databox/api/src/Elasticsearch/AQL/AQLGrammar.php:190— databox/api/src/Elasticsearch/AQL/AQLGrammar.php:190-196 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1751-1757 — 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 `databox/api/src/Elasticsearch/AQL/AQLGrammar.php:190` 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 (7 lines × 2) databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1613— databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1613-1619 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1722-1728 — 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 `databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1613` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) databox/api/src/Integration/Phraseanet/PhraseanetGenerateAssetRenditionsAction.php:61— databox/api/src/Integration/Phraseanet/PhraseanetGenerateAssetRenditionsAction.php:61-67 | databox/api/src/Integration/Phraseanet/PhraseanetGenerateAssetRenditionsEnqueueMethodAction.php:50-56 — 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 `databox/api/src/Integration/Phraseanet/PhraseanetGenerateAssetRenditionsAction.php:61` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) lib/php/notifier-bundle/src/Controller/Admin/NotificationCrudController.php:40— lib/php/notifier-bundle/src/Controller/Admin/NotificationCrudController.php:40-46 | lib/php/notifier-bundle/src/Controller/Admin/NotificationPreferenceCrudController.php:40-46 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 2) databox/api/src/Consumer/Handler/Collection/CollectionsMoveToTrashHandler.php:26— databox/api/src/Consumer/Handler/Collection/CollectionsMoveToTrashHandler.php:26-32 | databox/api/src/Consumer/Handler/Collection/CollectionsRestoreHandler.php:26-32 — 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, `databox/api/src/Consumer/Handler/Collection/CollectionsMoveToTrashHandler.php:33` calls `setParameter`, `DateTimeImmutable` and `databox/api/src/Consumer/Handler/Collection/CollectionsRestoreHandler.php:33` 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 (7 lines × 2) databox/api/src/Elasticsearch/AQL/AQLGrammar.php:17— databox/api/src/Elasticsearch/AQL/AQLGrammar.php:17-23 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1499-1505 — 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 lines × 2) databox/api/src/Integration/Core/Rendition/RenditionBuildAction.php:45— databox/api/src/Integration/Core/Rendition/RenditionBuildAction.php:45-52 | databox/api/src/Service/Workflow/Action/ReadMetadataAction.php:48-54 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 2) databox/api/src/Model/AuditActorTypeEnum.php:24— databox/api/src/Model/AuditActorTypeEnum.php:24-30 | databox/api/src/Model/AuditLogActionEnum.php:51-57 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 2) databox/api/src/Repository/Basket/BasketRepository.php:44— databox/api/src/Repository/Basket/BasketRepository.php:44-50 | databox/api/src/Repository/Profile/ProfileRepository.php:38-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.
ClassTooLong: AQLGrammar databox/api/src/Elasticsearch/AQL/AQLGrammar.php:7— ClassTooLong — 1619 significant lines (blank, comment-only and punctuation-only lines excluded), 67 methods. The bar is 400 significant lines; this is 1219 over it, 4.05× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: AttributeBatchEditorRoute databox/client/src/features/attributes/batch/AttributeBatchEditorRoute.tsx:1— ClassTooLong — 860 significant lines (blank, comment-only and punctuation-only lines excluded), 12 methods. The bar is 400 significant lines; this is 460 over it, 2.15× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: UploadDialog databox/client/src/features/upload/UploadDialog.tsx:1— ClassTooLong — 643 significant lines (blank, comment-only and punctuation-only lines excluded), 2 methods. The bar is 400 significant lines; this is 243 over it, 1.61× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: AnnotationLayer databox/client/src/features/annotations/AnnotationLayer.tsx:1— ClassTooLong — 601 significant lines (blank, comment-only and punctuation-only lines excluded), 6 methods. The bar is 400 significant lines; this is 201 over it, 1.50× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: EntityGrid databox/client/src/features/workspaces/manage/entities/EntityGrid.tsx:1— ClassTooLong — 500 significant lines (blank, comment-only and punctuation-only lines excluded), 3 methods. The bar is 400 significant lines; this is 100 over it, 1.25× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: DataTable databox/client/src/components/ui/data-table/DataTable.tsx:1— ClassTooLong — 460 significant lines (blank, comment-only and punctuation-only lines excluded), 3 methods. The bar is 400 significant lines; this is 60 over it, 1.15× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: UploadScreen uploader/client/src/features/upload/UploadScreen.tsx:1— ClassTooLong — 447 significant lines (blank, comment-only and punctuation-only lines excluded), 13 methods. The bar is 400 significant lines; this is 47 over it, 1.12× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: MessageComposer databox/client/src/features/discussion/MessageComposer.tsx:1— ClassTooLong — 446 significant lines (blank, comment-only and punctuation-only lines excluded), 8 methods. The bar is 400 significant lines; this is 46 over it, 1.12× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: ClipEditorDialog databox/client/src/features/clip/ClipEditorDialog.tsx:1— ClassTooLong — 432 significant lines (blank, comment-only and punctuation-only lines excluded), 3 methods. The bar is 400 significant lines; this is 32 over it, 1.08× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: ThemeEditorScreen databox/client/src/features/theme/ThemeEditorScreen.tsx:1— ClassTooLong — 420 significant lines (blank, comment-only and punctuation-only lines excluded), 7 methods. The bar is 400 significant lines; this is 20 over it, 1.05× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Duplicated block (10 lines × 2) databox/api/src/Automation/Action/AddToCollectionAction.php:32— databox/api/src/Automation/Action/AddToCollectionAction.php:32-41 | databox/api/src/Automation/Action/MoveToCollectionAction.php:35-44 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (10 lines × 2) databox/api/src/Command/FaceRecognitionRelinkCommand.php:58— databox/api/src/Command/FaceRecognitionRelinkCommand.php:58-67 | databox/api/src/Command/SimilarityIndexCommand.php:63-72 — 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 `databox/api/src/Command/FaceRecognitionRelinkCommand.php:58` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) databox/api/src/Elasticsearch/AQL/AQLGrammar.php:208— databox/api/src/Elasticsearch/AQL/AQLGrammar.php:208-217 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1769-1778 — 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 `databox/api/src/Elasticsearch/AQL/AQLGrammar.php:208` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 2) databox/api/src/Elasticsearch/AQL/AQLGrammar.php:672— databox/api/src/Elasticsearch/AQL/AQLGrammar.php:672-681 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1772-1781 — 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 `databox/api/src/Elasticsearch/AQL/AQLGrammar.php:672` 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 (10 lines × 2) databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1171— databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1171-1180 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1444-1453 — 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 `databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1171` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) databox/api/src/Integration/Core/FaceRecognition/FaceRecognitionIntegration.php:179— databox/api/src/Integration/Core/FaceRecognition/FaceRecognitionIntegration.php:179-188 | databox/api/src/Integration/Core/Similarity/SimilarityIntegration.php:71-80 — 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 `databox/api/src/Integration/Core/FaceRecognition/FaceRecognitionIntegration.php:179` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) databox/api/src/Api/Filter/ExactSearchFilter.php:136— databox/api/src/Api/Filter/ExactSearchFilter.php:136-145 | uploader/api/src/Api/Filter/ExactSearchFilter.php:99-108 — before extracting anything, compare `databox/api/src/Api/Filter/ExactSearchFilter.php` and `uploader/api/src/Api/Filter/ExactSearchFilter.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 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.
Duplicated block (10 lines × 2) databox/api/src/Api/Processor/ArchiveBasketProcessor.php:23— databox/api/src/Api/Processor/ArchiveBasketProcessor.php:23-32 | databox/api/src/Api/Processor/UnarchiveBasketProcessor.php:23-32 — before extracting anything, compare `databox/api/src/Api/Processor/ArchiveBasketProcessor.php` and `databox/api/src/Api/Processor/UnarchiveBasketProcessor.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. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The `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.
X2 · Cancellation propagation· Async function without AbortSignal · ×8
Async function without AbortSignal: saveUrlAs lib/js/next-ui/src/utils/misc.ts:91— `saveUrlAs` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: refresh lib/js/next-core/src/auth/oidc.ts:383— `refresh` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: doHandleCallback lib/js/next-core/src/auth/oidc.ts:638— `doHandleCallback` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: createJiraIssue databox/client/src/lib/ticketing/jira.ts:56— `createJiraIssue` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: attachScreenshot databox/client/src/lib/ticketing/jira.ts:106— `attachScreenshot` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: resolveSession databox/client/src/lib/ticketing/session.ts:54— `resolveSession` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: fetchRemoteValues databox/client/src/features/search/suggest/remoteValues.ts:39— `fetchRemoteValues` holds an AbortSignal but calls `getTags(…)` without it, so its caller's cancellation never reaches that call and it runs to its end after whatever wanted it has given up. Hand the signal on: `getTags(…, { signal })`.
Async function without AbortSignal: fetchStatuses dashboard/client/src/features/status/useServiceStatuses.ts:8— `fetchStatuses` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Swallowed exception (caught, then discarded) lib/php/workflow-bundle/Entity/WorkflowState.php:83— `catch (\Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) lib/php/workflow-bundle/Entity/WorkflowState.php:92— `catch (\Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) lib/php/workflow-bundle/Entity/WorkflowState.php:101— `catch (\Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) lib/php/workflow-bundle/Entity/WorkflowState.php:110— `catch (\Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) lib/php/rendition-factory/src/Image/ColorspaceDetector.php:93— `catch (\Throwable)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) expose/api/src/Security/PasswordTokenExtractor.php: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.
Swallowed exception (caught, then discarded) databox/client/src/features/stories/useStoryRenditionRefresh.ts:59— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included.
Swallowed exception (caught, then discarded) databox/client/src/features/integrations/rekognition/RekognitionPanel.tsx:79— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included.
D4 · Code Duplication· Edited copy of a member (4 corresponding lines) · ×7
Edited copy of a member (4 corresponding lines) expose/api/src/Controller/ClientLogAction.php:75— expose/api/src/Controller/ClientLogAction.php:75-78 | expose/api/src/Security/DownloadRequestFactory.php:60-63 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (4 corresponding lines) databox/api/src/Api/Provider/BasketAssetCollectionProvider.php:25— databox/api/src/Api/Provider/BasketAssetCollectionProvider.php:25-28 | databox/api/src/Api/Provider/ProfileItemCollectionProvider.php:25-28 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (4 corresponding lines) databox/api/src/Api/Mapper/Input/SavedSearchAutomationInputMapper.php:231— databox/api/src/Api/Mapper/Input/SavedSearchAutomationInputMapper.php:231-234 | databox/api/src/Automation/Action/AbstractAutomationAction.php:34-39 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (4 corresponding lines) databox/api/src/Entity/Core/Collection.php:326— databox/api/src/Entity/Core/Collection.php:326-329 | databox/api/src/Entity/Core/Tag.php:159-162 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (4 corresponding lines) databox/api/src/Integration/Blurhash/BlurhashAction.php:62— databox/api/src/Integration/Blurhash/BlurhashAction.php:62-65 | databox/api/src/Integration/Happyscribe/HappyscribeAction.php:154-157 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (4 corresponding lines) databox/api/src/Controller/Admin/JobStateCrudController.php:81— databox/api/src/Controller/Admin/JobStateCrudController.php:81-84 | databox/api/src/Controller/Admin/WorkflowStateCrudController.php:44-47 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (4 corresponding lines) databox/api/src/Controller/Admin/AssetEmbeddingCrudController.php:33— databox/api/src/Controller/Admin/AssetEmbeddingCrudController.php:33-37 | databox/api/src/Controller/Admin/OperationTaskCrudController.php:57-60 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (5 lines × 2) databox/api/src/Attribute/Type/KeywordAttributeType.php:44— databox/api/src/Attribute/Type/KeywordAttributeType.php:44-48 | databox/api/src/Attribute/Type/TextAttributeType.php:93-97 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (5 lines × 2) databox/api/src/Controller/Admin/EntityListCrudController.php:30— databox/api/src/Controller/Admin/EntityListCrudController.php:30-34 | databox/api/src/Controller/Admin/TagCrudController.php:41-45 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (5 lines × 2) databox/api/src/Entity/Core/AttributeDefinition.php:479— databox/api/src/Entity/Core/AttributeDefinition.php:479-483 | databox/api/src/Entity/Core/RenditionDefinition.php:401-405 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (5 lines × 2) expose/api/src/Serializer/EntityNormalizer.php:23— expose/api/src/Serializer/EntityNormalizer.php:23-27 | uploader/api/src/Serializer/EntityNormalizer.php:23-27 — 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) lib/php/admin-bundle/Filter/AssociationIdentifierFilter.php:79— lib/php/admin-bundle/Filter/AssociationIdentifierFilter.php:79-83 | lib/php/admin-bundle/Filter/ChildPropertyEntityFilter.php:103-107 — before extracting anything, compare `lib/php/admin-bundle/Filter/AssociationIdentifierFilter.php` and `lib/php/admin-bundle/Filter/ChildPropertyEntityFilter.php` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 57 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) lib/php/workflow/src/State/Repository/JobStatusCacheTrait.php:94— lib/php/workflow/src/State/Repository/JobStatusCacheTrait.php:94-98 | lib/php/workflow/src/State/Repository/MemoryStateRepository.php:125-129 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (5 lines × 2) databox/api/src/Elasticsearch/FacetHandler.php:55— databox/api/src/Elasticsearch/FacetHandler.php:55-59 | databox/api/src/Elasticsearch/FacetHandler.php:63-67 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication· Edited copy of a member (14 corresponding lines) · ×6
Edited copy of a member (14 corresponding lines) databox/api/src/Security/Voter/AttributePolicyVoter.php:32— databox/api/src/Security/Voter/AttributePolicyVoter.php:32-46 | databox/api/src/Security/Voter/RenditionPolicyVoter.php:32-45 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) lib/php/notifier-bundle/src/Controller/NotificationController.php:77— lib/php/notifier-bundle/src/Controller/NotificationController.php:77-98 | lib/php/notifier-bundle/src/Controller/NotificationController.php:104-117 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) databox/api/src/Controller/Admin/ProfileCrudController.php:63— databox/api/src/Controller/Admin/ProfileCrudController.php:63-79 | databox/api/src/Controller/Admin/SavedSearchCrudController.php:62-75 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) lib/php/auth-bundle/Controller/PermissionsController.php:38— lib/php/auth-bundle/Controller/PermissionsController.php:38-51 | lib/php/auth-bundle/Controller/PermissionsController.php:60-73 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) databox/api/src/Repository/Core/FileRepository.php:30— databox/api/src/Repository/Core/FileRepository.php:30-43 | databox/api/src/Repository/Core/FileRepository.php:105-118 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) databox/api/src/Validator/ValidAQLConstraintValidator.php:24— databox/api/src/Validator/ValidAQLConstraintValidator.php:24-41 | databox/api/src/Validator/YamlConstraintValidator.php:20-33 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (12 lines × 2) databox/api/src/Api/Extension/PageExtension.php:32— databox/api/src/Api/Extension/PageExtension.php:32-43 | databox/api/src/Api/Extension/WorkspaceExtension.php:70-81 — 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 `databox/api/src/Api/Extension/PageExtension.php:32` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) databox/api/src/Border/FileAnalyzer/Analyzer/ImageColorspaceAnalyzer.php:81— databox/api/src/Border/FileAnalyzer/Analyzer/ImageColorspaceAnalyzer.php:81-92 | databox/api/src/Border/FileAnalyzer/Analyzer/ImageDimensionAnalyzer.php:67-78 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (12 lines × 2) databox/api/src/Service/Storage/RenditionManager.php:238— databox/api/src/Service/Storage/RenditionManager.php:238-249 | databox/api/src/Service/Storage/RenditionManager.php:260-271 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (12 lines × 2) expose/api/src/Api/Upload/UploadRequestResolver.php:66— expose/api/src/Api/Upload/UploadRequestResolver.php:66-77 | uploader/api/src/Api/Processor/CreateAssetProcessor.php:94-105 — 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 (12 lines × 2) lib/php/rendition-factory/src/Transformer/Video/AudioTransformer.php:48— lib/php/rendition-factory/src/Transformer/Video/AudioTransformer.php:48-59 | lib/php/rendition-factory/src/Transformer/Video/VideoTransformer.php:67-78 — before extracting anything, compare `lib/php/rendition-factory/src/Transformer/Video/AudioTransformer.php` and `lib/php/rendition-factory/src/Transformer/Video/VideoTransformer.php` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 64 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/php/rendition-factory/src/Transformer/Video/AudioTransformer.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 (12 lines × 2) lib/php/rendition-factory/src/Transformer/Video/VideoSummaryTransformerModule.php:173— lib/php/rendition-factory/src/Transformer/Video/VideoSummaryTransformerModule.php:173-184 | lib/php/rendition-factory/src/Transformer/Video/VideoTransformer.php:43-54 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `lib/php/rendition-factory/src/Transformer/Video/VideoSummaryTransformerModule.php:173` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) databox/api/src/Api/Mapper/Input/WorkspaceEnvInputMapper.php:26— databox/api/src/Api/Mapper/Input/WorkspaceEnvInputMapper.php:26-34 | databox/api/src/Api/Mapper/Input/WorkspaceSecretInputMapper.php:26-34 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `databox/api/src/Api/Mapper/Input/WorkspaceEnvInputMapper.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 (9 lines × 2) databox/api/src/Api/Serializer/SecurityContextBuilder.php:24— databox/api/src/Api/Serializer/SecurityContextBuilder.php:24-32 | uploader/api/src/Serializer/AppContextBuilder.php:25-33 — 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 (9 lines × 2) databox/api/src/Consumer/Handler/Asset/AssetExportProcessHandler.php:167— databox/api/src/Consumer/Handler/Asset/AssetExportProcessHandler.php:167-175 | databox/api/src/Consumer/Handler/Asset/AssetExportProcessHandler.php:178-186 — 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 `databox/api/src/Consumer/Handler/Asset/AssetExportProcessHandler.php:167` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) databox/api/src/Security/Voter/ProfileVoter.php:40— databox/api/src/Security/Voter/ProfileVoter.php:40-48 | databox/api/src/Security/Voter/SavedSearchVoter.php:41-49 — before extracting anything, compare `databox/api/src/Security/Voter/ProfileVoter.php` and `databox/api/src/Security/Voter/SavedSearchVoter.php` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 36 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `databox/api/src/Security/Voter/ProfileVoter.php:40` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) lib/php/admin-bundle/Field/UserChoiceField.php:19— lib/php/admin-bundle/Field/UserChoiceField.php:19-27 | lib/php/admin-bundle/Filter/UserChoiceFilter.php:19-27 — 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) lib/php/rendition-factory/src/Transformer/Image/Imagine/Filter/StampFilter.php:91— lib/php/rendition-factory/src/Transformer/Image/Imagine/Filter/StampFilter.php:91-99 | lib/php/rendition-factory/src/Transformer/Image/Imagine/Filter/StampFilter.php:108-116 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) databox/api/src/Elasticsearch/AQL/AQLGrammar.php:645— databox/api/src/Elasticsearch/AQL/AQLGrammar.php:645-650 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:662-667 — 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 `databox/api/src/Elasticsearch/AQL/AQLGrammar.php:645` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) databox/api/src/Security/Voter/AssetVoter.php:55— databox/api/src/Security/Voter/AssetVoter.php:55-60 | databox/api/src/Security/Voter/CollectionVoter.php:61-67 — 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 `databox/api/src/Security/Voter/AssetVoter.php:55` 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 (6 lines × 2) databox/api/src/Security/Voter/AttributePolicyVoter.php:32— databox/api/src/Security/Voter/AttributePolicyVoter.php:32-37 | databox/api/src/Security/Voter/EntityListVoter.php:37-42 — 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) databox/api/src/Security/Voter/ProfileVoter.php:50— databox/api/src/Security/Voter/ProfileVoter.php:50-55 | databox/api/src/Security/Voter/SavedSearchVoter.php:51-56 — before extracting anything, compare `databox/api/src/Security/Voter/ProfileVoter.php` and `databox/api/src/Security/Voter/SavedSearchVoter.php` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 36 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 2) databox/api/src/Integration/IntegrationDataManager.php:29— databox/api/src/Integration/IntegrationDataManager.php:29-34 | databox/api/src/Integration/IntegrationManager.php:63-68 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The `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) expose/api/src/Kernel.php:19— expose/api/src/Kernel.php:19-24 | uploader/api/src/Kernel.php:20-25 — before extracting anything, compare `expose/api/src/Kernel.php` and `uploader/api/src/Kernel.php` as WHOLE FILES: 92% 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.
AC2 · Forms & labels· <CommandInput> field component without a label · ×5
<CommandInput> field component without a label databox/client/src/features/impersonation/SwitchUserDialog.tsx:87— 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.
<CommandInput> field component without a label databox/client/src/features/integrations/config/pickers/OAuthClientPicker.tsx:147— 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.
<CommandInput> field component without a label databox/client/src/features/integrations/config/pickers/SecretReferencePicker.tsx:275— 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.
<CommandInput> field component without a label databox/client/src/features/preferences/DataLocaleDialog.tsx:56— 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.
<CommandInput> field component without a label databox/client/src/features/search/conditions/ConditionBuilder.tsx:545— 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.
Focus outline removed inline dashboard/client/src/features/dashboard/ServiceCardView.tsx:136— <a> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline databox/client/src/features/annotations/TextEditor.tsx:73— <textarea> takes keyboard focus, and outline:none/0 in its inline style removes the focus ring with no chance of a :focus replacement (an inline style outranks every stylesheet rule). Keep a visible focus indicator.
Focus outline removed inline databox/client/src/features/integrations/config/pickers/SecretReferencePicker.tsx:230— <button> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline databox/client/src/features/share/ShareGallery.tsx:229— <button> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline databox/client/src/features/theme/ThemeEditorScreen.tsx:804— <input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Deprecated: tui-image-editor databox/client/package.json:65— tui-image-editor 3.15.3, declared in databox/client/package.json, is marked deprecated by its publisher: "Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: axios-retry databox/indexer/package.json:30— axios-retry 4.5.0, declared in databox/indexer/package.json, is marked deprecated by its publisher: "axios-retry is no longer maintained. See https://github.com/softonic/axios-retry for alternatives.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: @types/minio databox/indexer/package.json:43— @types/minio 7.1.1, declared in databox/indexer/package.json, is marked deprecated by its publisher: "This is a stub types definition. minio provides its own type definitions, so you do not need this installed.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: axios-retry lib/js/api/package.json:38— axios-retry 4.5.0, declared in lib/js/api/package.json, is marked deprecated by its publisher: "axios-retry is no longer maintained. See https://github.com/softonic/axios-retry for alternatives.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: @jonkoops/matomo-tracker-react lib/js/core/package.json:30— @jonkoops/matomo-tracker-react 0.7.0, declared in lib/js/core/package.json, is marked deprecated by its publisher: "This package is no longer maintained.". Replace it with the package or version that message names, or record why this one must stay.
D4 · Code Duplication· Edited copy of a member (11 corresponding lines) · ×5
Edited copy of a member (11 corresponding lines) lib/php/admin-bundle/Field/UserChoiceField.php:19— lib/php/admin-bundle/Field/UserChoiceField.php:19-29 | lib/php/admin-bundle/Filter/UserChoiceFilter.php:19-29 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) databox/api/src/Api/Provider/AutomationRunCollectionProvider.php:34— databox/api/src/Api/Provider/AutomationRunCollectionProvider.php:34-45 | databox/api/src/Api/Provider/SavedSearchAutomationCollectionProvider.php:34-44 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) databox/api/src/Doctrine/Delete/WorkspaceDelete.php:178— databox/api/src/Doctrine/Delete/WorkspaceDelete.php:178-188 | databox/api/src/Doctrine/Delete/WorkspaceDelete.php:207-217 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) databox/api/src/Attribute/Type/DateAttributeType.php:69— databox/api/src/Attribute/Type/DateAttributeType.php:69-79 | databox/api/src/Attribute/Type/DateTimeAttributeType.php:123-133 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) expose/api/src/Controller/GetPublicationCssAction.php:24— expose/api/src/Controller/GetPublicationCssAction.php:24-41 | expose/api/src/Controller/AbstractAssetAction.php:30-40 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (9 corresponding lines) · ×5
Edited copy of a member (9 corresponding lines) databox/api/src/Consumer/Handler/File/CopyFileToAssetHandler.php:25— databox/api/src/Consumer/Handler/File/CopyFileToAssetHandler.php:25-34 | databox/api/src/Consumer/Handler/File/CopyFileToRenditionHandler.php:25-33 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) databox/api/src/Attribute/BatchAttributeManager.php:395— databox/api/src/Attribute/BatchAttributeManager.php:395-403 | databox/api/src/Attribute/AttributeValidator.php:187-195 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) databox/api/src/Api/Provider/AssetAttachmentCollectionProvider.php:17— databox/api/src/Api/Provider/AssetAttachmentCollectionProvider.php:17-26 | databox/api/src/Api/Provider/AssetFileVersionCollectionProvider.php:14-22 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) databox/api/src/Integration/Auth/IntegrationTokenManager.php:82— databox/api/src/Integration/Auth/IntegrationTokenManager.php:82-91 | databox/api/src/Security/AttributeFilterManager.php:31-39 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) databox/api/src/Automation/Action/RemoteExportAction.php:322— databox/api/src/Automation/Action/RemoteExportAction.php:322-330 | databox/api/src/Automation/Export/RemoteDestinationConfig.php:210-218 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (10 corresponding lines) · ×5
Edited copy of a member (10 corresponding lines) databox/api/src/Api/Mapper/Output/WorkspaceEnvOutputMapper.php:30— databox/api/src/Api/Mapper/Output/WorkspaceEnvOutputMapper.php:30-40 | databox/api/src/Api/Mapper/Output/WorkspaceSecretOutputMapper.php:30-39 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) expose/api/src/Controller/AbstractAssetAction.php:45— expose/api/src/Controller/AbstractAssetAction.php:45-56 | expose/api/src/Controller/AbstractAssetAction.php:61-70 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) databox/api/src/Repository/Core/AttributeDefinitionRepository.php:276— databox/api/src/Repository/Core/AttributeDefinitionRepository.php:276-285 | databox/api/src/Repository/Core/AttributeDefinitionRepository.php:293-303 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) lib/php/admin-bundle/Form/GroupChoiceType.php:21— lib/php/admin-bundle/Form/GroupChoiceType.php:21-30 | lib/php/admin-bundle/Form/UserChoiceType.php:23-32 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) databox/api/src/Service/Import/ImportEntryNormalizer.php:131— databox/api/src/Service/Import/ImportEntryNormalizer.php:131-144 | databox/api/src/Integration/Phrasea/Expose/ExposeClient.php:124-133 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (16 lines × 2) databox/api/src/Automation/Action/AddToCollectionAction.php:46— databox/api/src/Automation/Action/AddToCollectionAction.php:46-61 | databox/api/src/Automation/Action/MoveToCollectionAction.php:49-64 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (16 lines × 2) databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1141— databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1141-1156 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1237-1252 — 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 `databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1141` 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) databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1190— databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1190-1205 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1463-1478 — 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 `databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1190` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 2) databox/api/src/Repository/Core/AttributeRepository.php:266— databox/api/src/Repository/Core/AttributeRepository.php:266-281 | databox/api/src/Repository/Core/AttributeRepository.php:342-357 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (16 lines × 2) expose/api/migrations/Version20210811113825.php:18— expose/api/migrations/Version20210811113825.php:18-33 | expose/api/migrations/Version20210811114618.php:18-33 — before extracting anything, compare `expose/api/migrations/Version20210811113825.php` and `expose/api/migrations/Version20210811114618.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 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. Read the line range as the matched WINDOW rather than a finished unit: at `expose/api/migrations/Version20210811113825.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 (13 lines × 2) databox/api/src/Api/Mapper/Input/AttributeInputMapper.php:36— databox/api/src/Api/Mapper/Input/AttributeInputMapper.php:36-48 | databox/api/src/Api/Mapper/Input/TemplateAttributeInputMapper.php:35-47 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `databox/api/src/Api/Mapper/Input/AttributeInputMapper.php:36` 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, `databox/api/src/Api/Mapper/Input/AttributeInputMapper.php:50` calls `resetAssetAttributesCache`, `getAsset` and `databox/api/src/Api/Mapper/Input/TemplateAttributeInputMapper.php:49` 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 × 2) databox/api/src/Elasticsearch/AQL/AQLGrammar.php:430— databox/api/src/Elasticsearch/AQL/AQLGrammar.php:430-442 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:495-507 — 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 `databox/api/src/Elasticsearch/AQL/AQLGrammar.php:430` 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 (13 lines × 2) databox/api/src/Integration/Aws/Rekognition/AwsRekognitionIntegration.php:323— databox/api/src/Integration/Aws/Rekognition/AwsRekognitionIntegration.php:323-335 | databox/api/src/Integration/Core/FaceRecognition/FaceRecognitionIntegration.php:188-200 — 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 `databox/api/src/Integration/Aws/Rekognition/AwsRekognitionIntegration.php:323` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) databox/api/src/Repository/Core/AttributeRepository.php:262— databox/api/src/Repository/Core/AttributeRepository.php:262-274 | databox/api/src/Repository/Core/AttributeRepository.php:313-325 — 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 `databox/api/src/Repository/Core/AttributeRepository.php:262` 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, `databox/api/src/Repository/Core/AttributeRepository.php:275` calls `andWhere` and `databox/api/src/Repository/Core/AttributeRepository.php:326` 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 (13 lines × 2) expose/api/src/Command/YamlToApiResourceCommand.php:171— expose/api/src/Command/YamlToApiResourceCommand.php:171-183 | uploader/api/src/Command/YamlToApiResourceCommand.php:171-183 — before extracting anything, compare `expose/api/src/Command/YamlToApiResourceCommand.php` and `uploader/api/src/Command/YamlToApiResourceCommand.php` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 152 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Anemic entity: AutomationSeenAsset databox/api/src/Entity/Automation/AutomationSeenAsset.php:18— `AutomationSeenAsset` 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.
Anemic entity: AutomationShare databox/api/src/Entity/Automation/AutomationShare.php:19— `AutomationShare` 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: AssetImportError databox/api/src/Entity/Core/AssetImportError.php:21— `AssetImportError` 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.
Anemic entity: NotificationDigest lib/php/notifier-bundle/src/Entity/NotificationDigest.php:22— `NotificationDigest` is an aggregate/entity with 7 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
Anemic entity: Subscription lib/php/notifier-bundle/src/Entity/Subscription.php:16— `Subscription` 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.
D4 · Code Duplication· Edited copy of a member (15 corresponding lines) · ×4
Edited copy of a member (15 corresponding lines) databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1605— databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1605-1619 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1714-1728 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) lib/php/auth-bundle/Controller/GroupsController.php:47— lib/php/auth-bundle/Controller/GroupsController.php:47-61 | lib/php/auth-bundle/Controller/GroupsController.php:67-83 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) lib/php/core-bundle/Mapping/ObjectMapping.php:15— lib/php/core-bundle/Mapping/ObjectMapping.php:15-29 | lib/php/core-bundle/Mapping/ObjectMapping.php:59-73 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) databox/api/src/OperationTask/OperationTaskManager.php:117— databox/api/src/OperationTask/OperationTaskManager.php:117-131 | databox/api/src/OperationTask/OperationTaskProgress.php:62-76 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (22 corresponding lines) · ×4
Edited copy of a member (22 corresponding lines) databox/api/src/Integration/Aws/Rekognition/AwsRekognitionIntegration.php:309— databox/api/src/Integration/Aws/Rekognition/AwsRekognitionIntegration.php:309-335 | databox/api/src/Integration/Core/FaceRecognition/FaceRecognitionIntegration.php:179-200 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (22 corresponding lines) databox/api/src/Api/Extension/PageExtension.php:31— databox/api/src/Api/Extension/PageExtension.php:31-52 | databox/api/src/Api/Extension/WorkspaceExtension.php:61-90 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (22 corresponding lines) databox/api/src/Automation/Action/RemoteExportAction.php:58— databox/api/src/Automation/Action/RemoteExportAction.php:58-79 | databox/api/src/Automation/Action/ShareExportAction.php:97-125 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (22 corresponding lines) databox/api/src/Automation/Action/SetPrivacyAction.php:46— databox/api/src/Automation/Action/SetPrivacyAction.php:46-72 | databox/api/src/Automation/Action/TrashAction.php:33-54 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (19 lines × 2) databox/api/src/Automation/Action/AttributeAction.php:133— databox/api/src/Automation/Action/AttributeAction.php:133-151 | databox/api/src/Automation/Action/TagsAction.php:77-95 — 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 `databox/api/src/Automation/Action/AttributeAction.php:133` 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 (19 lines × 2) databox/api/src/Documentation/FileAnalyzersDocumentationGenerator.php:53— databox/api/src/Documentation/FileAnalyzersDocumentationGenerator.php:53-71 | lib/php/rendition-factory/src/RenditionBuilderTransformersDocumentation.php:50-68 — 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 `databox/api/src/Documentation/FileAnalyzersDocumentationGenerator.php:53` 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. 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 × 2) databox/api/src/Elasticsearch/AQL/AQLGrammar.php:453— databox/api/src/Elasticsearch/AQL/AQLGrammar.php:453-471 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:498-516 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (19 lines × 2) lib/php/rendition-factory/src/Transformer/Video/VideoToAnimationTransformerModule.php:132— lib/php/rendition-factory/src/Transformer/Video/VideoToAnimationTransformerModule.php:132-150 | lib/php/rendition-factory/src/Transformer/Video/VideoToFrameTransformerModule.php:112-130 — before extracting anything, compare `lib/php/rendition-factory/src/Transformer/Video/VideoToAnimationTransformerModule.php` and `lib/php/rendition-factory/src/Transformer/Video/VideoToFrameTransformerModule.php` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 78 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 3) databox/api/src/Elasticsearch/AQL/AQLGrammar.php:85— databox/api/src/Elasticsearch/AQL/AQLGrammar.php:85-92 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:158-165 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1215-1222 — 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 (8 lines × 3) databox/api/src/Security/Voter/PageVoter.php:34— databox/api/src/Security/Voter/PageVoter.php:34-41 | databox/api/src/Security/Voter/ProfileVoter.php:40-47 | databox/api/src/Security/Voter/SavedSearchVoter.php:41-48 — before extracting anything, compare `databox/api/src/Security/Voter/ProfileVoter.php` and `databox/api/src/Security/Voter/SavedSearchVoter.php` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 36 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `databox/api/src/Security/Voter/PageVoter.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.
Duplicated block (8 lines × 3) lib/php/rendition-factory/src/Transformer/Video/AlbumArtworkTransformerModule.php:94— lib/php/rendition-factory/src/Transformer/Video/AlbumArtworkTransformerModule.php:94-101 | lib/php/rendition-factory/src/Transformer/Video/VideoToAnimationTransformerModule.php:133-140 | lib/php/rendition-factory/src/Transformer/Video/VideoToFrameTransformerModule.php:113-120 — before extracting anything, compare `lib/php/rendition-factory/src/Transformer/Video/VideoToAnimationTransformerModule.php` and `lib/php/rendition-factory/src/Transformer/Video/VideoToFrameTransformerModule.php` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 78 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/php/rendition-factory/src/Transformer/Video/AlbumArtworkTransformerModule.php:94` 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 lines × 3) lib/php/rendition-factory/src/Transformer/Video/VideoSummaryTransformerModule.php:129— lib/php/rendition-factory/src/Transformer/Video/VideoSummaryTransformerModule.php:129-136 | lib/php/rendition-factory/src/Transformer/Video/VideoToAnimationTransformerModule.php:130-137 | lib/php/rendition-factory/src/Transformer/Video/VideoToFrameTransformerModule.php:110-117 — before extracting anything, compare `lib/php/rendition-factory/src/Transformer/Video/VideoSummaryTransformerModule.php` and `lib/php/rendition-factory/src/Transformer/Video/VideoToAnimationTransformerModule.php` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 73 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `lib/php/rendition-factory/src/Transformer/Video/VideoSummaryTransformerModule.php:137` calls `getFormat` and `lib/php/rendition-factory/src/Transformer/Video/VideoToAnimationTransformerModule.php:140` 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 (6 lines × 3) databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1249— databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1249-1254 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1566-1571 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1675-1680 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1249` 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 (6 lines × 3) databox/api/src/Security/Voter/BasketVoter.php:36— databox/api/src/Security/Voter/BasketVoter.php:36-41 | databox/api/src/Security/Voter/ProfileVoter.php:43-48 | databox/api/src/Security/Voter/SavedSearchVoter.php:44-49 — before extracting anything, compare `databox/api/src/Security/Voter/ProfileVoter.php` and `databox/api/src/Security/Voter/SavedSearchVoter.php` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 36 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `databox/api/src/Security/Voter/BasketVoter.php:36` 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, `databox/api/src/Security/Voter/ProfileVoter.php:39` calls `tokenHasScope` and `databox/api/src/Security/Voter/BasketVoter.php:35` 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 lines × 3) databox/api/src/Controller/Admin/AssetPolicyCrudController.php:42— databox/api/src/Controller/Admin/AssetPolicyCrudController.php:42-47 | databox/api/src/Controller/Admin/AttributePolicyCrudController.php:32-37 | databox/api/src/Controller/Admin/TagCrudController.php:30-35 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
Duplicated block (6 lines × 3) databox/api/src/Integration/Core/FaceRecognition/FaceRecognitionClient.php:39— databox/api/src/Integration/Core/FaceRecognition/FaceRecognitionClient.php:39-44 | databox/api/src/Service/Vector/EmbedderClient.php:23-28 | databox/api/src/Service/Vector/EmbedderClient.php:36-41 — 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.
Sync-over-async blocking databox/indexer/src/handlers/fs/server.ts:16— `fs.existsSync` in `anonymous function` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking databox/indexer/src/handlers/phraseanet/indexer.ts:219— `fs.readFileSync` in `anonymous function` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking databox/indexer/src/handlers/phraseanet/indexer.ts:283— `fs.writeFileSync` in `anonymous function` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking databox/indexer/src/handlers/phraseanet/indexer.ts:444— `fs.writeFileSync` in `anonymous function` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
AC1 · Text alternatives· <canvas> without a text alternative · ×3
<canvas> without a text alternative databox/client/src/features/clip/TimelineParts.tsx:107— A <canvas> with no aria-label/title and no inner fallback content can't be described by assistive tech. Add a name or fallback content.
<canvas> without a text alternative databox/client/src/features/clip/VideoFilmstrip.tsx:176— A <canvas> with no aria-label/title and no inner fallback content can't be described by assistive tech. Add a name or fallback content.
<canvas> without a text alternative databox/client/src/features/clip/frameCanvas.ts:77— A <canvas> with no aria-label/title and no inner fallback content can't be described by assistive tech. Add a name or fallback content.
AC2 · Forms & labels· <RadioGroup> field component without a label · ×3
<RadioGroup> field component without a label databox/client/src/features/profiles/manage/ProfileFiltersTab.tsx:160— This UI-library field component has no label / aria-label / aria-labelledby / id, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id alone, wherever it is set, names nothing until a label points at it). The text inside it does not stand in for one: these compound APIs render a trigger with role="combobox" (or role="button"), and those roles take their name from the AUTHOR, not from their content — so the words on screen never reach the accessibility tree as a name. 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.
<RadioGroup> field component without a label databox/client/src/features/saved-searches/SavedSearchPrivacyField.tsx:50— This UI-library field component has no label / aria-label / aria-labelledby / id, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id alone, wherever it is set, names nothing until a label points at it). The text inside it does not stand in for one: these compound APIs render a trigger with role="combobox" (or role="button"), and those roles take their name from the AUTHOR, not from their content — so the words on screen never reach the accessibility tree as a name. 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.
<RadioGroup> field component without a label databox/client/src/features/saved-searches/automations/AutomationForm.tsx:443— 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· Page without a main landmark · ×3
Page without a main landmark databox/api/templates/terms/terms_pdf.html.twig: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 expose/api/templates/base.html.twig: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 REDACTED:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
AnnotationLayer.AnnotationLayer::onPointerDown (cognitive 30) databox/client/src/features/annotations/AnnotationLayer.tsx:311— AnnotationLayer.AnnotationLayer::onPointerDown has cognitive complexity 30 (threshold 15). Drivers by points: if/else 18 (23 pts), boolean chains 5, ternaries 2 (nesting depth added 5). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level. This shape REPEATS in the file: 3 other methods here (AnnotationLayer.AnnotationLayer, AnnotationLayer.AnnotationLayer::onPointerUp, AnnotationLayer.AnnotationLayer::cycleSelection) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
AnnotationLayer.AnnotationLayer::onPointerUp (cognitive 18) databox/client/src/features/annotations/AnnotationLayer.tsx:540— AnnotationLayer.AnnotationLayer::onPointerUp has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 3, match/switch 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: 3 other methods here (AnnotationLayer.AnnotationLayer, AnnotationLayer.AnnotationLayer::onPointerDown, AnnotationLayer.AnnotationLayer::cycleSelection) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
AnnotationLayer.AnnotationLayer::cycleSelection (cognitive 18) databox/client/src/features/annotations/AnnotationLayer.tsx:617— AnnotationLayer.AnnotationLayer::cycleSelection has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 3, ternaries 1 (2 pts), loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: 3 other methods here (AnnotationLayer.AnnotationLayer, AnnotationLayer.AnnotationLayer::onPointerDown, AnnotationLayer.AnnotationLayer::onPointerUp) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D4 · Code Duplication· Edited copy of a member (20 corresponding lines) · ×3
Edited copy of a member (20 corresponding lines) databox/api/src/Api/Serializer/GroupNormalizerContextBuilder.php:17— databox/api/src/Api/Serializer/GroupNormalizerContextBuilder.php:17-37 | uploader/api/src/Serializer/GroupNormalizerContextBuilder.php:11-30 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (20 corresponding lines) databox/api/src/Repository/Core/AttributeRepository.php:313— databox/api/src/Repository/Core/AttributeRepository.php:313-332 | databox/api/src/Repository/Core/AttributeRepository.php:337-360 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (20 corresponding lines) expose/api/src/Controller/Admin/DashboardController.php:27— expose/api/src/Controller/Admin/DashboardController.php:27-47 | uploader/api/src/Controller/Admin/DashboardController.php:27-46 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×3
Members sharing a duplicated core (4 members, 50+ identical tokens) databox/api/src/Command/FaceRecognitionIndexCommand.php:46— databox/api/src/Command/FaceRecognitionIndexCommand.php:46-97 | databox/api/src/Command/FaceRecognitionPhotosCommand.php:54-97 | databox/api/src/Command/FaceRecognitionRelinkCommand.php:46-74 | databox/api/src/Command/SimilarityIndexCommand.php:47-102 — 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) databox/api/src/Elasticsearch/AQL/AQLFunctionHandler.php:11— databox/api/src/Elasticsearch/AQL/AQLFunctionHandler.php:11-30 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:84-102 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:158-175 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1215-1231 — 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) lib/php/rendition-factory/src/Transformer/Video/AlbumArtworkTransformerModule.php:91— lib/php/rendition-factory/src/Transformer/Video/AlbumArtworkTransformerModule.php:91-125 | lib/php/rendition-factory/src/Transformer/Video/VideoSummaryTransformerModule.php:129-282 | lib/php/rendition-factory/src/Transformer/Video/VideoToAnimationTransformerModule.php:130-230 | lib/php/rendition-factory/src/Transformer/Video/VideoToFrameTransformerModule.php:110-153 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication· Edited copy of a member (16 corresponding lines) · ×3
Edited copy of a member (16 corresponding lines) databox/api/src/Api/Processor/FollowProcessor.php:32— databox/api/src/Api/Processor/FollowProcessor.php:32-47 | databox/api/src/Api/Processor/UnfollowProcessor.php:32-47 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (16 corresponding lines) databox/api/src/Entity/Core/AttributeDefinition.php:660— databox/api/src/Entity/Core/AttributeDefinition.php:660-675 | databox/api/src/Entity/Core/RenditionDefinition.php:298-316 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (16 corresponding lines) expose/api/src/Controller/DownloadAssetAction.php:17— expose/api/src/Controller/DownloadAssetAction.php:17-32 | expose/api/src/Controller/DownloadSubDefAction.php:17-35 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (13 corresponding lines) · ×3
Edited copy of a member (13 corresponding lines) lib/php/auth-bundle/Client/KeycloakClient.php:118— lib/php/auth-bundle/Client/KeycloakClient.php:118-131 | lib/php/auth-bundle/Client/KeycloakClient.php:195-207 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) databox/api/src/Controller/Admin/AttributePolicyCrudController.php:55— databox/api/src/Controller/Admin/AttributePolicyCrudController.php:55-70 | databox/api/src/Controller/Admin/RenditionPolicyCrudController.php:54-66 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) lib/php/workflow-bundle/Doctrine/DoctrineStateRepository.php:190— lib/php/workflow-bundle/Doctrine/DoctrineStateRepository.php:190-205 | lib/php/workflow-bundle/Doctrine/DoctrineStateRepository.php:213-225 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (7 corresponding lines) · ×3
Edited copy of a member (7 corresponding lines) lib/php/auth-bundle/Repository/GroupRepository.php:22— lib/php/auth-bundle/Repository/GroupRepository.php:22-28 | lib/php/auth-bundle/Repository/UserRepository.php:58-64 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) lib/php/auth-bundle/Repository/GroupRepository.php:11— lib/php/auth-bundle/Repository/GroupRepository.php:11-17 | lib/php/auth-bundle/Repository/UserRepository.php:15-23 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) lib/php/rendition-factory/src/Config/YamlLoader.php:17— lib/php/rendition-factory/src/Config/YamlLoader.php:17-23 | lib/php/workflow/src/Loader/YamlLoader.php:19-25 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (8 corresponding lines) · ×3
Edited copy of a member (8 corresponding lines) databox/api/src/Api/Processor/AssetsRestoreProcessor.php:36— databox/api/src/Api/Processor/AssetsRestoreProcessor.php:36-43 | databox/api/src/Api/Processor/CollectionsRestoreProcessor.php:36-43 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) databox/api/src/Integration/Aws/Rekognition/AwsRekognitionIntegration.php:257— databox/api/src/Integration/Aws/Rekognition/AwsRekognitionIntegration.php:257-267 | databox/api/src/Integration/RemoveBg/RemoveBgIntegration.php:73-80 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) databox/api/src/Api/Processor/CancelWorkflowProcessor.php:29— databox/api/src/Api/Processor/CancelWorkflowProcessor.php:29-36 | databox/api/src/Api/Processor/RerunWorkflowJobProcessor.php:29-37 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (21 lines × 2) databox/api/src/Elasticsearch/AQL/AQLGrammar.php:963— databox/api/src/Elasticsearch/AQL/AQLGrammar.php:963-983 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1066-1086 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (21 lines × 2) databox/api/src/Integration/Happyscribe/Consumer/ExportTranscriptionMessageHandler.php:47— databox/api/src/Integration/Happyscribe/Consumer/ExportTranscriptionMessageHandler.php:47-67 | databox/api/src/Integration/Happyscribe/Consumer/TranscriptionHappyscribeMessageHandler.php:46-66 — 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 `databox/api/src/Integration/Happyscribe/Consumer/ExportTranscriptionMessageHandler.php:47` 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) expose/api/src/Command/YamlToApiResourceCommand.php:193— expose/api/src/Command/YamlToApiResourceCommand.php:193-213 | uploader/api/src/Command/YamlToApiResourceCommand.php:193-213 — before extracting anything, compare `expose/api/src/Command/YamlToApiResourceCommand.php` and `uploader/api/src/Command/YamlToApiResourceCommand.php` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 152 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (20 lines × 2) databox/api/src/Command/FaceRecognitionPhotosCommand.php:54— databox/api/src/Command/FaceRecognitionPhotosCommand.php:54-73 | databox/api/src/Command/FaceRecognitionRelinkCommand.php:46-65 — 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 `databox/api/src/Command/FaceRecognitionPhotosCommand.php:54` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (20 lines × 2) databox/api/src/Integration/AbstractActionIntegrationUser.php:21— databox/api/src/Integration/AbstractActionIntegrationUser.php:21-40 | databox/api/src/Integration/Action/UserActionsTrait.php:25-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. Read the line range as the matched WINDOW rather than a finished unit: at `databox/api/src/Integration/AbstractActionIntegrationUser.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 (20 lines × 2) uploader/api/src/Serializer/ItemNormalizerDecorator.php:25— uploader/api/src/Serializer/ItemNormalizerDecorator.php:25-44 | uploader/api/src/Serializer/NormalizerDecorator.php:22-51 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `uploader/api/src/Serializer/ItemNormalizerDecorator.php:25` 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) databox/api/src/Elasticsearch/AQL/AQLGrammar.php:86— databox/api/src/Elasticsearch/AQL/AQLGrammar.php:86-102 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:159-175 — 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 (17 lines × 2) databox/api/src/Repository/Core/AttributeDefinitionRepository.php:42— databox/api/src/Repository/Core/AttributeDefinitionRepository.php:42-58 | databox/api/src/Repository/Core/RenditionDefinitionRepository.php:37-53 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `databox/api/src/Repository/Core/AttributeDefinitionRepository.php:42` 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 (17 lines × 2) expose/api/migrations/Version20200616120120.php:18— expose/api/migrations/Version20200616120120.php:18-34 | uploader/api/migrations/Version20220803131308.php:18-34 — before extracting anything, compare `expose/api/migrations/Version20200616120120.php` and `uploader/api/migrations/Version20220803131308.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. 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 `expose/api/migrations/Version20200616120120.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 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 (14 lines × 2) databox/api/src/Command/FaceRecognitionIndexCommand.php:68— databox/api/src/Command/FaceRecognitionIndexCommand.php:68-81 | databox/api/src/Command/SimilarityIndexCommand.php:75-88 — 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 `databox/api/src/Command/FaceRecognitionIndexCommand.php:68` 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, `databox/api/src/Command/SimilarityIndexCommand.php:72` calls `getIntegrationConfiguration` and `databox/api/src/Command/FaceRecognitionIndexCommand.php:66` 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 (14 lines × 2) databox/api/src/Http/FileUploadManager.php:24— databox/api/src/Http/FileUploadManager.php:24-37 | expose/api/src/Api/Upload/UploadRequestResolver.php:57-70 — 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) lib/php/rendition-factory/src/Transformer/Video/VideoSummaryTransformerModule.php:94— lib/php/rendition-factory/src/Transformer/Video/VideoSummaryTransformerModule.php:94-107 | lib/php/rendition-factory/src/Transformer/Video/VideoToFrameTransformerModule.php:75-88 — before extracting anything, compare `lib/php/rendition-factory/src/Transformer/Video/VideoSummaryTransformerModule.php` and `lib/php/rendition-factory/src/Transformer/Video/VideoToFrameTransformerModule.php` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 65 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 3) databox/api/src/Elasticsearch/AQL/AQLGrammar.php:755— databox/api/src/Elasticsearch/AQL/AQLGrammar.php:755-765 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1550-1560 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1659-1669 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `databox/api/src/Elasticsearch/AQL/AQLGrammar.php:755` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 3) lib/php/rendition-factory/src/Transformer/Video/AudioTransformer.php:37— lib/php/rendition-factory/src/Transformer/Video/AudioTransformer.php:37-47 | lib/php/rendition-factory/src/Transformer/Video/VideoSummaryTransformerModule.php:179-189 | lib/php/rendition-factory/src/Transformer/Video/VideoTransformer.php:49-59 — before extracting anything, compare `lib/php/rendition-factory/src/Transformer/Video/AudioTransformer.php` and `lib/php/rendition-factory/src/Transformer/Video/VideoTransformer.php` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 64 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 3) databox/api/src/Integration/Aws/Rekognition/AwsRekognitionIntegration.php:315— databox/api/src/Integration/Aws/Rekognition/AwsRekognitionIntegration.php:315-325 | databox/api/src/Integration/Core/FaceRecognition/FaceRecognitionIntegration.php:180-190 | databox/api/src/Integration/Core/Similarity/SimilarityIntegration.php:72-82 — 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 `databox/api/src/Integration/Aws/Rekognition/AwsRekognitionIntegration.php:315` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) databox/api/migrations/Version20260730100000.php:28— databox/api/migrations/Version20260730100000.php:28-38 | databox/api/migrations/Version20260730100000.php:56-66 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `databox/api/migrations/Version20260730100000.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.
Duplicated block (11 lines × 2) databox/api/src/Documentation/FileAnalyzersDocumentationGenerator.php:41— databox/api/src/Documentation/FileAnalyzersDocumentationGenerator.php:41-51 | lib/php/rendition-factory/src/RenditionBuilderTransformersDocumentation.php:38-48 — 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 `databox/api/src/Documentation/FileAnalyzersDocumentationGenerator.php:41` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) uploader/api/src/Api/DTO/Input/TargetFormInput.php:26— uploader/api/src/Api/DTO/Input/TargetFormInput.php:26-36 | uploader/api/src/Entity/Target.php:321-331 — 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.
Wholesale file copy (59 identical lines × 2 files) databox/client/src/app/providers.tsx:3— databox/client/src/app/providers.tsx:3 · expose/client/src/app/providers.tsx:3 — these 2 files are line-for-line copies of one another — 59 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 (59 identical lines × 2 files) databox/client/src/app/providers.tsx:3— databox/client/src/app/providers.tsx:3 · uploader/client/src/app/providers.tsx:3 — these 2 files are line-for-line copies of one another — 59 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 (59 identical lines × 2 files) expose/client/src/app/providers.tsx:3— expose/client/src/app/providers.tsx:3 · uploader/client/src/app/providers.tsx:3 — these 2 files are line-for-line copies of one another — 59 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.
Unused dependency '@testing-library/react' dashboard/client/package.json:41— Declared in dashboard/client/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 '@testing-library/react' lib/js/next-i18n/package.json:33— Declared in lib/js/next-i18n/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 '@testing-library/react' lib/js/next-theme/package.json:46— Declared in lib/js/next-theme/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.
AnnotationLayer.AnnotationLayer::onPointerDown (cyclomatic 27) databox/client/src/features/annotations/AnnotationLayer.tsx:311— AnnotationLayer.AnnotationLayer::onPointerDown has cyclomatic complexity 27 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This shape REPEATS in the file: 2 other methods here (AnnotationLayer.AnnotationLayer, AnnotationLayer.AnnotationLayer::onPointerUp) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
AnnotationLayer.AnnotationLayer::onPointerUp (cyclomatic 16) databox/client/src/features/annotations/AnnotationLayer.tsx:540— AnnotationLayer.AnnotationLayer::onPointerUp has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: 2 other methods here (AnnotationLayer.AnnotationLayer, AnnotationLayer.AnnotationLayer::onPointerDown) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
YamlToApiResourceCommand.dumpOperation (cyclomatic 25) expose/api/src/Command/YamlToApiResourceCommand.php:98— YamlToApiResourceCommand.dumpOperation has cyclomatic complexity 25 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
YamlToApiResourceCommand.dumpOperation (cyclomatic 25) uploader/api/src/Command/YamlToApiResourceCommand.php:98— YamlToApiResourceCommand.dumpOperation has cyclomatic complexity 25 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
http.createInstance (cyclomatic 16) expose/client/src/lib/api/http.ts:71— http.createInstance has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 3 function literals inside it that branch (lines 119, 84, 154). 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.
http.createInstance (cyclomatic 16) uploader/client/src/lib/api/http.ts:75— http.createInstance has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 3 function literals inside it that branch (lines 123, 88, 158). 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.
YamlToApiResourceCommand.dumpOperation (cognitive 18) expose/api/src/Command/YamlToApiResourceCommand.php:98— YamlToApiResourceCommand.dumpOperation has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (8 pts), match/switch 3 (6 pts), loops 2, ternaries 1 (2 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
YamlToApiResourceCommand.dumpOperation (cognitive 18) uploader/api/src/Command/YamlToApiResourceCommand.php:98— YamlToApiResourceCommand.dumpOperation has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (8 pts), match/switch 3 (6 pts), loops 2, ternaries 1 (2 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
YamlToApiResourceCommand.dump (cognitive 17) expose/api/src/Command/YamlToApiResourceCommand.php:39— YamlToApiResourceCommand.dump has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (6 pts), loops 3 (6 pts), match/switch 1 (3 pts), boolean chains 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
YamlToApiResourceCommand.dump (cognitive 17) uploader/api/src/Command/YamlToApiResourceCommand.php:39— YamlToApiResourceCommand.dump has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (6 pts), loops 3 (6 pts), match/switch 1 (3 pts), boolean chains 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
http.createInstance (cognitive 16) expose/client/src/lib/api/http.ts:71— http.createInstance has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (11 pts), boolean chains 3, ternaries 2 (nesting depth added 4). None of this is in the body itself: all 16 points belong to 3 function literals inside it that branch (lines 119, 84, 154). 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.
http.createInstance (cognitive 16) uploader/client/src/lib/api/http.ts:75— http.createInstance has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (11 pts), boolean chains 3, ternaries 2 (nesting depth added 4). None of this is in the body itself: all 16 points belong to 3 function literals inside it that branch (lines 123, 88, 158). 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.
D4 · Code Duplication· Edited copy of a member (35 corresponding lines) · ×2
Edited copy of a member (35 corresponding lines) lib/php/admin-bundle/Filter/AssociationIdentifierFilter.php:40— lib/php/admin-bundle/Filter/AssociationIdentifierFilter.php:40-74 | lib/php/admin-bundle/Filter/ChildPropertyEntityFilter.php:52-98 — These two members are one piece of code written twice and then edited apart: 35 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (35 corresponding lines) lib/php/rendition-factory/src/Transformer/Video/VideoSummaryTransformerModule.php:79— lib/php/rendition-factory/src/Transformer/Video/VideoSummaryTransformerModule.php:79-119 | lib/php/rendition-factory/src/Transformer/Video/VideoToFrameTransformerModule.php:70-104 — These two members are one piece of code written twice and then edited apart: 35 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (31 corresponding lines) · ×2
Edited copy of a member (31 corresponding lines) databox/api/src/Documentation/FileAnalyzersDocumentationGenerator.php:41— databox/api/src/Documentation/FileAnalyzersDocumentationGenerator.php:41-71 | lib/php/rendition-factory/src/RenditionBuilderTransformersDocumentation.php:38-68 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (31 corresponding lines) databox/api/src/Elasticsearch/AttributeEntitySearch.php:28— databox/api/src/Elasticsearch/AttributeEntitySearch.php:28-58 | databox/api/src/Elasticsearch/TagSearch.php:28-58 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (12 corresponding lines) · ×2
Edited copy of a member (12 corresponding lines) lib/php/workflow/src/Command/DumpWorkflowCommand.php:36— lib/php/workflow/src/Command/DumpWorkflowCommand.php:36-51 | lib/php/workflow/src/Executor/PlanExecutor.php:23-34 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) databox/api/src/Service/Workspace/TermsManager.php:146— databox/api/src/Service/Workspace/TermsManager.php:146-157 | lib/php/notifier-bundle/src/Manager/SubscriptionManager.php:23-34 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 10+ corresponding lines) · ×2
Edited copies of one member (4 members, 10+ corresponding lines) databox/api/src/Controller/Admin/AssetEmbeddingCrudController.php:63— databox/api/src/Controller/Admin/AssetEmbeddingCrudController.php:63-73 | databox/api/src/Controller/Admin/EntityListCrudController.php:49-58 | databox/api/src/Controller/Admin/IntegrationDataCrudController.php:65-75 | databox/api/src/Controller/Admin/TagCrudController.php:51-62 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
Edited copies of one member (4 members, 10+ corresponding lines) databox/api/src/Service/Import/AssetImportProgress.php:34— databox/api/src/Service/Import/AssetImportProgress.php:34-43 | databox/api/src/Service/Import/AssetImportProgress.php:48-57 | databox/api/src/Service/Import/AssetImportProgress.php:85-99 | databox/api/src/Service/Import/AssetImportProgress.php:104-114 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (5 corresponding lines) · ×2
Edited copy of a member (5 corresponding lines) expose/api/src/Security/Voter/AssetVoter.php:32— expose/api/src/Security/Voter/AssetVoter.php:32-37 | expose/api/src/Security/Voter/SubDefinitionVoter.php:29-33 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (5 corresponding lines) databox/api/src/Attribute/AttributeTypeRegistry.php:31— databox/api/src/Attribute/AttributeTypeRegistry.php:31-35 | databox/api/src/Integration/IntegrationRegistry.php:30-34 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 8+ corresponding lines) · ×2
Edited copies of one member (3 members, 8+ corresponding lines) databox/api/src/Repository/Basket/BasketRepository.php:31— databox/api/src/Repository/Basket/BasketRepository.php:31-39 | databox/api/src/Repository/Core/CollectionAssetRepository.php:16-23 | databox/api/src/Repository/Profile/ProfileRepository.php:25-33 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 8+ corresponding lines) databox/api/src/Command/ExportWorkspaceCommand.php:29— databox/api/src/Command/ExportWorkspaceCommand.php:29-36 | databox/api/src/Command/FaceRecognitionIndexCommand.php:34-41 | databox/api/src/Command/SimilarityIndexCommand.php:34-42 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Duplicated block (30 lines × 2) lib/php/admin-bundle/Filter/AssociationIdentifierFilter.php:88— lib/php/admin-bundle/Filter/AssociationIdentifierFilter.php:88-117 | lib/php/admin-bundle/Filter/ChildPropertyEntityFilter.php:134-163 — before extracting anything, compare `lib/php/admin-bundle/Filter/AssociationIdentifierFilter.php` and `lib/php/admin-bundle/Filter/ChildPropertyEntityFilter.php` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 57 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (30 lines × 2) lib/php/configurator-bundle/src/Entity/ConfiguratorEntry.php:42— lib/php/configurator-bundle/src/Entity/ConfiguratorEntry.php:42-91 | lib/php/core-bundle/Entity/AbstractUuidEntity.php:25-54 — 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 `lib/php/configurator-bundle/src/Entity/ConfiguratorEntry.php:42` 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 (23 lines × 2) databox/api/src/Elasticsearch/AttributeEntitySearch.php:36— databox/api/src/Elasticsearch/AttributeEntitySearch.php:36-58 | databox/api/src/Elasticsearch/TagSearch.php:36-58 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (23 lines × 2) databox/api/src/Repository/Core/AttributeDefinitionRepository.php:64— databox/api/src/Repository/Core/AttributeDefinitionRepository.php:64-86 | databox/api/src/Repository/Core/RenditionDefinitionRepository.php:70-92 — 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 `databox/api/src/Repository/Core/AttributeDefinitionRepository.php:64` 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, `databox/api/src/Repository/Core/RenditionDefinitionRepository.php:95` calls `andWhere` and `databox/api/src/Repository/Core/AttributeDefinitionRepository.php:88` 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 (22 lines × 2) lib/php/admin-bundle/Filter/AssociationIdentifierFilter.php:53— lib/php/admin-bundle/Filter/AssociationIdentifierFilter.php:53-74 | lib/php/admin-bundle/Filter/ChildPropertyEntityFilter.php:77-98 — before extracting anything, compare `lib/php/admin-bundle/Filter/AssociationIdentifierFilter.php` and `lib/php/admin-bundle/Filter/ChildPropertyEntityFilter.php` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 57 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/php/admin-bundle/Filter/AssociationIdentifierFilter.php:53` 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 (22 lines × 2) lib/php/rendition-factory/src/Transformer/Video/VideoSummaryTransformerModule.php:96— lib/php/rendition-factory/src/Transformer/Video/VideoSummaryTransformerModule.php:96-117 | lib/php/rendition-factory/src/Transformer/Video/VideoToAnimationTransformerModule.php:102-123 — before extracting anything, compare `lib/php/rendition-factory/src/Transformer/Video/VideoSummaryTransformerModule.php` and `lib/php/rendition-factory/src/Transformer/Video/VideoToAnimationTransformerModule.php` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 73 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (15–16 lines × 2) databox/api/src/Elasticsearch/AQL/AQLFunctionHandler.php:16— databox/api/src/Elasticsearch/AQL/AQLFunctionHandler.php:16-30 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1216-1231 — 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 `databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1216` 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–16 lines × 2) databox/api/src/Listener/AclListener.php:161— databox/api/src/Listener/AclListener.php:161-175 | databox/api/src/Listener/AclListener.php:203-218 — 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 `databox/api/src/Listener/AclListener.php:161` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) databox/api/src/Api/Serializer/GroupNormalizerContextBuilder.php:21— databox/api/src/Api/Serializer/GroupNormalizerContextBuilder.php:21-35 | uploader/api/src/Serializer/GroupNormalizerContextBuilder.php:14-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 `databox/api/src/Api/Serializer/GroupNormalizerContextBuilder.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 (15 lines × 2) databox/api/src/Command/FaceRecognitionIndexCommand.php:52— databox/api/src/Command/FaceRecognitionIndexCommand.php:52-66 | databox/api/src/Command/SimilarityIndexCommand.php:56-70 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `databox/api/src/Command/FaceRecognitionIndexCommand.php:52` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `databox/api/src/Command/SimilarityIndexCommand.php:72` calls `getIntegrationConfiguration` and `databox/api/src/Command/FaceRecognitionIndexCommand.php:68` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (13 lines × 3) lib/php/rendition-factory/src/Transformer/Video/VideoSummaryTransformerModule.php:106— lib/php/rendition-factory/src/Transformer/Video/VideoSummaryTransformerModule.php:106-119 | lib/php/rendition-factory/src/Transformer/Video/VideoToAnimationTransformerModule.php:112-124 | lib/php/rendition-factory/src/Transformer/Video/VideoToFrameTransformerModule.php:91-104 — before extracting anything, compare `lib/php/rendition-factory/src/Transformer/Video/VideoSummaryTransformerModule.php` and `lib/php/rendition-factory/src/Transformer/Video/VideoToAnimationTransformerModule.php` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 73 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. 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 (13 lines × 3) expose/api/src/Form/LayoutChoiceType.php:19— expose/api/src/Form/LayoutChoiceType.php:19-33 | expose/api/src/Form/MapLayoutChoiceType.php:19-31 | expose/api/src/Form/ThemeChoiceType.php:19-33 — before extracting anything, compare `expose/api/src/Form/LayoutChoiceType.php` and `expose/api/src/Form/ThemeChoiceType.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. 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 `expose/api/src/Form/LayoutChoiceType.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 (12 lines × 3) lib/php/rendition-factory/src/Transformer/Video/VideoSummaryTransformerModule.php:96— lib/php/rendition-factory/src/Transformer/Video/VideoSummaryTransformerModule.php:96-107 | lib/php/rendition-factory/src/Transformer/Video/VideoToAnimationTransformerModule.php:102-113 | lib/php/rendition-factory/src/Transformer/Video/VideoToFrameTransformerModule.php:77-88 — before extracting anything, compare `lib/php/rendition-factory/src/Transformer/Video/VideoSummaryTransformerModule.php` and `lib/php/rendition-factory/src/Transformer/Video/VideoToAnimationTransformerModule.php` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 73 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 3) lib/php/notifier-bundle/src/AlchemyNotifierBundle.php:129— lib/php/notifier-bundle/src/AlchemyNotifierBundle.php:129-145 | lib/php/webhook-bundle/DependencyInjection/AlchemyWebhookExtension.php:60-71 | lib/php/workflow-bundle/DependencyInjection/AlchemyWorkflowExtension.php:57-72 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
Duplicated block (9 lines × 3) databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1147— databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1147-1155 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1243-1251 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1382-1390 — 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. 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 (9 lines × 3) lib/php/notifier-bundle/src/Controller/NotificationController.php:77— lib/php/notifier-bundle/src/Controller/NotificationController.php:77-85 | lib/php/notifier-bundle/src/Controller/NotificationController.php:104-112 | lib/php/notifier-bundle/src/Controller/NotificationController.php:123-131 — 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 (7 lines × 4) databox/api/src/Security/Voter/AssetDataTemplateVoter.php:33— databox/api/src/Security/Voter/AssetDataTemplateVoter.php:33-39 | databox/api/src/Security/Voter/PageVoter.php:33-39 | databox/api/src/Security/Voter/ProfileVoter.php:39-45 | databox/api/src/Security/Voter/SavedSearchVoter.php:40-46 — before extracting anything, compare `databox/api/src/Security/Voter/ProfileVoter.php` and `databox/api/src/Security/Voter/SavedSearchVoter.php` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 36 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 4) databox/api/src/Integration/Aws/Rekognition/AbstractRekognitionAction.php:49— databox/api/src/Integration/Aws/Rekognition/AbstractRekognitionAction.php:49-55 | databox/api/src/Integration/Blurhash/BlurhashAction.php:106-112 | databox/api/src/Integration/Core/FaceRecognition/FaceRecognitionDetectAction.php:31-37 | databox/api/src/Integration/RemoveBg/RemoveBgAction.php:30-36 — 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 (42 lines × 2) databox/api/migrations/Version20250409113833.php:17— databox/api/migrations/Version20250409113833.php:17-60 | databox/api/migrations/Version20250429162120.php:14-55 — 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 `databox/api/migrations/Version20250409113833.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 (42 lines × 2) databox/api/src/Listener/AclAssetIndexUpdateService.php:22— databox/api/src/Listener/AclAssetIndexUpdateService.php:22-63 | databox/api/src/Listener/AclCollectionIndexUpdateService.php:22-63 — before extracting anything, compare `databox/api/src/Listener/AclAssetIndexUpdateService.php` and `databox/api/src/Listener/AclCollectionIndexUpdateService.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. 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 `databox/api/src/Listener/AclAssetIndexUpdateService.php:22` 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.
Low cohesion: AwsRekognitionIntegration (LCOM4 5) databox/api/src/Integration/Aws/Rekognition/AwsRekognitionIntegration.php:38— AwsRekognitionIntegration's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: FaceRecognitionIntegration (LCOM4 4) databox/api/src/Integration/Core/FaceRecognition/FaceRecognitionIntegration.php:45— FaceRecognitionIntegration's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
R10 · Code Duplication· Duplicated block with local edits (60 matched lines × 2 locations) · ×2
Duplicated block with local edits (60 matched lines × 2 locations) expose/client/src/features/admin/AdminPublicationList.tsx:41— expose/client/src/features/admin/AdminPublicationList.tsx:41 · expose/client/src/features/publications/PublicationList.tsx:32 — the two spans are one implementation copied and then locally edited — 334 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block with local edits (60 matched lines × 2 locations) expose/client/src/features/admin/ProfileEditScreen.tsx:47— expose/client/src/features/admin/ProfileEditScreen.tsx:47 · expose/client/src/features/admin/PublicationEditScreen.tsx:69 — the two spans are one implementation copied and then locally edited — 359 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Wholesale file copy (51 identical lines × 2 files) dashboard/client/src/app/providers.tsx:3— dashboard/client/src/app/providers.tsx:3 · expose/client/src/app/providers.tsx:3 — these 2 files are line-for-line copies of one another — 51 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 (51 identical lines × 2 files) dashboard/client/src/app/providers.tsx:3— dashboard/client/src/app/providers.tsx:3 · uploader/client/src/app/providers.tsx:3 — these 2 files are line-for-line copies of one another — 51 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 (41 matched lines × 2 locations) · ×2
Duplicated block with local edits (41 matched lines × 2 locations) databox/client/src/components/form/CollectionTreePicker.tsx:267— databox/client/src/components/form/CollectionTreePicker.tsx:267 · databox/client/src/components/form/CollectionTreePicker.tsx:439 — the two spans are one implementation copied and then locally edited — 152 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block with local edits (41 matched lines × 2 locations) databox/client/src/features/workspaces/manage/PolicyForm.tsx:65— databox/client/src/features/workspaces/manage/PolicyForm.tsx:65 · databox/client/src/features/workspaces/manage/tabs/TagManagerTab.tsx:78 — the two spans are one implementation copied and then locally edited — 281 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 (40 lines × 2 locations) databox/client/src/features/saved-searches/automations/actions/RemoteExportForm.tsx:136— databox/client/src/features/saved-searches/automations/actions/RemoteExportForm.tsx:136 · databox/client/src/features/saved-searches/automations/actions/ShareExportForm.tsx:260 — 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 (40 lines × 2 locations) databox/client/src/features/workspaces/manage/tabs/AttributePoliciesTab.tsx:20— databox/client/src/features/workspaces/manage/tabs/AttributePoliciesTab.tsx:20 · databox/client/src/features/workspaces/manage/tabs/RenditionPoliciesTab.tsx:20 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Duplicated block (35 lines × 2 locations) dashboard/client/src/lib/auth/loginWindow.ts:26— dashboard/client/src/lib/auth/loginWindow.ts:26 · expose/client/src/lib/auth/loginWindow.ts:36 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
Duplicated block (35 lines × 2 locations) lib/js/next-ui/src/ui/menu.tsx:108— lib/js/next-ui/src/ui/menu.tsx:108 · lib/js/next-ui/src/ui/menu.tsx:219 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Boundary violation [package:third-party-deep-import] expose/client/src/features/player/AudioPlayer.tsx:7— expose/client/src/features/player/AudioPlayer.tsx:7 imports wavesurfer.js/dist/plugins/timeline.esm.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] expose/client/src/features/player/AudioPlayer.tsx:8— expose/client/src/features/player/AudioPlayer.tsx:8 imports wavesurfer.js/dist/plugins/zoom.esm.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
AC1 · Text alternatives· <video> without a captions track · ×1
<video> without a captions track databox/client/src/features/clip/ClipEditorDialog.tsx:279— Video with no captions <track> offers no captions. This player's source is set at runtime, so there is no caption file to author here: give the player a way to carry captions — accept a track/captions URL alongside the media and render a <track kind="captions"> when one is supplied — and capture that asset wherever the media enters the product (upload, import or generation).
AC2 · Forms & labels· <Textarea> field component without a label · ×1
<Textarea> field component without a label databox/client/src/features/saved-searches/automations/actions/RemoteDestinationFields.tsx:51— 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.
AC3 · Page structure· Heading level jumps from h3 to h5 · ×1
Heading level jumps from h3 to h5 databox/api/templates/admin/integration_help.html.twig:27— 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 REDACTED:225— 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 expose/client/src/features/publication/Lightbox.tsx:57— 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· Animation without a prefers-reduced-motion guard · ×1
Animation without a prefers-reduced-motion guard databox/client/src/features/workflows/jobStatus.tsx:85— <span> moves — its `animate-ping` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
AssetMap.MapView (cyclomatic 98) databox/client/src/features/map/AssetMap.tsx:193— AssetMap.MapView has cyclomatic complexity 98 (threshold 15). Of this number, 19 points are the body's own statements and 79 belong to 40 function items 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.
CollectionVoter.doVote (cyclomatic 90) databox/api/src/Security/Voter/CollectionVoter.php:47— CollectionVoter.doVote has cyclomatic complexity 90 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
AttributeBatchEditorRoute.AttributeBatchEditorRoute (cyclomatic 90) databox/client/src/features/attributes/batch/AttributeBatchEditorRoute.tsx:143— AttributeBatchEditorRoute.AttributeBatchEditorRoute has cyclomatic complexity 90 (threshold 15). Of this number, 17 points are the body's own statements and 73 belong to 31 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.
AssetViewRoute.AssetViewRoute (cyclomatic 84) databox/client/src/features/assets/view/AssetViewRoute.tsx:110— AssetViewRoute.AssetViewRoute has cyclomatic complexity 84 (threshold 15). Of this number, 50 points are the body's own statements and 34 belong to 15 function items 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.
DefinitionManager.DefinitionManager (cyclomatic 74) databox/client/src/features/workspaces/manage/DefinitionManager.tsx:134— DefinitionManager.DefinitionManager has cyclomatic complexity 74 (threshold 15). Of this number, 51 points are the body's own statements and 23 belong to 10 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.
ClipEditorDialog.ClipEditorDialog (cyclomatic 71) databox/client/src/features/clip/ClipEditorDialog.tsx:81— ClipEditorDialog.ClipEditorDialog has cyclomatic complexity 71 (threshold 15). Of this number, 42 points are the body's own statements and 29 belong to 13 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.
PdfViewer.PdfDocumentViewer (cyclomatic 63) databox/client/src/features/assets/player/PdfViewer.tsx:109— PdfViewer.PdfDocumentViewer has cyclomatic complexity 63 (threshold 15). Of this number, 17 points are the body's own statements and 46 belong to 18 function items 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.
AssetThumb.AssetThumb (cyclomatic 62) databox/client/src/features/assets/list/AssetThumb.tsx:52— AssetThumb.AssetThumb has cyclomatic complexity 62 (threshold 15). Of this number, 43 points are the body's own statements and 19 belong to 7 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.
AssetVoter.voteOnAttribute (cyclomatic 59) databox/api/src/Security/Voter/AssetVoter.php:47— AssetVoter.voteOnAttribute has cyclomatic complexity 59 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
MessageComposer.MessageComposer (cyclomatic 55) databox/client/src/features/discussion/MessageComposer.tsx:150— MessageComposer.MessageComposer has cyclomatic complexity 55 (threshold 15). Of this number, 23 points are the body's own statements and 32 belong to 16 function items 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.
AttributeWidget.AttributeWidget (cyclomatic 54) databox/client/src/features/attributes/widgets/AttributeWidget.tsx:51— AttributeWidget.AttributeWidget has cyclomatic complexity 54 (threshold 15). Of this number, 47 points are the body's own statements and 7 belong to 6 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.
UploadScreen.UploadScreen (cyclomatic 54) uploader/client/src/features/upload/UploadScreen.tsx:114— UploadScreen.UploadScreen has cyclomatic complexity 54 (threshold 15). Of this number, 32 points are the body's own statements and 22 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.
useAssetActions.useAssetActions (cyclomatic 53) databox/client/src/features/assets/actions/useAssetActions.tsx:139— useAssetActions.useAssetActions has cyclomatic complexity 53 (threshold 15). Most of this is not in the body itself: 1 of the 53 points is its own statement and the rest belongs to 11 function literals inside it that branch (lines 157, 184, 322, …). 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.
AudioPlayer.AudioPlayer (cyclomatic 53) databox/client/src/features/assets/player/AudioPlayer.tsx:76— AudioPlayer.AudioPlayer has cyclomatic complexity 53 (threshold 15). Most of this is not in the body itself: 15 of the 53 points are its own statements and the rest belongs to 14 function literals inside it that branch (lines 276, 229, 208, …). 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.
AQLGrammar.match_operator (cyclomatic 49) databox/api/src/Elasticsearch/AQL/AQLGrammar.php:527— AQLGrammar.match_operator has cyclomatic complexity 49 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
EntityGrid.EntityGrid (cyclomatic 48) databox/client/src/features/workspaces/manage/entities/EntityGrid.tsx:116— EntityGrid.EntityGrid has cyclomatic complexity 48 (threshold 15). Most of this is not in the body itself: 12 of the 48 points are its own statements and the rest belongs to 14 function items inside it that branch (commitCell, setStatus, a function literal at line 322, …). 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.
IntegrationManager.IntegrationForm (cyclomatic 47) databox/client/src/features/integrations/manage/IntegrationManager.tsx:149— IntegrationManager.IntegrationForm has cyclomatic complexity 47 (threshold 15). Of this number, 30 points are the body's own statements and 17 belong to 5 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.
PdfViewer.PdfDocumentViewer (cyclomatic 46) expose/client/src/features/player/PdfViewer.tsx:101— PdfViewer.PdfDocumentViewer has cyclomatic complexity 46 (threshold 15). Of this number, 17 points are the body's own statements and 29 belong to 15 function items 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.
WorkspaceVoter.doVote (cyclomatic 45) databox/api/src/Security/Voter/WorkspaceVoter.php:64— WorkspaceVoter.doVote has cyclomatic complexity 45 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
Discussion.Discussion (cyclomatic 45) databox/client/src/features/discussion/Discussion.tsx:67— Discussion.Discussion has cyclomatic complexity 45 (threshold 15). Most of this is not in the body itself: 12 of the 45 points are its own statements and the rest belongs to 14 function items inside it that branch (a function literal at line 354, send, saveEdit, …). 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.
ZoomableImage.ZoomableImage (cyclomatic 44) databox/client/src/features/assets/player/ZoomableImage.tsx:44— ZoomableImage.ZoomableImage has cyclomatic complexity 44 (threshold 15). Of this number, 19 points are the body's own statements and 25 belong to 12 function items 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.
UploadDialog.UploadDialog (cyclomatic 42) databox/client/src/features/upload/UploadDialog.tsx:89— UploadDialog.UploadDialog has cyclomatic complexity 42 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (UploadDialog.UploadDialog::submit) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
AttributeDefinitionInputMapper.map (cyclomatic 41) databox/api/src/Api/Mapper/Input/AttributeDefinitionInputMapper.php:33— AttributeDefinitionInputMapper.map has cyclomatic complexity 41 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
collectionStore.useCollectionStore (cyclomatic 41) databox/client/src/features/collections/collectionStore.ts:151— collectionStore.useCollectionStore has cyclomatic complexity 41 (threshold 15). Most of this is not in the body itself: 1 of the 41 points is its own statement and the rest belongs to 15 function literals inside it that branch (lines 404, 211, 278, …). 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.
ShareDialog.ShareDialog (cyclomatic 41) databox/client/src/features/share/ShareDialog.tsx:116— ShareDialog.ShareDialog has cyclomatic complexity 41 (threshold 15). Of this number, 27 points are the body's own statements and 14 belong to 10 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.
SecretReferencePicker.SecretReferencePicker (cyclomatic 40) databox/client/src/features/integrations/config/pickers/SecretReferencePicker.tsx:66— SecretReferencePicker.SecretReferencePicker has cyclomatic complexity 40 (threshold 15). Of this number, 36 points are the body's own statements and 4 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
SearchProvider.SearchProvider (cyclomatic 40) databox/client/src/features/search/SearchProvider.tsx:100— SearchProvider.SearchProvider has cyclomatic complexity 40 (threshold 15). Most of this is not in the body itself: 5 of the 40 points are its own statements and the rest belongs to 17 function literals inside it that branch (lines 258, 361, 222, …). 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.
BatchAttributeManager.handleBatch (cyclomatic 39) databox/api/src/Attribute/BatchAttributeManager.php:92— BatchAttributeManager.handleBatch has cyclomatic complexity 39 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ClientThemeNormalizer.normalize (cyclomatic 39) databox/api/src/Service/Admin/ClientThemeNormalizer.php:73— ClientThemeNormalizer.normalize has cyclomatic complexity 39 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
AsyncCombobox.AsyncCombobox (cyclomatic 39) lib/js/next-ui/src/form/AsyncCombobox.tsx:91— AsyncCombobox.AsyncCombobox has cyclomatic complexity 39 (threshold 15). Of this number, 21 points are the body's own statements and 18 belong to 11 function items 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.
AttributesEditor.AttributesEditor (cyclomatic 38) databox/client/src/features/attributes/editor/AttributesEditor.tsx:52— AttributesEditor.AttributesEditor has cyclomatic complexity 38 (threshold 15). Most of this is not in the body itself: 5 of the 38 points are its own statements and the rest belongs to 5 function items inside it that branch (onKeyDown, a function literal at line 168, a function literal at line 104, …). 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.
DataTable.DataTable::onKeyDown (cyclomatic 37) databox/client/src/components/ui/data-table/DataTable.tsx:305— DataTable.DataTable::onKeyDown has cyclomatic complexity 37 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AnnotationLayer.AnnotationLayer (cyclomatic 37) databox/client/src/features/annotations/AnnotationLayer.tsx:105— AnnotationLayer.AnnotationLayer has cyclomatic complexity 37 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: 2 other methods here (AnnotationLayer.AnnotationLayer::onPointerDown, AnnotationLayer.AnnotationLayer::onPointerUp) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
AuditLogListener.logRelations (cyclomatic 35) databox/api/src/Doctrine/Listener/AuditLogListener.php:280— AuditLogListener.logRelations has cyclomatic complexity 35 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AclEditor.AclEditor (cyclomatic 34) databox/client/src/features/permissions/AclEditor.tsx:54— AclEditor.AclEditor has cyclomatic complexity 34 (threshold 15). Most of this is not in the body itself: 8 of the 34 points are its own statements and the rest belongs to 12 function items inside it that branch (a function literal at line 274, a function literal at line 379, add, …). 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.
AutomationForm.AutomationFormDialog (cyclomatic 34) databox/client/src/features/saved-searches/automations/AutomationForm.tsx:94— AutomationForm.AutomationFormDialog has cyclomatic complexity 34 (threshold 15). Of this number, 21 points are the body's own statements and 13 belong to 8 function items 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.
SearchBar.SearchBar (cyclomatic 34) databox/client/src/features/search/SearchBar.tsx:36— SearchBar.SearchBar has cyclomatic complexity 34 (threshold 15). Most of this is not in the body itself: 8 of the 34 points are its own statements and the rest belongs to 5 function items inside it that branch (a function literal at line 130, applyTextSuggestion, applyItem, …). 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.
ThemeEditorScreen.ThemeEditorScreen (cyclomatic 34) databox/client/src/features/theme/ThemeEditorScreen.tsx:194— ThemeEditorScreen.ThemeEditorScreen has cyclomatic complexity 34 (threshold 15). Of this number, 20 points are the body's own statements and 14 belong to 7 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.
AQLToESQuery.createCriteria (cyclomatic 33) databox/api/src/Elasticsearch/AQL/AQLToESQuery.php:124— AQLToESQuery.createCriteria has cyclomatic complexity 33 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
FieldDefinition.fromArray (cyclomatic 33) uploader/api/src/Form/Builder/FieldDefinition.php:51— FieldDefinition.fromArray has cyclomatic complexity 33 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Parser.criteria (cyclomatic 33) databox/client/src/features/search/aql/parser.ts:270— Parser.criteria has cyclomatic complexity 33 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
operatorLabel.getOperatorLabel (cyclomatic 33) databox/client/src/features/search/aql/operatorLabel.ts:11— operatorLabel.getOperatorLabel has cyclomatic complexity 33 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
ZoomableImage.ZoomableImage (cyclomatic 33) expose/client/src/features/player/ZoomableImage.tsx:36— ZoomableImage.ZoomableImage has cyclomatic complexity 33 (threshold 15). Most of this is not in the body itself: 10 of the 33 points are its own statements and the rest belongs to 11 function items inside it that branch (measure, a function literal at line 221, a function literal at line 254, …). 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.
AssetInputMapper.map (cyclomatic 32) databox/api/src/Api/Mapper/Input/AssetInputMapper.php:53— AssetInputMapper.map has cyclomatic complexity 32 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
SavedSearchAutomationInputMapper.map (cyclomatic 32) databox/api/src/Api/Mapper/Input/SavedSearchAutomationInputMapper.php:39— SavedSearchAutomationInputMapper.map has cyclomatic complexity 32 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
indexer.phraseanetIndexer (cyclomatic 32) databox/indexer/src/handlers/phraseanet/indexer.ts:41— indexer.phraseanetIndexer has cyclomatic complexity 32 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
customTheme.normalizeClientTheme (cyclomatic 32) lib/js/next-theme/src/customTheme.ts:409— customTheme.normalizeClientTheme has cyclomatic complexity 32 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
VideoJsPlayer.VideoJsPlayerBody (cyclomatic 31) databox/client/src/features/assets/player/VideoJsPlayer.tsx:337— VideoJsPlayer.VideoJsPlayerBody has cyclomatic complexity 31 (threshold 15). Most of this is not in the body itself: 11 of the 31 points are its own statements and the rest belongs to 11 function items inside it that branch (a function literal at line 447, a function literal at line 384, a function literal at line 398, …). 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.
FieldInspector.InputFieldInspector (cyclomatic 31) uploader/client/src/features/form-builder/editor/FieldInspector.tsx:107— FieldInspector.InputFieldInspector has cyclomatic complexity 31 (threshold 15). Of this number, 19 points are the body's own statements and 12 belong to 6 function items 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.
CsvAttributeEntityImporter.import (cyclomatic 30) databox/api/src/Service/Asset/Attribute/AttributeEntity/Importer/CsvAttributeEntityImporter.php:29— CsvAttributeEntityImporter.import has cyclomatic complexity 30 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ImportEntryNormalizer.normalize (cyclomatic 30) databox/api/src/Service/Import/ImportEntryNormalizer.php:52— ImportEntryNormalizer.normalize has cyclomatic complexity 30 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CreateDynamicRenditionDialog.CreateDynamicRenditionDialog (cyclomatic 30) databox/client/src/features/assets/manage/dialogs/CreateDynamicRenditionDialog.tsx:33— CreateDynamicRenditionDialog.CreateDynamicRenditionDialog has cyclomatic complexity 30 (threshold 15). Most of this is not in the body itself: 12 of the 30 points are its own statements and the rest belongs to 6 function items inside it that branch (buildDefinition, a function literal at line 110, isImage, …). 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.
BasketIntegrations.ExposeIntegration (cyclomatic 30) databox/client/src/features/baskets/manage/BasketIntegrations.tsx:126— BasketIntegrations.ExposeIntegration has cyclomatic complexity 30 (threshold 15). Most of this is not in the body itself: 5 of the 30 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 215, a function literal at line 488, a function literal at line 319, …). 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.
parser.tokenize (cyclomatic 30) databox/client/src/features/search/aql/parser.ts:55— parser.tokenize has cyclomatic complexity 30 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AttributeDefinitionsTab.DefinitionForm (cyclomatic 30) databox/client/src/features/workspaces/manage/tabs/AttributeDefinitionsTab.tsx:139— AttributeDefinitionsTab.DefinitionForm has cyclomatic complexity 30 (threshold 15). Of this number, 17 points are the body's own statements and 13 belong to 4 function items 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.
AssetSearch.buildQuery (cyclomatic 29) databox/api/src/Elasticsearch/AssetSearch.php:308— AssetSearch.buildQuery has cyclomatic complexity 29 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CollectionsPanel.WorkspaceItem (cyclomatic 29) databox/client/src/features/collections/tree/CollectionsPanel.tsx:275— CollectionsPanel.WorkspaceItem has cyclomatic complexity 29 (threshold 15). Most of this is not in the body itself: 13 of the 29 points are its own statements and the rest belongs to 4 function items inside it that branch (menu, a function literal at line 292, a function literal at line 380, …). 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.
AssetSearch.applySort (cyclomatic 28) databox/api/src/Elasticsearch/AssetSearch.php:617— AssetSearch.applySort has cyclomatic complexity 28 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
PublicationVoter.voteOnAttribute (cyclomatic 28) expose/api/src/Security/Voter/PublicationVoter.php:59— PublicationVoter.voteOnAttribute has cyclomatic complexity 28 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
MetadataTagsField.MetadataTagsField (cyclomatic 28) databox/client/src/components/form/MetadataTagsField.tsx:43— MetadataTagsField.MetadataTagsField has cyclomatic complexity 28 (threshold 15). Of this number, 14 points are the body's own statements and 14 belong to 5 function items 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.
AttributeList.AttributeList (cyclomatic 28) databox/client/src/features/attributes/AttributeList.tsx:61— AttributeList.AttributeList has cyclomatic complexity 28 (threshold 15). Most of this is not in the body itself: 4 of the 28 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 89, 183, 220). 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.
CropRectEditor.CropRectEditor (cyclomatic 28) databox/client/src/features/clip/CropRectEditor.tsx:95— CropRectEditor.CropRectEditor has cyclomatic complexity 28 (threshold 15). Most of this is not in the body itself: 5 of the 28 points are its own statements and the rest belongs to 5 function items inside it that branch (onPointerDown, onPointerUp, onPointerMove, …). 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.
CollectionsPanel.CollectionItem (cyclomatic 28) databox/client/src/features/collections/tree/CollectionsPanel.tsx:502— CollectionsPanel.CollectionItem has cyclomatic complexity 28 (threshold 15). Of this number, 19 points are the body's own statements and 9 belong to 3 function items 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.
FacetsPanel.FacetsPanel (cyclomatic 28) databox/client/src/features/search/facets/FacetsPanel.tsx:48— FacetsPanel.FacetsPanel has cyclomatic complexity 28 (threshold 15). Most of this is not in the body itself: 5 of the 28 points are its own statements and the rest belongs to 11 function literals inside it that branch (lines 210, 89, 68, …). 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.
TicketDialog.TicketDialog (cyclomatic 28) databox/client/src/features/ticketing/TicketDialog.tsx:64— TicketDialog.TicketDialog has cyclomatic complexity 28 (threshold 15). Of this number, 14 points are the body's own statements and 14 belong to 7 function items 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.
StructureImporter.importSubdefsStructure (cyclomatic 28) databox/indexer/src/handlers/phraseanet/StructureImporter.ts:236— StructureImporter.importSubdefsStructure has cyclomatic complexity 28 (threshold 15). Of this number, 27 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AssetOutputMapper.map (cyclomatic 27) databox/api/src/Api/Mapper/Output/AssetOutputMapper.php:71— AssetOutputMapper.map has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AttributeAction.validateConfig (cyclomatic 27) databox/api/src/Automation/Action/AttributeAction.php:44— AttributeAction.validateConfig has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AssetExportProcessHandler.__invoke (cyclomatic 27) databox/api/src/Consumer/Handler/Asset/AssetExportProcessHandler.php:66— AssetExportProcessHandler.__invoke has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AQLGrammar.match_within_rectangle_operator (cyclomatic 27) databox/api/src/Elasticsearch/AQL/AQLGrammar.php:861— AQLGrammar.match_within_rectangle_operator has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
profileStore.useProfileStore (cyclomatic 27) databox/client/src/features/profiles/profileStore.ts:65— profileStore.useProfileStore has cyclomatic complexity 27 (threshold 15). Most of this is not in the body itself: 1 of the 27 points is its own statement and the rest belongs to 15 function literals inside it that branch (lines 137, 71, 105, …). 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.
ProfileGridTab.ProfileGridTab (cyclomatic 27) databox/client/src/features/profiles/manage/ProfileGridTab.tsx:136— ProfileGridTab.ProfileGridTab has cyclomatic complexity 27 (threshold 15). Most of this is not in the body itself: 2 of the 27 points are its own statements and the rest belongs to 10 function items inside it that branch (onDragEnd, a function literal at line 186, addTo, …). 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.
AudioPlayer.AudioPlayer (cyclomatic 27) expose/client/src/features/player/AudioPlayer.tsx:52— AudioPlayer.AudioPlayer has cyclomatic complexity 27 (threshold 15). Most of this is not in the body itself: 13 of the 27 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 115, 134, 121, …). 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.
FormBuilderEditor.FormBuilderEditor (cyclomatic 27) uploader/client/src/features/admin/FormBuilderEditor.tsx:62— FormBuilderEditor.FormBuilderEditor has cyclomatic complexity 27 (threshold 15). Of this number, 18 points are the body's own statements and 9 belong to 4 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.
canDrop.canDropAssets (cyclomatic 26) databox/client/src/features/dnd/canDrop.ts:71— canDrop.canDropAssets has cyclomatic complexity 26 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CollectionOutputMapper.map (cyclomatic 25) databox/api/src/Api/Mapper/Output/CollectionOutputMapper.php:63— CollectionOutputMapper.map has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ColorspaceDetector.parseJpeg (cyclomatic 25) lib/php/rendition-factory/src/Image/ColorspaceDetector.php:164— ColorspaceDetector.parseJpeg has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
DeleteAssetsDialog.DeleteAssetsDialog (cyclomatic 25) databox/client/src/features/assets/actions/DeleteAssetsDialog.tsx:35— DeleteAssetsDialog.DeleteAssetsDialog has cyclomatic complexity 25 (threshold 15). Of this number, 17 points are the body's own statements and 8 belong to 2 function items 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.
FormBuilder.FormBuilder (cyclomatic 25) uploader/client/src/features/form-builder/editor/FormBuilder.tsx:96— FormBuilder.FormBuilder has cyclomatic complexity 25 (threshold 15). Most of this is not in the body itself: 2 of the 25 points are its own statements and the rest belongs to 9 function items inside it that branch (onDragEnd, create, remove, …). 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.
Migration20230807Command.execute (cyclomatic 24) configurator/src/Command/Migration20230807Command.php:27— Migration20230807Command.execute has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
RenditionDefinitionInputMapper.map (cyclomatic 24) databox/api/src/Api/Mapper/Input/RenditionDefinitionInputMapper.php:20— RenditionDefinitionInputMapper.map has cyclomatic complexity 24 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
AQLGrammar.match_value (cyclomatic 24) databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1801— AQLGrammar.match_value has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
TranslateAction.doHandle (cyclomatic 24) databox/api/src/Integration/Aws/Translate/TranslateAction.php:31— TranslateAction.doHandle has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
IntegrationWorkflowRepository.createIntegrationsToWorkflow (cyclomatic 24) databox/api/src/Service/Workflow/IntegrationWorkflowRepository.php:72— IntegrationWorkflowRepository.createIntegrationsToWorkflow has cyclomatic complexity 24 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
Version20261111120000.kindOf (cyclomatic 24) uploader/api/migrations/Version20261111120000.php:369— Version20261111120000.kindOf has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
SortableSections.SortableSections (cyclomatic 24) databox/client/src/components/layout/SortableSections.tsx:48— SortableSections.SortableSections has cyclomatic complexity 24 (threshold 15). Most of this is not in the body itself: 3 of the 24 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 148, 170, 79, …). 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.
AnnotationToolbar.AnnotationToolbar (cyclomatic 24) databox/client/src/features/annotations/AnnotationToolbar.tsx:71— AnnotationToolbar.AnnotationToolbar has cyclomatic complexity 24 (threshold 15). Of this number, 18 points are the body's own statements and 6 belong to 6 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.
attributeEditorModel.computeBatchActions (cyclomatic 24) databox/client/src/features/attributes/editor/attributeEditorModel.ts:104— attributeEditorModel.computeBatchActions has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
entityColumns.buildEntityColumns (cyclomatic 24) databox/client/src/features/workspaces/manage/entities/entityColumns.tsx:196— entityColumns.buildEntityColumns has cyclomatic complexity 24 (threshold 15). Most of this is not in the body itself: 8 of the 24 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 292, 467, 217, …). 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.
UnsavedChangesGuard.UnsavedChangesGuard (cyclomatic 24) lib/js/next-ui/src/modals/UnsavedChangesGuard.tsx:29— UnsavedChangesGuard.UnsavedChangesGuard has cyclomatic complexity 24 (threshold 15). Most of this is not in the body itself: 1 of the 24 points is its own statement and the rest belongs to 8 function literals inside it that branch (lines 62, 104, 41, …). 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.
AssetListener.onFlush (cyclomatic 23) databox/api/src/Doctrine/Listener/AssetListener.php:32— AssetListener.onFlush has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
DateNormalizer.normalizeDate (cyclomatic 23) databox/api/src/Elasticsearch/AQL/DateNormalizer.php:11— DateNormalizer.normalizeDate has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
WorkspaceIntegrationVoter.voteOnAttribute (cyclomatic 23) databox/api/src/Security/Voter/WorkspaceIntegrationVoter.php:33— WorkspaceIntegrationVoter.voteOnAttribute has cyclomatic complexity 23 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
CollectionTreePicker.CollectionTreeNode (cyclomatic 23) databox/client/src/components/form/CollectionTreePicker.tsx:363— CollectionTreePicker.CollectionTreeNode has cyclomatic complexity 23 (threshold 15). Of this number, 18 points are the body's own statements and 5 belong to 5 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
TopBar.TopBar (cyclomatic 23) databox/client/src/components/layout/TopBar.tsx:65— TopBar.TopBar has cyclomatic complexity 23 (threshold 15). Of this number, 20 points are the body's own statements and 3 belong to 2 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.
ClipTimeline.ClipTimeline (cyclomatic 23) databox/client/src/features/clip/ClipTimeline.tsx:75— ClipTimeline.ClipTimeline has cyclomatic complexity 23 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This shape REPEATS in the file: one other method here (ClipTimeline.ClipTimeline::onKeyDown) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
ConfigForm.TextField (cyclomatic 23) databox/client/src/features/integrations/config/ConfigForm.tsx:299— ConfigForm.TextField has cyclomatic complexity 23 (threshold 15). Of this number, 16 points are the body's own statements and 7 belong to 5 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.
SearchConditionChip.HumanizedValue (cyclomatic 23) databox/client/src/features/search/conditions/SearchConditionChip.tsx:373— SearchConditionChip.HumanizedValue has cyclomatic complexity 23 (threshold 15). Of this number, 22 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
FilterRulesTab.AttributeRules (cyclomatic 23) databox/client/src/features/workspaces/manage/tabs/FilterRulesTab.tsx:66— FilterRulesTab.AttributeRules has cyclomatic complexity 23 (threshold 15). Of this number, 17 points are the body's own statements and 6 belong to 3 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.
AuditLogCollectionProvider.applyFilters (cyclomatic 22) databox/api/src/Api/Provider/AuditLogCollectionProvider.php:57— AuditLogCollectionProvider.applyFilters has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AttributeDataImporter.importAttributes (cyclomatic 22) databox/api/src/Attribute/AttributeDataImporter.php:27— AttributeDataImporter.importAttributes has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AQLGrammar.match_within_circle_operator (cyclomatic 22) databox/api/src/Elasticsearch/AQL/AQLGrammar.php:781— AQLGrammar.match_within_circle_operator has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
FileAnalysisUnblocker.unblockAsset (cyclomatic 22) databox/api/src/File/FileAnalysisUnblocker.php:88— FileAnalysisUnblocker.unblockAsset has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
BasketVoter.voteOnAttribute (cyclomatic 22) databox/api/src/Security/Voter/BasketVoter.php:34— BasketVoter.voteOnAttribute has cyclomatic complexity 22 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
ClientThemeNormalizer.normalizeFonts (cyclomatic 22) databox/api/src/Service/Admin/ClientThemeNormalizer.php:193— ClientThemeNormalizer.normalizeFonts has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
PublicationFilter.apply (cyclomatic 22) expose/api/src/Filter/PublicationFilter.php:53— PublicationFilter.apply has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
VideoSummaryTransformerModule.transform (cyclomatic 22) lib/php/rendition-factory/src/Transformer/Video/VideoSummaryTransformerModule.php:127— VideoSummaryTransformerModule.transform has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Version20261111120000.mergeBuilderTranslations (cyclomatic 22) uploader/api/migrations/Version20261111120000.php:305— Version20261111120000.mergeBuilderTranslations has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
EntityValueCard.EntityValueCard (cyclomatic 22) databox/client/src/features/entities/explore/EntityValueCard.tsx:83— EntityValueCard.EntityValueCard has cyclomatic complexity 22 (threshold 15). Of this number, 15 points are the body's own statements and 7 belong to 4 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.
ConditionDialog.ConditionDialog (cyclomatic 22) databox/client/src/features/search/conditions/ConditionDialog.tsx:47— ConditionDialog.ConditionDialog has cyclomatic complexity 22 (threshold 15). Of this number, 11 points are the body's own statements and 11 belong to 4 function items 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.
AuthProvider.AuthProvider (cyclomatic 22) databox/client/src/lib/auth/AuthProvider.tsx:89— AuthProvider.AuthProvider has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 6 of the 22 points are its own statements and the rest belongs to 9 function literals inside it that branch (lines 146, 105, 112, …). 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.
PublicationEditScreen.PublicationEditForm (cyclomatic 22) expose/client/src/features/admin/PublicationEditScreen.tsx:86— PublicationEditScreen.PublicationEditForm has cyclomatic complexity 22 (threshold 15). Of this number, 11 points are the body's own statements and 11 belong to 3 function items 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.
PublicationHeader.PublicationHeader (cyclomatic 22) expose/client/src/features/publication/PublicationHeader.tsx:44— PublicationHeader.PublicationHeader has cyclomatic complexity 22 (threshold 15). Of this number, 16 points are the body's own statements and 6 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
customTheme.normalizeFonts (cyclomatic 22) lib/js/next-theme/src/customTheme.ts:512— customTheme.normalizeFonts has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
definition.validateValues (cyclomatic 22) REDACTED:369— definition.validateValues has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AQLGrammar.match_function_call (cyclomatic 21) databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1411— AQLGrammar.match_function_call has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ExportDialog.ExportDialog (cyclomatic 21) databox/client/src/features/assets/actions/ExportDialog.tsx:31— ExportDialog.ExportDialog 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 6 function items inside it that branch (submit, a function literal at line 72, a function literal at line 86, …). 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.
basketStore.useBasketStore (cyclomatic 21) databox/client/src/features/baskets/basketStore.ts:35— basketStore.useBasketStore has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 1 of the 21 points is its own statement and the rest belongs to 9 function literals inside it that branch (lines 43, 122, 92, …). 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.
VideoFilmstrip.VideoFilmstrip (cyclomatic 21) databox/client/src/features/clip/VideoFilmstrip.tsx:33— VideoFilmstrip.VideoFilmstrip has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 8 of the 21 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 127, 178, 56, …). 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.
ImportAssetsDialog.ImportAssetsDialog (cyclomatic 21) databox/client/src/features/import/ImportAssetsDialog.tsx:105— ImportAssetsDialog.ImportAssetsDialog has cyclomatic complexity 21 (threshold 15). Of this number, 11 points are the body's own statements and 10 belong to 4 function items 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.
InstancePermissionsScreen.InstancePermissionsScreen (cyclomatic 21) databox/client/src/features/permissions/InstancePermissionsScreen.tsx:82— InstancePermissionsScreen.InstancePermissionsScreen has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 7 of the 21 points are its own statements and the rest belongs to 9 function items inside it that branch (getRowLabel, a function literal at line 312, run, …). 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.
ExposePublishForm.ExposePublishForm (cyclomatic 21) databox/client/src/features/saved-searches/automations/actions/ExposePublishForm.tsx:180— ExposePublishForm.ExposePublishForm has cyclomatic complexity 21 (threshold 15). Of this number, 14 points are the body's own statements and 7 belong to 4 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.
ShareAssetView.ShareAssetView (cyclomatic 21) databox/client/src/features/share/ShareAssetView.tsx:47— ShareAssetView.ShareAssetView has cyclomatic complexity 21 (threshold 15). Of this number, 13 points are the body's own statements and 8 belong to 2 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.
useRequestErrorHandler.useRequestErrorHandler (cyclomatic 21) lib/js/api/src/useRequestErrorHandler.ts:14— useRequestErrorHandler.useRequestErrorHandler has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 1 of the 21 points is its own statement and the rest belongs to one function literal inside it that branches (line 17). The decisions are inside the literal, 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 literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
FileTile.FileTile (cyclomatic 21) uploader/client/src/features/upload/FileTile.tsx:36— FileTile.FileTile has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AttributeAssigner.assignAttributeFromInput (cyclomatic 20) databox/api/src/Attribute/AttributeAssigner.php:40— AttributeAssigner.assignAttributeFromInput has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AQLGrammar.match_in_operator (cyclomatic 20) databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1140— AQLGrammar.match_in_operator has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AQLGrammar.match_value_product (cyclomatic 20) databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1515— AQLGrammar.match_value_product has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (AQLGrammar.match_value_sum) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
AQLGrammar.match_value_sum (cyclomatic 20) databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1624— AQLGrammar.match_value_sum has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (AQLGrammar.match_value_product) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
ExposeClient.getAssetProperties (cyclomatic 20) databox/api/src/Integration/Phrasea/Expose/ExposeClient.php:183— ExposeClient.getAssetProperties has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
VideoTransformer.doVideo (cyclomatic 20) lib/php/rendition-factory/src/Transformer/Video/VideoTransformer.php:24— VideoTransformer.doVideo has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Version20261111120000.convertLiForm (cyclomatic 20) uploader/api/migrations/Version20261111120000.php:182— Version20261111120000.convertLiForm has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CopyMoveDialog.CopyMoveDialog (cyclomatic 20) databox/client/src/features/assets/actions/CopyMoveDialog.tsx:25— CopyMoveDialog.CopyMoveDialog has cyclomatic complexity 20 (threshold 15). Of this number, 16 points are the body's own statements and 4 belong to one function item inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
EntityListExploreScreen.ExploreBrowser (cyclomatic 20) databox/client/src/features/entities/explore/EntityListExploreScreen.tsx:83— EntityListExploreScreen.ExploreBrowser has cyclomatic complexity 20 (threshold 15). Of this number, 17 points are the body's own statements and 3 belong to 3 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.
ProfileAttributesTab.ProfileSectionEditor (cyclomatic 20) databox/client/src/features/profiles/manage/ProfileAttributesTab.tsx:115— ProfileAttributesTab.ProfileSectionEditor has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 1 of the 20 points is its own statement and the rest belongs to 8 function items inside it that branch (onDragEnd, insertionAt, add, …). 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.
useSearchSuggestions.useSearchSuggestions (cyclomatic 20) databox/client/src/features/search/suggest/useSearchSuggestions.ts:36— useSearchSuggestions.useSearchSuggestions has cyclomatic complexity 20 (threshold 15). Of this number, 19 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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.
ConditionBuilder.pickerFor (cyclomatic 20) databox/client/src/features/search/conditions/ConditionBuilder.tsx:686— ConditionBuilder.pickerFor has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
indexer.importStory (cyclomatic 20) databox/indexer/src/handlers/phraseanet/indexer.ts:488— indexer.importStory has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Version20250415153255.up (cyclomatic 19) configurator/migrations/Version20250415153255.php:24— Version20250415153255.up has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
EnvParser.parse (cyclomatic 19) configurator/src/Documentation/Parser/EnvParser.php:27— EnvParser.parse has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Version20260901151900.up (cyclomatic 19) databox/api/migrations/Version20260901151900.php:35— Version20260901151900.up has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
FaceRecognitionDoctrineListener.onFlush (cyclomatic 19) databox/api/src/Integration/Core/FaceRecognition/FaceRecognitionDoctrineListener.php:56— FaceRecognitionDoctrineListener.onFlush has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AclListener.handleChange (cyclomatic 19) databox/api/src/Listener/AclListener.php:139— AclListener.handleChange has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AclListener.indexObject (cyclomatic 19) databox/api/src/Listener/AclListener.php:272— AclListener.indexObject has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
GridCardZones.GridCardZones (cyclomatic 19) databox/client/src/features/assets/list/layouts/GridCardZones.tsx:88— GridCardZones.GridCardZones has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 3 of the 19 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 107, 211). 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.
AuditLogScreen.AuditLogScreen (cyclomatic 19) databox/client/src/features/audit-log/AuditLogScreen.tsx:113— AuditLogScreen.AuditLogScreen has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 9 of the 19 points are its own statements and the rest belongs to 10 function literals inside it that branch (lines 127, 279, 302, …). 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.
ClipTimeline.ClipTimeline::onKeyDown (cyclomatic 19) databox/client/src/features/clip/ClipTimeline.tsx:145— ClipTimeline.ClipTimeline::onKeyDown has cyclomatic complexity 19 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing. This shape REPEATS in the file: one other method here (ClipTimeline.ClipTimeline) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
RekognitionPanel.RekognitionPanel (cyclomatic 19) databox/client/src/features/integrations/rekognition/RekognitionPanel.tsx:115— RekognitionPanel.RekognitionPanel has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 6 of the 19 points are its own statements and the rest belongs to 4 function items inside it that branch (a function literal at line 302, a function literal at line 351, run, …). 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.
Parser.atom (cyclomatic 19) databox/client/src/features/search/aql/parser.ts:530— Parser.atom has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ResultProvider.ResultProvider (cyclomatic 19) databox/client/src/features/search/ResultProvider.tsx:51— ResultProvider.ResultProvider has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 1 of the 19 points is its own statement and the rest belongs to 5 function literals inside it that branch (lines 117, 155, 92, …). 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.
WorkflowHeader.WorkflowHeader (cyclomatic 19) databox/client/src/features/workflows/WorkflowHeader.tsx:55— WorkflowHeader.WorkflowHeader has cyclomatic complexity 19 (threshold 15). Of this number, 18 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
http.createInstance (cyclomatic 19) databox/client/src/lib/api/http.ts:83— http.createInstance has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 1 of the 19 points is its own statement and the rest belongs to 3 function literals inside it that branch (lines 96, 143, 178). 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.
useFileDrop.useFileDrop (cyclomatic 19) uploader/client/src/features/upload/useFileDrop.tsx:28— useFileDrop.useFileDrop has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 1 of the 19 points is its own statement and the rest belongs to 3 function items inside it that branch (reportRejections, a function literal at line 138, listNames). 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.
CollectionInputMapper.map (cyclomatic 18) databox/api/src/Api/Mapper/Input/CollectionInputMapper.php:24— CollectionInputMapper.map has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AuditLogListener.onFlush (cyclomatic 18) databox/api/src/Doctrine/Listener/AuditLogListener.php:86— AuditLogListener.onFlush has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AuditLogListener.logSemanticChange (cyclomatic 18) databox/api/src/Doctrine/Listener/AuditLogListener.php:178— AuditLogListener.logSemanticChange has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AQLGrammar.match_condition (cyclomatic 18) databox/api/src/Elasticsearch/AQL/AQLGrammar.php:182— AQLGrammar.match_condition has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AQLGrammar.match_between_operator (cyclomatic 18) databox/api/src/Elasticsearch/AQL/AQLGrammar.php:957— AQLGrammar.match_between_operator has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AttributeSearch.buildFacets (cyclomatic 18) databox/api/src/Elasticsearch/AttributeSearch.php:356— AttributeSearch.buildFacets has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
PrivacyField.PrivacyField (cyclomatic 18) databox/client/src/components/form/PrivacyField.tsx:59— PrivacyField.PrivacyField has cyclomatic complexity 18 (threshold 15). Of this number, 16 points are the body's own statements and 2 belong to 2 function literals 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.
QuarantineScreen.QuarantineScreen (cyclomatic 18) databox/client/src/features/assets/quarantine/QuarantineScreen.tsx:61— QuarantineScreen.QuarantineScreen has cyclomatic complexity 18 (threshold 15). Of this number, 12 points are the body's own statements and 6 belong to 5 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.
AttributeList.AttributeRow (cyclomatic 18) databox/client/src/features/attributes/AttributeList.tsx:233— AttributeList.AttributeRow has cyclomatic complexity 18 (threshold 15). Of this number, 17 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AttributesEditor.AttributeField (cyclomatic 18) databox/client/src/features/attributes/editor/AttributesEditor.tsx:250— AttributesEditor.AttributeField has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 4 of the 18 points are its own statements and the rest belongs to 7 function items inside it that branch (annotationButton, a function literal at line 401, a function literal at line 302, …). 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.
useTimelineDrag.useTimelineDrag::move (cyclomatic 18) databox/client/src/features/clip/useTimelineDrag.ts:129— useTimelineDrag.useTimelineDrag::move has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CollectionsPanel.CollectionsPanel (cyclomatic 18) databox/client/src/features/collections/tree/CollectionsPanel.tsx:75— CollectionsPanel.CollectionsPanel has cyclomatic complexity 18 (threshold 15). Of this number, 13 points are the body's own statements and 5 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CreateAttributeDialog.CreateAttributeDialog (cyclomatic 18) databox/client/src/features/integrations/config/pickers/CreateAttributeDialog.tsx:41— CreateAttributeDialog.CreateAttributeDialog has cyclomatic complexity 18 (threshold 15). Of this number, 12 points are the body's own statements and 6 belong to one function item inside it that branches. 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.
OperationTasksScreen.TaskDetails (cyclomatic 18) databox/client/src/features/operation-tasks/OperationTasksScreen.tsx:574— OperationTasksScreen.TaskDetails has cyclomatic complexity 18 (threshold 15). Of this number, 14 points are the body's own statements and 4 belong to 3 function items 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.
DateHistogramFacet.DateHistogramFacet (cyclomatic 18) databox/client/src/features/search/facets/widgets/DateHistogramFacet.tsx:19— DateHistogramFacet.DateHistogramFacet has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 5 of the 18 points are its own statements and the rest belongs to 5 function items inside it that branch (a function literal at line 48, a function literal at line 56, a function literal at line 101, …). 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.
ShareDownloadDialog.ShareDownloadDialog (cyclomatic 18) databox/client/src/features/share/ShareDownloadDialog.tsx:43— ShareDownloadDialog.ShareDownloadDialog has cyclomatic complexity 18 (threshold 15). Of this number, 9 points are the body's own statements and 9 belong to 6 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.
multiPartUpload.multipartUpload (cyclomatic 18) lib/js/api/src/multiPartUpload.ts:140— multiPartUpload.multipartUpload has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 8 of the 18 points are its own statements and the rest belongs to 7 function items inside it that branch (uploadPart, getUrl, throwIfAborted, …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
sentryTunnel.createSentryTunnelHandler.<returned closure> (cyclomatic 18) lib/js/next-core/src/server/sentryTunnel.ts:215— sentryTunnel.createSentryTunnelHandler.<returned closure> has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
WorkspaceInputMapper.map (cyclomatic 17) databox/api/src/Api/Mapper/Input/WorkspaceInputMapper.php:28— WorkspaceInputMapper.map has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
AttributeSearch.buildAttributeQuery (cyclomatic 17) databox/api/src/Elasticsearch/AttributeSearch.php:238— AttributeSearch.buildAttributeQuery has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
FileAnalyzerAction.doHandle (cyclomatic 17) databox/api/src/Integration/Core/FileAnalyzer/FileAnalyzerAction.php:26— FileAnalyzerAction.doHandle has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AssetImportInputFactory.create (cyclomatic 17) databox/api/src/Service/Import/AssetImportInputFactory.php:39— AssetImportInputFactory.create has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CollectionTreePicker.CollectionTreePicker (cyclomatic 17) databox/client/src/components/form/CollectionTreePicker.tsx:79— CollectionTreePicker.CollectionTreePicker has cyclomatic complexity 17 (threshold 15). Of this number, 11 points are the body's own statements and 6 belong to 4 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.
TagsInput.TagsInput (cyclomatic 17) databox/client/src/components/form/TagsInput.tsx:38— TagsInput.TagsInput has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 3 of the 17 points are its own statements and the rest belongs to 5 function items inside it that branch (onKeyDown, a function literal at line 55, add, …). 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.
AssetRenditionsTab.RenditionCard (cyclomatic 17) databox/client/src/features/assets/manage/tabs/AssetRenditionsTab.tsx:155— AssetRenditionsTab.RenditionCard has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
FilePlayer.FilePlayer (cyclomatic 17) databox/client/src/features/assets/player/FilePlayer.tsx:89— FilePlayer.FilePlayer has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
useTimelineView.useTimelineView (cyclomatic 17) databox/client/src/features/clip/useTimelineView.ts:31— useTimelineView.useTimelineView has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 7 of the 17 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 113, 48, 138). 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.
messageMarkup.parseMessage (cyclomatic 17) databox/client/src/features/discussion/messageMarkup.ts:136— messageMarkup.parseMessage has cyclomatic complexity 17 (threshold 15). Of this number, 15 points are the body's own statements and 2 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AppDndProvider.AppDndProvider (cyclomatic 17) databox/client/src/features/dnd/AppDndProvider.tsx:60— AppDndProvider.AppDndProvider has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 1 of the 17 points is its own statement and the rest belongs to 6 function items inside it that branch (onDragEnd, a function literal at line 76, a function literal at line 112, …). 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.
ProfileAttributesTab.DisplayedRow (cyclomatic 17) databox/client/src/features/profiles/manage/ProfileAttributesTab.tsx:351— ProfileAttributesTab.DisplayedRow has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
SavedSearchList.SavedSearchRow (cyclomatic 17) databox/client/src/features/saved-searches/SavedSearchList.tsx:131— SavedSearchList.SavedSearchRow has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 8 of the 17 points are its own statements and the rest belongs to 3 function items inside it that branch (menu, open, a function literal at line 194). 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.
SortByButton.SortEditor (cyclomatic 17) databox/client/src/features/search/sort/SortByButton.tsx:101— SortByButton.SortEditor has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 3 of the 17 points are its own statements and the rest belongs to 10 function items inside it that branch (a function literal at line 159, onDragEnd, a function literal at line 189, …). 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.
SharePage.ShareContent (cyclomatic 17) databox/client/src/features/share/SharePage.tsx:156— SharePage.ShareContent has cyclomatic complexity 17 (threshold 15). Of this number, 11 points are the body's own statements and 6 belong to 3 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.
UploadDialog.UploadDialog::submit (cyclomatic 17) databox/client/src/features/upload/UploadDialog.tsx:232— UploadDialog.UploadDialog::submit has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (UploadDialog.UploadDialog) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
axios.createHttpClient (cyclomatic 17) databox/indexer/src/lib/axios.ts:25— axios.createHttpClient has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 2 of the 17 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 48, 104, 164). 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.
shared.createAsset (cyclomatic 17) databox/indexer/src/handlers/phraseanet/shared.ts:140— shared.createAsset has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
WorkspaceIntegrationInputMapper.map (cyclomatic 16) databox/api/src/Api/Mapper/Input/WorkspaceIntegrationInputMapper.php:31— WorkspaceIntegrationInputMapper.map has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
PutProfileItemProcessor.process (cyclomatic 16) databox/api/src/Api/Processor/PutProfileItemProcessor.php:27— PutProfileItemProcessor.process has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
AttributeValidator.validateAttributeInputs (cyclomatic 16) databox/api/src/Attribute/AttributeValidator.php:108— AttributeValidator.validateAttributeInputs has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
FilenameAnalyzer.analyzeFile (cyclomatic 16) databox/api/src/Border/FileAnalyzer/Analyzer/FilenameAnalyzer.php:70— FilenameAnalyzer.analyzeFile has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AQLToESQuery.expressionToScript (cyclomatic 16) databox/api/src/Elasticsearch/AQL/AQLToESQuery.php:530— AQLToESQuery.expressionToScript has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AssetSearch.applySavedSearch (cyclomatic 16) databox/api/src/Elasticsearch/AssetSearch.php:561— AssetSearch.applySavedSearch has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AssetPostTransformListener.compileAttributes (cyclomatic 16) databox/api/src/Elasticsearch/Listener/AssetPostTransformListener.php:111— AssetPostTransformListener.compileAttributes has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ProfileItem.validate (cyclomatic 16) databox/api/src/Entity/Profile/ProfileItem.php:427— ProfileItem.validate has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
FileAnalysisReevaluator.rewriteAnalysis (cyclomatic 16) databox/api/src/File/FileAnalysisReevaluator.php:65— FileAnalysisReevaluator.rewriteAnalysis has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AssetDataTemplateVoter.voteOnAttribute (cyclomatic 16) databox/api/src/Security/Voter/AssetDataTemplateVoter.php:31— AssetDataTemplateVoter.voteOnAttribute has cyclomatic complexity 16 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
AttributeEntityVoter.voteOnAttribute (cyclomatic 16) databox/api/src/Security/Voter/AttributeEntityVoter.php:29— AttributeEntityVoter.voteOnAttribute has cyclomatic complexity 16 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
PageVoter.voteOnAttribute (cyclomatic 16) databox/api/src/Security/Voter/PageVoter.php:31— PageVoter.voteOnAttribute has cyclomatic complexity 16 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
ShareVoter.voteOnAttribute (cyclomatic 16) databox/api/src/Security/Voter/ShareVoter.php:34— ShareVoter.voteOnAttribute has cyclomatic complexity 16 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
PublicationProfileVoter.voteOnAttribute (cyclomatic 16) expose/api/src/Security/Voter/PublicationProfileVoter.php:28— PublicationProfileVoter.voteOnAttribute has cyclomatic complexity 16 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
AssetNormalizer.normalize (cyclomatic 16) expose/api/src/Serializer/Normalizer/AssetNormalizer.php:40— AssetNormalizer.normalize has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
VideoToAnimationTransformerModule.transform (cyclomatic 16) lib/php/rendition-factory/src/Transformer/Video/VideoToAnimationTransformerModule.php:128— VideoToAnimationTransformerModule.transform has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
FilePicker.FilePicker (cyclomatic 16) databox/client/src/components/form/FilePicker.tsx:23— FilePicker.FilePicker has cyclomatic complexity 16 (threshold 15). Of this number, 12 points are the body's own statements and 4 belong to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
GridLayout.GridItem (cyclomatic 16) databox/client/src/features/assets/list/layouts/GridLayout.tsx:92— GridLayout.GridItem has cyclomatic complexity 16 (threshold 15). Of this number, 15 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AssetPanel.useSingleLineTabs (cyclomatic 16) databox/client/src/features/assets/view/AssetPanel.tsx:257— AssetPanel.useSingleLineTabs has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 5 function literals inside it that branch (lines 307, 270, 275, …). 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.
StoryCarousel.StoryCarousel (cyclomatic 16) databox/client/src/features/assets/view/StoryCarousel.tsx:136— StoryCarousel.StoryCarousel has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 6 of the 16 points are its own statements and the rest belongs to 7 function items inside it that branch (move, onDragEnd, a function literal at line 285, …). 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.
WebVttTranscript.WebVttTranscript (cyclomatic 16) databox/client/src/features/attributes/types/WebVttTranscript.tsx:42— WebVttTranscript.WebVttTranscript has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 2 of the 16 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 73, 127, 59, …). 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.
BasketsPanel.BasketRow (cyclomatic 16) databox/client/src/features/baskets/BasketsPanel.tsx:127— BasketsPanel.BasketRow has cyclomatic complexity 16 (threshold 15). Of this number, 8 points are the body's own statements and 8 belong to 3 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.
BasketViewRoute.BasketViewRoute (cyclomatic 16) databox/client/src/features/baskets/view/BasketViewRoute.tsx:53— BasketViewRoute.BasketViewRoute has cyclomatic complexity 16 (threshold 15). Of this number, 10 points are the body's own statements and 6 belong to 4 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.
useClipPlayback.useClipPlayback (cyclomatic 16) databox/client/src/features/clip/useClipPlayback.ts:23— useClipPlayback.useClipPlayback has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 2 of the 16 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 51, 34, 42, …). 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.
executeDrop.dropAssets (cyclomatic 16) databox/client/src/features/dnd/executeDrop.ts:94— executeDrop.dropAssets has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
SaveSearchDialog.SaveSearchDialog (cyclomatic 16) databox/client/src/features/saved-searches/SaveSearchDialog.tsx:25— SaveSearchDialog.SaveSearchDialog has cyclomatic complexity 16 (threshold 15). Of this number, 10 points are the body's own statements and 6 belong to one function item inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
AttributeActionForm.AttributeActionForm (cyclomatic 16) databox/client/src/features/saved-searches/automations/actions/AttributeActionForm.tsx:25— AttributeActionForm.AttributeActionForm has cyclomatic complexity 16 (threshold 15). Of this number, 9 points are the body's own statements and 7 belong to 3 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.
filterSuggestions.suggestFields (cyclomatic 16) databox/client/src/features/search/suggest/filterSuggestions.ts:117— filterSuggestions.suggestFields has cyclomatic complexity 16 (threshold 15). Of this number, 14 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ConditionBuilder.FieldPicker (cyclomatic 16) databox/client/src/features/search/conditions/ConditionBuilder.tsx:438— ConditionBuilder.FieldPicker has cyclomatic complexity 16 (threshold 15). Of this number, 10 points are the body's own statements and 6 belong to 4 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.
ConditionBuilder.ValueInput (cyclomatic 16) databox/client/src/features/search/conditions/ConditionBuilder.tsx:597— ConditionBuilder.ValueInput has cyclomatic complexity 16 (threshold 15). Of this number, 14 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
EntityForm.EntityForm::save (cyclomatic 16) databox/client/src/features/workspaces/manage/entities/EntityForm.tsx:70— EntityForm.EntityForm::save has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
UploadScreen.Stepper (cyclomatic 16) uploader/client/src/features/upload/UploadScreen.tsx:920— UploadScreen.Stepper has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 3 of the 16 points are its own statements and the rest belongs to one function literal inside it that branches (line 959). The decisions are inside the literal, 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 literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
D12 · Dependency Hygiene· One package at two majors across the workspace · ×1
One package at two majors across the workspace: @sentry/react — `@sentry/react` is maintained at 2 different major versions inside this one repository — major 7 in lib/js/core/package.json; major 11 in lib/js/next-core/package.json. Every major carries its own breaking changes, advisories and upgrade path, so the cost of keeping current is paid more than once; and where the packages are installed together, the resolver cannot dedupe them, so both copies ship.
AQLGrammar.match_operator (cognitive 246) databox/api/src/Elasticsearch/AQL/AQLGrammar.php:527— AQLGrammar.match_operator has cognitive complexity 246 (threshold 15). Drivers by points: if/else 40 (150 pts), loops 13 (55 pts), ternaries 7 (41 pts) (nesting depth added 186). 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.
ClipEditorDialog.ClipEditorDialog (cognitive 110) databox/client/src/features/clip/ClipEditorDialog.tsx:81— ClipEditorDialog.ClipEditorDialog has cognitive complexity 110 (threshold 15). Drivers by points: ternaries 39 (75 pts), if/else 15 (20 pts), boolean chains 14, error handling 1 (nesting depth added 41). Of this number, 72 points are the body's own statements and 38 belong to 13 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.
AttributeBatchEditorRoute.AttributeBatchEditorRoute (cognitive 107) databox/client/src/features/attributes/batch/AttributeBatchEditorRoute.tsx:143— AttributeBatchEditorRoute.AttributeBatchEditorRoute has cognitive complexity 107 (threshold 15). Drivers by points: ternaries 35 (60 pts), if/else 27 (28 pts), boolean chains 18, error handling 1 (nesting depth added 26). Of this number, 22 points are the body's own statements and 85 belong to 31 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.
DefinitionManager.DefinitionManager (cognitive 106) databox/client/src/features/workspaces/manage/DefinitionManager.tsx:134— DefinitionManager.DefinitionManager has cognitive complexity 106 (threshold 15). Drivers by points: ternaries 28 (73 pts), boolean chains 19, if/else 7 (11 pts), error handling 2 (3 pts) (nesting depth added 50). Of this number, 56 points are the body's own statements and 50 belong to 10 function items inside it that branch. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
AssetMap.MapView (cognitive 104) databox/client/src/features/map/AssetMap.tsx:193— AssetMap.MapView has cognitive complexity 104 (threshold 15). Drivers by points: if/else 43 (47 pts), ternaries 25 (30 pts), boolean chains 26, match/switch 1 (nesting depth added 9). Of this number, 22 points are the body's own statements and 82 belong to 40 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
BatchAttributeManager.handleBatch (cognitive 100) databox/api/src/Attribute/BatchAttributeManager.php:92— BatchAttributeManager.handleBatch has cognitive complexity 100 (threshold 15). Drivers by points: if/else 27 (70 pts), loops 8 (21 pts), error handling 1 (4 pts), boolean chains 3, match/switch 1 (2 pts) (nesting depth added 60). 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.
AssetViewRoute.AssetViewRoute (cognitive 97) databox/client/src/features/assets/view/AssetViewRoute.tsx:110— AssetViewRoute.AssetViewRoute has cognitive complexity 97 (threshold 15). Drivers by points: ternaries 38 (54 pts), if/else 21 (22 pts), boolean chains 21 (nesting depth added 17). Of this number, 64 points are the body's own statements and 33 belong to 15 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
indexer.phraseanetIndexer (cognitive 92) databox/indexer/src/handlers/phraseanet/indexer.ts:41— indexer.phraseanetIndexer has cognitive complexity 92 (threshold 15). Drivers by points: if/else 16 (50 pts), loops 11 (33 pts), ternaries 2 (5 pts), boolean chains 2, error handling 1 (2 pts) (nesting depth added 60). 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.
AssetExportProcessHandler.__invoke (cognitive 83) databox/api/src/Consumer/Handler/Asset/AssetExportProcessHandler.php:66— AssetExportProcessHandler.__invoke has cognitive complexity 83 (threshold 15). Drivers by points: if/else 15 (46 pts), loops 5 (18 pts), error handling 3 (10 pts), ternaries 2 (8 pts), boolean chains 1 (nesting depth added 57). 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.
AQLGrammar.match_value (cognitive 83) databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1801— AQLGrammar.match_value has cognitive complexity 83 (threshold 15). Drivers by points: if/else 12 (42 pts), ternaries 6 (26 pts), loops 5 (15 pts) (nesting depth added 60). 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.
useAssetActions.useAssetActions (cognitive 83) databox/client/src/features/assets/actions/useAssetActions.tsx:139— useAssetActions.useAssetActions has cognitive complexity 83 (threshold 15). Drivers by points: if/else 35 (61 pts), ternaries 6 (13 pts), boolean chains 7, error handling 1 (2 pts) (nesting depth added 34). None of this is in the body itself: all 83 points belong to 11 function literals inside it that branch (lines 157, 322, 184, …). 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.
AssetThumb.AssetThumb (cognitive 80) databox/client/src/features/assets/list/AssetThumb.tsx:52— AssetThumb.AssetThumb has cognitive complexity 80 (threshold 15). Drivers by points: ternaries 26 (45 pts), boolean chains 21, if/else 9 (14 pts) (nesting depth added 24). Of this number, 55 points are the body's own statements and 25 belong to 7 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.
AssetSearch.applySort (cognitive 75) databox/api/src/Elasticsearch/AssetSearch.php:617— AssetSearch.applySort has cognitive complexity 75 (threshold 15). Drivers by points: if/else 20 (61 pts), error handling 2 (7 pts), boolean chains 5, loops 1 (2 pts) (nesting depth added 47). 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.
CollectionVoter.doVote (cognitive 75) databox/api/src/Security/Voter/CollectionVoter.php:47— CollectionVoter.doVote has cognitive complexity 75 (threshold 15). Drivers by points: boolean chains 67, if/else 4 (5 pts), ternaries 2, match/switch 1 (nesting depth added 1). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
ExposeClient.getAssetProperties (cognitive 73) databox/api/src/Integration/Phrasea/Expose/ExposeClient.php:183— ExposeClient.getAssetProperties has cognitive complexity 73 (threshold 15). Drivers by points: if/else 12 (37 pts), loops 8 (27 pts), ternaries 2 (9 pts) (nesting depth added 51). 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.
attributeEditorModel.computeBatchActions (cognitive 73) databox/client/src/features/attributes/editor/attributeEditorModel.ts:104— attributeEditorModel.computeBatchActions has cognitive complexity 73 (threshold 15). Drivers by points: if/else 15 (52 pts), loops 4 (11 pts), ternaries 2 (7 pts), boolean chains 3 (nesting depth added 49). 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.
AQLGrammar.match_value_product (cognitive 67) databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1515— AQLGrammar.match_value_product has cognitive complexity 67 (threshold 15). Drivers by points: if/else 14 (46 pts), loops 5 (15 pts), ternaries 2 (6 pts) (nesting depth added 46). 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. This shape REPEATS in the file: one other method here (AQLGrammar.match_value_sum) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
AQLGrammar.match_value_sum (cognitive 67) databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1624— AQLGrammar.match_value_sum has cognitive complexity 67 (threshold 15). Drivers by points: if/else 14 (46 pts), loops 5 (15 pts), ternaries 2 (6 pts) (nesting depth added 46). 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. This shape REPEATS in the file: one other method here (AQLGrammar.match_value_product) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TranslateAction.doHandle (cognitive 67) databox/api/src/Integration/Aws/Translate/TranslateAction.php:31— TranslateAction.doHandle has cognitive complexity 67 (threshold 15). Drivers by points: if/else 15 (40 pts), loops 8 (19 pts), ternaries 2 (8 pts) (nesting depth added 42). 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.
CsvAttributeEntityImporter.import (cognitive 65) databox/api/src/Service/Asset/Attribute/AttributeEntity/Importer/CsvAttributeEntityImporter.php:29— CsvAttributeEntityImporter.import has cognitive complexity 65 (threshold 15). Drivers by points: if/else 17 (38 pts), ternaries 3 (15 pts), loops 4 (7 pts), match/switch 1 (4 pts), boolean chains 1 (nesting depth added 39). 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.
DateNormalizer.normalizeDate (cognitive 63) databox/api/src/Elasticsearch/AQL/DateNormalizer.php:11— DateNormalizer.normalizeDate has cognitive complexity 63 (threshold 15). Drivers by points: if/else 17 (52 pts), ternaries 2 (8 pts), boolean chains 3 (nesting depth added 41). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
MessageComposer.MessageComposer (cognitive 63) databox/client/src/features/discussion/MessageComposer.tsx:150— MessageComposer.MessageComposer has cognitive complexity 63 (threshold 15). Drivers by points: ternaries 19 (29 pts), if/else 21 (22 pts), boolean chains 12 (nesting depth added 11). Of this number, 25 points are the body's own statements and 38 belong to 16 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
AssetPostTransformListener.compileAttributes (cognitive 62) databox/api/src/Elasticsearch/Listener/AssetPostTransformListener.php:111— AssetPostTransformListener.compileAttributes has cognitive complexity 62 (threshold 15). Drivers by points: if/else 11 (37 pts), loops 5 (23 pts), boolean chains 2 (nesting depth added 44). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
AttributeWidget.AttributeWidget (cognitive 62) databox/client/src/features/attributes/widgets/AttributeWidget.tsx:51— AttributeWidget.AttributeWidget has cognitive complexity 62 (threshold 15). Drivers by points: ternaries 21 (48 pts), boolean chains 13, match/switch 1 (nesting depth added 27). Of this number, 51 points are the body's own statements and 11 belong to 6 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.
IntegrationManager.IntegrationForm (cognitive 62) databox/client/src/features/integrations/manage/IntegrationManager.tsx:149— IntegrationManager.IntegrationForm has cognitive complexity 62 (threshold 15). Drivers by points: ternaries 22 (39 pts), boolean chains 15, if/else 5, error handling 2 (3 pts) (nesting depth added 18). Of this number, 35 points are the body's own statements and 27 belong to 5 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.
IntegrationWorkflowRepository.createIntegrationsToWorkflow (cognitive 61) databox/api/src/Service/Workflow/IntegrationWorkflowRepository.php:72— IntegrationWorkflowRepository.createIntegrationsToWorkflow has cognitive complexity 61 (threshold 15). Drivers by points: if/else 8 (24 pts), loops 10 (24 pts), error handling 2 (10 pts), boolean chains 3 (nesting depth added 38). 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.
UploadScreen.UploadScreen (cognitive 61) uploader/client/src/features/upload/UploadScreen.tsx:114— UploadScreen.UploadScreen has cognitive complexity 61 (threshold 15). Drivers by points: ternaries 22 (35 pts), boolean chains 13, if/else 12, error handling 1 (nesting depth added 13). Of this number, 42 points are the body's own statements and 19 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.
AQLGrammar.match_within_rectangle_operator (cognitive 59) databox/api/src/Elasticsearch/AQL/AQLGrammar.php:861— AQLGrammar.match_within_rectangle_operator has cognitive complexity 59 (threshold 15). Drivers by points: if/else 31 (50 pts), ternaries 4 (8 pts), loops 1 (nesting depth added 23). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PdfViewer.PdfDocumentViewer (cognitive 59) databox/client/src/features/assets/player/PdfViewer.tsx:109— PdfViewer.PdfDocumentViewer has cognitive complexity 59 (threshold 15). Drivers by points: ternaries 18 (22 pts), boolean chains 20, if/else 16 (17 pts) (nesting depth added 5). Of this number, 16 points are the body's own statements and 43 belong to 18 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
StructureImporter.importSubdefsStructure (cognitive 57) databox/indexer/src/handlers/phraseanet/StructureImporter.ts:236— StructureImporter.importSubdefsStructure has cognitive complexity 57 (threshold 15). Drivers by points: if/else 15 (47 pts), loops 4 (6 pts), boolean chains 4 (nesting depth added 34). Of this number, 56 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Version20260901151900.up (cognitive 55) databox/api/migrations/Version20260901151900.php:35— Version20260901151900.up has cognitive complexity 55 (threshold 15). Drivers by points: if/else 11 (35 pts), loops 5 (13 pts), ternaries 1 (5 pts), boolean chains 2 (nesting depth added 36). 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.
AQLGrammar.match_function_call (cognitive 55) databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1411— AQLGrammar.match_function_call has cognitive complexity 55 (threshold 15). Drivers by points: if/else 20 (41 pts), ternaries 3 (8 pts), loops 3 (6 pts) (nesting depth added 29). 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.
AudioPlayer.AudioPlayer (cognitive 55) databox/client/src/features/assets/player/AudioPlayer.tsx:76— AudioPlayer.AudioPlayer has cognitive complexity 55 (threshold 15). Drivers by points: if/else 21 (23 pts), ternaries 13 (15 pts), boolean chains 13, error handling 1 (3 pts), loops 1 (nesting depth added 6). Of this number, 16 points are the body's own statements and 39 belong to 14 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.
ThemeEditorScreen.ThemeEditorScreen (cognitive 55) databox/client/src/features/theme/ThemeEditorScreen.tsx:194— ThemeEditorScreen.ThemeEditorScreen has cognitive complexity 55 (threshold 15). Drivers by points: ternaries 19 (39 pts), if/else 8 (9 pts), boolean chains 6, error handling 1 (nesting depth added 21). Of this number, 36 points are the body's own statements and 19 belong to 7 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.
UploadDialog.UploadDialog (cognitive 55) databox/client/src/features/upload/UploadDialog.tsx:89— UploadDialog.UploadDialog has cognitive complexity 55 (threshold 15). Drivers by points: ternaries 38 (67 pts), if/else 18 (30 pts), boolean chains 12, error handling 1 (nesting depth added 41). 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. This shape REPEATS in the file: one other method here (UploadDialog.UploadDialog::submit) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
AttributeDefinitionInputMapper.map (cognitive 54) databox/api/src/Api/Mapper/Input/AttributeDefinitionInputMapper.php:33— AttributeDefinitionInputMapper.map has cognitive complexity 54 (threshold 15). Drivers by points: if/else 39 (50 pts), error handling 1 (3 pts), boolean chains 1 (nesting depth added 13). 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.
AQLGrammar.match_in_operator (cognitive 53) databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1140— AQLGrammar.match_in_operator has cognitive complexity 53 (threshold 15). Drivers by points: if/else 20 (41 pts), loops 3 (6 pts), ternaries 2 (6 pts) (nesting depth added 28). 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.
AclEditor.AclEditor (cognitive 53) databox/client/src/features/permissions/AclEditor.tsx:54— AclEditor.AclEditor has cognitive complexity 53 (threshold 15). Drivers by points: ternaries 19 (39 pts), boolean chains 8, if/else 3 (4 pts), error handling 2 (nesting depth added 21). Most of this is not in the body itself: 11 of the 53 points are its own statements and the rest belongs to 12 function items inside it that branch (a function literal at line 274, a function literal at line 379, add, …). 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.
AttributeDataImporter.importAttributes (cognitive 50) databox/api/src/Attribute/AttributeDataImporter.php:27— AttributeDataImporter.importAttributes has cognitive complexity 50 (threshold 15). Drivers by points: if/else 11 (33 pts), loops 3 (10 pts), match/switch 1 (3 pts), boolean chains 2, ternaries 1 (2 pts) (nesting depth added 32). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AssetSearch.buildQuery (cognitive 50) databox/api/src/Elasticsearch/AssetSearch.php:308— AssetSearch.buildQuery has cognitive complexity 50 (threshold 15). Drivers by points: if/else 20 (33 pts), loops 6 (11 pts), ternaries 1 (4 pts), boolean chains 2 (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Version20261111120000.mergeBuilderTranslations (cognitive 50) uploader/api/migrations/Version20261111120000.php:305— Version20261111120000.mergeBuilderTranslations has cognitive complexity 50 (threshold 15). Drivers by points: loops 6 (19 pts), ternaries 5 (14 pts), if/else 4 (11 pts), boolean chains 6 (nesting depth added 29). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
parser.tokenize (cognitive 50) databox/client/src/features/search/aql/parser.ts:55— parser.tokenize has cognitive complexity 50 (threshold 15). Drivers by points: if/else 16 (37 pts), boolean chains 9, loops 2 (4 pts) (nesting depth added 23). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
EntityGrid.EntityGrid (cognitive 50) databox/client/src/features/workspaces/manage/entities/EntityGrid.tsx:116— EntityGrid.EntityGrid has cognitive complexity 50 (threshold 15). Drivers by points: if/else 18 (20 pts), boolean chains 13, ternaries 10 (12 pts), error handling 4 (5 pts) (nesting depth added 5). Most of this is not in the body itself: 8 of the 50 points are its own statements and the rest belongs to 14 function items inside it that branch (commitCell, setStatus, a function literal at line 322, …). 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.
AssetVoter.voteOnAttribute (cognitive 49) databox/api/src/Security/Voter/AssetVoter.php:47— AssetVoter.voteOnAttribute has cognitive complexity 49 (threshold 15). Drivers by points: boolean chains 45, if/else 2, match/switch 1, ternaries 1. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
EnvParser.parse (cognitive 48) configurator/src/Documentation/Parser/EnvParser.php:27— EnvParser.parse has cognitive complexity 48 (threshold 15). Drivers by points: if/else 7 (26 pts), ternaries 3 (11 pts), loops 3 (8 pts), boolean chains 3 (nesting depth added 32). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
ClipTimeline.ClipTimeline (cognitive 48) databox/client/src/features/clip/ClipTimeline.tsx:75— ClipTimeline.ClipTimeline has cognitive complexity 48 (threshold 15). Drivers by points: ternaries 21 (25 pts), if/else 9 (12 pts), boolean chains 10, match/switch 1 (nesting depth added 7). Of this number, 24 points are the body's own statements and 24 belong to 7 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
AQLGrammar.match_within_circle_operator (cognitive 47) databox/api/src/Elasticsearch/AQL/AQLGrammar.php:781— AQLGrammar.match_within_circle_operator has cognitive complexity 47 (threshold 15). Drivers by points: if/else 25 (40 pts), ternaries 3 (6 pts), loops 1 (nesting depth added 18). 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.
ZoomableImage.ZoomableImage (cognitive 47) databox/client/src/features/assets/player/ZoomableImage.tsx:44— ZoomableImage.ZoomableImage has cognitive complexity 47 (threshold 15). Drivers by points: boolean chains 20, ternaries 10 (14 pts), if/else 13 (nesting depth added 4). Of this number, 21 points are the body's own statements and 26 belong to 12 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
Parser.criteria (cognitive 47) databox/client/src/features/search/aql/parser.ts:270— Parser.criteria has cognitive complexity 47 (threshold 15). Drivers by points: if/else 29 (42 pts), boolean chains 3, ternaries 1 (2 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ShareDialog.ShareDialog (cognitive 47) databox/client/src/features/share/ShareDialog.tsx:116— ShareDialog.ShareDialog has cognitive complexity 47 (threshold 15). Drivers by points: ternaries 17 (29 pts), boolean chains 17, if/else 1 (nesting depth added 12). Of this number, 29 points are the body's own statements and 18 belong to 10 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.
AssetInputMapper.map (cognitive 45) databox/api/src/Api/Mapper/Input/AssetInputMapper.php:53— AssetInputMapper.map has cognitive complexity 45 (threshold 15). Drivers by points: if/else 22 (36 pts), boolean chains 5, loops 2 (4 pts) (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SecretReferencePicker.SecretReferencePicker (cognitive 45) databox/client/src/features/integrations/config/pickers/SecretReferencePicker.tsx:66— SecretReferencePicker.SecretReferencePicker has cognitive complexity 45 (threshold 15). Drivers by points: ternaries 21 (34 pts), boolean chains 10, if/else 1 (nesting depth added 13). Of this number, 41 points are the body's own statements and 4 belong to 2 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
definition.validateValues (cognitive 45) REDACTED:369— definition.validateValues has cognitive complexity 45 (threshold 15). Drivers by points: if/else 10 (33 pts), boolean chains 7, loops 2 (3 pts), ternaries 1 (2 pts) (nesting depth added 25). 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.
AssetOutputMapper.map (cognitive 44) databox/api/src/Api/Mapper/Output/AssetOutputMapper.php:71— AssetOutputMapper.map has cognitive complexity 44 (threshold 15). Drivers by points: if/else 18 (32 pts), boolean chains 6, ternaries 2 (4 pts), loops 1 (2 pts) (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AuditLogListener.logRelations (cognitive 44) databox/api/src/Doctrine/Listener/AuditLogListener.php:280— AuditLogListener.logRelations has cognitive complexity 44 (threshold 15). Drivers by points: if/else 12 (30 pts), boolean chains 8, loops 6 (nesting depth added 18). 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.
AQLGrammar.match_condition (cognitive 44) databox/api/src/Elasticsearch/AQL/AQLGrammar.php:182— AQLGrammar.match_condition has cognitive complexity 44 (threshold 15). Drivers by points: if/else 14 (30 pts), ternaries 3 (9 pts), loops 3 (5 pts) (nesting depth added 24). 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.
ClientThemeNormalizer.normalize (cognitive 44) databox/api/src/Service/Admin/ClientThemeNormalizer.php:73— ClientThemeNormalizer.normalize has cognitive complexity 44 (threshold 15). Drivers by points: if/else 26 (33 pts), boolean chains 10, loops 1 (nesting depth added 7). 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.
EntityValueCard.EntityValueCard (cognitive 44) databox/client/src/features/entities/explore/EntityValueCard.tsx:83— EntityValueCard.EntityValueCard has cognitive complexity 44 (threshold 15). Drivers by points: ternaries 17 (37 pts), if/else 2 (5 pts), boolean chains 2 (nesting depth added 23). Of this number, 27 points are the body's own statements and 17 belong to 4 function items inside it that branch. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
PdfViewer.PdfDocumentViewer (cognitive 44) expose/client/src/features/player/PdfViewer.tsx:101— PdfViewer.PdfDocumentViewer has cognitive complexity 44 (threshold 15). Drivers by points: ternaries 15 (17 pts), boolean chains 14, if/else 12 (13 pts) (nesting depth added 3). Of this number, 16 points are the body's own statements and 28 belong to 15 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
AssetListener.onFlush (cognitive 43) databox/api/src/Doctrine/Listener/AssetListener.php:32— AssetListener.onFlush has cognitive complexity 43 (threshold 15). Drivers by points: if/else 12 (30 pts), loops 6 (9 pts), boolean chains 4 (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FieldDefinition.fromArray (cognitive 43) uploader/api/src/Form/Builder/FieldDefinition.php:51— FieldDefinition.fromArray has cognitive complexity 43 (threshold 15). Drivers by points: if/else 19 (30 pts), boolean chains 10, ternaries 1 (2 pts), match/switch 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Migration20230807Command.execute (cognitive 42) configurator/src/Command/Migration20230807Command.php:27— Migration20230807Command.execute has cognitive complexity 42 (threshold 15). Drivers by points: if/else 9 (20 pts), loops 10 (15 pts), match/switch 1 (3 pts), ternaries 1 (3 pts), boolean chains 1 (nesting depth added 20). 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.
AQLGrammar.match_between_operator (cognitive 42) databox/api/src/Elasticsearch/AQL/AQLGrammar.php:957— AQLGrammar.match_between_operator has cognitive complexity 42 (threshold 15). Drivers by points: if/else 22 (35 pts), ternaries 2 (4 pts), loops 2 (3 pts) (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Discussion.Discussion (cognitive 42) databox/client/src/features/discussion/Discussion.tsx:67— Discussion.Discussion has cognitive complexity 42 (threshold 15). Drivers by points: ternaries 16 (18 pts), boolean chains 12, if/else 10, error handling 2 (nesting depth added 2). Most of this is not in the body itself: 8 of the 42 points are its own statements and the rest belongs to 14 function items inside it that branch (a function literal at line 354, send, saveEdit, …). 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.
CollectionOutputMapper.map (cognitive 41) databox/api/src/Api/Mapper/Output/CollectionOutputMapper.php:63— CollectionOutputMapper.map has cognitive complexity 41 (threshold 15). Drivers by points: if/else 21 (35 pts), boolean chains 5, loops 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AttributeSearch.createClustersFromDefinitions (cognitive 41) databox/api/src/Elasticsearch/AttributeSearch.php:106— AttributeSearch.createClustersFromDefinitions has cognitive complexity 41 (threshold 15). Drivers by points: loops 6 (16 pts), if/else 5 (12 pts), ternaries 3 (11 pts), boolean chains 2 (nesting depth added 25). 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.
ImportEntryNormalizer.normalize (cognitive 41) databox/api/src/Service/Import/ImportEntryNormalizer.php:52— ImportEntryNormalizer.normalize has cognitive complexity 41 (threshold 15). Drivers by points: if/else 15 (25 pts), boolean chains 10, loops 4 (6 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AQLGrammar.match_expression (cognitive 40) databox/api/src/Elasticsearch/AQL/AQLGrammar.php:33— AQLGrammar.match_expression has cognitive complexity 40 (threshold 15). Drivers by points: if/else 13 (28 pts), loops 3 (6 pts), ternaries 2 (6 pts) (nesting depth added 22). 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. This shape REPEATS in the file: one other method here (AQLGrammar.match_and_expression) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
AQLGrammar.match_and_expression (cognitive 40) databox/api/src/Elasticsearch/AQL/AQLGrammar.php:107— AQLGrammar.match_and_expression has cognitive complexity 40 (threshold 15). Drivers by points: if/else 13 (28 pts), loops 3 (6 pts), ternaries 2 (6 pts) (nesting depth added 22). 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. This shape REPEATS in the file: one other method here (AQLGrammar.match_expression) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
customTheme.normalizeClientTheme (cognitive 40) lib/js/next-theme/src/customTheme.ts:409— customTheme.normalizeClientTheme has cognitive complexity 40 (threshold 15). Drivers by points: if/else 20 (30 pts), boolean chains 9, ternaries 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AsyncCombobox.AsyncCombobox (cognitive 40) lib/js/next-ui/src/form/AsyncCombobox.tsx:91— AsyncCombobox.AsyncCombobox has cognitive complexity 40 (threshold 15). Drivers by points: ternaries 16 (21 pts), boolean chains 12, if/else 7 (nesting depth added 5). Of this number, 20 points are the body's own statements and 20 belong to 11 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
EnvVarDocumentationGenerator.getContent (cognitive 39) configurator/src/Documentation/EnvVarDocumentationGenerator.php:16— EnvVarDocumentationGenerator.getContent has cognitive complexity 39 (threshold 15). Drivers by points: if/else 10 (27 pts), ternaries 3 (9 pts), loops 2 (3 pts) (nesting depth added 24). 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.
SavedSearchAutomationInputMapper.map (cognitive 39) databox/api/src/Api/Mapper/Input/SavedSearchAutomationInputMapper.php:39— SavedSearchAutomationInputMapper.map has cognitive complexity 39 (threshold 15). Drivers by points: if/else 18 (23 pts), boolean chains 12, ternaries 2 (4 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AttributeSearch.buildAttributeQuery (cognitive 39) databox/api/src/Elasticsearch/AttributeSearch.php:238— AttributeSearch.buildAttributeQuery has cognitive complexity 39 (threshold 15). Drivers by points: if/else 10 (30 pts), loops 3 (7 pts), boolean chains 2 (nesting depth added 24). 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.
Version20261111120000.convertLiForm (cognitive 39) uploader/api/migrations/Version20261111120000.php:182— Version20261111120000.convertLiForm has cognitive complexity 39 (threshold 15). Drivers by points: if/else 15 (34 pts), boolean chains 3, loops 1, ternaries 1 (nesting depth added 19). 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.
canDrop.canDropAssets (cognitive 39) databox/client/src/features/dnd/canDrop.ts:71— canDrop.canDropAssets has cognitive complexity 39 (threshold 15). Drivers by points: if/else 20 (37 pts), boolean chains 1, match/switch 1 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BasketIntegrations.ExposeIntegration (cognitive 38) databox/client/src/features/baskets/manage/BasketIntegrations.tsx:126— BasketIntegrations.ExposeIntegration has cognitive complexity 38 (threshold 15). Drivers by points: ternaries 16 (26 pts), boolean chains 8, if/else 3, error handling 1 (nesting depth added 10). Most of this is not in the body itself: 4 of the 38 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 215, a function literal at line 488, a function literal at line 319, …). 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.
ClientThemeNormalizer.normalizeFonts (cognitive 37) databox/api/src/Service/Admin/ClientThemeNormalizer.php:193— ClientThemeNormalizer.normalizeFonts has cognitive complexity 37 (threshold 15). Drivers by points: if/else 11 (23 pts), boolean chains 6, ternaries 2 (5 pts), loops 2 (3 pts) (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
collectionStore.useCollectionStore (cognitive 37) databox/client/src/features/collections/collectionStore.ts:151— collectionStore.useCollectionStore has cognitive complexity 37 (threshold 15). Drivers by points: if/else 19 (20 pts), boolean chains 14, ternaries 2, error handling 1 (nesting depth added 1). None of this is in the body itself: all 37 points belong to 15 function literals inside it that branch (lines 404, 211, 278, …). 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.
entityColumns.buildEntityColumns (cognitive 37) databox/client/src/features/workspaces/manage/entities/entityColumns.tsx:196— entityColumns.buildEntityColumns has cognitive complexity 37 (threshold 15). Drivers by points: ternaries 12 (21 pts), if/else 7 (10 pts), loops 2 (4 pts), boolean chains 2 (nesting depth added 14). Most of this is not in the body itself: 9 of the 37 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 292, 467, 217, …). 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.
AssetPostTransformListener.compileSuggestions (cognitive 36) databox/api/src/Elasticsearch/Listener/AssetPostTransformListener.php:209— AssetPostTransformListener.compileSuggestions has cognitive complexity 36 (threshold 15). Drivers by points: if/else 4 (15 pts), loops 4 (11 pts), ternaries 3 (9 pts), boolean chains 1 (nesting depth added 24). 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.
ColorspaceDetector.parseJpeg (cognitive 36) lib/php/rendition-factory/src/Image/ColorspaceDetector.php:164— ColorspaceDetector.parseJpeg has cognitive complexity 36 (threshold 15). Drivers by points: if/else 9 (20 pts), boolean chains 10, loops 2 (3 pts), match/switch 1 (3 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AnnotationLayer.AnnotationLayer (cognitive 36) databox/client/src/features/annotations/AnnotationLayer.tsx:105— AnnotationLayer.AnnotationLayer has cognitive complexity 36 (threshold 15). Drivers by points: if/else 66 (90 pts), ternaries 36 (57 pts), boolean chains 42, match/switch 2, loops 1 (nesting depth added 45). 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. This shape REPEATS in the file: 3 other methods here (AnnotationLayer.AnnotationLayer::onPointerDown, AnnotationLayer.AnnotationLayer::onPointerUp, AnnotationLayer.AnnotationLayer::cycleSelection) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
SearchProvider.SearchProvider (cognitive 36) databox/client/src/features/search/SearchProvider.tsx:100— SearchProvider.SearchProvider has cognitive complexity 36 (threshold 15). Drivers by points: if/else 13, ternaries 10 (12 pts), boolean chains 10, error handling 1 (nesting depth added 2). Most of this is not in the body itself: 4 of the 36 points are its own statements and the rest belongs to 17 function literals inside it that branch (lines 361, 258, 318, …). 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.
AQLGrammar.match_geo_operator (cognitive 35) databox/api/src/Elasticsearch/AQL/AQLGrammar.php:723— AQLGrammar.match_geo_operator has cognitive complexity 35 (threshold 15). Drivers by points: if/else 10 (21 pts), ternaries 2 (8 pts), loops 3 (6 pts) (nesting depth added 20). 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.
AclListener.handleChange (cognitive 35) databox/api/src/Listener/AclListener.php:139— AclListener.handleChange has cognitive complexity 35 (threshold 15). Drivers by points: if/else 14 (34 pts), match/switch 1 (nesting depth added 20). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
AttributeList.AttributeList (cognitive 35) databox/client/src/features/attributes/AttributeList.tsx:61— AttributeList.AttributeList has cognitive complexity 35 (threshold 15). Drivers by points: if/else 12 (17 pts), ternaries 5 (9 pts), boolean chains 8, loops 1 (nesting depth added 9). Most of this is not in the body itself: 3 of the 35 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 89, 183, 220). 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.
AttributeAssigner.assignAttributeFromInput (cognitive 34) databox/api/src/Attribute/AttributeAssigner.php:40— AttributeAssigner.assignAttributeFromInput has cognitive complexity 34 (threshold 15). Drivers by points: if/else 16 (28 pts), boolean chains 3, ternaries 1 (3 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CreateDynamicRenditionDialog.CreateDynamicRenditionDialog (cognitive 34) databox/client/src/features/assets/manage/dialogs/CreateDynamicRenditionDialog.tsx:33— CreateDynamicRenditionDialog.CreateDynamicRenditionDialog has cognitive complexity 34 (threshold 15). Drivers by points: ternaries 9 (13 pts), if/else 10 (11 pts), boolean chains 10 (nesting depth added 5). Most of this is not in the body itself: 15 of the 34 points are its own statements and the rest belongs to 6 function items inside it that branch (buildDefinition, a function literal at line 110, isImage, …). 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.
messageMarkup.parseMessage (cognitive 34) databox/client/src/features/discussion/messageMarkup.ts:136— messageMarkup.parseMessage has cognitive complexity 34 (threshold 15). Drivers by points: if/else 7 (13 pts), ternaries 3 (10 pts), loops 3 (7 pts), boolean chains 4 (nesting depth added 17). Of this number, 32 points are the body's own statements and 2 belong to 2 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AutomationForm.AutomationFormDialog (cognitive 34) databox/client/src/features/saved-searches/automations/AutomationForm.tsx:94— AutomationForm.AutomationFormDialog has cognitive complexity 34 (threshold 15). Drivers by points: ternaries 16 (17 pts), if/else 6 (9 pts), boolean chains 7, error handling 1 (nesting depth added 4). Of this number, 17 points are the body's own statements and 17 belong to 8 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
ZoomableImage.ZoomableImage (cognitive 34) expose/client/src/features/player/ZoomableImage.tsx:36— ZoomableImage.ZoomableImage has cognitive complexity 34 (threshold 15). Drivers by points: boolean chains 13, if/else 13, ternaries 6 (8 pts) (nesting depth added 2). Most of this is not in the body itself: 10 of the 34 points are its own statements and the rest belongs to 11 function items inside it that branch (a function literal at line 221, a function literal at line 254, measure, …). 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.
FieldInspector.InputFieldInspector (cognitive 34) uploader/client/src/features/form-builder/editor/FieldInspector.tsx:107— FieldInspector.InputFieldInspector has cognitive complexity 34 (threshold 15). Drivers by points: ternaries 19 (24 pts), boolean chains 10 (nesting depth added 5). Of this number, 21 points are the body's own statements and 13 belong to 6 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
AuditLogCollectionProvider.applyFilters (cognitive 33) databox/api/src/Api/Provider/AuditLogCollectionProvider.php:57— AuditLogCollectionProvider.applyFilters has cognitive complexity 33 (threshold 15). Drivers by points: ternaries 6 (13 pts), if/else 7 (10 pts), boolean chains 4, error handling 1 (3 pts), loops 3 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AttributeAction.validateConfig (cognitive 33) databox/api/src/Automation/Action/AttributeAction.php:44— AttributeAction.validateConfig has cognitive complexity 33 (threshold 15). Drivers by points: if/else 11 (18 pts), boolean chains 8, ternaries 3 (6 pts), match/switch 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AQLGrammar.match_is_operator (cognitive 33) databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1056— AQLGrammar.match_is_operator has cognitive complexity 33 (threshold 15). Drivers by points: if/else 16 (26 pts), ternaries 2 (4 pts), loops 2 (3 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AQLToESQuery.expressionToScript (cognitive 33) databox/api/src/Elasticsearch/AQL/AQLToESQuery.php:530— AQLToESQuery.expressionToScript has cognitive complexity 33 (threshold 15). Drivers by points: if/else 8 (17 pts), loops 3 (11 pts), match/switch 1 (3 pts), boolean chains 2 (nesting depth added 19). 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.
FaceRecognitionDoctrineListener.onFlush (cognitive 33) databox/api/src/Integration/Core/FaceRecognition/FaceRecognitionDoctrineListener.php:56— FaceRecognitionDoctrineListener.onFlush has cognitive complexity 33 (threshold 15). Drivers by points: if/else 10 (26 pts), boolean chains 4, loops 3 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
VideoSummaryTransformerModule.transform (cognitive 33) lib/php/rendition-factory/src/Transformer/Video/VideoSummaryTransformerModule.php:127— VideoSummaryTransformerModule.transform has cognitive complexity 33 (threshold 15). Drivers by points: if/else 11 (19 pts), loops 5 (10 pts), boolean chains 4 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SearchBar.SearchBar (cognitive 33) databox/client/src/features/search/SearchBar.tsx:36— SearchBar.SearchBar has cognitive complexity 33 (threshold 15). Drivers by points: if/else 15 (18 pts), boolean chains 10, ternaries 4, match/switch 1 (nesting depth added 3). Most of this is not in the body itself: 7 of the 33 points are its own statements and the rest belongs to 5 function items inside it that branch (a function literal at line 130, applyTextSuggestion, a function literal at line 222, …). 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.
FacetsPanel.FacetsPanel (cognitive 33) databox/client/src/features/search/facets/FacetsPanel.tsx:48— FacetsPanel.FacetsPanel has cognitive complexity 33 (threshold 15). Drivers by points: ternaries 14 (20 pts), boolean chains 8, if/else 4 (5 pts) (nesting depth added 7). Most of this is not in the body itself: 5 of the 33 points are its own statements and the rest belongs to 11 function literals inside it that branch (lines 210, 89, 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.
indexer.importStory (cognitive 33) databox/indexer/src/handlers/phraseanet/indexer.ts:488— indexer.importStory has cognitive complexity 33 (threshold 15). Drivers by points: if/else 12 (21 pts), error handling 2 (5 pts), ternaries 2 (4 pts), boolean chains 3 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AuditLogListener.onFlush (cognitive 32) databox/api/src/Doctrine/Listener/AuditLogListener.php:86— AuditLogListener.onFlush has cognitive complexity 32 (threshold 15). Drivers by points: if/else 6 (14 pts), loops 8 (11 pts), ternaries 1 (5 pts), boolean chains 2 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
InitialValuesDocumentationGenerator.getContent (cognitive 32) databox/api/src/Documentation/InitialValuesDocumentationGenerator.php:18— InitialValuesDocumentationGenerator.getContent has cognitive complexity 32 (threshold 15). Drivers by points: if/else 5 (12 pts), loops 4 (10 pts), ternaries 3 (10 pts) (nesting depth added 20). 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.
AQLGrammar.match_value_or_expr (cognitive 32) databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1733— AQLGrammar.match_value_or_expr has cognitive complexity 32 (threshold 15). Drivers by points: if/else 12 (24 pts), ternaries 2 (5 pts), loops 2 (3 pts) (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WorkflowOrchestrator.getNextJob (cognitive 32) lib/php/workflow/src/WorkflowOrchestrator.php:306— WorkflowOrchestrator.getNextJob has cognitive complexity 32 (threshold 15). Drivers by points: if/else 8 (25 pts), loops 2 (3 pts), boolean chains 2, ternaries 2 (nesting depth added 18). 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.
AnnotationToolbar.AnnotationToolbar (cognitive 32) databox/client/src/features/annotations/AnnotationToolbar.tsx:71— AnnotationToolbar.AnnotationToolbar has cognitive complexity 32 (threshold 15). Drivers by points: ternaries 14 (22 pts), boolean chains 6, if/else 2 (4 pts) (nesting depth added 10). Of this number, 22 points are the body's own statements and 10 belong to 6 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.
GridLayout.GridItem (cognitive 32) databox/client/src/features/assets/list/layouts/GridLayout.tsx:92— GridLayout.GridItem has cognitive complexity 32 (threshold 15). Drivers by points: ternaries 11 (29 pts), boolean chains 3 (nesting depth added 18). Of this number, 28 points are the body's own statements and 4 belong to one function literal inside it that branches. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
CropRectEditor.CropRectEditor (cognitive 32) databox/client/src/features/clip/CropRectEditor.tsx:95— CropRectEditor.CropRectEditor has cognitive complexity 32 (threshold 15). Drivers by points: ternaries 8 (15 pts), boolean chains 9, if/else 8 (nesting depth added 7). Most of this is not in the body itself: 5 of the 32 points are its own statements and the rest belongs to 5 function items inside it that branch (onPointerDown, onPointerUp, onPointerMove, …). 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.
ConfigForm.TextField (cognitive 32) databox/client/src/features/integrations/config/ConfigForm.tsx:299— ConfigForm.TextField has cognitive complexity 32 (threshold 15). Drivers by points: ternaries 12 (23 pts), boolean chains 6, if/else 3 (nesting depth added 11). Of this number, 24 points are the body's own statements and 8 belong to 5 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.
FileTile.FileTile (cognitive 32) uploader/client/src/features/upload/FileTile.tsx:36— FileTile.FileTile has cognitive complexity 32 (threshold 15). Drivers by points: ternaries 14 (26 pts), boolean chains 6 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AQLGrammar.match_keyword_operator (cognitive 31) databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1276— AQLGrammar.match_keyword_operator has cognitive complexity 31 (threshold 15). Drivers by points: if/else 13 (21 pts), ternaries 3 (7 pts), loops 2 (3 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AttributesEditor.AttributesEditor (cognitive 31) databox/client/src/features/attributes/editor/AttributesEditor.tsx:52— AttributesEditor.AttributesEditor has cognitive complexity 31 (threshold 15). Drivers by points: ternaries 10 (13 pts), if/else 9 (10 pts), boolean chains 8 (nesting depth added 4). Most of this is not in the body itself: 5 of the 31 points are its own statements and the rest belongs to 5 function items inside it that branch (a function literal at line 168, onKeyDown, a function literal at line 104, …). 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.
CollectionsPanel.CollectionItem (cognitive 31) databox/client/src/features/collections/tree/CollectionsPanel.tsx:502— CollectionsPanel.CollectionItem has cognitive complexity 31 (threshold 15). Drivers by points: ternaries 18 (22 pts), boolean chains 8, if/else 1 (nesting depth added 4). Of this number, 21 points are the body's own statements and 10 belong to 3 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
EntityListExploreScreen.ExploreBrowser (cognitive 31) databox/client/src/features/entities/explore/EntityListExploreScreen.tsx:83— EntityListExploreScreen.ExploreBrowser has cognitive complexity 31 (threshold 15). Drivers by points: ternaries 13 (25 pts), boolean chains 5, if/else 1 (nesting depth added 12). Of this number, 28 points are the body's own statements and 3 belong to 3 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.
profileStore.useProfileStore (cognitive 31) databox/client/src/features/profiles/profileStore.ts:65— profileStore.useProfileStore has cognitive complexity 31 (threshold 15). Drivers by points: if/else 13, ternaries 9 (13 pts), boolean chains 5 (nesting depth added 4). None of this is in the body itself: all 31 points belong to 15 function literals inside it that branch (lines 137, 71, 105, …). 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.
customTheme.normalizeFonts (cognitive 31) lib/js/next-theme/src/customTheme.ts:512— customTheme.normalizeFonts has cognitive complexity 31 (threshold 15). Drivers by points: if/else 9 (19 pts), boolean chains 7, ternaries 2 (4 pts), loops 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AttributeSearch.buildFacets (cognitive 30) databox/api/src/Elasticsearch/AttributeSearch.php:356— AttributeSearch.buildFacets has cognitive complexity 30 (threshold 15). Drivers by points: if/else 7 (19 pts), loops 2 (4 pts), ternaries 2 (4 pts), match/switch 1 (2 pts), boolean chains 1 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
VideoTransformer.doVideo (cognitive 30) lib/php/rendition-factory/src/Transformer/Video/VideoTransformer.php:24— VideoTransformer.doVideo has cognitive complexity 30 (threshold 15). Drivers by points: if/else 18 (28 pts), boolean chains 1, loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Version20261111120000.kindOf (cognitive 30) uploader/api/migrations/Version20261111120000.php:369— Version20261111120000.kindOf has cognitive complexity 30 (threshold 15). Drivers by points: if/else 11 (13 pts), ternaries 5 (10 pts), boolean chains 7 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MetadataTagsField.MetadataTagsField (cognitive 30) databox/client/src/components/form/MetadataTagsField.tsx:43— MetadataTagsField.MetadataTagsField has cognitive complexity 30 (threshold 15). Drivers by points: ternaries 12 (17 pts), boolean chains 9, if/else 4 (nesting depth added 5). Most of this is not in the body itself: 14 of the 30 points are its own statements and the rest belongs to 5 function items inside it that branch (a function literal at line 216, a function literal at line 126, add, …). 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.
DataTable.DataTable::onKeyDown (cognitive 30) databox/client/src/components/ui/data-table/DataTable.tsx:305— DataTable.DataTable::onKeyDown has cognitive complexity 30 (threshold 15). Drivers by points: if/else 9 (16 pts), boolean chains 7, ternaries 3 (6 pts), match/switch 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
VideoJsPlayer.VideoJsPlayerBody (cognitive 30) databox/client/src/features/assets/player/VideoJsPlayer.tsx:337— VideoJsPlayer.VideoJsPlayerBody has cognitive complexity 30 (threshold 15). Drivers by points: if/else 11 (12 pts), boolean chains 10, ternaries 8 (nesting depth added 1). Most of this is not in the body itself: 10 of the 30 points are its own statements and the rest belongs to 11 function items inside it that branch (a function literal at line 447, a function literal at line 384, a function literal at line 398, …). 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.
AttributeDefinitionsTab.DefinitionForm (cognitive 30) databox/client/src/features/workspaces/manage/tabs/AttributeDefinitionsTab.tsx:139— AttributeDefinitionsTab.DefinitionForm has cognitive complexity 30 (threshold 15). Drivers by points: ternaries 16 (17 pts), boolean chains 12, error handling 1 (nesting depth added 1). Of this number, 17 points are the body's own statements and 13 belong to 4 function items inside it that branch. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
shared.createAsset (cognitive 30) databox/indexer/src/handlers/phraseanet/shared.ts:140— shared.createAsset has cognitive complexity 30 (threshold 15). Drivers by points: if/else 5 (16 pts), loops 5 (7 pts), match/switch 2 (6 pts), boolean chains 1 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AttributeValidator.validateAttributeInputs (cognitive 29) databox/api/src/Attribute/AttributeValidator.php:108— AttributeValidator.validateAttributeInputs has cognitive complexity 29 (threshold 15). Drivers by points: if/else 10 (22 pts), error handling 1 (4 pts), boolean chains 2, loops 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TagsAction.processBatch (cognitive 29) databox/api/src/Automation/Action/TagsAction.php:60— TagsAction.processBatch has cognitive complexity 29 (threshold 15). Drivers by points: loops 7 (14 pts), if/else 5 (12 pts), error handling 1 (2 pts), boolean chains 1 (nesting depth added 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
AssetPermissionComputer.doGetAssetPermissionFields (cognitive 29) databox/api/src/Elasticsearch/AssetPermissionComputer.php:84— AssetPermissionComputer.doGetAssetPermissionFields has cognitive complexity 29 (threshold 15). Drivers by points: if/else 14 (27 pts), loops 2 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FileAnalysisUnblocker.unblockAsset (cognitive 29) databox/api/src/File/FileAnalysisUnblocker.php:88— FileAnalysisUnblocker.unblockAsset has cognitive complexity 29 (threshold 15). Drivers by points: if/else 15 (22 pts), loops 2 (4 pts), match/switch 1 (2 pts), ternaries 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
InitialAttributeValuesResolver.resolveInitialAttributes (cognitive 29) databox/api/src/Service/Asset/Attribute/InitialAttributeValuesResolver.php:34— InitialAttributeValuesResolver.resolveInitialAttributes has cognitive complexity 29 (threshold 15). Drivers by points: if/else 5 (13 pts), loops 4 (11 pts), error handling 1 (4 pts), boolean chains 1 (nesting depth added 18). 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.
ShareDownloadDialog.ShareDownloadDialog (cognitive 29) databox/client/src/features/share/ShareDownloadDialog.tsx:43— ShareDownloadDialog.ShareDownloadDialog has cognitive complexity 29 (threshold 15). Drivers by points: ternaries 13 (25 pts), boolean chains 2, if/else 1, loops 1 (nesting depth added 12). Most of this is not in the body itself: 14 of the 29 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 195, a function literal at line 52, a function literal at line 85, …). 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.
InitialValuesDocumentationGenerator.dumpExpected (cognitive 28) databox/api/src/Documentation/InitialValuesDocumentationGenerator.php:100— InitialValuesDocumentationGenerator.dumpExpected has cognitive complexity 28 (threshold 15). Drivers by points: loops 4 (15 pts), if/else 6 (13 pts) (nesting depth added 18). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
FileAnalysisReevaluator.rewriteAnalysis (cognitive 28) databox/api/src/File/FileAnalysisReevaluator.php:65— FileAnalysisReevaluator.rewriteAnalysis has cognitive complexity 28 (threshold 15). Drivers by points: if/else 8 (18 pts), loops 3 (5 pts), boolean chains 4, ternaries 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PublicationFilter.apply (cognitive 28) expose/api/src/Filter/PublicationFilter.php:53— PublicationFilter.apply has cognitive complexity 28 (threshold 15). Drivers by points: if/else 11 (25 pts), boolean chains 2, match/switch 1 (nesting depth added 14). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
RenditionCreator.buildHashesDiffer (cognitive 28) lib/php/rendition-factory/src/RenditionCreator.php:180— RenditionCreator.buildHashesDiffer has cognitive complexity 28 (threshold 15). Drivers by points: if/else 8 (19 pts), ternaries 2 (6 pts), boolean chains 2, loops 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ConsoleWorkflowDumper.dumpWorkflow (cognitive 28) lib/php/workflow/src/Dumper/ConsoleWorkflowDumper.php:25— ConsoleWorkflowDumper.dumpWorkflow has cognitive complexity 28 (threshold 15). Drivers by points: ternaries 4 (16 pts), loops 4 (8 pts), if/else 2 (3 pts), boolean chains 1 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TopBar.TopBar (cognitive 28) databox/client/src/components/layout/TopBar.tsx:65— TopBar.TopBar has cognitive complexity 28 (threshold 15). Drivers by points: ternaries 15 (21 pts), boolean chains 6, if/else 1 (nesting depth added 6). Of this number, 20 points are the body's own statements and 8 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AttributeList.AttributeRow (cognitive 28) databox/client/src/features/attributes/AttributeList.tsx:233— AttributeList.AttributeRow has cognitive complexity 28 (threshold 15). Drivers by points: ternaries 12 (23 pts), boolean chains 4, if/else 1 (nesting depth added 11). Of this number, 27 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AuditLogScreen.AuditLogScreen (cognitive 28) databox/client/src/features/audit-log/AuditLogScreen.tsx:113— AuditLogScreen.AuditLogScreen has cognitive complexity 28 (threshold 15). Drivers by points: ternaries 11 (20 pts), boolean chains 6, if/else 1 (2 pts) (nesting depth added 10). Most of this is not in the body itself: 13 of the 28 points are its own statements and the rest belongs to 10 function literals inside it that branch (lines 127, 279, 302, …). 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.
BasketViewRoute.BasketViewRoute (cognitive 28) databox/client/src/features/baskets/view/BasketViewRoute.tsx:53— BasketViewRoute.BasketViewRoute has cognitive complexity 28 (threshold 15). Drivers by points: ternaries 10 (23 pts), boolean chains 3, error handling 1, if/else 1 (nesting depth added 13). Of this number, 18 points are the body's own statements and 10 belong to 4 function items inside it that branch. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
CollectionsPanel.WorkspaceItem (cognitive 28) databox/client/src/features/collections/tree/CollectionsPanel.tsx:275— CollectionsPanel.WorkspaceItem has cognitive complexity 28 (threshold 15). Drivers by points: ternaries 14 (19 pts), boolean chains 8, if/else 1 (nesting depth added 5). Most of this is not in the body itself: 11 of the 28 points are its own statements and the rest belongs to 4 function items inside it that branch (menu, a function literal at line 292, a function literal at line 380, …). 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.
ConditionBuilder.ValueInput (cognitive 28) databox/client/src/features/search/conditions/ConditionBuilder.tsx:597— ConditionBuilder.ValueInput has cognitive complexity 28 (threshold 15). Drivers by points: ternaries 13 (26 pts), if/else 2 (nesting depth added 13). Of this number, 23 points are the body's own statements and 5 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TicketDialog.TicketDialog (cognitive 28) databox/client/src/features/ticketing/TicketDialog.tsx:64— TicketDialog.TicketDialog has cognitive complexity 28 (threshold 15). Drivers by points: ternaries 8 (10 pts), if/else 8 (9 pts), boolean chains 7, error handling 2 (nesting depth added 3). Most of this is not in the body itself: 13 of the 28 points are its own statements and the rest belongs to 7 function items inside it that branch (capture, submit, requestClose, …). 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.
UploadDialog.UploadDialog::submit (cognitive 28) databox/client/src/features/upload/UploadDialog.tsx:232— UploadDialog.UploadDialog::submit has cognitive complexity 28 (threshold 15). Drivers by points: if/else 10 (15 pts), ternaries 7 (13 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (UploadDialog.UploadDialog) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
AdminPublicationList.AdminPublicationList (cognitive 28) expose/client/src/features/admin/AdminPublicationList.tsx:30— AdminPublicationList.AdminPublicationList has cognitive complexity 28 (threshold 15). Drivers by points: ternaries 9 (27 pts), boolean chains 1 (nesting depth added 18). Most of this is not in the body itself: 7 of the 28 points are its own statements and the rest belongs to one function literal inside it that branches (line 97). The decisions are inside the literal, 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 literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
RenditionDefinitionInputMapper.map (cognitive 27) databox/api/src/Api/Mapper/Input/RenditionDefinitionInputMapper.php:20— RenditionDefinitionInputMapper.map has cognitive complexity 27 (threshold 15). Drivers by points: if/else 23 (27 pts) (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
SavedSearchAutomationInputMapper.checkActionConstraints (cognitive 27) databox/api/src/Api/Mapper/Input/SavedSearchAutomationInputMapper.php:195— SavedSearchAutomationInputMapper.checkActionConstraints has cognitive complexity 27 (threshold 15). Drivers by points: if/else 5 (9 pts), ternaries 2 (8 pts), loops 3 (7 pts), boolean chains 3 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DocUniqueIdAnalyzer.analyzeFile (cognitive 27) databox/api/src/Border/FileAnalyzer/Analyzer/DocUniqueIdAnalyzer.php:84— DocUniqueIdAnalyzer.analyzeFile has cognitive complexity 27 (threshold 15). Drivers by points: if/else 10 (19 pts), loops 3 (6 pts), boolean chains 2 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FileAnalyzerAction.doHandle (cognitive 27) databox/api/src/Integration/Core/FileAnalyzer/FileAnalyzerAction.php:26— FileAnalyzerAction.doHandle has cognitive complexity 27 (threshold 15). Drivers by points: if/else 12 (19 pts), loops 2 (4 pts), match/switch 1 (3 pts), boolean chains 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WorkspaceVoter.doVote (cognitive 27) databox/api/src/Security/Voter/WorkspaceVoter.php:64— WorkspaceVoter.doVote has cognitive complexity 27 (threshold 15). Drivers by points: boolean chains 24, if/else 1, match/switch 1, ternaries 1. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
AttributeValueResolver.resolveAttrValues (cognitive 27) databox/api/src/Service/Asset/Attribute/AttributeValueResolver.php:55— AttributeValueResolver.resolveAttrValues has cognitive complexity 27 (threshold 15). Drivers by points: if/else 8 (18 pts), loops 1 (4 pts), error handling 1 (3 pts), ternaries 1 (2 pts) (nesting depth added 16). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
ArrayUtil.arrayAreSame (cognitive 27) databox/api/src/Util/ArrayUtil.php:9— ArrayUtil.arrayAreSame has cognitive complexity 27 (threshold 15). Drivers by points: if/else 9 (20 pts), loops 3 (7 pts) (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DeleteAssetsDialog.DeleteAssetsDialog (cognitive 27) databox/client/src/features/assets/actions/DeleteAssetsDialog.tsx:35— DeleteAssetsDialog.DeleteAssetsDialog has cognitive complexity 27 (threshold 15). Drivers by points: ternaries 13 (17 pts), boolean chains 9, if/else 1 (nesting depth added 4). Of this number, 16 points are the body's own statements and 11 belong to 2 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
ProfileAttributesTab.DisplayedRow (cognitive 27) databox/client/src/features/profiles/manage/ProfileAttributesTab.tsx:351— ProfileAttributesTab.DisplayedRow has cognitive complexity 27 (threshold 15). Drivers by points: ternaries 12 (23 pts), boolean chains 4 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PublicationHeader.PublicationHeader (cognitive 27) expose/client/src/features/publication/PublicationHeader.tsx:44— PublicationHeader.PublicationHeader has cognitive complexity 27 (threshold 15). Drivers by points: ternaries 13 (21 pts), boolean chains 6 (nesting depth added 8). Of this number, 17 points are the body's own statements and 10 belong to 2 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FormBuilderEditor.FormBuilderEditor (cognitive 27) uploader/client/src/features/admin/FormBuilderEditor.tsx:62— FormBuilderEditor.FormBuilderEditor has cognitive complexity 27 (threshold 15). Drivers by points: ternaries 10 (13 pts), boolean chains 6, if/else 4 (6 pts), loops 1 (2 pts) (nesting depth added 6). Of this number, 17 points are the body's own statements and 10 belong to 4 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.
AttributeAction.processBatch (cognitive 26) databox/api/src/Automation/Action/AttributeAction.php:119— AttributeAction.processBatch has cognitive complexity 26 (threshold 15). Drivers by points: loops 6 (13 pts), if/else 5 (11 pts), error handling 1 (2 pts) (nesting depth added 14). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
AttributeEntityListener.onFlush (cognitive 26) databox/api/src/Doctrine/Listener/AttributeEntityListener.php:27— AttributeEntityListener.onFlush has cognitive complexity 26 (threshold 15). Drivers by points: if/else 9 (24 pts), loops 2 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AQLGrammar.match_boolean (cognitive 26) databox/api/src/Elasticsearch/AQL/AQLGrammar.php:429— AQLGrammar.match_boolean has cognitive complexity 26 (threshold 15). Drivers by points: if/else 8 (20 pts), loops 3 (6 pts) (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LocaleUtil.getBestLocale (cognitive 26) lib/php/core-bundle/Util/LocaleUtil.php:23— LocaleUtil.getBestLocale has cognitive complexity 26 (threshold 15). Drivers by points: if/else 7 (20 pts), loops 3 (6 pts) (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Parser.atom (cognitive 26) databox/client/src/features/search/aql/parser.ts:530— Parser.atom has cognitive complexity 26 (threshold 15). Drivers by points: if/else 8 (18 pts), loops 1 (4 pts), boolean chains 3, match/switch 1 (nesting depth added 13). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
FilterRulesTab.AttributeRules (cognitive 26) databox/client/src/features/workspaces/manage/tabs/FilterRulesTab.tsx:66— FilterRulesTab.AttributeRules has cognitive complexity 26 (threshold 15). Drivers by points: ternaries 12 (19 pts), boolean chains 5, if/else 2 (nesting depth added 7). Of this number, 21 points are the body's own statements and 5 belong to 3 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.
AudioPlayer.AudioPlayer (cognitive 26) expose/client/src/features/player/AudioPlayer.tsx:52— AudioPlayer.AudioPlayer has cognitive complexity 26 (threshold 15). Drivers by points: ternaries 8 (10 pts), boolean chains 8, if/else 8 (nesting depth added 2). Of this number, 14 points are the body's own statements and 12 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.
CollectionInputMapper.map (cognitive 25) databox/api/src/Api/Mapper/Input/CollectionInputMapper.php:24— CollectionInputMapper.map has cognitive complexity 25 (threshold 15). Drivers by points: if/else 15 (25 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AttributeValidator.doValidateAttribute (cognitive 25) databox/api/src/Attribute/AttributeValidator.php:52— AttributeValidator.doValidateAttribute has cognitive complexity 25 (threshold 15). Drivers by points: if/else 8 (20 pts), loops 1 (3 pts), boolean chains 2 (nesting depth added 14). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
RemoteExportAction.processBatch (cognitive 25) databox/api/src/Automation/Action/RemoteExportAction.php:82— RemoteExportAction.processBatch has cognitive complexity 25 (threshold 15). Drivers by points: if/else 6 (12 pts), loops 4 (10 pts), error handling 1 (3 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AutomationRunner.execute (cognitive 25) databox/api/src/Automation/AutomationRunner.php:145— AutomationRunner.execute has cognitive complexity 25 (threshold 15). Drivers by points: if/else 8 (17 pts), boolean chains 3, loops 3, error handling 1 (2 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AssetPermissionComputer.doGetCollectionHierarchyInfo (cognitive 25) databox/api/src/Elasticsearch/AssetPermissionComputer.php:241— AssetPermissionComputer.doGetCollectionHierarchyInfo has cognitive complexity 25 (threshold 15). Drivers by points: if/else 11 (20 pts), boolean chains 4, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AssetSearch.applySavedSearch (cognitive 25) databox/api/src/Elasticsearch/AssetSearch.php:561— AssetSearch.applySavedSearch has cognitive complexity 25 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 6, ternaries 1 (3 pts), loops 1 (2 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DumpCommand.execute (cognitive 25) lib/php/metadata-manipulator-bundle/src/Command/DumpCommand.php:35— DumpCommand.execute has cognitive complexity 25 (threshold 15). Drivers by points: ternaries 3 (12 pts), if/else 5 (9 pts), loops 2 (4 pts) (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WorkflowOrchestrator.doRerunJobs (cognitive 25) lib/php/workflow/src/WorkflowOrchestrator.php:241— WorkflowOrchestrator.doRerunJobs has cognitive complexity 25 (threshold 15). Drivers by points: if/else 7 (16 pts), loops 3 (5 pts), boolean chains 3, ternaries 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
messageDoc.listToLines (cognitive 25) databox/client/src/features/discussion/messageDoc.ts:264— messageDoc.listToLines has cognitive complexity 25 (threshold 15). Drivers by points: if/else 5 (11 pts), ternaries 3 (9 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
executeDrop.dropAssets (cognitive 25) databox/client/src/features/dnd/executeDrop.ts:94— executeDrop.dropAssets has cognitive complexity 25 (threshold 15). Drivers by points: if/else 8 (15 pts), ternaries 3 (8 pts), boolean chains 1, match/switch 1 (nesting depth added 12). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
ConditionDialog.ConditionDialog (cognitive 25) databox/client/src/features/search/conditions/ConditionDialog.tsx:47— ConditionDialog.ConditionDialog has cognitive complexity 25 (threshold 15). Drivers by points: ternaries 10 (11 pts), if/else 7 (9 pts), boolean chains 4, error handling 1 (nesting depth added 3). Most of this is not in the body itself: 10 of the 25 points are its own statements and the rest belongs to 4 function items inside it that branch (switchMode, submit, a function literal at line 61, …). 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.
SearchConditionChip.HumanizedValue (cognitive 25) databox/client/src/features/search/conditions/SearchConditionChip.tsx:373— SearchConditionChip.HumanizedValue has cognitive complexity 25 (threshold 15). Drivers by points: if/else 11 (14 pts), boolean chains 7, ternaries 4 (nesting depth added 3). Of this number, 24 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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.
SavedSearchAutomationInputMapper.mapActions (cognitive 24) databox/api/src/Api/Mapper/Input/SavedSearchAutomationInputMapper.php:120— SavedSearchAutomationInputMapper.mapActions has cognitive complexity 24 (threshold 15). Drivers by points: ternaries 3 (7 pts), if/else 3 (6 pts), loops 3 (5 pts), boolean chains 4, error handling 1 (2 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WorkspaceOutputMapper.map (cognitive 24) databox/api/src/Api/Mapper/Output/WorkspaceOutputMapper.php:56— WorkspaceOutputMapper.map has cognitive complexity 24 (threshold 15). Drivers by points: ternaries 5 (15 pts), if/else 6 (7 pts), boolean chains 2 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AclListener.indexObject (cognitive 24) databox/api/src/Listener/AclListener.php:272— AclListener.indexObject has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (20 pts), match/switch 2 (3 pts), boolean chains 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SortableSections.SortableSections (cognitive 24) databox/client/src/components/layout/SortableSections.tsx:48— SortableSections.SortableSections has cognitive complexity 24 (threshold 15). Drivers by points: if/else 10 (12 pts), boolean chains 5, ternaries 4 (5 pts), error handling 1, loops 1 (nesting depth added 3). Most of this is not in the body itself: 2 of the 24 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 79, 148, 97, …). 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.
CopyMoveDialog.CopyMoveDialog (cognitive 24) databox/client/src/features/assets/actions/CopyMoveDialog.tsx:25— CopyMoveDialog.CopyMoveDialog has cognitive complexity 24 (threshold 15). Drivers by points: ternaries 11 (15 pts), boolean chains 7, if/else 2 (nesting depth added 4). Of this number, 18 points are the body's own statements and 6 belong to one function item inside it that branches. 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.
Version20260730090000.up (cognitive 23) databox/api/migrations/Version20260730090000.php:23— Version20260730090000.up has cognitive complexity 23 (threshold 15). Drivers by points: if/else 5 (13 pts), ternaries 3 (6 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AQLToESQuery.createCriteria (cognitive 23) databox/api/src/Elasticsearch/AQL/AQLToESQuery.php:124— AQLToESQuery.createCriteria has cognitive complexity 23 (threshold 15). Drivers by points: if/else 11 (13 pts), boolean chains 5, ternaries 2 (4 pts), match/switch 1 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
AssetImportInputFactory.create (cognitive 23) databox/api/src/Service/Import/AssetImportInputFactory.php:39— AssetImportInputFactory.create has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (12 pts), loops 4 (6 pts), ternaries 1 (3 pts), boolean chains 2 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CollectionTreePicker.CollectionTreeNode (cognitive 23) databox/client/src/components/form/CollectionTreePicker.tsx:363— CollectionTreePicker.CollectionTreeNode has cognitive complexity 23 (threshold 15). Drivers by points: boolean chains 10, ternaries 7 (10 pts), if/else 3 (nesting depth added 3). Of this number, 17 points are the body's own statements and 6 belong to 5 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.
QuarantineScreen.QuarantineScreen (cognitive 23) databox/client/src/features/assets/quarantine/QuarantineScreen.tsx:61— QuarantineScreen.QuarantineScreen has cognitive complexity 23 (threshold 15). Drivers by points: ternaries 10 (17 pts), boolean chains 3, if/else 3 (nesting depth added 7). Of this number, 17 points are the body's own statements and 6 belong to 5 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.
basketStore.useBasketStore (cognitive 23) databox/client/src/features/baskets/basketStore.ts:35— basketStore.useBasketStore has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (10 pts), ternaries 6 (7 pts), boolean chains 5, error handling 1 (nesting depth added 2). None of this is in the body itself: all 23 points belong to 9 function literals inside it that branch (lines 122, 43, 92, …). 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.
CollectionsPanel.CollectionsPanel (cognitive 23) databox/client/src/features/collections/tree/CollectionsPanel.tsx:75— CollectionsPanel.CollectionsPanel has cognitive complexity 23 (threshold 15). Drivers by points: ternaries 8 (15 pts), boolean chains 8 (nesting depth added 7). Of this number, 18 points are the body's own statements and 5 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
InstancePermissionsScreen.InstancePermissionsScreen (cognitive 23) databox/client/src/features/permissions/InstancePermissionsScreen.tsx:82— InstancePermissionsScreen.InstancePermissionsScreen has cognitive complexity 23 (threshold 15). Drivers by points: ternaries 9 (13 pts), boolean chains 5, if/else 3, error handling 1, loops 1 (nesting depth added 4). Most of this is not in the body itself: 6 of the 23 points are its own statements and the rest belongs to 9 function items inside it that branch (getRowLabel, a function literal at line 312, run, …). 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.
http.createInstance (cognitive 23) databox/client/src/lib/api/http.ts:83— http.createInstance has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (15 pts), ternaries 3 (5 pts), boolean chains 3 (nesting depth added 8). None of this is in the body itself: all 23 points belong to 3 function literals inside it that branch (lines 96, 143, 178). 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.
axios.createHttpClient (cognitive 23) databox/indexer/src/lib/axios.ts:25— axios.createHttpClient has cognitive complexity 23 (threshold 15). Drivers by points: if/else 11 (16 pts), boolean chains 3, error handling 1 (3 pts), ternaries 1 (nesting depth added 7). Most of this is not in the body itself: 1 of the 23 points is its own statement and the rest belongs to 3 function literals inside it that branch (lines 104, 48, 164). 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.
PublicationEditScreen.PublicationEditForm (cognitive 23) expose/client/src/features/admin/PublicationEditScreen.tsx:86— PublicationEditScreen.PublicationEditForm has cognitive complexity 23 (threshold 15). Drivers by points: ternaries 11 (12 pts), boolean chains 6, if/else 3 (4 pts), error handling 1 (nesting depth added 2). Most of this is not in the body itself: 10 of the 23 points are its own statements and the rest belongs to 3 function items inside it that branch (submit, a function literal at line 109, a function literal at line 316). 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.
multiPartUpload.multipartUpload (cognitive 23) lib/js/api/src/multiPartUpload.ts:140— multiPartUpload.multipartUpload has cognitive complexity 23 (threshold 15). Drivers by points: if/else 12 (17 pts), error handling 2, ternaries 2, boolean chains 1, loops 1 (nesting depth added 5). Of this number, 12 points are the body's own statements and 11 belong to 7 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.
FilenameAnalyzer.analyzeFile (cognitive 22) databox/api/src/Border/FileAnalyzer/Analyzer/FilenameAnalyzer.php:70— FilenameAnalyzer.analyzeFile has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 4, loops 2 (4 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AssetPermissionComputer.doGetWorkspaceHierarchyInfo (cognitive 22) databox/api/src/Elasticsearch/AssetPermissionComputer.php:188— AssetPermissionComputer.doGetWorkspaceHierarchyInfo has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (19 pts), boolean chains 2, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AssetSortGroupMapper.resolveSortGroups (cognitive 22) databox/api/src/Service/Asset/AssetSortGroupMapper.php:28— AssetSortGroupMapper.resolveSortGroups has cognitive complexity 22 (threshold 15). Drivers by points: if/else 4 (15 pts), loops 3 (7 pts) (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DynamicAttributeBag.__call (cognitive 22) databox/api/src/Service/Asset/Attribute/DynamicAttributeBag.php:31— DynamicAttributeBag.__call has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (13 pts), loops 3 (8 pts), ternaries 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ProxyCachePurger.purgeUri (cognitive 22) expose/api/src/Http/Cache/ProxyCachePurger.php:27— ProxyCachePurger.purgeUri has cognitive complexity 22 (threshold 15). Drivers by points: loops 3 (9 pts), if/else 3 (8 pts), error handling 1 (5 pts) (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
IndexRemover.collectIndicesToRemove (cognitive 22) lib/php/es-bundle/Service/IndexRemover.php:28— IndexRemover.collectIndicesToRemove has cognitive complexity 22 (threshold 15). Drivers by points: if/else 5 (14 pts), boolean chains 4, loops 2 (3 pts), ternaries 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AttributesEditor.AttributeField (cognitive 22) databox/client/src/features/attributes/editor/AttributesEditor.tsx:250— AttributesEditor.AttributeField has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 9 (14 pts), boolean chains 6, if/else 2 (nesting depth added 5). Most of this is not in the body itself: 3 of the 22 points are its own statements and the rest belongs to 7 function items inside it that branch (annotationButton, a function literal at line 401, a function literal at line 302, …). 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.
ShareAssetView.ShareAssetView (cognitive 22) databox/client/src/features/share/ShareAssetView.tsx:47— ShareAssetView.ShareAssetView has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 9 (11 pts), if/else 6, boolean chains 5 (nesting depth added 2). Of this number, 14 points are the body's own statements and 8 belong to 2 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.
SharePage.ShareContent (cognitive 22) databox/client/src/features/share/SharePage.tsx:156— SharePage.ShareContent has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 10 (13 pts), if/else 8, boolean chains 1 (nesting depth added 3). Of this number, 13 points are the body's own statements and 9 belong to 3 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.
WorkflowHeader.WorkflowHeader (cognitive 22) databox/client/src/features/workflows/WorkflowHeader.tsx:55— WorkflowHeader.WorkflowHeader has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 10 (15 pts), boolean chains 4, if/else 3 (nesting depth added 5). Of this number, 21 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AuthProvider.AuthProvider (cognitive 22) databox/client/src/lib/auth/AuthProvider.tsx:89— AuthProvider.AuthProvider has cognitive complexity 22 (threshold 15). Drivers by points: if/else 11, boolean chains 6, ternaries 5. Most of this is not in the body itself: 5 of the 22 points are its own statements and the rest belongs to 9 function literals inside it that branch (lines 146, 224, 105, …). 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.
StructureImporter.importMetadataStructure (cognitive 22) databox/indexer/src/handlers/phraseanet/StructureImporter.ts:429— StructureImporter.importMetadataStructure has cognitive complexity 22 (threshold 15). Drivers by points: if/else 3 (8 pts), ternaries 2 (6 pts), error handling 1 (4 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FormBuilder.FormBuilder (cognitive 22) uploader/client/src/features/form-builder/editor/FormBuilder.tsx:96— FormBuilder.FormBuilder has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (9 pts), ternaries 6 (8 pts), boolean chains 4, match/switch 1 (nesting depth added 3). Most of this is not in the body itself: 1 of the 22 points is its own statement and the rest belongs to 9 function items inside it that branch (onDragEnd, a function literal at line 339, create, …). 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.
useFileDrop.useFileDrop (cognitive 22) uploader/client/src/features/upload/useFileDrop.tsx:28— useFileDrop.useFileDrop has cognitive complexity 22 (threshold 15). Drivers by points: if/else 11 (12 pts), ternaries 5 (8 pts), boolean chains 1, loops 1 (nesting depth added 4). None of this is in the body itself: all 22 points belong to 3 function items inside it that branch (reportRejections, a function literal at line 138, listNames). 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.
AttributeInputTrait.assignAttributes (cognitive 21) databox/api/src/Api/Mapper/Input/AttributeInputTrait.php:66— AttributeInputTrait.assignAttributes has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (16 pts), loops 2 (5 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PublicationVoter.voteOnAttribute (cognitive 21) expose/api/src/Security/Voter/PublicationVoter.php:59— PublicationVoter.voteOnAttribute has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 20, match/switch 1. The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
GridCardZones.GridCardZones (cognitive 21) databox/client/src/features/assets/list/layouts/GridCardZones.tsx:88— GridCardZones.GridCardZones has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 5, ternaries 2 (3 pts), loops 1 (nesting depth added 6). Most of this is not in the body itself: 2 of the 21 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 107, 211). 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.
VideoFilmstrip.VideoFilmstrip (cognitive 21) databox/client/src/features/clip/VideoFilmstrip.tsx:33— VideoFilmstrip.VideoFilmstrip has cognitive complexity 21 (threshold 15). Drivers by points: if/else 12, ternaries 4 (5 pts), boolean chains 4 (nesting depth added 1). Most of this is not in the body itself: 8 of the 21 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 127, 178, 56, …). 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.
canDrop.canDropCollection (cognitive 21) databox/client/src/features/dnd/canDrop.ts:199— canDrop.canDropCollection has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (18 pts), boolean chains 2, match/switch 1 (nesting depth added 9). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
RekognitionPanel.RekognitionPanel (cognitive 21) databox/client/src/features/integrations/rekognition/RekognitionPanel.tsx:115— RekognitionPanel.RekognitionPanel has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 9 (12 pts), boolean chains 8, error handling 1 (nesting depth added 3). Most of this is not in the body itself: 5 of the 21 points are its own statements and the rest belongs to 4 function items inside it that branch (a function literal at line 302, a function literal at line 351, run, …). 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.
ExposePublishForm.ExposePublishForm (cognitive 21) databox/client/src/features/saved-searches/automations/actions/ExposePublishForm.tsx:180— ExposePublishForm.ExposePublishForm has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 7 (9 pts), boolean chains 8, if/else 4 (nesting depth added 2). Of this number, 12 points are the body's own statements and 9 belong to 4 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.
OAuthClient.createAxiosInterceptor.<returned closure> (cognitive 21) lib/js/auth/src/client/OAuthClient.ts:585— OAuthClient.createAxiosInterceptor.<returned closure> has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (15 pts), boolean chains 3, error handling 1 (3 pts) (nesting depth added 10). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
AttributeEntityExtension.applyToCollection (cognitive 20) databox/api/src/Api/Extension/AttributeEntityExtension.php:31— AttributeEntityExtension.applyToCollection has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (11 pts), loops 2 (4 pts), ternaries 2 (3 pts), boolean chains 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ConfigSchemaDumper.dumpType (cognitive 20) databox/api/src/Integration/Config/ConfigSchemaDumper.php:79— ConfigSchemaDumper.dumpType has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11 (16 pts), boolean chains 2, ternaries 1 (2 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RenditionIntegration.getWorkflowJobDefinitions (cognitive 20) databox/api/src/Integration/Core/Rendition/RenditionIntegration.php:61— RenditionIntegration.getWorkflowJobDefinitions has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (13 pts), loops 4 (7 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SearchIndexer.indexClass (cognitive 20) lib/php/es-bundle/Indexer/SearchIndexer.php:108— SearchIndexer.indexClass has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (14 pts), ternaries 1 (3 pts), loops 1 (2 pts), match/switch 1 (nesting depth added 11). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
Version20261111120000.mergeLiFormTranslations (cognitive 20) uploader/api/migrations/Version20261111120000.php:271— Version20261111120000.mergeLiFormTranslations has cognitive complexity 20 (threshold 15). Drivers by points: if/else 3 (9 pts), loops 3 (8 pts), boolean chains 3 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
messageDoc.tokenize (cognitive 20) databox/client/src/features/discussion/messageDoc.ts:155— messageDoc.tokenize has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 2, ternaries 1 (2 pts), loops 1 (nesting depth added 7). Of this number, 17 points are the body's own statements and 3 belong to one function item inside it that branches. To reduce it, split the body 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.
OperationTasksScreen.OperationTasksScreen (cognitive 20) databox/client/src/features/operation-tasks/OperationTasksScreen.tsx:254— OperationTasksScreen.OperationTasksScreen has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 9 (16 pts), boolean chains 4 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ConditionBuilder.ConditionRow (cognitive 20) databox/client/src/features/search/conditions/ConditionBuilder.tsx:276— ConditionBuilder.ConditionRow has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 10 (16 pts), boolean chains 2, if/else 2 (nesting depth added 6). Most of this is not in the body itself: 9 of the 20 points are its own statements and the rest belongs to 4 function items inside it that branch (a function literal at line 334, setValue, a function literal at line 299, …). 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.
WorkflowsScreen.WorkflowsScreen (cognitive 20) databox/client/src/features/workflows/WorkflowsScreen.tsx:48— WorkflowsScreen.WorkflowsScreen has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 11 (18 pts), boolean chains 2 (nesting depth added 7). Of this number, 10 points are the body's own statements and 10 belong to 2 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ProfileList.ProfileList (cognitive 20) expose/client/src/features/admin/ProfileList.tsx:22— ProfileList.ProfileList has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 7 (20 pts) (nesting depth added 13). Most of this is not in the body itself: 7 of the 20 points are its own statements and the rest belongs to one function literal inside it that branches (line 97). The decisions are inside the literal, 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 literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
WorkspaceIntegrationInputMapper.map (cognitive 19) databox/api/src/Api/Mapper/Input/WorkspaceIntegrationInputMapper.php:31— WorkspaceIntegrationInputMapper.map has cognitive complexity 19 (threshold 15). Drivers by points: if/else 11 (13 pts), error handling 1 (2 pts), loops 1 (2 pts), ternaries 1 (2 pts) (nesting depth added 5). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
AuditLogListener.logSemanticChange (cognitive 19) databox/api/src/Doctrine/Listener/AuditLogListener.php:178— AuditLogListener.logSemanticChange has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 4 (8 pts), if/else 3 (5 pts), boolean chains 4, match/switch 1 (2 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
OrphanFileRemover.getColumns (cognitive 19) databox/api/src/File/OrphanFileRemover.php:57— OrphanFileRemover.getColumns has cognitive complexity 19 (threshold 15). Drivers by points: if/else 4 (13 pts), loops 2 (5 pts), boolean chains 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TranscriptionHappyscribeMessageHandler.__invoke (cognitive 19) databox/api/src/Integration/Happyscribe/Consumer/TranscriptionHappyscribeMessageHandler.php:31— TranscriptionHappyscribeMessageHandler.__invoke has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (16 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AttributeMetadataEmbedder.buildMetadataBag (cognitive 19) databox/api/src/Service/Asset/Attribute/AttributeMetadataEmbedder.php:31— AttributeMetadataEmbedder.buildMetadataBag has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (12 pts), loops 3 (4 pts), boolean chains 2, ternaries 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RenditionBuilder.buildRendition (cognitive 19) databox/api/src/Service/Asset/RenditionBuilder.php:52— RenditionBuilder.buildRendition has cognitive complexity 19 (threshold 15). Drivers by points: if/else 12 (16 pts), boolean chains 2, error handling 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MetadataNormalizer.denormalize (cognitive 19) databox/api/src/Service/Metadata/MetadataNormalizer.php:53— MetadataNormalizer.denormalize has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (12 pts), error handling 1 (3 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AssetNormalizer.normalize (cognitive 19) expose/api/src/Serializer/Normalizer/AssetNormalizer.php:40— AssetNormalizer.normalize has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 3, loops 1 (2 pts), ternaries 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FilesystemUtils.rrmdir (cognitive 19) lib/php/core-bundle/Util/FilesystemUtils.php:9— FilesystemUtils.rrmdir has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (14 pts), loops 1 (3 pts), boolean chains 2 (nesting depth added 10). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
NotificationDeliverer.deliverTo (cognitive 19) lib/php/notifier-bundle/src/Delivery/NotificationDeliverer.php:55— NotificationDeliverer.deliverTo has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (10 pts), error handling 2 (5 pts), boolean chains 3, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ShapeControl.ShapeControl (cognitive 19) databox/client/src/features/annotations/ShapeControl.tsx:22— ShapeControl.ShapeControl has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 8 (12 pts), if/else 5 (6 pts), boolean chains 1 (nesting depth added 5). Of this number, 14 points are the body's own statements and 5 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FilePlayer.FilePlayer (cognitive 19) databox/client/src/features/assets/player/FilePlayer.tsx:89— FilePlayer.FilePlayer has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 6 (10 pts), if/else 4 (6 pts), boolean chains 2, match/switch 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BasketsPanel.BasketRow (cognitive 19) databox/client/src/features/baskets/BasketsPanel.tsx:127— BasketsPanel.BasketRow has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 12 (16 pts), boolean chains 3 (nesting depth added 4). Most of this is not in the body itself: 7 of the 19 points are its own statements and the rest belongs to 3 function items inside it that branch (menu, a function literal at line 143, a function literal at line 221). 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.
ConfigForm.ListField (cognitive 19) databox/client/src/features/integrations/config/ConfigForm.tsx:762— ConfigForm.ListField has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 7 (13 pts), if/else 4, boolean chains 2 (nesting depth added 6). Of this number, 13 points are the body's own statements and 6 belong to 3 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.
SelectProfileDialog.ProfileRow (cognitive 19) databox/client/src/features/profiles/SelectProfileDialog.tsx:110— SelectProfileDialog.ProfileRow has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 11 (17 pts), boolean chains 2 (nesting depth added 6). Of this number, 17 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
filterSuggestions.suggestFields (cognitive 19) databox/client/src/features/search/suggest/filterSuggestions.ts:117— filterSuggestions.suggestFields has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 4, loops 1, ternaries 1 (nesting depth added 4). Of this number, 18 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ConditionBuilder.pickerFor (cognitive 19) databox/client/src/features/search/conditions/ConditionBuilder.tsx:686— ConditionBuilder.pickerFor has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 5 (10 pts), boolean chains 4, if/else 2 (3 pts), match/switch 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DateHistogramFacet.DateHistogramFacet (cognitive 19) databox/client/src/features/search/facets/widgets/DateHistogramFacet.tsx:19— DateHistogramFacet.DateHistogramFacet has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 6 (9 pts), boolean chains 5, if/else 4 (5 pts) (nesting depth added 4). Most of this is not in the body itself: 4 of the 19 points are its own statements and the rest belongs to 5 function items inside it that branch (a function literal at line 48, a function literal at line 56, a function literal at line 101, …). 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.
useFormSubmit.useFormSubmit.doSubmit (cognitive 19) lib/js/api/src/useFormSubmit.ts:42— useFormSubmit.useFormSubmit.doSubmit has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (11 pts), error handling 2 (6 pts), boolean chains 1, ternaries 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Version20250415153255.up (cognitive 18) configurator/migrations/Version20250415153255.php:24— Version20250415153255.up has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 18. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
AssetPolicyInputMapper.map (cognitive 18) databox/api/src/Api/Mapper/Input/AssetPolicyInputMapper.php:27— AssetPolicyInputMapper.map has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (11 pts), loops 2 (6 pts), boolean chains 1 (nesting depth added 6). 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.
AutomationRunner.finalize (cognitive 18) databox/api/src/Automation/AutomationRunner.php:313— AutomationRunner.finalize has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 2, match/switch 1 (2 pts), ternaries 1 (2 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FaceRecognitionIndexCommand.execute (cognitive 18) databox/api/src/Command/FaceRecognitionIndexCommand.php:44— FaceRecognitionIndexCommand.execute has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (9 pts), ternaries 2 (5 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SimilarityIndexCommand.execute (cognitive 18) databox/api/src/Command/SimilarityIndexCommand.php:45— SimilarityIndexCommand.execute has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (9 pts), ternaries 2 (5 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ClusterGroup.mix (cognitive 18) databox/api/src/Elasticsearch/AQL/ClusterGroup.php:52— ClusterGroup.mix has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 2 (8 pts), boolean chains 4, if/else 1 (3 pts), loops 2 (3 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AbstractSearch.createACLBoolQuery (cognitive 18) databox/api/src/Elasticsearch/AbstractSearch.php:116— AbstractSearch.createACLBoolQuery has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11 (16 pts), loops 1 (2 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
IndexMappingDiff.propertiesDiffer (cognitive 18) databox/api/src/Elasticsearch/Mapping/IndexMappingDiff.php:37— IndexMappingDiff.propertiesDiffer has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (16 pts), boolean chains 1, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ProfileItem.validate (cognitive 18) databox/api/src/Entity/Profile/ProfileItem.php:427— ProfileItem.validate has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 2, match/switch 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FileAnalysisReevaluator.restoreLink (cognitive 18) databox/api/src/File/FileAnalysisReevaluator.php:149— FileAnalysisReevaluator.restoreLink has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (12 pts), loops 3 (4 pts), boolean chains 2 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
StoryContactSheetInputResolver.resolve (cognitive 18) databox/api/src/Service/Asset/StoryContactSheetInputResolver.php:35— StoryContactSheetInputResolver.resolve has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (11 pts), boolean chains 4, loops 2 (3 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ImportEntryNormalizer.normalizeAttributes (cognitive 18) databox/api/src/Service/Import/ImportEntryNormalizer.php:160— ImportEntryNormalizer.normalizeAttributes has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (12 pts), loops 2 (4 pts), boolean chains 2 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AssetSimilarityScorer.getReferenceAssetId (cognitive 18) databox/api/src/Service/Vector/AssetSimilarityScorer.php:36— AssetSimilarityScorer.getReferenceAssetId has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (11 pts), boolean chains 5, loops 1, ternaries 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ExposeDataPersister.process (cognitive 18) expose/api/src/DataPersister/ExposeDataPersister.php:32— ExposeDataPersister.process has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 4, error handling 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FormDefinition.fromArray (cognitive 18) uploader/api/src/Form/Builder/FormDefinition.php:26— FormDefinition.fromArray has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 5, loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
route.POST (cognitive 18) databox/client/src/app/api/ticketing/route.ts:31— route.POST has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (8 pts), error handling 5 (6 pts), ternaries 2 (4 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PrivacyField.PrivacyField (cognitive 18) databox/client/src/components/form/PrivacyField.tsx:59— PrivacyField.PrivacyField has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 8, ternaries 6 (8 pts), if/else 2 (nesting depth added 2). Of this number, 14 points are the body's own statements and 4 belong to 2 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.
ExportDialog.ExportDialog (cognitive 18) databox/client/src/features/assets/actions/ExportDialog.tsx:31— ExportDialog.ExportDialog has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 12, boolean chains 4, if/else 2. Most of this is not in the body itself: 4 of the 18 points are its own statements and the rest belongs to 6 function items inside it that branch (submit, a function literal at line 72, a function literal at line 86, …). 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.
ListLayout.ListLayout (cognitive 18) databox/client/src/features/assets/list/layouts/ListLayout.tsx:38— ListLayout.ListLayout has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 6 (8 pts), if/else 4 (6 pts), boolean chains 3, loops 1 (nesting depth added 4). Most of this is not in the body itself: 1 of the 18 points is its own statement and the rest belongs to 5 function literals inside it that branch (lines 41, 102, 85, …). 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.
webVtt.parseWebVtt (cognitive 18) databox/client/src/features/assets/player/webVtt.ts:90— webVtt.parseWebVtt has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (11 pts), loops 2 (3 pts), boolean chains 2, ternaries 1 (2 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ImportAssetsDialog.ImportAssetsDialog (cognitive 18) databox/client/src/features/import/ImportAssetsDialog.tsx:105— ImportAssetsDialog.ImportAssetsDialog has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 7, ternaries 6 (7 pts), if/else 4 (nesting depth added 1). Most of this is not in the body itself: 8 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 118, a function literal at line 140, a function literal at line 174, …). 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.
NotificationsMenu.NotificationsMenu (cognitive 18) databox/client/src/features/notifications/NotificationsMenu.tsx:46— NotificationsMenu.NotificationsMenu has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 10 (13 pts), if/else 2 (3 pts), boolean chains 2 (nesting depth added 4). Most of this is not in the body itself: 8 of the 18 points are its own statements and the rest belongs to 5 function items inside it that branch (a function literal at line 149, a function literal at line 86, a function literal at line 69, …). 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.
OperationTasksScreen.TaskDetails (cognitive 18) databox/client/src/features/operation-tasks/OperationTasksScreen.tsx:574— OperationTasksScreen.TaskDetails has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 11 (12 pts), if/else 4, boolean chains 2 (nesting depth added 1). Of this number, 14 points are the body's own statements and 4 belong to 3 function items inside it that branch. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ProfileAttributesTab.ProfileSectionEditor (cognitive 18) databox/client/src/features/profiles/manage/ProfileAttributesTab.tsx:115— ProfileAttributesTab.ProfileSectionEditor has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (9 pts), ternaries 6, boolean chains 3 (nesting depth added 1). None of this is in the body itself: all 18 points belong to 8 function items inside it that branch (onDragEnd, insertionAt, add, …). 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.
AttributeActionForm.AttributeActionForm (cognitive 18) databox/client/src/features/saved-searches/automations/actions/AttributeActionForm.tsx:25— AttributeActionForm.AttributeActionForm has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 9 (13 pts), boolean chains 5 (nesting depth added 4). Of this number, 9 points are the body's own statements and 9 belong to 3 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.
SavedSearchList.SavedSearchRow (cognitive 18) databox/client/src/features/saved-searches/SavedSearchList.tsx:131— SavedSearchList.SavedSearchRow has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 8 (9 pts), boolean chains 5, if/else 3 (4 pts) (nesting depth added 2). Most of this is not in the body itself: 6 of the 18 points are its own statements and the rest belongs to 3 function items inside it that branch (menu, open, a function literal at line 194). 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.
operatorLabel.getOperatorLabel (cognitive 18) databox/client/src/features/search/aql/operatorLabel.ts:11— operatorLabel.getOperatorLabel has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 8 (16 pts), boolean chains 1, match/switch 1 (nesting depth added 8). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
SecretManager.SecretManager (cognitive 18) databox/client/src/features/secrets/SecretManager.tsx:56— SecretManager.SecretManager has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 11 (17 pts), boolean chains 1 (nesting depth added 6). Of this number, 14 points are the body's own statements and 4 belong to 4 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.
FileSelectionStep.FileSelectionStep (cognitive 18) uploader/client/src/features/upload/FileSelectionStep.tsx:44— FileSelectionStep.FileSelectionStep has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 10 (16 pts), boolean chains 1, if/else 1 (nesting depth added 6). Of this number, 17 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WorkspaceInputMapper.map (cognitive 17) databox/api/src/Api/Mapper/Input/WorkspaceInputMapper.php:28— WorkspaceInputMapper.map has cognitive complexity 17 (threshold 15). Drivers by points: if/else 13 (14 pts), boolean chains 3 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ExposePublishAction.finish (cognitive 17) databox/api/src/Automation/Action/ExposePublishAction.php:200— ExposePublishAction.finish has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (9 pts), error handling 3 (5 pts), boolean chains 2, loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PhraseanetIntegrationController.webhookEventAction (cognitive 17) databox/api/src/Controller/Integration/PhraseanetIntegrationController.php:125— PhraseanetIntegrationController.webhookEventAction has cognitive complexity 17 (threshold 15). Drivers by points: if/else 3 (8 pts), error handling 2 (6 pts), boolean chains 2, match/switch 1 (nesting depth added 9). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
AQLGrammar.match_identifier (cognitive 17) databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1985— AQLGrammar.match_identifier has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (9 pts), ternaries 2 (5 pts), loops 2 (3 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MultipartUploader.putPart (cognitive 17) lib/php/core-bundle/Upload/MultipartUploader.php:105— MultipartUploader.putPart has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (10 pts), error handling 2 (4 pts), boolean chains 2, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
VideoToAnimationTransformerModule.getDimensionsInset (cognitive 17) lib/php/rendition-factory/src/Transformer/Video/VideoToAnimationTransformerModule.php:233— VideoToAnimationTransformerModule.getDimensionsInset has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (8 pts), ternaries 2 (4 pts), error handling 1 (3 pts), boolean chains 1, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
services.getServiceCards (cognitive 17) dashboard/client/src/features/dashboard/services.ts:34— services.getServiceCards has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (8 pts), boolean chains 4, ternaries 2 (4 pts), loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FilePicker.FilePicker (cognitive 17) databox/client/src/components/form/FilePicker.tsx:23— FilePicker.FilePicker has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 11 (14 pts), if/else 2, boolean chains 1 (nesting depth added 3). Of this number, 13 points are the body's own statements and 4 belong to one function literal inside it that branches. 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.
TagsInput.TagsInput (cognitive 17) databox/client/src/components/form/TagsInput.tsx:38— TagsInput.TagsInput has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (10 pts), boolean chains 6, ternaries 1 (nesting depth added 1). Most of this is not in the body itself: 2 of the 17 points are its own statements and the rest belongs to 5 function items inside it that branch (onKeyDown, a function literal at line 55, add, …). 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.
useTimelineDrag.useTimelineDrag::move (cognitive 17) databox/client/src/features/clip/useTimelineDrag.ts:129— useTimelineDrag.useTimelineDrag::move has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 2, match/switch 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ConditionBuilder.fromQuery (cognitive 17) databox/client/src/features/search/aql/serializer.ts:181— ConditionBuilder.fromQuery has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (7 pts), error handling 1 (3 pts), loops 2 (3 pts), ternaries 2 (3 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ResultProvider.ResultProvider (cognitive 17) databox/client/src/features/search/ResultProvider.tsx:51— ResultProvider.ResultProvider has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 6 (7 pts), if/else 4 (5 pts), boolean chains 4, error handling 1 (nesting depth added 2). None of this is in the body itself: all 17 points belong to 5 function literals inside it that branch (lines 117, 155, 92, …). 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.
ShareDialog.ShareItem (cognitive 17) databox/client/src/features/share/ShareDialog.tsx:518— ShareDialog.ShareItem has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 7 (13 pts), boolean chains 2, error handling 1, if/else 1 (nesting depth added 6). Of this number, 14 points are the body's own statements and 3 belong to 2 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
useRequestErrorHandler.useRequestErrorHandler (cognitive 17) lib/js/api/src/useRequestErrorHandler.ts:14— useRequestErrorHandler.useRequestErrorHandler has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (11 pts), boolean chains 5, match/switch 1 (nesting depth added 4). None of this is in the body itself: all 17 points belong to one function literal inside it that branches (line 17). The decisions are inside the literal, 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 literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
FormCanvas.FieldCard (cognitive 17) uploader/client/src/features/form-builder/editor/FormCanvas.tsx:214— FormCanvas.FieldCard has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 8 (13 pts), boolean chains 4 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
HttpClientUtil.waitForHostHttp (cognitive 16) REDACTED:85— HttpClientUtil.waitForHostHttp has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (11 pts), error handling 1 (2 pts), boolean chains 1, loops 1, ternaries 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ProfileItemInput.validate (cognitive 16) databox/api/src/Api/Model/Input/ProfileItemInput.php:57— ProfileItemInput.validate has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 1, match/switch 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AddToProfileProcessor.process (cognitive 16) databox/api/src/Api/Processor/AddToProfileProcessor.php:37— AddToProfileProcessor.process has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (11 pts), match/switch 1 (2 pts), ternaries 1 (2 pts), loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ResolveEntitiesProcessor.process (cognitive 16) databox/api/src/Api/Processor/ResolveEntitiesProcessor.php:38— ResolveEntitiesProcessor.process has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (6 pts), ternaries 2 (4 pts), boolean chains 2, error handling 1 (2 pts), loops 2 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ShareProcessor.process (cognitive 16) databox/api/src/Api/Processor/ShareProcessor.php:35— ShareProcessor.process has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (9 pts), loops 3, boolean chains 2, ternaries 2 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PopulatePassCrudController.addPopulate (cognitive 16) databox/api/src/Controller/Admin/PopulatePassCrudController.php:120— PopulatePassCrudController.addPopulate has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (14 pts), loops 1 (2 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CollectionSearch.applyFilters (cognitive 16) databox/api/src/Elasticsearch/CollectionSearch.php:185— CollectionSearch.applyFilters has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (11 pts), match/switch 1 (3 pts), loops 2 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, 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.
OAuthRedirectUriMatcher.isAllowed (cognitive 16) databox/api/src/Integration/Auth/OAuthRedirectUriMatcher.php:68— OAuthRedirectUriMatcher.isAllowed has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (11 pts), boolean chains 4, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
HappyscribeAction.doHandle (cognitive 16) databox/api/src/Integration/Happyscribe/HappyscribeAction.php:37— HappyscribeAction.doHandle has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (12 pts), boolean chains 1, error handling 1, loops 1, ternaries 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, 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.
BasketVoter.voteOnAttribute (cognitive 16) databox/api/src/Security/Voter/BasketVoter.php:34— BasketVoter.voteOnAttribute has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 14, match/switch 1, ternaries 1. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
WorkspaceIntegrationVoter.voteOnAttribute (cognitive 16) databox/api/src/Security/Voter/WorkspaceIntegrationVoter.php:33— WorkspaceIntegrationVoter.voteOnAttribute has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 12, ternaries 2, if/else 1, match/switch 1. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
AttributesResolver.assignHighlight (cognitive 16) databox/api/src/Service/Asset/Attribute/AttributesResolver.php:128— AttributesResolver.assignHighlight has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (11 pts), loops 2 (5 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AssetPolicySection.import (cognitive 16) databox/api/src/Service/Workspace/Template/Section/AssetPolicySection.php:43— AssetPolicySection.import has cognitive complexity 16 (threshold 15). Drivers by points: loops 4 (11 pts), if/else 2 (4 pts), boolean chains 1 (nesting depth added 9). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
ExtractEmbeddedPreviewTransformerModule.transform (cognitive 16) lib/php/rendition-factory/src/Transformer/ExtractEmbeddedPreviewTransformerModule.php:59— ExtractEmbeddedPreviewTransformerModule.transform has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (8 pts), boolean chains 4, error handling 2 (3 pts), loops 1 (nesting depth added 3). 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.
VideoToAnimationTransformerModule.transform (cognitive 16) lib/php/rendition-factory/src/Transformer/Video/VideoToAnimationTransformerModule.php:128— VideoToAnimationTransformerModule.transform has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (11 pts), boolean chains 4, match/switch 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
JobStatusCacheTrait.cacheJobState (cognitive 16) lib/php/workflow/src/State/Repository/JobStatusCacheTrait.php:47— JobStatusCacheTrait.cacheJobState has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (13 pts), loops 1 (3 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CommitProcessor.process (cognitive 16) uploader/api/src/Api/Processor/CommitProcessor.php:49— CommitProcessor.process has cognitive complexity 16 (threshold 15). Drivers by points: if/else 11 (13 pts), ternaries 1 (2 pts), boolean chains 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
DataboxCatalog.getTagOptions (cognitive 16) uploader/api/src/Databox/DataboxCatalog.php:140— DataboxCatalog.getTagOptions has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (9 pts), error handling 1 (3 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CollectionTreePicker.CollectionTreePicker (cognitive 16) databox/client/src/components/form/CollectionTreePicker.tsx:79— CollectionTreePicker.CollectionTreePicker has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 7 (8 pts), boolean chains 6, if/else 2 (nesting depth added 1). Of this number, 10 points are the body's own statements and 6 belong to 4 function literals inside it that branch. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
CollectionTreePicker.WorkspaceNode (cognitive 16) databox/client/src/components/form/CollectionTreePicker.tsx:224— CollectionTreePicker.WorkspaceNode has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 6 (9 pts), boolean chains 6, if/else 1 (nesting depth added 3). Of this number, 12 points are the body's own statements and 4 belong to 3 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.
SelectionProvider.computeSelection (cognitive 16) databox/client/src/features/assets/list/SelectionProvider.tsx:80— SelectionProvider.computeSelection has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (9 pts), ternaries 2 (4 pts), boolean chains 3 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AssetRenditionsTab.RenditionCard (cognitive 16) databox/client/src/features/assets/manage/tabs/AssetRenditionsTab.tsx:155— AssetRenditionsTab.RenditionCard has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 12, boolean chains 4. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
AssetPanel.useSingleLineTabs (cognitive 16) databox/client/src/features/assets/view/AssetPanel.tsx:257— AssetPanel.useSingleLineTabs has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (10 pts), boolean chains 3, ternaries 1 (2 pts), loops 1 (nesting depth added 2). None of this is in the body itself: all 16 points belong to 5 function literals inside it that branch (lines 307, 270, 286, …). 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.
WebVttTranscript.WebVttTranscript (cognitive 16) databox/client/src/features/attributes/types/WebVttTranscript.tsx:42— WebVttTranscript.WebVttTranscript has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6, ternaries 4 (6 pts), boolean chains 4 (nesting depth added 2). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 5 function literals inside it that branch (lines 127, 73, 59, …). 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.
MessageAttachments.PostedAttachments (cognitive 16) databox/client/src/features/discussion/MessageAttachments.tsx:32— MessageAttachments.PostedAttachments has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 6 (8 pts), boolean chains 7, if/else 1 (nesting depth added 2). Most of this is not in the body itself: 2 of the 16 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 100, 56). 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.
messageDoc.blockToMarkup (cognitive 16) databox/client/src/features/discussion/messageDoc.ts:310— messageDoc.blockToMarkup has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 4 (9 pts), loops 2 (4 pts), boolean chains 2, match/switch 1 (nesting depth added 7). Of this number, 13 points are the body's own statements and 3 belong to one function literal inside it that branches. The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
DragGhost.DragGhost (cognitive 16) databox/client/src/features/dnd/DragGhost.tsx:16— DragGhost.DragGhost has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 7 (9 pts), if/else 5, boolean chains 2 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, 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.
ProfileGridTab.ProfileGridTab::onDragEnd (cognitive 16) databox/client/src/features/profiles/manage/ProfileGridTab.tsx:247— ProfileGridTab.ProfileGridTab::onDragEnd has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 3, ternaries 1 (2 pts) (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
entityColumns.entityPatchFromCell (cognitive 16) databox/client/src/features/workspaces/manage/entities/entityColumns.tsx:116— entityColumns.entityPatchFromCell has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (10 pts), boolean chains 3, ternaries 1 (2 pts), match/switch 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
EntityForm.EntityForm::save (cognitive 16) databox/client/src/features/workspaces/manage/entities/EntityForm.tsx:70— EntityForm.EntityForm::save has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 5, ternaries 5, if/else 3 (4 pts), error handling 2 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
configDraft.fromDraft (cognitive 16) expose/client/src/features/admin/config/configDraft.ts:82— configDraft.fromDraft has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 7 (11 pts), boolean chains 5 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
sentryTunnel.createSentryTunnelHandler.<returned closure> (cognitive 16) lib/js/next-core/src/server/sentryTunnel.ts:215— sentryTunnel.createSentryTunnelHandler.<returned closure> has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (8 pts), boolean chains 4, ternaries 2, error handling 1, loops 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
UnsavedChangesGuard.UnsavedChangesGuard (cognitive 16) lib/js/next-ui/src/modals/UnsavedChangesGuard.tsx:29— UnsavedChangesGuard.UnsavedChangesGuard has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8, boolean chains 7, ternaries 1. None of this is in the body itself: all 16 points belong to 8 function literals inside it that branch (lines 62, 104, 45, …). 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.
definition.normalizeValues (cognitive 16) REDACTED:427— definition.normalizeValues has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (11 pts), ternaries 2 (4 pts), loops 1 (nesting depth added 8). Of this number, 12 points are the body's own statements and 4 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FileSelectionStep.UploadConstraints (cognitive 16) uploader/client/src/features/upload/FileSelectionStep.tsx:261— FileSelectionStep.UploadConstraints has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 8 (10 pts), boolean chains 5, if/else 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
Change coupling: AssetInputMapper.php ↔ AssetOutput.php databox/api/src/Api/Mapper/Input/AssetInputMapper.php:1— `databox/api/src/Api/Mapper/Input/AssetInputMapper.php` and `databox/api/src/Api/Model/Output/AssetOutput.php` change together 55% of the time (6 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `9fbad4ae` Revert "PS-807 Story asset (#576)" (#581) (at that commit the file was still `databox/api/src/Api/InputTransformer/AssetInputTransformer.php`); `fafc86a2` PS-807 Story asset (#576) (at that commit the file was still `databox/api/src/Api/InputTransformer/AssetInputTransformer.php`); `72875988` squash of PS-807_story-asset, rebased form master ; WIP review not ap… (at that commit the file was still `databox/api/src/Api/InputTransformer/AssetInputTransformer.php`) — run `git show` on any of them.
D4 · Code Duplication· Near-duplicate member family (7 members, 16 shared lines) · ×1
Near-duplicate member family (7 members, 16 shared lines) databox/api/src/Elasticsearch/AQL/AQLGrammar.php:34— databox/api/src/Elasticsearch/AQL/AQLGrammar.php:34-80 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:108-154 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:297-322 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1277-1324 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1412-1484 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1516-1592 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1625-1701 — These 7 members are variants of one another: a block of 16 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 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· Near-duplicate member family (7 members, 9 shared lines) · ×1
Near-duplicate member family (7 members, 9 shared lines) databox/api/src/Elasticsearch/AQL/AQLGrammar.php:34— databox/api/src/Elasticsearch/AQL/AQLGrammar.php:34-80 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:108-154 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:263-282 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:297-322 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:528-713 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:958-1014 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1277-1324 — These 7 members are variants of one another: a block of 9 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 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· Near-duplicate member family (6 members, 15 shared lines) · ×1
Near-duplicate member family (6 members, 15 shared lines) databox/api/src/Elasticsearch/AQL/AQLGrammar.php:183— databox/api/src/Elasticsearch/AQL/AQLGrammar.php:183-252 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:782-844 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:862-939 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1141-1211 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1412-1484 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1734-1783 — These 6 members are variants of one another: a block of 15 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
D4 · Code Duplication· Near-duplicate member family (5 members, 22 shared lines) · ×1
Near-duplicate member family (5 members, 22 shared lines) databox/api/src/Elasticsearch/AQL/AQLGrammar.php:34— databox/api/src/Elasticsearch/AQL/AQLGrammar.php:34-80 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:108-154 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1141-1211 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1516-1592 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1625-1701 — These 5 members are variants of one another: a block of 22 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 5 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 5 times.
D4 · Code Duplication· Near-duplicate member family (5 members, 20 shared lines) · ×1
Near-duplicate member family (5 members, 20 shared lines) databox/api/src/Elasticsearch/AQL/AQLGrammar.php:34— databox/api/src/Elasticsearch/AQL/AQLGrammar.php:34-80 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:108-154 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1516-1592 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1625-1701 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1986-2016 — These 5 members are variants of one another: a block of 20 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 5 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 5 times.
D4 · Code Duplication· Edited copy of a member (57 corresponding lines) · ×1
Edited copy of a member (57 corresponding lines) databox/api/src/Api/Model/Input/ProfileItemInput.php:59— databox/api/src/Api/Model/Input/ProfileItemInput.php:59-115 | databox/api/src/Entity/Profile/ProfileItem.php:429-493 — These two members are one piece of code written twice and then edited apart: 57 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (40 corresponding lines) · ×1
Edited copy of a member (40 corresponding lines) databox/api/src/Doctrine/Delete/CollectionDelete.php:36— databox/api/src/Doctrine/Delete/CollectionDelete.php:36-75 | databox/api/src/Doctrine/Delete/WorkspaceDelete.php:55-94 — These two members are one piece of code written twice and then edited apart: 40 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (28 corresponding lines) · ×1
Edited copy of a member (28 corresponding lines) databox/api/src/Api/Filter/ExactSearchFilter.php:53— databox/api/src/Api/Filter/ExactSearchFilter.php:53-80 | uploader/api/src/Api/Filter/ExactSearchFilter.php:45-76 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (47 corresponding lines) · ×1
Edited copy of a member (47 corresponding lines) databox/api/src/Repository/Core/AttributeDefinitionRepository.php:42— databox/api/src/Repository/Core/AttributeDefinitionRepository.php:42-88 | databox/api/src/Repository/Core/RenditionDefinitionRepository.php:37-98 — These two members are one piece of code written twice and then edited apart: 47 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (33 corresponding lines) · ×1
Edited copy of a member (33 corresponding lines) databox/api/src/Automation/Action/AddToCollectionAction.php:46— databox/api/src/Automation/Action/AddToCollectionAction.php:46-84 | databox/api/src/Automation/Action/MoveToCollectionAction.php:49-81 — These two members are one piece of code written twice and then edited apart: 33 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (42 corresponding lines) · ×1
Edited copy of a member (42 corresponding lines) databox/api/src/Consumer/Handler/Collection/CollectionsMoveToTrashHandler.php:26— databox/api/src/Consumer/Handler/Collection/CollectionsMoveToTrashHandler.php:26-68 | databox/api/src/Consumer/Handler/Collection/CollectionsRestoreHandler.php:26-67 — These two members are one piece of code written twice and then edited apart: 42 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 21+ corresponding lines) · ×1
Edited copies of one member (4 members, 21+ corresponding lines) databox/api/src/Security/Voter/AssetDataTemplateVoter.php:33— databox/api/src/Security/Voter/AssetDataTemplateVoter.php:33-54 | databox/api/src/Security/Voter/PageVoter.php:33-53 | databox/api/src/Security/Voter/ProfileVoter.php:39-60 | databox/api/src/Security/Voter/SavedSearchVoter.php:40-61 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 21 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (32 corresponding lines) · ×1
Edited copy of a member (32 corresponding lines) databox/api/src/Service/Asset/RenditionBuildHashManager.php:67— databox/api/src/Service/Asset/RenditionBuildHashManager.php:67-103 | databox/api/src/Service/Asset/RenditionBuildHashManager.php:108-139 — These two members are one piece of code written twice and then edited apart: 32 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (36 corresponding lines) · ×1
Edited copy of a member (36 corresponding lines) databox/api/src/Api/Mapper/Input/AttributePolicyInputMapper.php:21— databox/api/src/Api/Mapper/Input/AttributePolicyInputMapper.php:21-67 | databox/api/src/Api/Mapper/Input/TagInputMapper.php:21-56 — These two members are one piece of code written twice and then edited apart: 36 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (19 corresponding lines) · ×1
Edited copy of a member (19 corresponding lines) databox/api/src/Border/FileAnalyzer.php:68— databox/api/src/Border/FileAnalyzer.php:68-86 | databox/api/src/Border/FileAnalyzer.php:106-132 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (27 corresponding lines) · ×1
Edited copy of a member (27 corresponding lines) expose/api/src/Controller/PostDownloadAssetViaEmailAction.php:26— expose/api/src/Controller/PostDownloadAssetViaEmailAction.php:26-52 | expose/api/src/Controller/PostDownloadSubDefViaEmailAction.php:26-55 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (24 corresponding lines) · ×1
Edited copy of a member (24 corresponding lines) databox/api/src/Api/Mapper/Input/AttributeInputMapper.php:27— databox/api/src/Api/Mapper/Input/AttributeInputMapper.php:27-52 | databox/api/src/Api/Mapper/Input/TemplateAttributeInputMapper.php:26-49 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 12+ corresponding lines) · ×1
Edited copies of one member (3 members, 12+ corresponding lines) databox/api/src/Elasticsearch/AQL/AQLGrammar.php:12— databox/api/src/Elasticsearch/AQL/AQLGrammar.php:12-23 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:367-378 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1494-1505 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 17+ corresponding lines) · ×1
Edited copies of one member (4 members, 17+ corresponding lines) databox/api/src/Service/Workspace/Template/Section/AlternateUrlSection.php:31— databox/api/src/Service/Workspace/Template/Section/AlternateUrlSection.php:31-47 | databox/api/src/Service/Workspace/Template/Section/RenditionPolicySection.php:34-52 | databox/api/src/Service/Workspace/Template/Section/TagSection.php:34-52 | databox/api/src/Service/Workspace/Template/Section/WorkspaceEnvSection.php:31-47 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 17 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (21 corresponding lines) · ×1
Edited copy of a member (21 corresponding lines) databox/api/src/Api/Mapper/Input/WorkspaceEnvInputMapper.php:20— databox/api/src/Api/Mapper/Input/WorkspaceEnvInputMapper.php:20-40 | databox/api/src/Api/Mapper/Input/WorkspaceSecretInputMapper.php:20-41 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 10+ corresponding lines) · ×1
Edited copies of one member (3 members, 10+ corresponding lines) databox/api/src/Service/Asset/StoryContactSheetInputResolver.php:91— databox/api/src/Service/Asset/StoryContactSheetInputResolver.php:91-100 | databox/api/src/Service/Storage/RenditionManager.php:238-252 | databox/api/src/Service/Storage/RenditionManager.php:260-273 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 21+ corresponding lines) · ×1
Edited copies of one member (3 members, 21+ corresponding lines) databox/api/src/Repository/Page/PageRepository.php:24— databox/api/src/Repository/Page/PageRepository.php:24-44 | databox/api/src/Repository/Profile/ProfileRepository.php:89-110 | databox/api/src/Repository/SavedSearch/SavedSearchRepository.php:25-46 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 21 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 8+ corresponding lines) · ×1
Edited copies of one member (4 members, 8+ corresponding lines) databox/api/src/Controller/Admin/AttributeCrudController.php:47— databox/api/src/Controller/Admin/AttributeCrudController.php:47-60 | databox/api/src/Controller/Admin/FileCrudController.php:52-59 | expose/api/src/Controller/Admin/AssetCrudController.php:45-52 | lib/php/admin-bundle/Controller/MultipartUploadCrudController.php:42-49 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (6 members, 7+ corresponding lines) · ×1
Edited copies of one member (6 members, 7+ corresponding lines) databox/api/src/Controller/Admin/AssetPolicyCrudController.php:53— databox/api/src/Controller/Admin/AssetPolicyCrudController.php:53-59 | databox/api/src/Controller/Admin/AttributeEntityCrudController.php:40-49 | databox/api/src/Controller/Admin/OperationTaskCrudController.php:42-51 | databox/api/src/Controller/Admin/PageCrudController.php:49-56 | databox/api/src/Controller/Admin/ProfileCrudController.php:51-57 | databox/api/src/Controller/Admin/SavedSearchCrudController.php:50-56 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 9+ corresponding lines) · ×1
Edited copies of one member (3 members, 9+ corresponding lines) databox/api/src/Controller/Admin/AttributeFilterRuleCrudController.php:56— databox/api/src/Controller/Admin/AttributeFilterRuleCrudController.php:56-66 | databox/api/src/Controller/Admin/WorkspaceEnvCrudController.php:45-53 | databox/api/src/Controller/Admin/WorkspaceSecretCrudController.php:46-57 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (5 members, 6+ corresponding lines) · ×1
Edited copies of one member (5 members, 6+ corresponding lines) databox/api/src/Controller/Admin/AttributeDefinitionCrudController.php:42— databox/api/src/Controller/Admin/AttributeDefinitionCrudController.php:42-47 | databox/api/src/Controller/Admin/CollectionCrudController.php:53-58 | databox/api/src/Controller/Admin/ProfileItemCrudController.php:29-34 | databox/api/src/Controller/Admin/RenditionDefinitionCrudController.php:36-41 | databox/api/src/Controller/Admin/RenditionPolicyCrudController.php:32-37 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 6+ corresponding lines) · ×1
Edited copies of one member (3 members, 6+ corresponding lines) databox/api/src/Controller/Admin/AssetCrudController.php:97— databox/api/src/Controller/Admin/AssetCrudController.php:97-102 | expose/api/src/Controller/Admin/SubDefinitionCrudController.php:43-48 | uploader/api/src/Controller/Admin/AssetCrudController.php:49-55 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 1+ corresponding lines) · ×1
Edited copies of one member (3 members, 1+ corresponding lines) databox/api/src/Security/Voter/AssetRenditionVoter.php:40— databox/api/src/Security/Voter/AssetRenditionVoter.php:40-40 | databox/api/src/Security/Voter/CollectionVoter.php:44-44 | databox/api/src/Security/Voter/WorkspaceVoter.php:61-61 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 1 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 5+ corresponding lines) · ×1
Edited copies of one member (3 members, 5+ corresponding lines) databox/api/src/Automation/AutomationActionRegistry.php:29— databox/api/src/Automation/AutomationActionRegistry.php:29-33 | databox/api/src/Border/FileAnalyzerRegistry.php:31-36 | databox/api/src/OperationTask/OperationTaskRegistry.php:18-22 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 5 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 3+ corresponding lines) · ×1
Edited copies of one member (3 members, 3+ corresponding lines) databox/api/src/Controller/Admin/DashboardController.php:28— databox/api/src/Controller/Admin/DashboardController.php:28-33 | expose/api/src/Controller/Admin/DashboardController.php:20-22 | uploader/api/src/Controller/Admin/DashboardController.php:20-22 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 3 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 3+ corresponding lines) · ×1
Edited copies of one member (4 members, 3+ corresponding lines) databox/api/src/Controller/Admin/AssetRenditionCrudController.php:37— databox/api/src/Controller/Admin/AssetRenditionCrudController.php:37-40 | databox/api/src/Controller/Admin/IntegrationDataCrudController.php:44-47 | lib/php/admin-bundle/Controller/MultipartUploadCrudController.php:28-30 | uploader/api/src/Controller/Admin/AssetCrudController.php:32-34 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 3 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
Duplicated block (64 lines × 2) expose/api/src/Command/YamlToApiResourceCommand.php:100— expose/api/src/Command/YamlToApiResourceCommand.php:100-163 | uploader/api/src/Command/YamlToApiResourceCommand.php:100-163 — before extracting anything, compare `expose/api/src/Command/YamlToApiResourceCommand.php` and `uploader/api/src/Command/YamlToApiResourceCommand.php` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 152 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 `expose/api/src/Command/YamlToApiResourceCommand.php:100` 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 (45 lines × 2) databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1526— databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1526-1570 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1635-1679 — 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 `databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1526` 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 (9–26 lines × 21) databox/api/migrations/Version20250507124452.php:23— databox/api/migrations/Version20250507124452.php:23-48 | databox/api/migrations/Version20250527150940.php:23-48 | databox/api/migrations/Version20250527150940.php:103-128 | databox/api/migrations/Version20250618134613.php:23-48 | databox/api/migrations/Version20250618134613.php:55-80 | databox/api/migrations/Version20250618142033.php:23-48 | databox/api/migrations/Version20250618142033.php:67-92 | databox/api/migrations/Version20260520171528.php:19-28 | databox/api/migrations/Version20260610134844.php:23-47 | databox/api/migrations/Version20260805170000.php:19-27 | databox/api/migrations/Version20260903080000.php:19-27 | databox/api/migrations/Version20260907230000.php:19-29 | databox/api/migrations/Version20260909160000.php:19-32 | databox/api/migrations/Version20260909160000.php:63-80 | databox/api/migrations/Version20260923120000.php:29-40 | databox/api/migrations/Version20261022130000.php:19-27 | databox/api/migrations/Version20261022130000.php:45-54 | expose/api/migrations/Version20200512114816.php:26-34 | expose/api/migrations/Version20261006120001.php:19-27 | uploader/api/migrations/Version20261006120002.php:19-27 | uploader/api/migrations/Version20261111150000.php:19-28 — there are 21 copies across 16 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 21 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `databox/api/migrations/Version20250507124452.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. 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 after the matched lines, `databox/api/migrations/Version20250527150940.php:50` calls `addSql` and `databox/api/migrations/Version20250507124452.php:48` 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 (24–25 lines × 2) databox/api/src/Api/Filter/ExactSearchFilter.php:57— databox/api/src/Api/Filter/ExactSearchFilter.php:57-80 | uploader/api/src/Api/Filter/ExactSearchFilter.php:52-76 — before extracting anything, compare `databox/api/src/Api/Filter/ExactSearchFilter.php` and `uploader/api/src/Api/Filter/ExactSearchFilter.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 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 `uploader/api/src/Api/Filter/ExactSearchFilter.php:52` 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 (23 lines × 3) lib/php/rendition-factory/src/Transformer/Video/AudioTransformer.php:97— lib/php/rendition-factory/src/Transformer/Video/AudioTransformer.php:97-119 | lib/php/rendition-factory/src/Transformer/Video/VideoTransformer.php:134-156 | lib/php/rendition-factory/src/Transformer/Video/VideoTransformer.php:247-269 — before extracting anything, compare `lib/php/rendition-factory/src/Transformer/Video/AudioTransformer.php` and `lib/php/rendition-factory/src/Transformer/Video/VideoTransformer.php` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 64 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (20–21 lines × 2) expose/api/src/Controller/PostDownloadAssetViaEmailAction.php:33— expose/api/src/Controller/PostDownloadAssetViaEmailAction.php:33-52 | expose/api/src/Controller/PostDownloadSubDefViaEmailAction.php:35-55 — 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, `expose/api/src/Controller/PostDownloadSubDefViaEmailAction.php:33` calls `setSubDefinition` and `expose/api/src/Controller/PostDownloadAssetViaEmailAction.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 (11–17 lines × 2) databox/api/src/Consumer/Handler/Search/AttributeEntityDeleteHandler.php:39— databox/api/src/Consumer/Handler/Search/AttributeEntityDeleteHandler.php:39-55 | databox/api/src/Consumer/Handler/Search/AttributeEntityListClearHandler.php:42-52 — 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 `databox/api/src/Consumer/Handler/Search/AttributeEntityDeleteHandler.php:39` 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 × 3) databox/api/src/Integration/Happyscribe/Consumer/ExportTranscriptionMessageHandler.php:49— databox/api/src/Integration/Happyscribe/Consumer/ExportTranscriptionMessageHandler.php:49-64 | databox/api/src/Integration/Happyscribe/Consumer/TranscriptionHappyscribeMessageHandler.php:48-63 | databox/api/src/Integration/Happyscribe/Consumer/TranslateTranscriptionMessageHandler.php:37-52 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `databox/api/src/Integration/Happyscribe/Consumer/ExportTranscriptionMessageHandler.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 (54 lines × 2) expose/api/src/Command/YamlToApiResourceCommand.php:41— expose/api/src/Command/YamlToApiResourceCommand.php:41-94 | uploader/api/src/Command/YamlToApiResourceCommand.php:41-94 — before extracting anything, compare `expose/api/src/Command/YamlToApiResourceCommand.php` and `uploader/api/src/Command/YamlToApiResourceCommand.php` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 152 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 `expose/api/src/Command/YamlToApiResourceCommand.php:41` 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 (15 lines × 4) databox/api/src/Elasticsearch/AQL/AQLGrammar.php:65— databox/api/src/Elasticsearch/AQL/AQLGrammar.php:65-79 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:139-153 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1577-1591 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1686-1700 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `databox/api/src/Elasticsearch/AQL/AQLGrammar.php:65` 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 (14 lines × 5) databox/api/src/Elasticsearch/AQL/AQLGrammar.php:546— databox/api/src/Elasticsearch/AQL/AQLGrammar.php:546-559 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:568-581 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:590-603 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:612-625 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:634-647 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `databox/api/src/Elasticsearch/AQL/AQLGrammar.php:546` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (13 lines × 6) databox/api/src/Elasticsearch/AQL/AQLGrammar.php:63— databox/api/src/Elasticsearch/AQL/AQLGrammar.php:63-75 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:137-149 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1188-1200 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1461-1473 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1575-1587 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1684-1696 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `databox/api/src/Elasticsearch/AQL/AQLGrammar.php:63` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11–13 lines × 4) databox/api/src/Elasticsearch/AQL/AQLGrammar.php:238— databox/api/src/Elasticsearch/AQL/AQLGrammar.php:238-250 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:465-477 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:677-687 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1881-1893 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `databox/api/src/Elasticsearch/AQL/AQLGrammar.php:238` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12–13 lines × 2) lib/php/rendition-factory/src/Transformer/Video/AudioTransformer.php:71— lib/php/rendition-factory/src/Transformer/Video/AudioTransformer.php:71-82 | lib/php/rendition-factory/src/Transformer/Video/VideoTransformer.php:107-119 — before extracting anything, compare `lib/php/rendition-factory/src/Transformer/Video/AudioTransformer.php` and `lib/php/rendition-factory/src/Transformer/Video/VideoTransformer.php` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 64 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/php/rendition-factory/src/Transformer/Video/AudioTransformer.php:71` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 4) databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1813— databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1813-1824 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1827-1838 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1841-1852 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1855-1866 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1813` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11–12 lines × 2) lib/php/storage-bundle/Cdn/CloudFrontUrlGenerator.php:53— lib/php/storage-bundle/Cdn/CloudFrontUrlGenerator.php:53-63 | lib/php/storage-bundle/Storage/UrlSigner.php:46-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 (11 lines × 7) databox/api/src/Elasticsearch/AQL/AQLGrammar.php:62— databox/api/src/Elasticsearch/AQL/AQLGrammar.php:62-72 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:136-146 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1187-1197 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1308-1318 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1460-1470 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1574-1584 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1683-1693 — all 7 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `databox/api/src/Elasticsearch/AQL/AQLGrammar.php:62` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 6) databox/api/src/Elasticsearch/AQL/AQLGrammar.php:211— databox/api/src/Elasticsearch/AQL/AQLGrammar.php:211-221 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:546-556 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:568-578 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:590-600 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:612-622 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:634-644 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `databox/api/src/Elasticsearch/AQL/AQLGrammar.php:211` 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 after the matched lines, `databox/api/src/Elasticsearch/AQL/AQLGrammar.php:647` calls `whitespace` and `databox/api/src/Elasticsearch/AQL/AQLGrammar.php:222` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (11 lines × 5) databox/api/src/Elasticsearch/AQL/AQLGrammar.php:70— databox/api/src/Elasticsearch/AQL/AQLGrammar.php:70-80 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:144-154 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1582-1592 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1691-1701 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:2006-2016 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `databox/api/src/Elasticsearch/AQL/AQLGrammar.php:70` 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 (9–11 lines × 5) databox/api/src/Elasticsearch/AQL/AQLGrammar.php:216— databox/api/src/Elasticsearch/AQL/AQLGrammar.php:216-224 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1815-1825 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1829-1839 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1843-1853 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1857-1867 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `databox/api/src/Elasticsearch/AQL/AQLGrammar.php:216` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9–11 lines × 2) expose/api/src/Controller/DownloadPublicationArchiveAction.php:54— expose/api/src/Controller/DownloadPublicationArchiveAction.php:54-62 | expose/api/src/Controller/PostPublicationArchiveRequestAction.php:39-49 — 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 (10 lines × 7) databox/api/src/Elasticsearch/AQL/AQLGrammar.php:543— databox/api/src/Elasticsearch/AQL/AQLGrammar.php:543-552 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:565-574 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:587-596 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:609-618 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:631-640 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:652-661 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:669-678 — all 7 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `databox/api/src/Elasticsearch/AQL/AQLGrammar.php:543` 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 (3–10 lines × 6) databox/api/src/Elasticsearch/AQL/AQLGrammar.php:43— databox/api/src/Elasticsearch/AQL/AQLGrammar.php:43-52 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:117-126 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1167-1176 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1348-1350 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1525-1532 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1634-1641 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `databox/api/src/Elasticsearch/AQL/AQLGrammar.php:43` 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 lines × 3) databox/api/src/Elasticsearch/AQL/AQLGrammar.php:388— databox/api/src/Elasticsearch/AQL/AQLGrammar.php:388-397 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1734-1743 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1802-1811 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `databox/api/src/Elasticsearch/AQL/AQLGrammar.php:388` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 23) databox/api/migrations/Version20250507124452.php:25— databox/api/migrations/Version20250507124452.php:25-49 | databox/api/migrations/Version20250527150940.php:25-49 | databox/api/migrations/Version20250527150940.php:105-129 | databox/api/migrations/Version20250618134613.php:25-49 | databox/api/migrations/Version20250618134613.php:57-81 | databox/api/migrations/Version20250618142033.php:25-49 | databox/api/migrations/Version20250618142033.php:69-93 | databox/api/migrations/Version20260316144506.php:21-30 | databox/api/migrations/Version20260520171528.php:20-29 | databox/api/migrations/Version20260610134844.php:24-47 | databox/api/migrations/Version20260805170000.php:20-28 | databox/api/migrations/Version20260903080000.php:20-28 | databox/api/migrations/Version20260903080000.php:60-68 | databox/api/migrations/Version20260907230000.php:20-30 | databox/api/migrations/Version20260909160000.php:20-43 | databox/api/migrations/Version20260909160000.php:64-81 | databox/api/migrations/Version20260923120000.php:30-44 | databox/api/migrations/Version20261022130000.php:20-28 | databox/api/migrations/Version20261022130000.php:46-55 | expose/api/migrations/Version20200512114816.php:27-35 | expose/api/migrations/Version20261006120001.php:20-28 | uploader/api/migrations/Version20261006120002.php:20-28 | uploader/api/migrations/Version20261111150000.php:20-29 — there are 23 copies across 17 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 23 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `databox/api/migrations/Version20250507124452.php:25` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `databox/api/migrations/Version20250618134613.php:52` calls `down` and `databox/api/migrations/Version20260909160000.php:44` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9 lines × 8) databox/api/src/Elasticsearch/AQL/AQLGrammar.php:34— databox/api/src/Elasticsearch/AQL/AQLGrammar.php:34-42 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:108-116 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:297-305 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1277-1285 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1412-1420 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1516-1524 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1625-1633 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1986-1994 — all 8 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `databox/api/src/Elasticsearch/AQL/AQLGrammar.php:34` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 5) databox/api/src/Elasticsearch/AQL/AQLGrammar.php:244— databox/api/src/Elasticsearch/AQL/AQLGrammar.php:244-252 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:477-485 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:705-713 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1775-1783 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1905-1913 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `databox/api/src/Elasticsearch/AQL/AQLGrammar.php:244` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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–9 lines × 5) databox/api/src/Elasticsearch/AQL/AQLGrammar.php:276— databox/api/src/Elasticsearch/AQL/AQLGrammar.php:276-282 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:314-322 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1006-1014 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1107-1113 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1257-1263 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `databox/api/src/Elasticsearch/AQL/AQLGrammar.php:276` 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 (19 lines × 4) databox/api/src/Elasticsearch/AQL/AQLGrammar.php:226— databox/api/src/Elasticsearch/AQL/AQLGrammar.php:226-244 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:399-417 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:743-761 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1869-1887 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `databox/api/src/Elasticsearch/AQL/AQLGrammar.php:226` 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, `databox/api/src/Elasticsearch/AQL/AQLGrammar.php:247` calls `setPos` and `databox/api/src/Elasticsearch/AQL/AQLGrammar.php:763` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9 lines × 4) databox/api/src/Elasticsearch/AQL/AQLGrammar.php:836— databox/api/src/Elasticsearch/AQL/AQLGrammar.php:836-844 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:931-939 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1203-1211 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1476-1484 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `databox/api/src/Elasticsearch/AQL/AQLGrammar.php:836` 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 (8 lines × 14) expose/api/migrations/Version20200512114816.php:24— expose/api/migrations/Version20200512114816.php:24-32 | expose/api/migrations/Version20200512114816.php:71-78 | expose/api/migrations/Version20200520055430.php:24-31 | expose/api/migrations/Version20200520091751.php:24-31 | expose/api/migrations/Version20200609184232.php:24-33 | expose/api/migrations/Version20201015082010.php:24-31 | expose/api/migrations/Version20201015082010.php:37-44 | expose/api/migrations/Version20201209130408.php:24-31 | expose/api/migrations/Version20201209130408.php:37-44 | expose/api/migrations/Version20221207170541.php:24-31 | expose/api/migrations/Version20221207170541.php:41-48 | uploader/api/migrations/Version20201210171415.php:34-41 | uploader/api/migrations/Version20220802161731.php:24-31 | uploader/api/migrations/Version20220802161731.php:50-57 — there are 14 copies across 9 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 14 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 after the matched lines, `expose/api/migrations/Version20221207170541.php:31` calls `addSql`, `VARCHAR` and `expose/api/migrations/Version20200520091751.php:31` 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 × 13) databox/api/src/Elasticsearch/AQL/AQLGrammar.php:224— databox/api/src/Elasticsearch/AQL/AQLGrammar.php:224-231 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:234-241 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:397-404 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:407-414 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:741-748 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:751-758 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1743-1750 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1811-1818 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1825-1832 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1839-1846 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1853-1860 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1867-1874 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1877-1884 — all 13 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 (8 lines × 6) databox/api/src/Elasticsearch/AQL/AQLGrammar.php:207— databox/api/src/Elasticsearch/AQL/AQLGrammar.php:207-214 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:835-842 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:930-937 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1202-1209 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1475-1482 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1768-1775 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `databox/api/src/Elasticsearch/AQL/AQLGrammar.php:207` 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 (4–8 lines × 14) databox/api/src/Elasticsearch/AQL/AQLGrammar.php:57— databox/api/src/Elasticsearch/AQL/AQLGrammar.php:57-60 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:131-134 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:271-274 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:309-312 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:346-349 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:533-540 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:555-562 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:577-584 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:599-606 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:621-628 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:987-990 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1001-1004 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1292-1295 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1298-1305 — all 14 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `databox/api/src/Elasticsearch/AQL/AQLGrammar.php:57` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `databox/api/src/Elasticsearch/AQL/AQLGrammar.php:540` calls `packhas` and `databox/api/src/Elasticsearch/AQL/AQLGrammar.php:60` does not — after which the two agree again for 5 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (7–8 lines × 2) databox/api/src/Elasticsearch/AssetPermissionComputer.php:193— databox/api/src/Elasticsearch/AssetPermissionComputer.php:193-200 | databox/api/src/Elasticsearch/AssetPermissionComputer.php:248-254 — 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 `databox/api/src/Elasticsearch/AssetPermissionComputer.php:193` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (6 lines × 17) databox/api/src/Elasticsearch/AQL/AQLGrammar.php:206— databox/api/src/Elasticsearch/AQL/AQLGrammar.php:206-211 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:789-794 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:804-809 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:819-824 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:834-839 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:869-874 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:884-889 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:899-904 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:914-919 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:929-934 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1156-1161 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1176-1181 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1201-1206 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1423-1428 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1449-1454 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1474-1479 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1767-1772 — all 17 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. 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, `databox/api/src/Elasticsearch/AQL/AQLGrammar.php:787` calls `literal` and `databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1175` 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 lines × 13) databox/api/src/Elasticsearch/AQL/AQLGrammar.php:192— databox/api/src/Elasticsearch/AQL/AQLGrammar.php:192-197 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:790-795 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:805-810 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:820-825 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:870-875 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:885-890 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:900-905 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:915-920 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1157-1162 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1177-1182 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1424-1429 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1450-1455 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1753-1758 — all 13 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. 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, `databox/api/src/Elasticsearch/AQL/AQLGrammar.php:787` calls `literal`, `whitespace` and `databox/api/src/Elasticsearch/AQL/AQLGrammar.php:191` 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 (2–6 lines × 12) databox/api/src/Elasticsearch/AQL/AQLGrammar.php:202— databox/api/src/Elasticsearch/AQL/AQLGrammar.php:202-205 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:800-803 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:815-818 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:830-833 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:880-883 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:895-898 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:910-913 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:925-928 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:992-997 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1286-1291 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1421-1422 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1763-1766 — all 12 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. 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 × 19) databox/api/src/Elasticsearch/AQL/AQLGrammar.php:62— databox/api/src/Elasticsearch/AQL/AQLGrammar.php:62-68 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:136-142 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:276-280 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:314-320 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:543-549 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:565-571 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:587-593 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:609-615 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:631-637 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:652-658 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:669-675 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1006-1012 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1107-1111 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1187-1193 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1257-1261 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1308-1314 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1460-1466 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1574-1580 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1683-1689 — all 19 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `databox/api/src/Elasticsearch/AQL/AQLGrammar.php:62` 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 (3–5 lines × 13) databox/api/src/Elasticsearch/AQL/AQLGrammar.php:220— databox/api/src/Elasticsearch/AQL/AQLGrammar.php:220-224 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:348-350 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:393-397 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:737-741 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1087-1091 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1430-1434 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1739-1743 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1807-1811 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1821-1825 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1835-1839 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1849-1853 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1863-1867 | databox/api/src/Elasticsearch/AQL/AQLGrammar.php:1998-2002 — all 13 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. 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 after the matched lines, `databox/api/src/Elasticsearch/AQL/AQLGrammar.php:2002` calls `packread` and `databox/api/src/Elasticsearch/AQL/AQLGrammar.php:350` 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) lib/php/rendition-factory/src/Transformer/Video/AudioTransformer.php:48— lib/php/rendition-factory/src/Transformer/Video/AudioTransformer.php:48-52 | lib/php/rendition-factory/src/Transformer/Video/AudioTransformer.php:55-59 | lib/php/rendition-factory/src/Transformer/Video/VideoTransformer.php:60-64 | lib/php/rendition-factory/src/Transformer/Video/VideoTransformer.php:67-71 — before extracting anything, compare `lib/php/rendition-factory/src/Transformer/Video/AudioTransformer.php` and `lib/php/rendition-factory/src/Transformer/Video/VideoTransformer.php` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 64 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/php/rendition-factory/src/Transformer/Video/AudioTransformer.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 (7 lines × 3) lib/php/rendition-factory/src/Transformer/Video/VideoSummaryTransformerModule.php:140— lib/php/rendition-factory/src/Transformer/Video/VideoSummaryTransformerModule.php:140-146 | lib/php/rendition-factory/src/Transformer/Video/VideoToAnimationTransformerModule.php:140-146 | lib/php/rendition-factory/src/Transformer/Video/VideoToFrameTransformerModule.php:120-126 — before extracting anything, compare `lib/php/rendition-factory/src/Transformer/Video/VideoSummaryTransformerModule.php` and `lib/php/rendition-factory/src/Transformer/Video/VideoToAnimationTransformerModule.php` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 73 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `lib/php/rendition-factory/src/Transformer/Video/VideoSummaryTransformerModule.php:137` calls `getFormat` and `lib/php/rendition-factory/src/Transformer/Video/VideoToAnimationTransformerModule.php:137` 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 (14 lines × 14) databox/api/migrations/Version20211110163225.php:17— databox/api/migrations/Version20211110163225.php:17-32 | databox/api/migrations/Version20211130111708.php:17-32 | databox/api/migrations/Version20220215121926.php:17-32 | databox/api/migrations/Version20220328124926.php:17-32 | databox/api/migrations/Version20230220143020.php:17-32 | databox/api/migrations/Version20241009104832.php:17-32 | databox/api/migrations/Version20250210130752.php:17-30 | databox/api/migrations/Version20250520103201.php:17-42 | databox/api/migrations/Version20250613161540.php:17-42 | databox/api/migrations/Version20260428153126.php:14-28 | databox/api/migrations/Version20260916180000.php:14-27 | expose/api/migrations/Version20230925141126.php:17-32 | uploader/api/migrations/Version20250709095655.php:17-32 | uploader/api/migrations/Version20250728121736.php:17-32 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `databox/api/migrations/Version20211110163225.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 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 (13 lines × 12) databox/api/migrations/Version20211117160351.php:17— databox/api/migrations/Version20211117160351.php:17-31 | databox/api/migrations/Version20211210164044.php:17-31 | databox/api/migrations/Version20220406124752.php:17-31 | databox/api/migrations/Version20230131100045.php:17-31 | databox/api/migrations/Version20230314155537.php:17-31 | databox/api/migrations/Version20240422152450.php:17-31 | databox/api/migrations/Version20250923095101.php:17-39 | databox/api/migrations/Version20251210134458.php:17-31 | databox/api/migrations/Version20251215165129.php:14-28 | databox/api/migrations/Version20260316152513.php:14-27 | databox/api/migrations/Version20260324145622.php:17-71 | expose/api/migrations/Version20240429125910.php:17-29 — before extracting anything, compare `databox/api/migrations/Version20240422152450.php` and `expose/api/migrations/Version20240429125910.php` as WHOLE FILES: 82% 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 `databox/api/migrations/Version20211117160351.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 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 (13 lines × 42) databox/api/migrations/Version20211117162050.php:17— databox/api/migrations/Version20211117162050.php:17-31 | databox/api/migrations/Version20211129103921.php:17-31 | databox/api/migrations/Version20211210162319.php:17-31 | databox/api/migrations/Version20220121134124.php:17-31 | databox/api/migrations/Version20220209091412.php:17-31 | databox/api/migrations/Version20220217104744.php:17-31 | databox/api/migrations/Version20220321105200.php:17-31 | databox/api/migrations/Version20220406112910.php:17-31 | databox/api/migrations/Version20220406114452.php:17-31 | databox/api/migrations/Version20220419085533.php:17-31 | databox/api/migrations/Version20220608095100.php:17-31 | databox/api/migrations/Version20220711093017.php:17-31 | databox/api/migrations/Version20220713144330.php:17-31 | databox/api/migrations/Version20221129133820.php:17-31 | databox/api/migrations/Version20230124162302.php:17-31 | databox/api/migrations/Version20230125114038.php:17-31 | databox/api/migrations/Version20230206140900.php:17-31 | databox/api/migrations/Version20230215153244.php:17-31 | databox/api/migrations/Version20231221125408.php:17-31 | databox/api/migrations/Version20240603153054.php:17-31 | databox/api/migrations/Version20241008094404.php:17-31 | databox/api/migrations/Version20241009133041.php:17-31 | databox/api/migrations/Version20241023151611.php:17-31 | databox/api/migrations/Version20250106104251.php:17-31 | databox/api/migrations/Version20250116084913.php:17-31 | databox/api/migrations/Version20250120202158.php:17-29 | databox/api/migrations/Version20250128114531.php:17-31 | databox/api/migrations/Version20250618134458.php:17-37 | databox/api/migrations/Version20251006152544.php:17-31 | databox/api/migrations/Version20260210152654.php:17-31 | databox/api/migrations/Version20260316113320.php:17-31 | databox/api/migrations/Version20260428164220.php:17-29 | databox/api/migrations/Version20260602095331.php:14-26 | databox/api/migrations/Version20260609120204.php:14-26 | databox/api/migrations/Version20260616125142.php:14-26 | databox/api/migrations/Version20261105022500.php:14-26 | databox/api/migrations/Version20261109140000.php:14-26 | databox/api/migrations/Version20261112170000.php:14-26 | expose/api/migrations/Version20260528082329.php:17-30 | expose/api/migrations/Version20260803170820.php:17-31 | uploader/api/migrations/Version20260528082406.php:17-31 | uploader/api/migrations/Version20260803170610.php:17-31 — before extracting anything, compare `expose/api/migrations/Version20260528082329.php` and `uploader/api/migrations/Version20260528082406.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 `databox/api/migrations/Version20211117162050.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 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 (12 lines × 13) databox/api/migrations/Version20211124135744.php:17— databox/api/migrations/Version20211124135744.php:17-28 | databox/api/migrations/Version20220711092639.php:17-39 | databox/api/migrations/Version20220831152649.php:17-34 | databox/api/migrations/Version20230503085950.php:17-35 | databox/api/migrations/Version20230920121714.php:17-35 | databox/api/migrations/Version20250409113833.php:17-60 | databox/api/migrations/Version20250429162120.php:14-55 | databox/api/migrations/Version20250930150503.php:17-35 | databox/api/migrations/Version20260713140456.php:14-37 | databox/api/migrations/Version20260923170509.php:17-39 | databox/api/migrations/Version20261013120000.php:14-32 | expose/api/migrations/Version20260923170510.php:18-35 | uploader/api/migrations/Version20260923170511.php:18-35 — before extracting anything, compare `expose/api/migrations/Version20260923170510.php` and `uploader/api/migrations/Version20260923170511.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 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 `databox/api/migrations/Version20211124135744.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 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 (14 lines × 8) databox/api/migrations/Version20230605141142.php:17— databox/api/migrations/Version20230605141142.php:17-32 | databox/api/migrations/Version20250218171621.php:14-27 | databox/api/migrations/Version20250619131954.php:17-32 | databox/api/migrations/Version20251125103125.php:17-32 | databox/api/migrations/Version20260610114413.php:14-27 | databox/api/migrations/Version20260623170437.php:17-31 | databox/api/migrations/Version20260715152916.php:14-27 | expose/api/migrations/Version20261111140000.php:14-27 — 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 `databox/api/migrations/Version20230605141142.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 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) databox/api/migrations/Version20240227095941.php:17— databox/api/migrations/Version20240227095941.php:17-35 | databox/api/migrations/Version20260622153228.php:17-34 | databox/api/migrations/Version20260831135811.php:14-30 | expose/api/migrations/Version20260831135814.php:14-30 | uploader/api/migrations/Version20260831135816.php:14-30 — before extracting anything, compare `databox/api/migrations/Version20260831135811.php` and `expose/api/migrations/Version20260831135814.php` as WHOLE FILES: 94% 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 `databox/api/migrations/Version20240227095941.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 (48 lines × 3) databox/api/migrations/Version20260803170229.php:17— databox/api/migrations/Version20260803170229.php:17-64 | expose/api/migrations/Version20260801143915.php:17-64 | uploader/api/migrations/Version20260801143813.php:17-64 — before extracting anything, compare `databox/api/migrations/Version20260803170229.php` and `expose/api/migrations/Version20260801143915.php` as WHOLE FILES: 94% 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 `databox/api/migrations/Version20260803170229.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 (21 lines × 3) databox/api/migrations/Version20260831160000.php:14— databox/api/migrations/Version20260831160000.php:14-34 | expose/api/migrations/Version20260831160001.php:14-34 | uploader/api/migrations/Version20260831160002.php:14-34 — before extracting anything, compare `databox/api/migrations/Version20260831160000.php` and `expose/api/migrations/Version20260831160001.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. 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 `databox/api/migrations/Version20260831160000.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 (31 lines × 2) databox/api/src/Api/Model/Output/ShareAlternateUrlOutput.php:33— databox/api/src/Api/Model/Output/ShareAlternateUrlOutput.php:33-75 | databox/api/src/Api/Model/Output/ShareAttachmentOutput.php:25-55 — 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 `databox/api/src/Api/Model/Output/ShareAlternateUrlOutput.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.
Duplicated block (52 lines × 2) databox/api/src/Entity/Core/AttributePolicy.php:117— databox/api/src/Entity/Core/AttributePolicy.php:117-178 | databox/api/src/Entity/Core/RenditionPolicy.php:122-173 — 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 `databox/api/src/Entity/Core/AttributePolicy.php:117` 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 × 20) expose/api/migrations/Version20200513100756.php:18— expose/api/migrations/Version20200513100756.php:18-37 | expose/api/migrations/Version20200519123453.php:18-37 | expose/api/migrations/Version20200527084226.php:18-37 | expose/api/migrations/Version20200527121619.php:18-37 | expose/api/migrations/Version20201112133143.php:18-37 | expose/api/migrations/Version20210518161346.php:18-37 | expose/api/migrations/Version20210518162600.php:18-37 | expose/api/migrations/Version20210609180500.php:18-37 | expose/api/migrations/Version20220711092924.php:18-37 | expose/api/migrations/Version20230426152120.php:18-37 | uploader/api/migrations/Version20200506111259.php:18-37 | uploader/api/migrations/Version20210726161245.php:18-37 | uploader/api/migrations/Version20210726164053.php:18-37 | uploader/api/migrations/Version20210726164842.php:18-37 | uploader/api/migrations/Version20220711093044.php:18-37 | uploader/api/migrations/Version20220803151028.php:18-37 | uploader/api/migrations/Version20220808123353.php:18-37 | uploader/api/migrations/Version20220809072827.php:18-37 | uploader/api/migrations/Version20220809144818.php:18-37 | uploader/api/migrations/Version20220810151022.php:18-37 — before extracting anything, compare `expose/api/migrations/Version20220711092924.php` and `uploader/api/migrations/Version20210726164842.php` as WHOLE FILES: 82% 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 `expose/api/migrations/Version20200513100756.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 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 × 14) expose/api/migrations/Version20200514140554.php:18— expose/api/migrations/Version20200514140554.php:18-35 | expose/api/migrations/Version20200520093115.php:18-35 | expose/api/migrations/Version20200527092118.php:18-35 | expose/api/migrations/Version20200611173711.php:18-35 | expose/api/migrations/Version20200618081923.php:18-35 | expose/api/migrations/Version20210416124710.php:18-35 | expose/api/migrations/Version20210601144644.php:18-35 | uploader/api/migrations/Version20210617203448.php:18-35 | uploader/api/migrations/Version20210726161029.php:18-35 | uploader/api/migrations/Version20220502153533.php:18-35 | uploader/api/migrations/Version20220803131440.php:18-35 | uploader/api/migrations/Version20220809143311.php:18-35 | uploader/api/migrations/Version20221027194021.php:18-35 | uploader/api/migrations/Version20230206145209.php:18-35 — before extracting anything, compare `expose/api/migrations/Version20200514140554.php` and `expose/api/migrations/Version20200520093115.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 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. Read the line range as the matched WINDOW rather than a finished unit: at `expose/api/migrations/Version20200514140554.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 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 × 3) expose/api/migrations/Version20210727120409.php:18— expose/api/migrations/Version20210727120409.php:18-36 | uploader/api/migrations/Version20210726152112.php:18-36 | uploader/api/migrations/Version20221027194101.php:18-36 — before extracting anything, compare `expose/api/migrations/Version20210727120409.php` and `uploader/api/migrations/Version20210726152112.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 `expose/api/migrations/Version20210727120409.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 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 × 20) expose/api/migrations/Version20200514140554.php:18— expose/api/migrations/Version20200514140554.php:18-35 | expose/api/migrations/Version20200520093115.php:18-35 | expose/api/migrations/Version20200527092118.php:18-35 | expose/api/migrations/Version20200611173711.php:18-35 | expose/api/migrations/Version20200618081923.php:18-35 | expose/api/migrations/Version20210416124710.php:18-35 | expose/api/migrations/Version20210601144644.php:18-35 | expose/api/migrations/Version20210727120409.php:18-36 | expose/api/migrations/Version20210811113825.php:18-33 | expose/api/migrations/Version20210811114618.php:18-33 | expose/api/migrations/Version20210908102624.php:18-27 | uploader/api/migrations/Version20210617203448.php:18-35 | uploader/api/migrations/Version20210726152112.php:18-36 | uploader/api/migrations/Version20210726161029.php:18-35 | uploader/api/migrations/Version20220502153533.php:18-35 | uploader/api/migrations/Version20220803131440.php:18-35 | uploader/api/migrations/Version20220809143311.php:18-35 | uploader/api/migrations/Version20221027194021.php:18-35 | uploader/api/migrations/Version20221027194101.php:18-36 | uploader/api/migrations/Version20230206145209.php:18-35 — before extracting anything, compare `expose/api/migrations/Version20200514140554.php` and `expose/api/migrations/Version20200520093115.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 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. Read the line range as the matched WINDOW rather than a finished unit: at `expose/api/migrations/Version20200514140554.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 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 × 2) expose/api/migrations/Version20260923170510.php:18— expose/api/migrations/Version20260923170510.php:18-35 | uploader/api/migrations/Version20260923170511.php:18-35 — before extracting anything, compare `expose/api/migrations/Version20260923170510.php` and `uploader/api/migrations/Version20260923170511.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 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 `expose/api/migrations/Version20260923170510.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 (26 lines × 4) lib/php/rendition-factory/src/Transformer/Video/Format/MkvFormat.php:19— lib/php/rendition-factory/src/Transformer/Video/Format/MkvFormat.php:19-44 | lib/php/rendition-factory/src/Transformer/Video/Format/Mpeg4Format.php:19-44 | lib/php/rendition-factory/src/Transformer/Video/Format/MpegFormat.php:19-44 | lib/php/rendition-factory/src/Transformer/Video/Format/QuicktimeFormat.php:19-44 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 4 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `lib/php/rendition-factory/src/Transformer/Video/Format/MkvFormat.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 (5 lines × 3) databox/api/src/Controller/Admin/AssetExportCrudController.php:33— databox/api/src/Controller/Admin/AssetExportCrudController.php:33-37 | databox/api/src/Controller/Admin/AuditLogCrudController.php:39-43 | lib/php/track-bundle/src/Controller/ChangeLogCrudController.php:32-36 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. 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) databox/api/src/Controller/Admin/PageCrudController.php:38— databox/api/src/Controller/Admin/PageCrudController.php:38-43 | databox/api/src/Controller/Admin/ProfileCrudController.php:40-45 | databox/api/src/Controller/Admin/SavedSearchCrudController.php:39-44 | databox/api/src/Controller/Admin/WorkspaceTemplateCrudController.php:28-33 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 4 call sites, so a change lands once.
Duplicated block (9 lines × 7) lib/php/rendition-factory/src/Transformer/Document/DocumentToPdfTransformerModule.php:37— lib/php/rendition-factory/src/Transformer/Document/DocumentToPdfTransformerModule.php:37-50 | lib/php/rendition-factory/src/Transformer/Document/PdfToImageTransformerModule.php:30-38 | lib/php/rendition-factory/src/Transformer/DownloadTransformerModule.php:29-37 | lib/php/rendition-factory/src/Transformer/ExtractEmbeddedPreviewTransformerModule.php:32-40 | lib/php/rendition-factory/src/Transformer/Image/ContactSheet/ContactSheetGeneratorModule.php:54-64 | lib/php/rendition-factory/src/Transformer/Image/SetDpiTransformerModule.php:36-44 | lib/php/rendition-factory/src/Transformer/VoidTransformerModule.php:23-31 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 7 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 7 times.
Duplicated block (10 lines × 4) lib/php/rendition-factory/src/Transformer/Video/AlbumArtworkTransformerModule.php:56— lib/php/rendition-factory/src/Transformer/Video/AlbumArtworkTransformerModule.php:56-65 | lib/php/rendition-factory/src/Transformer/Video/VideoSummaryTransformerModule.php:64-73 | lib/php/rendition-factory/src/Transformer/Video/VideoToAnimationTransformerModule.php:52-61 | lib/php/rendition-factory/src/Transformer/Video/VideoToFrameTransformerModule.php:55-64 — before extracting anything, compare `lib/php/rendition-factory/src/Transformer/Video/VideoSummaryTransformerModule.php` and `lib/php/rendition-factory/src/Transformer/Video/VideoToAnimationTransformerModule.php` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 73 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Coverage not measured — JavaScript/TypeScript suite — Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — dashboard/client/ runs vitest but declares no coverage provider, so the suite can run and still produce no lcov — add `@vitest/coverage-v8` (or `@vitest/coverage-istanbul`) as a devDependency. Coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan.
Duplication concentrated across 5 sibling directories (84 clone groups) databox/client/src/lib/api/http.ts:1— 84 duplicated blocks under the repository root have copies in at least two of the sibling directories dashboard, databox, expose, lib, uploader — 57 of them are reported below, and 27 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 84 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 84 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 84 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 25 sibling directories (82 clone groups) databox/client/src/features/baskets/manage/BasketManageRoute.tsx:117— 82 duplicated blocks under databox/client/src/features/ have copies in at least two of the sibling directories attributes, audit-log, baskets, clip, collections, discussion (+19 more sibling(s) not listed) — 37 of them are reported below, and 45 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 82 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 82 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 82 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 4 sibling directories (14 clone groups) databox/client/src/features/annotations/AnnotationsProvider.tsx:221— 14 duplicated blocks under databox/client/src/ have copies in at least two of the sibling directories components, features, hooks, lib — 5 of them are reported below, and 9 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 14 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 14 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 14 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 (8 clone groups) databox/client/src/features/workspaces/manage/entities/EntityListsTab.tsx:26— 8 duplicated blocks under databox/client/src/features/workspaces/manage/ have copies in at least two of the sibling directories entities, tabs — 3 of them are reported below, and 5 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 8 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 8 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 8 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication· Duplicated block with local edits (262 matched lines × 2 locations) · ×1
Duplicated block with local edits (262 matched lines × 2 locations) databox/client/src/features/workspaces/manage/tabs/AttributeDefinitionsTab.tsx:41— databox/client/src/features/workspaces/manage/tabs/AttributeDefinitionsTab.tsx:41 · databox/client/src/features/workspaces/manage/tabs/RenditionDefinitionsTab.tsx:35 — the two spans are one implementation copied and then locally edited — 1363 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Wholesale file copy (160 identical lines × 3 files) databox/client/src/lib/api/http.ts:1— databox/client/src/lib/api/http.ts:1 · expose/client/src/lib/api/http.ts:1 · uploader/client/src/lib/api/http.ts:1 — these 3 files are line-for-line copies of one another — 160 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 (158 matched lines × 2 locations) · ×1
Duplicated block with local edits (158 matched lines × 2 locations) databox/client/src/features/collections/tree/CollectionsPanel.tsx:275— databox/client/src/features/collections/tree/CollectionsPanel.tsx:275 · databox/client/src/features/collections/tree/CollectionsPanel.tsx:508 — the two spans are one implementation copied and then locally edited — 720 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (107 matched lines × 2 locations) · ×1
Duplicated block with local edits (107 matched lines × 2 locations) databox/client/src/components/form/code/CodeEditor.tsx:15— databox/client/src/components/form/code/CodeEditor.tsx:15 · uploader/client/src/components/form/code/CodeEditor.tsx:10 — the two spans are one implementation copied and then locally edited — 590 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (99 matched lines × 2 locations) · ×1
Duplicated block with local edits (99 matched lines × 2 locations) databox/client/src/features/integrations/config/pickers/CreateSecretDialog.tsx:100— databox/client/src/features/integrations/config/pickers/CreateSecretDialog.tsx:100 · databox/client/src/features/integrations/config/pickers/VariableDialog.tsx:52 — the two spans are one implementation copied and then locally edited — 774 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 (90 matched lines × 2 locations) · ×1
Duplicated block with local edits (90 matched lines × 2 locations) databox/client/src/features/baskets/manage/BasketManageRoute.tsx:117— databox/client/src/features/baskets/manage/BasketManageRoute.tsx:117 · databox/client/src/features/saved-searches/manage/SavedSearchManageRoute.tsx:94 — the two spans are one implementation copied and then locally edited — 586 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 (85 matched lines × 2 locations) · ×1
Duplicated block with local edits (85 matched lines × 2 locations) databox/client/src/features/integrations/config/pickers/AttributePicker.tsx:24— databox/client/src/features/integrations/config/pickers/AttributePicker.tsx:24 · databox/client/src/features/integrations/config/pickers/RenditionPicker.tsx:13 — the two spans are one implementation copied and then locally edited — 406 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Wholesale file copy (82 identical lines × 2 files) databox/client/src/lib/utils/format.ts:2— databox/client/src/lib/utils/format.ts:2 · expose/client/src/lib/utils/format.ts:2 — these 2 files are line-for-line copies of one another — 82 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 (80 identical lines × 3 files) dashboard/client/src/lib/auth/AuthProvider.tsx:11— dashboard/client/src/lib/auth/AuthProvider.tsx:11 · expose/client/src/lib/auth/AuthProvider.tsx:11 · uploader/client/src/lib/auth/AuthProvider.tsx:11 — these 3 files are line-for-line copies of one another — 80 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 (77 matched lines × 2 locations) · ×1
Duplicated block with local edits (77 matched lines × 2 locations) databox/client/src/lib/auth/AuthProvider.tsx:61— databox/client/src/lib/auth/AuthProvider.tsx:61 · expose/client/src/lib/auth/AuthProvider.tsx:32 — the two spans are one implementation copied and then locally edited — 449 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 (73 matched lines × 2 locations) · ×1
Duplicated block with local edits (73 matched lines × 2 locations) databox/client/src/features/workspaces/manage/tabs/RenditionDefinitionsTab.tsx:53— databox/client/src/features/workspaces/manage/tabs/RenditionDefinitionsTab.tsx:53 · databox/client/src/features/workspaces/manage/tabs/TagManagerTab.tsx:35 — the two spans are one implementation copied and then locally edited — 384 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 (62 matched lines × 2 locations) · ×1
Duplicated block with local edits (62 matched lines × 2 locations) databox/client/src/features/workspaces/manage/tabs/AssetPoliciesTab.tsx:335— databox/client/src/features/workspaces/manage/tabs/AssetPoliciesTab.tsx:335 · databox/client/src/features/workspaces/manage/tabs/AssetPoliciesTab.tsx:447 — the two spans are one implementation copied and then locally edited — 300 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (57 matched lines × 2 locations) · ×1
Duplicated block with local edits (57 matched lines × 2 locations) databox/client/src/lib/api/metadata.ts:231— databox/client/src/lib/api/metadata.ts:231 · databox/client/src/lib/api/metadata.ts:363 — the two spans are one implementation copied and then locally edited — 301 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (57 lines × 3 locations) databox/client/src/lib/utils/locale.ts:7— databox/client/src/lib/utils/locale.ts:7 · expose/client/src/lib/utils/locale.ts:7 · uploader/client/src/lib/utils/locale.ts:7 — the 3 copies are spread across 3 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete.
Duplicated block (56 lines × 2 locations) dashboard/client/src/app/layout.tsx:18— dashboard/client/src/app/layout.tsx:18 · uploader/client/src/app/layout.tsx:17 — 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.
Wholesale file copy (54 identical lines × 2 files) databox/client/src/app/layout.tsx:1— databox/client/src/app/layout.tsx:1 · expose/client/src/app/layout.tsx:1 — these 2 files are line-for-line copies of one another — 54 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Duplicated block (54 lines × 2 locations) uploader/client/src/features/admin/FormScreens.tsx:18— uploader/client/src/features/admin/FormScreens.tsx:18 · uploader/client/src/features/admin/TargetDataScreens.tsx:17 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
R10 · Code Duplication· Duplicated block with local edits (43 matched lines × 2 locations) · ×1
Duplicated block with local edits (43 matched lines × 2 locations) databox/client/src/lib/analytics/useContentTracking.ts:13— databox/client/src/lib/analytics/useContentTracking.ts:13 · expose/client/src/lib/analytics/useContentTracking.ts:13 — 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) databox/client/src/lib/api/upload.ts:38— databox/client/src/lib/api/upload.ts:38 · uploader/client/src/lib/api/upload.ts:29 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
R10 · Code Duplication· Duplicated block with local edits (42 matched lines × 2 locations) · ×1
Duplicated block with local edits (42 matched lines × 2 locations) dashboard/client/src/lib/config/server.ts:74— dashboard/client/src/lib/config/server.ts:74 · uploader/client/src/lib/config/server.ts:92 — the two spans are one implementation copied and then locally edited — 202 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 (35 matched lines × 2 locations) · ×1
Duplicated block with local edits (35 matched lines × 2 locations) databox/client/src/lib/config/server.ts:5— databox/client/src/lib/config/server.ts:5 · expose/client/src/lib/config/server.ts:5 — 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.
Duplicated block (33 lines × 2 locations) databox/client/src/lib/api/metadata.ts:73— databox/client/src/lib/api/metadata.ts:73 · databox/client/src/lib/api/misc.ts:316 — 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 (32 lines × 2 locations) expose/client/src/features/admin/AdminPublicationList.tsx:66— expose/client/src/features/admin/AdminPublicationList.tsx:66 · expose/client/src/features/admin/ProfileList.tsx:66 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Complex function DefinitionManager (cyclomatic 58, cognitive 45) databox/client/src/features/workspaces/manage/DefinitionManager.tsx:134— DefinitionManager has cyclomatic complexity 58 and cognitive complexity 45; 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 AttributeWidget (cyclomatic 48, cognitive 45) databox/client/src/features/attributes/widgets/AttributeWidget.tsx:51— AttributeWidget has cyclomatic complexity 48 and cognitive complexity 45; 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 ClipEditorDialog (cyclomatic 45, cognitive 43) databox/client/src/features/clip/ClipEditorDialog.tsx:81— ClipEditorDialog has cyclomatic complexity 45 and cognitive complexity 43; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 IntegrationForm (cyclomatic 44, cognitive 42) databox/client/src/features/integrations/manage/IntegrationManager.tsx:149— IntegrationForm has cyclomatic complexity 44 and cognitive complexity 42; 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 UploadDialog (cyclomatic 43, cognitive 39) databox/client/src/features/upload/UploadDialog.tsx:89— UploadDialog has cyclomatic complexity 43 and cognitive complexity 39; 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 DefinitionForm (cyclomatic 42, cognitive 41) databox/client/src/features/workspaces/manage/tabs/AttributeDefinitionsTab.tsx:139— DefinitionForm has cyclomatic complexity 42 and cognitive complexity 41; 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 phraseanetIndexer (cyclomatic 40, cognitive 103) databox/indexer/src/handlers/phraseanet/indexer.ts:41— phraseanetIndexer has cyclomatic complexity 40 and cognitive complexity 103; 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 AnnotationLayer (cyclomatic 40, cognitive 33) databox/client/src/features/annotations/AnnotationLayer.tsx:105— AnnotationLayer has cyclomatic complexity 40 and cognitive complexity 33; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 onKeyDown (cyclomatic 38, cognitive 32) databox/client/src/components/ui/data-table/DataTable.tsx:305— onKeyDown has cyclomatic complexity 38 and cognitive complexity 32; 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 SecretReferencePicker (cyclomatic 37, cognitive 29) databox/client/src/features/integrations/config/pickers/SecretReferencePicker.tsx:66— SecretReferencePicker has cyclomatic complexity 37 and cognitive complexity 29; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 importSubdefsStructure (cyclomatic 35, cognitive 74) databox/indexer/src/handlers/phraseanet/StructureImporter.ts:236— importSubdefsStructure has cyclomatic complexity 35 and cognitive complexity 74; 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 normalizeClientTheme (cyclomatic 34, cognitive 43) lib/js/next-theme/src/customTheme.ts:409— normalizeClientTheme has cyclomatic complexity 34 and cognitive complexity 43; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function UploadScreen (cyclomatic 34, cognitive 31) uploader/client/src/features/upload/UploadScreen.tsx:114— UploadScreen has cyclomatic complexity 34 and cognitive complexity 31; 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 criteria (cyclomatic 33, cognitive 47) databox/client/src/features/search/aql/parser.ts:270— criteria has cyclomatic complexity 33 and cognitive complexity 47; 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 getOperatorLabel (cyclomatic 33, cognitive 18) databox/client/src/features/search/aql/operatorLabel.ts:11— getOperatorLabel has cyclomatic complexity 33 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 tokenize (cyclomatic 30, cognitive 55) databox/client/src/features/search/aql/parser.ts:55— tokenize has cyclomatic complexity 30 and cognitive complexity 55; 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 ShareDialog (cyclomatic 29, cognitive 24) databox/client/src/features/share/ShareDialog.tsx:116— ShareDialog has cyclomatic complexity 29 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 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 computeBatchActions (cyclomatic 28, cognitive 78) databox/client/src/features/attributes/editor/attributeEditorModel.ts:104— computeBatchActions has cyclomatic complexity 28 and cognitive complexity 78; 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 AutomationFormDialog (cyclomatic 28, cognitive 23) databox/client/src/features/saved-searches/automations/AutomationForm.tsx:94— AutomationFormDialog has cyclomatic complexity 28 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 onPointerDown (cyclomatic 27, cognitive 30) databox/client/src/features/annotations/AnnotationLayer.tsx:311— onPointerDown has cyclomatic complexity 27 and cognitive complexity 30; 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 ThemeEditorScreen (cyclomatic 27, cognitive 26) databox/client/src/features/theme/ThemeEditorScreen.tsx:194— ThemeEditorScreen has cyclomatic complexity 27 and cognitive complexity 26; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 canDropAssets (cyclomatic 26, cognitive 39) databox/client/src/features/dnd/canDrop.ts:71— canDropAssets has cyclomatic complexity 26 and cognitive complexity 39; 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 AsyncCombobox (cyclomatic 25, cognitive 22) lib/js/next-ui/src/form/AsyncCombobox.tsx:91— AsyncCombobox has cyclomatic complexity 25 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function MessageComposer (cyclomatic 25, cognitive 21) databox/client/src/features/discussion/MessageComposer.tsx:150— MessageComposer has cyclomatic complexity 25 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 25, cognitive 21) lib/js/api/src/useRequestErrorHandler.ts:17— (anonymous) has cyclomatic complexity 25 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function importStory (cyclomatic 24, cognitive 41) databox/indexer/src/handlers/phraseanet/indexer.ts:488— importStory has cyclomatic complexity 24 and cognitive complexity 41; 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 validateValues (cyclomatic 23, cognitive 47) REDACTED:369— validateValues has cyclomatic complexity 23 and cognitive complexity 47; 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 TopBar (cyclomatic 23, cognitive 22) databox/client/src/components/layout/TopBar.tsx:65— TopBar has cyclomatic complexity 23 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function ClipTimeline (cyclomatic 23, cognitive 21) databox/client/src/features/clip/ClipTimeline.tsx:75— ClipTimeline has cyclomatic complexity 23 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function FormBuilderEditor (cyclomatic 23, cognitive 20) uploader/client/src/features/admin/FormBuilderEditor.tsx:62— FormBuilderEditor has cyclomatic complexity 23 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 normalizeFonts (cyclomatic 22, cognitive 32) lib/js/next-theme/src/customTheme.ts:512— normalizeFonts has cyclomatic complexity 22 and cognitive complexity 32; 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 HumanizedValue (cyclomatic 22, cognitive 24) databox/client/src/features/search/conditions/SearchConditionChip.tsx:373— HumanizedValue has cyclomatic complexity 22 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 AttributeRow (cyclomatic 22, cognitive 21) databox/client/src/features/attributes/AttributeList.tsx:233— AttributeRow has cyclomatic complexity 22 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function CollectionItem (cyclomatic 22, cognitive 21) databox/client/src/features/collections/tree/CollectionsPanel.tsx:502— CollectionItem has cyclomatic complexity 22 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function InputFieldInspector (cyclomatic 22, cognitive 21) uploader/client/src/features/form-builder/editor/FieldInspector.tsx:107— InputFieldInspector has cyclomatic complexity 22 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function FileTile (cyclomatic 22, cognitive 21) uploader/client/src/features/upload/FileTile.tsx:36— FileTile has cyclomatic complexity 22 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 21, cognitive 28) databox/client/src/features/attributes/AttributeList.tsx:89— (anonymous) has cyclomatic complexity 21 and cognitive complexity 28; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function useSearchSuggestions (cyclomatic 21, cognitive 16) databox/client/src/features/search/suggest/useSearchSuggestions.ts:36— useSearchSuggestions has cyclomatic complexity 21 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function importMetadataStructure (cyclomatic 20, cognitive 37) databox/indexer/src/handlers/phraseanet/StructureImporter.ts:429— importMetadataStructure has cyclomatic complexity 20 and cognitive complexity 37; 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 createAsset (cyclomatic 20, cognitive 37) databox/indexer/src/handlers/phraseanet/shared.ts:140— createAsset has cyclomatic complexity 20 and cognitive complexity 37; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R3 · Large Files· lib/js/core/src/mimeTypes.ts · ×1
lib/js/core/src/mimeTypes.ts: 2089 lines of code lib/js/core/src/mimeTypes.ts:1— lib/js/core/src/mimeTypes.ts has 2089 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· databox/client/src/features/attributes/batch/AttributeBatchEditorRoute.tsx · ×1
databox/client/src/features/attributes/batch/AttributeBatchEditorRoute.tsx: 1567 lines of code databox/client/src/features/attributes/batch/AttributeBatchEditorRoute.tsx:1— databox/client/src/features/attributes/batch/AttributeBatchEditorRoute.tsx has 1567 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· databox/client/src/types/api.ts · ×1
databox/client/src/types/api.ts: 1250 lines of code databox/client/src/types/api.ts:1— databox/client/src/types/api.ts has 1250 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· databox/client/src/features/map/AssetMap.tsx · ×1
databox/client/src/features/map/AssetMap.tsx: 1194 lines of code databox/client/src/features/map/AssetMap.tsx:1— databox/client/src/features/map/AssetMap.tsx has 1194 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· uploader/client/src/features/upload/UploadScreen.tsx · ×1
uploader/client/src/features/upload/UploadScreen.tsx: 1016 lines of code uploader/client/src/features/upload/UploadScreen.tsx:1— uploader/client/src/features/upload/UploadScreen.tsx has 1016 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· databox/client/src/features/search/conditions/ConditionBuilder.tsx · ×1
databox/client/src/features/search/conditions/ConditionBuilder.tsx: 931 lines of code databox/client/src/features/search/conditions/ConditionBuilder.tsx:1— databox/client/src/features/search/conditions/ConditionBuilder.tsx has 931 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· databox/client/src/features/upload/UploadDialog.tsx · ×1
databox/client/src/features/upload/UploadDialog.tsx: 922 lines of code databox/client/src/features/upload/UploadDialog.tsx:1— databox/client/src/features/upload/UploadDialog.tsx has 922 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· databox/client/src/features/annotations/AnnotationLayer.tsx · ×1
databox/client/src/features/annotations/AnnotationLayer.tsx: 876 lines of code databox/client/src/features/annotations/AnnotationLayer.tsx:1— databox/client/src/features/annotations/AnnotationLayer.tsx has 876 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· databox/client/src/features/integrations/config/ConfigForm.tsx · ×1
databox/client/src/features/integrations/config/ConfigForm.tsx: 869 lines of code databox/client/src/features/integrations/config/ConfigForm.tsx:1— databox/client/src/features/integrations/config/ConfigForm.tsx has 869 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· databox/client/src/features/share/ShareDialog.tsx · ×1
databox/client/src/features/share/ShareDialog.tsx: 866 lines of code databox/client/src/features/share/ShareDialog.tsx:1— databox/client/src/features/share/ShareDialog.tsx has 866 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· databox/client/src/features/theme/ThemeEditorScreen.tsx · ×1
databox/client/src/features/theme/ThemeEditorScreen.tsx: 846 lines of code databox/client/src/features/theme/ThemeEditorScreen.tsx:1— databox/client/src/features/theme/ThemeEditorScreen.tsx has 846 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· databox/indexer/src/handlers/phraseanet/StructureImporter.ts · ×1
databox/indexer/src/handlers/phraseanet/StructureImporter.ts: 820 lines of code databox/indexer/src/handlers/phraseanet/StructureImporter.ts:1— databox/indexer/src/handlers/phraseanet/StructureImporter.ts has 820 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· databox/client/src/features/collections/tree/CollectionsPanel.tsx · ×1
databox/client/src/features/collections/tree/CollectionsPanel.tsx: 795 lines of code databox/client/src/features/collections/tree/CollectionsPanel.tsx:1— databox/client/src/features/collections/tree/CollectionsPanel.tsx has 795 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· databox/client/src/components/form/selects.tsx · ×1
databox/client/src/components/form/selects.tsx: 765 lines of code databox/client/src/components/form/selects.tsx:1— databox/client/src/components/form/selects.tsx has 765 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· databox/client/src/features/workspaces/manage/entities/EntityGrid.tsx · ×1
databox/client/src/features/workspaces/manage/entities/EntityGrid.tsx: 756 lines of code databox/client/src/features/workspaces/manage/entities/EntityGrid.tsx:1— databox/client/src/features/workspaces/manage/entities/EntityGrid.tsx has 756 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· expose/client/src/features/admin/config/ConfigForm.tsx · ×1
expose/client/src/features/admin/config/ConfigForm.tsx: 733 lines of code expose/client/src/features/admin/config/ConfigForm.tsx:1— expose/client/src/features/admin/config/ConfigForm.tsx has 733 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· databox/client/src/features/annotations/shapes.tsx · ×1
databox/client/src/features/annotations/shapes.tsx: 722 lines of code databox/client/src/features/annotations/shapes.tsx:1— databox/client/src/features/annotations/shapes.tsx has 722 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· databox/client/src/features/operation-tasks/OperationTasksScreen.tsx · ×1
databox/client/src/features/operation-tasks/OperationTasksScreen.tsx: 721 lines of code databox/client/src/features/operation-tasks/OperationTasksScreen.tsx:1— databox/client/src/features/operation-tasks/OperationTasksScreen.tsx has 721 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· databox/client/src/features/profiles/manage/ProfileGridTab.tsx · ×1
databox/client/src/features/profiles/manage/ProfileGridTab.tsx: 712 lines of code databox/client/src/features/profiles/manage/ProfileGridTab.tsx:1— databox/client/src/features/profiles/manage/ProfileGridTab.tsx has 712 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
REDACTED: 698 lines of code REDACTED:1— REDACTED has 698 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· databox/client/src/features/workspaces/manage/DefinitionManager.tsx · ×1
databox/client/src/features/workspaces/manage/DefinitionManager.tsx: 692 lines of code databox/client/src/features/workspaces/manage/DefinitionManager.tsx:1— databox/client/src/features/workspaces/manage/DefinitionManager.tsx has 692 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· databox/indexer/src/handlers/phraseanet/indexer.ts · ×1
databox/indexer/src/handlers/phraseanet/indexer.ts: 690 lines of code databox/indexer/src/handlers/phraseanet/indexer.ts:1— databox/indexer/src/handlers/phraseanet/indexer.ts has 690 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· databox/client/src/features/discussion/MessageComposer.tsx · ×1
databox/client/src/features/discussion/MessageComposer.tsx: 684 lines of code databox/client/src/features/discussion/MessageComposer.tsx:1— databox/client/src/features/discussion/MessageComposer.tsx has 684 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· databox/client/src/lib/api/misc.ts · ×1
databox/client/src/lib/api/misc.ts: 674 lines of code databox/client/src/lib/api/misc.ts:1— databox/client/src/lib/api/misc.ts has 674 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· databox/client/src/components/ui/data-table/DataTable.tsx · ×1
databox/client/src/components/ui/data-table/DataTable.tsx: 669 lines of code databox/client/src/components/ui/data-table/DataTable.tsx:1— databox/client/src/components/ui/data-table/DataTable.tsx has 669 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· databox/client/src/features/clip/ClipEditorDialog.tsx · ×1
databox/client/src/features/clip/ClipEditorDialog.tsx: 653 lines of code databox/client/src/features/clip/ClipEditorDialog.tsx:1— databox/client/src/features/clip/ClipEditorDialog.tsx has 653 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· lib/js/next-core/src/auth/oidc.ts · ×1
lib/js/next-core/src/auth/oidc.ts: 642 lines of code lib/js/next-core/src/auth/oidc.ts:1— lib/js/next-core/src/auth/oidc.ts has 642 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· databox/client/src/features/search/pinned/PinnedFilters.tsx · ×1
databox/client/src/features/search/pinned/PinnedFilters.tsx: 631 lines of code databox/client/src/features/search/pinned/PinnedFilters.tsx:1— databox/client/src/features/search/pinned/PinnedFilters.tsx has 631 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· databox/client/src/features/profiles/manage/ProfileAttributesTab.tsx · ×1
databox/client/src/features/profiles/manage/ProfileAttributesTab.tsx: 594 lines of code databox/client/src/features/profiles/manage/ProfileAttributesTab.tsx:1— databox/client/src/features/profiles/manage/ProfileAttributesTab.tsx has 594 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· databox/client/src/features/saved-searches/automations/AutomationForm.tsx · ×1
databox/client/src/features/saved-searches/automations/AutomationForm.tsx: 592 lines of code databox/client/src/features/saved-searches/automations/AutomationForm.tsx:1— databox/client/src/features/saved-searches/automations/AutomationForm.tsx has 592 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· databox/client/src/features/audit-log/AuditLogScreen.tsx · ×1
databox/client/src/features/audit-log/AuditLogScreen.tsx: 580 lines of code databox/client/src/features/audit-log/AuditLogScreen.tsx:1— databox/client/src/features/audit-log/AuditLogScreen.tsx has 580 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· databox/client/src/lib/api/assets.ts · ×1
databox/client/src/lib/api/assets.ts: 578 lines of code databox/client/src/lib/api/assets.ts:1— databox/client/src/lib/api/assets.ts has 578 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· databox/client/src/components/form/CollectionTreePicker.tsx · ×1
databox/client/src/components/form/CollectionTreePicker.tsx: 577 lines of code databox/client/src/components/form/CollectionTreePicker.tsx:1— databox/client/src/components/form/CollectionTreePicker.tsx has 577 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· databox/client/src/features/workspaces/manage/tabs/AttributeDefinitionsTab.tsx · ×1
databox/client/src/features/workspaces/manage/tabs/AttributeDefinitionsTab.tsx: 577 lines of code databox/client/src/features/workspaces/manage/tabs/AttributeDefinitionsTab.tsx:1— databox/client/src/features/workspaces/manage/tabs/AttributeDefinitionsTab.tsx has 577 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· databox/client/src/features/baskets/manage/BasketIntegrations.tsx · ×1
databox/client/src/features/baskets/manage/BasketIntegrations.tsx: 576 lines of code databox/client/src/features/baskets/manage/BasketIntegrations.tsx:1— databox/client/src/features/baskets/manage/BasketIntegrations.tsx has 576 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· databox/client/src/features/workspaces/manage/tabs/AssetPoliciesTab.tsx · ×1
databox/client/src/features/workspaces/manage/tabs/AssetPoliciesTab.tsx: 574 lines of code databox/client/src/features/workspaces/manage/tabs/AssetPoliciesTab.tsx:1— databox/client/src/features/workspaces/manage/tabs/AssetPoliciesTab.tsx has 574 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· lib/js/auth/src/client/OAuthClient.ts · ×1
lib/js/auth/src/client/OAuthClient.ts: 564 lines of code lib/js/auth/src/client/OAuthClient.ts:1— lib/js/auth/src/client/OAuthClient.ts has 564 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· databox/client/src/features/search/aql/parser.ts · ×1
databox/client/src/features/search/aql/parser.ts: 554 lines of code databox/client/src/features/search/aql/parser.ts:1— databox/client/src/features/search/aql/parser.ts has 554 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· lib/js/next-theme/src/customTheme.ts · ×1
lib/js/next-theme/src/customTheme.ts: 554 lines of code lib/js/next-theme/src/customTheme.ts:1— lib/js/next-theme/src/customTheme.ts has 554 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· expose/client/src/features/player/PdfViewer.tsx · ×1
expose/client/src/features/player/PdfViewer.tsx: 550 lines of code expose/client/src/features/player/PdfViewer.tsx:1— expose/client/src/features/player/PdfViewer.tsx has 550 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R6 · Tooling· Type errors in this package cannot fail any build or CI step · ×1
Type errors in this package cannot fail any build or CI step lib/js/auth/package.json:16— `lib/js/auth` is TypeScript, but a type error in it cannot fail anything this repository runs: its `format` script (`prettier --ignore-path .gitignore --write "**/*.+(js|ts|json|cjs|tsx|jsx)"`) compiles TypeScript with a transpile-only tool that strips types without checking them, and no script, config or CI step of the package runs `tsc --noEmit` or another type checker over it. Add a type check that can fail — a `typecheck` script running `tsc --noEmit` (or `vue-tsc`/`svelte-check`) that CI or the workspace pipeline runs, or a build step that checks before it bundles.
Dead file (~550 LoC) databox/client/src/features/discussion/Discussion.tsx— no import path from any entry point (199 application, 95 tooling, 302 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 (~410 LoC) databox/client/src/features/annotations/AnnotationToolbar.tsx— no import path from any entry point (199 application, 95 tooling, 302 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (databox/client/src/features/annotations/useAnnotationLayer.tsx) — 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 (~231 LoC) databox/client/src/features/baskets/BasketSwitcher.tsx— no import path from any entry point (199 application, 95 tooling, 302 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 (~181 LoC) databox/client/src/features/annotations/useAnnotationLayer.tsx— no import path from any entry point (199 application, 95 tooling, 302 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 (~66 LoC) databox/client/src/features/clip/ClipFrame.tsx— no import path from any entry point (199 application, 95 tooling, 302 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~52 LoC) lib/js/core/src/popup.ts— no import path from any entry point (199 application, 95 tooling, 302 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~36 LoC) databox/client/src/features/dnd/DragScope.tsx— no import path from any entry point (199 application, 95 tooling, 302 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (databox/client/src/features/dnd/useAssetDrag.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~34 LoC) databox/client/src/features/dnd/useAssetDrag.ts— no import path from any entry point (199 application, 95 tooling, 302 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 (~26 LoC) databox/client/src/features/search/useSimilarSearch.ts— no import path from any entry point (199 application, 95 tooling, 302 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 '@hookform/resolvers' databox/client/package.json:29— Declared in databox/client/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 '@wavesurfer/react' databox/client/package.json:40— Declared in databox/client/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 'vaul' databox/client/package.json:66— Declared in databox/client/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 '@api-platform/create-client' databox/indexer/package.json:40— Declared in databox/indexer/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-hook-form' expose/client/package.json:41— Declared in expose/client/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 'js-cookie' lib/js/auth/package.json:24— Declared in lib/js/auth/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.
Third-party script without Subresource Integrity databox/api/templates/admin/integration_help.html.twig:12— `https://cdnjs.cloudflare.com/ajax/libs/highlight.js/11.7.0/highlight.min.js` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. 3 such include(s) across the repository's markup.
Duplicated predicate databox/client/src/lib/utils/locale.ts:73— `!!locale && rtlLanguages.includes(locale.split(/[-_]/)[0])` appears character-identically in 3 files — databox/client/src/lib/utils/locale.ts, expose/client/src/lib/utils/locale.ts, uploader/client/src/lib/utils/locale.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate databox/client/src/lib/analytics/useContentTracking.ts:54— `!assetId || !piece || !name || !fileType` appears character-identically in 2 files — databox/client/src/lib/analytics/useContentTracking.ts, expose/client/src/lib/analytics/useContentTracking.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate databox/client/src/app/layout.tsx:46— `!config.logo && typeof stackLogo?.src === 'string' && stackLogo.src` appears character-identically in 2 files — databox/client/src/app/layout.tsx, expose/client/src/app/layout.tsx. 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 databox/client/src/lib/api/http.ts:101— `!ctx.anonymous && isApiUrl(request.url, config.apiUrl)` appears character-identically in 3 files — databox/client/src/lib/api/http.ts, expose/client/src/lib/api/http.ts, uploader/client/src/lib/api/http.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate lib/js/next-core/src/config/stackConfig.ts:116— `!data || typeof data !== 'object' || Array.isArray(data)` appears character-identically in 2 files — lib/js/next-core/src/config/stackConfig.ts, uploader/client/src/features/upload/engine/resumeStorage.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate databox/client/src/features/integrations/config/ConfigForm.tsx:711— `!schema.variants || !schema.discriminator` appears character-identically in 2 files — databox/client/src/features/integrations/config/ConfigForm.tsx, databox/client/src/features/integrations/config/schema.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate databox/client/src/components/chips.tsx:202— `collection.deleted && 'line-through opacity-60'` appears character-identically in 2 files — databox/client/src/components/chips.tsx, databox/client/src/features/collections/tree/CollectionsPanel.tsx. 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 databox/client/src/components/layout/TopBar.tsx:189— `config.displayServicesMenu && config.dashboardUrl` appears character-identically in 3 files — databox/client/src/components/layout/TopBar.tsx, expose/client/src/components/layout/TopBar.tsx, uploader/client/src/components/layout/TopBar.tsx. 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 databox/client/src/components/form/MetadataTagsField.tsx:96— `disabled && 'cursor-not-allowed opacity-50'` appears character-identically in 2 files — databox/client/src/components/form/MetadataTagsField.tsx, databox/client/src/components/form/TagsInput.tsx. 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 databox/client/src/lib/api/upload.ts:94— `e instanceof PartUploadError && e.status === 403` appears character-identically in 2 files — databox/client/src/lib/api/upload.ts, uploader/client/src/lib/api/upload.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate dashboard/client/src/lib/auth/loginWindow.ts:44— `event.origin !== window.location.origin || event.source !== popup || !isTokensMessage(event.data)` appears character-identically in 2 files — dashboard/client/src/lib/auth/loginWindow.ts, expose/client/src/lib/auth/loginWindow.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate databox/client/src/lib/analytics/useContentTracking.ts:62— `getFileKind(fileType) === FileKind.Video && isMediaTrackingEnabled()` appears character-identically in 2 files — databox/client/src/lib/analytics/useContentTracking.ts, expose/client/src/lib/analytics/useContentTracking.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate databox/client/src/components/layout/TopBar.tsx:97— `hasRole(AppRole.DataboxAdmin) || hasRole(AppRole.Admin)` appears character-identically in 7 files — databox/client/src/components/layout/TopBar.tsx, databox/client/src/features/audit-log/AuditLogScreen.tsx, databox/client/src/features/integrations/manage/InstanceIntegrationsScreen.tsx, databox/client/src/features/permissions/InstancePermissionsScreen.tsx. 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 lib/js/next-core/src/analytics/matomo.ts:52— `initialized || typeof window === 'undefined'` appears character-identically in 2 files — lib/js/next-core/src/analytics/matomo.ts, lib/js/next-core/src/monitoring/sentry.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate databox/client/src/components/form/FileOrUrlInput.tsx:87— `isDragActive && 'border-primary bg-primary/5'` appears character-identically in 3 files — databox/client/src/components/form/FileOrUrlInput.tsx, databox/client/src/features/import/ImportAssetsDialog.tsx, databox/client/src/features/upload/UploadDialog.tsx. 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 databox/client/src/features/map/AssetMap.tsx:313— `map && appliedStyle.current !== styleUrl` appears character-identically in 2 files — databox/client/src/features/map/AssetMap.tsx, databox/client/src/features/map/GeoPointMap.tsx. 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 databox/client/src/features/import/ImportAssetsDialog.tsx:175— `privacyInfo.data && !privacyInfo.data.canEditAssetPrivacy` appears character-identically in 2 files — databox/client/src/features/import/ImportAssetsDialog.tsx, databox/client/src/features/upload/UploadDialog.tsx. 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 databox/client/src/lib/ticketing/config.ts:78— `process.env.KEYCLOAK_REALM_NAME || 'phrasea'` appears character-identically in 2 files — databox/client/src/lib/ticketing/config.ts, databox/client/src/lib/ticketing/session.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate databox/client/src/lib/api/http.ts:146— `response.status === 401 && !ctx.anonymous && !ctx.retried && isApiUrl(request.url, config.apiUrl)` appears character-identically in 3 files — databox/client/src/lib/api/http.ts, expose/client/src/lib/api/http.ts, uploader/client/src/lib/api/http.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate uploader/client/src/features/admin/FormBuilderEditor.tsx:303— `save.error && Object.keys(errors).length === 0` appears character-identically in 2 files — uploader/client/src/features/admin/FormBuilderEditor.tsx, uploader/client/src/features/admin/TargetDataEditor.tsx. 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 expose/client/src/lib/auth/RequireAuth.tsx:23— `status === 'anonymous' && !loggedOut && !loggingOut` appears character-identically in 2 files — expose/client/src/lib/auth/RequireAuth.tsx, uploader/client/src/lib/auth/RequireAuth.tsx. 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 dashboard/client/src/app/auth/window/page.tsx:23— `status === 'authenticated' && !handOverTokens()` appears character-identically in 2 files — dashboard/client/src/app/auth/window/page.tsx, expose/client/src/app/auth/window/page.tsx. 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 databox/indexer/src/handlers/phraseanet/indexer.ts:638— `story.cover_record_id !== null && story.cover_record_id !== undefined` appears character-identically in 2 files — databox/indexer/src/handlers/phraseanet/indexer.ts, databox/indexer/src/handlers/phraseanet/shared.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate databox/client/src/features/dnd/DragGhost.tsx:26— `targetName(target) || t('dnd.untitled', 'untitled')` appears character-identically in 2 files — databox/client/src/features/dnd/DragGhost.tsx, databox/client/src/features/dnd/executeDrop.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate databox/client/src/features/integrations/config/pickers/CreateSecretDialog.tsx:114— `trimmed !== '' && !isValidSecretName(trimmed)` appears character-identically in 2 files — databox/client/src/features/integrations/config/pickers/CreateSecretDialog.tsx, databox/client/src/features/integrations/config/pickers/VariableDialog.tsx. 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 databox/indexer/src/amqp.ts:32— `error` at line 32 is handed a template literal with `${…}` substitutions 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 the values beside a constant message instead: `logger.error({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.error('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging databox/indexer/src/amqp.ts:33— `info` at line 33 is handed a template literal with `${…}` substitutions 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 the values beside a constant message instead: `logger.info({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.info('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging databox/indexer/src/pathFilter.ts:11— `debug` at line 11 is handed a template literal with `${…}` substitutions 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 the values beside a constant message instead: `logger.debug({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.debug('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging databox/indexer/src/pathFilter.ts:15— `debug` at line 15 is handed a template literal with `${…}` substitutions 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 the values beside a constant message instead: `logger.debug({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.debug('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging databox/indexer/src/server.ts:84— `info` at line 84 is handed a template literal with `${…}` substitutions 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 the values beside a constant message instead: `logger.info({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.info('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging databox/indexer/src/server.ts:104— `warn` at line 104 is handed a template literal with `${…}` substitutions 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 the values beside a constant message instead: `logger.warn({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.warn('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging databox/indexer/src/server.ts:114— `warn` at line 114 is handed a template literal with `${…}` substitutions 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 the values beside a constant message instead: `logger.warn({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.warn('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging databox/indexer/src/lib/axios.ts:79— `warn` at line 79 is handed a template literal with `${…}` substitutions 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 the values beside a constant message instead: `logger.warn({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.warn('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging databox/indexer/src/lib/axios.ts:86— `debug` at line 86 is handed a template literal with `${…}` substitutions 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 the values beside a constant message instead: `logger.debug({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.debug('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging databox/indexer/src/lib/axios.ts:169— `debug` at line 169 is handed a template literal with `${…}` substitutions 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 the values beside a constant message instead: `logger.debug({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.debug('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging databox/indexer/src/handlers/s3_amqp/indexer.ts:25— `info` at line 25 is handed a template literal with `${…}` substitutions 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 the values beside a constant message instead: `logger.info({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.info('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging databox/indexer/src/handlers/phraseanet/StructureImporter.ts:308— `error` at line 308 is handed a template literal with `${…}` substitutions 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 the values beside a constant message instead: `logger.error({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.error('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging databox/indexer/src/handlers/phraseanet/StructureImporter.ts:323— `error` at line 323 is handed a template literal with `${…}` substitutions 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 the values beside a constant message instead: `logger.error({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.error('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging databox/indexer/src/handlers/phraseanet/StructureImporter.ts:327— `error` at line 327 is handed a template literal with `${…}` substitutions 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 the values beside a constant message instead: `logger.error({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.error('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging databox/indexer/src/handlers/phraseanet/StructureImporter.ts:348— `info` at line 348 is handed a template literal with `${…}` substitutions 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 the values beside a constant message instead: `logger.info({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.info('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging databox/indexer/src/handlers/phraseanet/StructureImporter.ts:364— `info` at line 364 is handed a template literal with `${…}` substitutions 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 the values beside a constant message instead: `logger.info({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.info('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging databox/indexer/src/handlers/phraseanet/StructureImporter.ts:371— `info` at line 371 is handed a template literal with `${…}` substitutions 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 the values beside a constant message instead: `logger.info({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.info('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging databox/indexer/src/handlers/phraseanet/StructureImporter.ts:380— `info` at line 380 is handed a template literal with `${…}` substitutions 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 the values beside a constant message instead: `logger.info({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.info('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging databox/indexer/src/handlers/phraseanet/StructureImporter.ts:397— `error` at line 397 is handed a template literal with `${…}` substitutions 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 the values beside a constant message instead: `logger.error({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.error('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging databox/indexer/src/handlers/phraseanet/StructureImporter.ts:508— `info` at line 508 is handed a template literal with `${…}` substitutions 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 the values beside a constant message instead: `logger.info({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.info('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging databox/indexer/src/handlers/phraseanet/StructureImporter.ts:534— `info` at line 534 is handed a template literal with `${…}` substitutions 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 the values beside a constant message instead: `logger.info({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.info('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging databox/indexer/src/handlers/phraseanet/StructureImporter.ts:540— `info` at line 540 is handed a template literal with `${…}` substitutions 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 the values beside a constant message instead: `logger.info({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.info('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging databox/indexer/src/handlers/phraseanet/indexer.ts:71— `info` at line 71 is handed a template literal with `${…}` substitutions 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 the values beside a constant message instead: `logger.info({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.info('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging databox/indexer/src/handlers/phraseanet/indexer.ts:85— `info` at line 85 is handed a template literal with `${…}` substitutions 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 the values beside a constant message instead: `logger.info({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.info('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging databox/indexer/src/handlers/phraseanet/indexer.ts:120— `info` at line 120 is handed a template literal with `${…}` substitutions 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 the values beside a constant message instead: `logger.info({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.info('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Deprecated: @jonkoops/matomo-tracker REDACTED:2011— @jonkoops/matomo-tracker 0.7.0 is resolved in REDACTED and is marked deprecated by its publisher: "This package is no longer maintained.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: abab REDACTED:4406— abab 2.0.6 is resolved in REDACTED and is marked deprecated by its publisher: "Use your platform's native atob() and btoa() methods instead". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: are-we-there-yet REDACTED:4642— are-we-there-yet 2.0.0 is resolved in REDACTED and is marked deprecated by its publisher: "This package is no longer supported.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: domexception REDACTED:5381— domexception 1.0.1 is resolved in REDACTED and is marked deprecated by its publisher: "Use your platform's native DOMException instead". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: gauge REDACTED:5915— gauge 3.0.2 is resolved in REDACTED and is marked deprecated by its publisher: "This package is no longer supported.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: glob REDACTED:5977— glob 10.5.0 is resolved in REDACTED and is marked deprecated by its publisher: "Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: glob REDACTED:5982— glob 7.2.3 is resolved in REDACTED and is marked deprecated by its publisher: "Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: gulp-header REDACTED:6014— gulp-header 1.8.12 is resolved in REDACTED and is marked deprecated by its publisher: "Removed event-stream from gulp-header". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: har-validator REDACTED:6042— har-validator 5.1.5 is resolved in REDACTED and is marked deprecated by its publisher: "this library is no longer supported". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: highlight.js REDACTED:6119— highlight.js 9.18.5 is resolved in REDACTED and is marked deprecated by its publisher: "Support has ended for 9.x series. Upgrade to @latest". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: inflight REDACTED:6211— inflight 1.0.6 is resolved in REDACTED and is marked deprecated by its publisher: "This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: lodash.template REDACTED:6758— lodash.template 4.18.1 is resolved in REDACTED and is marked deprecated by its publisher: "This package is deprecated. Use https://socket.dev/npm/package/eta instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: node-domexception REDACTED:7047— node-domexception 1.0.0 is resolved in REDACTED and is marked deprecated by its publisher: "Use your platform's native DOMException instead". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: npmlog REDACTED:7091— npmlog 5.0.1 is resolved in REDACTED and is marked deprecated by its publisher: "This package is no longer supported.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: prebuild-install REDACTED:7284— prebuild-install 7.1.3 is resolved in REDACTED and is marked deprecated by its publisher: "No longer maintained. Please contact the author of the relevant native addon; alternatives are available.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: request-promise-native REDACTED:7634— request-promise-native 1.0.9 is resolved in REDACTED and is marked deprecated by its publisher: "request-promise-native has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: request REDACTED:7641— request 2.88.2 is resolved in REDACTED and is marked deprecated by its publisher: "request has been deprecated, see https://github.com/request/request/issues/3142". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: resolve-url REDACTED:7664— resolve-url 0.2.1 is resolved in REDACTED and is marked deprecated by its publisher: "https://github.com/lydell/resolve-url#deprecated". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: rimraf REDACTED:7693— rimraf 3.0.2 is resolved in REDACTED and is marked deprecated by its publisher: "Rimraf versions prior to v4 are no longer supported". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: source-map-resolve REDACTED:7944— source-map-resolve 0.5.3 is resolved in REDACTED and is marked deprecated by its publisher: "See https://github.com/lydell/source-map-resolve#deprecated". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: source-map-url REDACTED:7951— source-map-url 0.4.1 is resolved in REDACTED and is marked deprecated by its publisher: "See https://github.com/lydell/source-map-url#deprecated". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: tar REDACTED:8165— tar 6.2.1 is resolved in REDACTED and is marked deprecated by its publisher: "Old versions of tar are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: tui-code-snippet REDACTED:8318— tui-code-snippet 2.3.3 is resolved in REDACTED and is marked deprecated by its publisher: "Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: tui-color-picker REDACTED:8322— tui-color-picker 2.2.8 is resolved in REDACTED and is marked deprecated by its publisher: "Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: urix REDACTED:8445— urix 0.1.0 is resolved in REDACTED and is marked deprecated by its publisher: "Please see https://github.com/lydell/urix#deprecated". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Orphaned file lib/php/rendition-factory/src/Image/ColorspaceDetector.php:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file lib/php/admin-bundle/Filter/ChildPropertyEntityFilter.php:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file databox/api/src/Integration/Happyscribe/HappyscribeAction.php:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file databox/api/src/Integration/Happyscribe/Consumer/TranscriptionHappyscribeMessageHandler.php:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file databox/api/src/Entity/Core/AssetPolicy/AssetPolicy.php:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file uploader/api/src/Command/YamlToApiResourceCommand.php:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file expose/api/src/Command/YamlToApiResourceCommand.php:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file lib/php/auth-bundle/Security/OAuthAuthorizationAuthenticator.php:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file databox/api/src/Integration/Happyscribe/Consumer/ExportTranscriptionMessageHandler.php:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file lib/php/auth-bundle/Security/AccessTokenAuthenticator.php:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file databox/api/src/Api/Extension/RenditionDefinitionExtension.php:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file databox/api/src/Api/Processor/CopyAssetProcessor.php:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file databox/api/src/Integration/Happyscribe/Consumer/TranslateTranscriptionMessageHandler.php:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file databox/api/src/Controller/Admin/AssetPolicyCrudController.php:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file databox/api/src/Integration/Aws/Translate/AwsTranslateIntegration.php:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file databox/api/src/Service/Asset/AssetPolicy/AssetPolicyManager.php:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file databox/api/src/Api/Mapper/Input/AssetPolicyInputMapper.php:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file databox/api/src/Service/Matomo/MatomoManager.php:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Silent fallback default in catch expose/api/src/Security/PasswordTokenExtractor.php:25— `getPasswords` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it propagate. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment in the catch or in the docblock, and the row stops firing.
Silent fallback default in catch dashboard/client/src/features/status/health.ts:51— `probeApi` swallows every exception into `return 'down'` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch databox/client/src/components/layout/layoutStore.ts:37— `readTab` swallows every exception into `return 'facets'` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch databox/client/src/features/attributes/batch/AttributeBatchEditorRoute.tsx:150— `AttributeBatchEditorRoute` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch databox/client/src/features/discussion/messageAttachments.ts:52— `getFileAttachments` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch databox/client/src/features/discussion/messageAttachments.ts:77— `getAnnotationAttachments` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch databox/client/src/features/preferences/store.ts:83— `readLocal` swallows every exception into `return {}` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch databox/client/src/features/saved-searches/automations/AutomationForm.tsx:75— `browserTimezone` swallows every exception into `return 'UTC'` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch databox/client/src/features/stories/pinnedStoriesStore.ts:28— `read` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch databox/client/src/lib/ticketing/session.ts:36— `decodeClaims` swallows every exception into `return {}` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch expose/client/src/lib/api/passwords.ts:23— `decodePasswords` swallows every exception into `return {}` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch lib/js/auth/src/stateNonce.ts:17— `readNonces` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch uploader/client/src/features/upload/engine/resumeStorage.ts:74— `read` swallows every exception into `return {}` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
P2 · Observability· Console output used as the logging channel · ×12
Console output used as the logging channel databox/indexer/src/configLoader.ts:110— `databox/indexer/src/configLoader.ts` reports through `console.*` at line 110 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel databox/indexer/src/env.ts:5— `databox/indexer/src/env.ts` reports through `console.*` at line 5 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel databox/indexer/src/eventHandler.ts:28— `databox/indexer/src/eventHandler.ts` reports through `console.*` at line 28 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel databox/indexer/src/eventHandler.ts:45— `databox/indexer/src/eventHandler.ts` reports through `console.*` at line 45 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel databox/indexer/src/init.ts:8— `databox/indexer/src/init.ts` reports through `console.*` at line 8 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel databox/indexer/src/init.ts:11— `databox/indexer/src/init.ts` reports through `console.*` at line 11 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel databox/indexer/src/shutdown.ts:40— `databox/indexer/src/shutdown.ts` reports through `console.*` at line 40 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel databox/indexer/src/shutdown.ts:47— `databox/indexer/src/shutdown.ts` reports through `console.*` at line 47 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel databox/indexer/src/shutdown.ts:56— `databox/indexer/src/shutdown.ts` reports through `console.*` at line 56 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel databox/indexer/src/shutdown.ts:64— `databox/indexer/src/shutdown.ts` reports through `console.*` at line 64 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel databox/indexer/src/command/list.ts:9— `databox/indexer/src/command/list.ts` reports through `console.*` at line 9 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel databox/indexer/src/command/list.ts:11— `databox/indexer/src/command/list.ts` reports through `console.*` at line 11 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
X7 · Silent fallback defaults· Pending state with no failure state · ×11
Pending state with no failure state uploader/client/src/lib/auth/RequireAuth.tsx:47— The view draws `<FullPageLoader/>` under `status !== 'authenticated'`, but `status` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
Pending state with no failure state expose/client/src/lib/auth/RequireAuth.tsx:48— The view draws `<FullPageLoader/>` under `status !== 'authenticated'`, but `status` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
Pending state with no failure state expose/client/src/features/player/AudioPlayer.tsx:189— The view draws `<div class="absolute inset-0 flex items-center justify-center">` under `! isReady`, but `isReady` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
Pending state with no failure state databox/client/src/lib/auth/RequireAuth.tsx:21— The view draws `<FullPageLoader/>` under `status !== 'authenticated'`, but `status` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
Pending state with no failure state databox/client/src/features/workspaces/manage/entities/EntityAssetsPreviewDialog.tsx:78— The view draws `<div class="flex justify-center py-6">` under `assets . isLoading`, but `assets` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
Pending state with no failure state databox/client/src/features/search/pinned/PinnedFilters.tsx:499— The view draws `<div class="flex justify-center p-3">` under `isFetching && ! data`, but `isFetching` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
Pending state with no failure state databox/client/src/features/preferences/UserPreferencesGate.tsx:89— The view draws `<FullPageLoader label= />` under `! loaded || ! definitionsHydrated || ( authenticated && ! profilesReady )`, but `loaded` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
Pending state with no failure state databox/client/src/features/permissions/ConfirmDeleteButton.tsx:26— The view draws `<span class="inline-flex size-7 items-center justify-center">` under `state === 'deleting'`, but `state` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
Pending state with no failure state databox/client/src/features/integrations/config/pickers/SecretReferencePicker.tsx:293— The view draws `<div class="flex justify-center py-4">` under `listable && ( loading || system . 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.
Pending state with no failure state databox/client/src/features/impersonation/SwitchUserDialog.tsx:141— The view draws `<Spinner/>` under `switchingTo === u . id`, but `switchingTo` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
Pending state with no failure state databox/client/src/features/attributes/batch/AttributeBatchEditorRoute.tsx:725— The view draws `<div className= >` under `! initialized || ! currentDef`, but `initialized` 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.
X23 · Unguarded diagnostic materialisation· Diagnostic log message is built whether or not it is wanted · ×8
Diagnostic log message is built whether or not it is wanted lib/php/es-bundle/Indexer/SearchIndexer.php:113— `debug` at line 113 is called with an argument built by `implode('", "', $ids)` (line 113), whose cost grows with the collection it walks. PHP evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isHandling` test, no debug flag, and no placeholder context array that lets the logger build the text only when the level is on.
Diagnostic log message is built whether or not it is wanted databox/indexer/src/lib/axios.ts:86— `debug` at line 86 is called with an argument built by `JSON.stringify(error.response.data)` (line 89), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted databox/indexer/src/lib/axios.ts:116— `debug` at line 116 is called with an argument built by `JSON.stringify(error.response.headers, undefined, 2)` (line 118), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted databox/indexer/src/lib/axios.ts:169— `debug` at line 169 is called with an argument built by `obfuscate(JSON.stringify(config.headers, null, 2))` (line 170), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted databox/indexer/src/handlers/phraseanet/indexer.ts:584— `debug` at line 584 is called with an argument built by `Object.keys(phraseanetDatabox.collections)` (line 585), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted databox/indexer/src/handlers/phraseanet/indexer.ts:587— `debug` at line 587 is called with an argument built by `JSON.stringify(phraseanetDatabox.collections[story.base_id])` (line 588), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted databox/api/src/Integration/Phraseanet/PhraseanetGenerateAssetRenditionsAction.php:63— `debug` at line 63 is called with an argument built by `json_encode($data, JSON_THROW_ON_ERROR)` (line 63), whose cost grows with the collection it walks. PHP evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isHandling` test, no debug flag, and no placeholder context array that lets the logger build the text only when the level is on.
Diagnostic log message is built whether or not it is wanted databox/api/src/Integration/Phraseanet/PhraseanetGenerateAssetRenditionsEnqueueMethodAction.php:52— `debug` at line 52 is called with an argument built by `json_encode($data, JSON_THROW_ON_ERROR)` (line 52), whose cost grows with the collection it walks. PHP evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isHandling` test, no debug flag, and no placeholder context array that lets the logger build the text only when the level is on.
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×7
Projects may be oversized for their cohesion databox/api/composer.json:1— `databox/api` (102595 LoC, 1601 module-visible types across 203 directories) overshoots its size bounds. 7 of 36 build unit(s) (Composer, npm) overshoot their size bounds, lowering Project Cohesion to 6.1/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
Projects may be oversized for their cohesion databox/client/package.json:1— `databox/client` (94454 LoC, 698 module-visible types across 147 directories) overshoots its size bounds. 7 of 36 build unit(s) (Composer, npm) overshoot their size bounds, lowering Project Cohesion to 6.1/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
Projects may be oversized for their cohesion uploader/api/composer.json:1— `uploader/api` (11083 LoC, 166 module-visible types across 37 directories) overshoots its size bounds. 7 of 36 build unit(s) (Composer, npm) overshoot their size bounds, lowering Project Cohesion to 6.1/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
Projects may be oversized for their cohesion expose/client/package.json:1— `expose/client` (9456 LoC, 111 module-visible types across 37 directories) overshoots its size bounds. 7 of 36 build unit(s) (Composer, npm) overshoot their size bounds, lowering Project Cohesion to 6.1/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
Projects may be oversized for their cohesion expose/api/composer.json:1— `expose/api` (13346 LoC, 184 module-visible types across 33 directories) overshoots its size bounds. 7 of 36 build unit(s) (Composer, npm) overshoot their size bounds, lowering Project Cohesion to 6.1/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
Projects may be oversized for their cohesion uploader/client/package.json:1— `uploader/client` (9915 LoC, 101 module-visible types across 33 directories) overshoots its size bounds. 7 of 36 build unit(s) (Composer, npm) overshoot their size bounds, lowering Project Cohesion to 6.1/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
Projects may be oversized for their cohesion lib/php/rendition-factory/composer.json:1— `lib/php/rendition-factory` (6049 LoC, 92 module-visible types across 24 directories) overshoots its size bounds. 7 of 36 build unit(s) (Composer, npm) overshoot their size bounds, lowering Project Cohesion to 6.1/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
Outdated (npm): chokidar databox/indexer/package.json:31— chokidar is pinned at 3.6.0; registry.npmjs.org publishes 6.0.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): commander databox/indexer/package.json:32— commander is pinned at 11.1.0; registry.npmjs.org publishes 15.1.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): i18next dashboard/client/package.json:27— i18next is pinned at 24.2.1; registry.npmjs.org publishes 27.1.3 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-dropzone databox/client/package.json:58— react-dropzone is pinned at 14.4.1; registry.npmjs.org publishes 20.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-i18next dashboard/client/package.json:34— react-i18next is pinned at 15.7.4; registry.npmjs.org publishes 18.0.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.
DM2 · Strongly-typed ids· Primitive id on a domain type · ×4
Primitive id on a domain type: AssetOutput.threadKey — `AssetOutput.threadKey` is a raw `string` — give it a strongly-typed id: a dedicated single-field type wrapping the `string`, in whatever form your language spells that.
Primitive id on a domain type: AssetOutput.trackingId — `AssetOutput.trackingId` is a raw `string` — give it a strongly-typed id: a dedicated single-field type wrapping the `string`, in whatever form your language spells that.
Primitive id on a domain type: AssetOutput.externalId — `AssetOutput.externalId` is a raw `string` — give it a strongly-typed id: a dedicated single-field type wrapping the `string`, in whatever form your language spells that.
Primitive id on a domain type: AssetOutput.resolvedTrackingId — `AssetOutput.resolvedTrackingId` is a raw `string` — give it a strongly-typed id: a dedicated single-field type wrapping the `string`, in whatever form your language spells that.
R7 · Dead Code· Unused export 'getPreferredLanguages' · ×3
Unused export 'getPreferredLanguages' databox/client/src/lib/utils/locale.ts:13— Nothing imports this binding — it is safe to review for removal.
Unused export 'getPreferredLanguages' expose/client/src/lib/utils/locale.ts:13— Nothing imports this binding — it is safe to review for removal.
Unused export 'getPreferredLanguages' uploader/client/src/lib/utils/locale.ts:13— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'pickFieldTranslation' · ×3
Unused export 'pickFieldTranslation' databox/client/src/lib/utils/locale.ts:60— Nothing imports this binding — it is safe to review for removal.
Unused export 'pickFieldTranslation' expose/client/src/lib/utils/locale.ts:60— Nothing imports this binding — it is safe to review for removal.
Unused export 'pickFieldTranslation' uploader/client/src/lib/utils/locale.ts:60— Nothing imports this binding — it is safe to review for removal.
D21 · Naming Consistency· `baseURL` spells `URL` where 55 names in the project spell it `Url` · ×2
`baseURL` spells `URL` where 55 names in the project spell it `Url` databox/indexer/src/databox/client.ts:27— 55 of 57 names in project @alchemy/phrasea spell the token `Url` (55 of 57; unit: names in project @alchemy/phrasea containing `Url`). Peers: services.consoleUrl (dashboard/client/src/features/dashboard/services.ts:29); services.consoleUrl(keycloakUrl) (dashboard/client/src/features/dashboard/services.ts:29); health.probeApi(apiUrl) (dashboard/client/src/features/status/health.ts:39); groups.createDataboxGroupsApi(apiUrl) (dashboard/client/src/lib/api/groups.ts:19); FileOrUrlInput.FileOrUrlInput (databox/client/src/components/form/FileOrUrlInput.tsx:24). Rename to `baseUrl`. [rule N6]
`baseURL` spells `URL` where 55 names in the project spell it `Url` lib/js/api/src/httpClient.ts:9— 55 of 57 names in project @alchemy/phrasea spell the token `Url` (55 of 57; unit: names in project @alchemy/phrasea containing `Url`). Peers: services.consoleUrl (dashboard/client/src/features/dashboard/services.ts:29); services.consoleUrl(keycloakUrl) (dashboard/client/src/features/dashboard/services.ts:29); health.probeApi(apiUrl) (dashboard/client/src/features/status/health.ts:39); groups.createDataboxGroupsApi(apiUrl) (dashboard/client/src/lib/api/groups.ts:19); FileOrUrlInput.FileOrUrlInput (databox/client/src/components/form/FileOrUrlInput.tsx:24). Rename to `baseUrl`. [rule N6]
redundant comment databox/client/src/features/dnd/canDrop.test.ts:52— "ws1: root > child > grandchild ; other (root)" repeats the code it sits on: 4 of its 4 words (ws, root, child, grandchild) are already in `const collections: Record<string, CollectionNode> = {`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment databox/indexer/src/handlers/phraseanet/indexer.ts:562— "then create the story collection" repeats the code it sits on: 3 of its 3 words (create, story, collection) are already in `storyCollectionId = await databoxClient.createCollection(`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
Fat interface: AttributeTypeInterface (24 methods) databox/api/src/Attribute/Type/AttributeTypeInterface.php:10— `AttributeTypeInterface` declares 24 methods: `getElasticSearchType`, `getElasticSearchTextSubField`, `getElasticSearchSearchType`, `getAdditionalSubFields`, `getElasticSearchRawField`, `getElasticSearchSortSubField`, `supportsElasticSearchFuzziness`, `getFacetType`, `supportsAggregation`, `getElasticSearchMapping`, `normalizeValue`, `convertToDbValue`, `denormalizeValue`, `normalizeElasticsearchValue`, `getStringValue`, `getGroupValueLabel`, `isMappingLocaleAware`, `isLocaleAware`, `supportsSuggest`, `supportsTranslations`, `validate`, `getAggregationField`, `normalizeBuckets`, `isListed`. Counted over its public instance methods, once per name; constants and static methods are not counted. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 347 significant file(s) lose their only recent owner: lib/js/core/src/mimeTypes.ts, databox/api/src/Elasticsearch/AQL/AQLGrammar.php, databox/client/src/features/attributes/batch/AttributeBatchEditorRoute.tsx, databox/client/src/features/map/AssetMap.tsx, databox/client/src/features/upload/UploadDialog.tsx, databox/client/src/features/theme/ThemeEditorScreen.tsx, databox/client/src/types/api.ts, databox/client/src/features/share/ShareDialog.tsx (+339 more). Pair on, review, or document these before any departure.
D16 · Bus Factor· Further sole-owners (lower concentration) · ×1
Further sole-owners (lower concentration) — 2 other contributor(s) are each the sole owner of a small amount of code below the off-boarding threshold — folded into the bus-factor score and metrics (350 single-owned of 1097 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 1097 of the 3043 production source files in this repository met that bar). They are anonymized user #2 (2 file(s)), anonymized user #3 (1 file(s)) — spread or document their files in the same way, at lower priority than the named off-boarding risks above. The files folded here: databox/api/src/Integration/Aws/Translate/TranslateAction.php, lib/php/rendition-factory/src/Transformer/ExtractEmbeddedPreviewTransformerModule.php, databox/indexer/src/handlers/phraseanet/shared.ts.
No ADRs found uploader/api/composer.json:2— No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`. ADRs are expected here because `uploader/api/composer.json` makes this repository a deployable product (line 2).
D28 · Secrets (history)· Rotate the exposed credentials · ×1
D34 · Knowledge Freshness· Orphaned files with no living knowledge · ×1
Orphaned files with no living knowledge — 18 of 1097 analysed file(s) have no living knowledge left — their last meaningful change has decayed away, so if one breaks, no one currently understands it (counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 1097 of the 3043 production source files in this repository met that bar). None is large enough to earn a read-through of its own, so this row stands in for the per-file rows rather than raising one each — most significant first: lib/php/rendition-factory/src/Image/ColorspaceDetector.php, lib/php/admin-bundle/Filter/ChildPropertyEntityFilter.php, lib/php/auth-bundle/Security/OAuthAuthorizationAuthenticator.php, databox/api/src/Integration/Happyscribe/HappyscribeAction.php, databox/api/src/Integration/Happyscribe/Consumer/TranscriptionHappyscribeMessageHandler.php, lib/php/auth-bundle/Security/AccessTokenAuthenticator.php, databox/api/src/Entity/Core/AssetPolicy/AssetPolicy.php, expose/api/src/Command/YamlToApiResourceCommand.php (and 10 more). Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
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.
M2 · Architecture documentation· Architecture diagram out of date · ×1
Architecture diagram out of date README.md:83— `README.md` draws the system's parts, and the drawing no longer matches the code: it leaves out `dashboard-client`, `dev`, which the repository has beside the units it does draw. A diagram of a system that no longer exists misleads the reader it was drawn for, so it is not credited as documenting the shape.
Logging is not universal — Only 16/23 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `dashboard/client`, `databox/client`, `expose/client`, `lib/js/next-core`, `lib/js/next-theme` and 2 more.
No SAST REDACTED:9— 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 8 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:16— `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`.
No changelog — No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
R7 · Dead Code· Unused export 'defaultFrameDuration' · ×1
Unused export 'defaultFrameDuration' databox/client/src/features/annotations/common.ts:50— Nothing imports this binding — it is safe to review for removal.
Unused export 'AnnotationId' databox/client/src/features/annotations/types.ts:29— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'CueAnnotation' · ×1
Unused export 'CueAnnotation' databox/client/src/features/annotations/types.ts:114— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'TimeRangeAnnotation' · ×1
Unused export 'TimeRangeAnnotation' databox/client/src/features/annotations/types.ts:120— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'FileIntegrationTab' · ×1
Unused export 'FileIntegrationTab' databox/client/src/features/integrations/FileIntegrations.tsx:46— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'assetPermissions' · ×1
Unused export 'assetPermissions' databox/client/src/features/permissions/permissionDefinitions.ts:33— Nothing imports this binding — it is safe to review for removal.
Unused export 'hasMask' databox/client/src/features/permissions/permissionTypes.ts:78— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'useIsStoryPinned' · ×1
Unused export 'useIsStoryPinned' databox/client/src/features/stories/pinnedStoriesStore.ts:73— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'clearRecentErrors' · ×1
Unused export 'clearRecentErrors' databox/client/src/features/ticketing/context.ts:67— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'getSavedSearchAutomation' · ×1
Unused export 'getSavedSearchAutomation' REDACTED:42— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'exportChannel' · ×1
Unused export 'exportChannel' databox/client/src/lib/realtime/channels.ts:23— Nothing imports this binding — it is safe to review for removal.
Unused export 'isIriOf' databox/client/src/lib/utils/iri.ts:14— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'AttrDefinitionIndex' · ×1
Unused export 'AttrDefinitionIndex' databox/indexer/src/handlers/phraseanet/shared.ts:7— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'RESERVED_SEGMENTS' · ×1
Unused export 'RESERVED_SEGMENTS' expose/client/src/lib/routes.ts:4— Nothing imports this binding — it is safe to review for removal.
Unused export 'NO_LOCALE' expose/client/src/lib/utils/locale.ts:75— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'BuilderFormState' · ×1
Unused export 'BuilderFormState' uploader/client/src/features/form-builder/render/useBuilderForm.ts:87— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'UPLOAD_LINK_QUOTA_EXCEEDED' · ×1
Unused export 'UPLOAD_LINK_QUOTA_EXCEEDED' uploader/client/src/lib/api/uploadLinks.ts:28— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'getDataboxWorkspace' · ×1
Unused export 'getDataboxWorkspace' uploader/client/src/lib/api/uploader.ts:243— Nothing imports this binding — it is safe to review for removal.
Security headers incomplete infra/docker/nginx-fpm-base/tpl/default.conf:8— Set: Content-Security-Policy, Referrer-Policy, Strict-Transport-Security, X-Content-Type-Options. Missing: X-Frame-Options — the four headers that carry the points of this card's security-headers term (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options), 0.5 each. (−0.5 on this card.)
X2 · Cancellation propagation· Not all async functions that make a request accept an AbortSignal · ×1
Not all async functions that make a request accept an AbortSignal — Only 11/19 async functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
X5 · Nullable reference types· PHP static analysis does not check null everywhere · ×1
PHP static analysis does not check null everywhere — 0/3 of this repository's PHPStan/Psalm configuration(s) run at a level that checks null — PHPStan level 8 or above (`max` included), or Psalm `errorLevel` 3 or below (Psalm's default, with none stated, is 1). A PHPStan level written neither in the file nor in an include inside the repository is 0, PHPStan's own default. Below those levels the checker removes `null` from a union before any rule looks, so `$order->customer()->name()` on a `?Customer` passes, and the first null reaching it is an `Error: Call to a member function name() on null` in production.
Outdated (npm): @hookform/resolvers — @hookform/resolvers is pinned at 5.9.2; registry.npmjs.org publishes 7.0.6 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @sentry/react — @sentry/react is pinned at 11.11.0; registry.npmjs.org publishes 11.12.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): @tanstack/react-query — @tanstack/react-query is pinned at 5.105.3; registry.npmjs.org publishes 5.107.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): @tanstack/react-query-devtools — @tanstack/react-query-devtools is pinned at 5.105.3; registry.npmjs.org publishes 5.107.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): @tanstack/react-table — @tanstack/react-table is pinned at 8.21.3; 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): @tanstack/react-virtual — @tanstack/react-virtual is pinned at 3.14.25; registry.npmjs.org publishes 3.14.26 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): @tiptap/core — @tiptap/core is pinned at 3.32.2; registry.npmjs.org publishes 3.34.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): @tiptap/extensions — @tiptap/extensions is pinned at 3.32.2; registry.npmjs.org publishes 3.34.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): @tiptap/pm — @tiptap/pm is pinned at 3.32.2; registry.npmjs.org publishes 3.34.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): @tiptap/react — @tiptap/react is pinned at 3.32.2; registry.npmjs.org publishes 3.34.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): @tiptap/starter-kit — @tiptap/starter-kit is pinned at 3.32.2; registry.npmjs.org publishes 3.34.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): @videojs/react — @videojs/react is pinned at 10.2.0; registry.npmjs.org publishes 10.4.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): amqplib — amqplib is pinned at 0.10.9; registry.npmjs.org publishes 2.4.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): axios — axios is pinned at 1.21.0; registry.npmjs.org publishes 1.21.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): dompurify — dompurify is pinned at 3.4.17; registry.npmjs.org publishes 3.4.18 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): express — express is pinned at 4.22.3; registry.npmjs.org publishes 5.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): lucide-react — lucide-react is pinned at 1.67.0; registry.npmjs.org publishes 1.73.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): mapbox-gl — mapbox-gl is pinned at 3.34.2; registry.npmjs.org publishes 3.35.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): minio — minio is pinned at 7.1.3; registry.npmjs.org publishes 8.0.7 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): next — next is pinned at 16.4.4; registry.npmjs.org publishes 16.4.6 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): pdfjs-dist — pdfjs-dist is pinned at 6.3.289; registry.npmjs.org publishes 6.5.438 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-hook-form — react-hook-form is pinned at 7.91.0; registry.npmjs.org publishes 7.92.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-pdf — react-pdf is pinned at 11.0.0; registry.npmjs.org publishes 11.1.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): twig — twig is pinned at 1.17.1; registry.npmjs.org publishes 3.0.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): wavesurfer.js — wavesurfer.js is pinned at 7.12.12; registry.npmjs.org publishes 8.1.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.
No assertions (declared): testAcceptedCouple lib/php/storage-bundle/Tests/FileValidatorTest.php:20— This test performs no assertions and its author said so, with the test framework's own declaration for exactly that (PHPUnit `#[DoesNotPerformAssertions]`, which switches off PHPUnit's "This test did not perform any assertions" warning). It is reported for visibility and is NOT counted against this dimension's score: D10 looks for tests that verify nothing unintentionally. Worth a read anyway — such a test passes as long as the code under it does not throw, so if it was meant to check something, the declaration is now hiding that it does not.
No assertions (declared): testEmptyConfigurationAcceptsEverything lib/php/storage-bundle/Tests/FileValidatorTest.php:84— This test performs no assertions and its author said so, with the test framework's own declaration for exactly that (PHPUnit `#[DoesNotPerformAssertions]`, which switches off PHPUnit's "This test did not perform any assertions" warning). It is reported for visibility and is NOT counted against this dimension's score: D10 looks for tests that verify nothing unintentionally. Worth a read anyway — such a test passes as long as the code under it does not throw, so if it was meant to check something, the declaration is now hiding that it does not.
Skipped (documented): testDetectOfficeDocuments lib/php/storage-bundle/Tests/ContentTypeDetectorTest.php:60— Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by markTestSkipped()
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 1385 file(s) — `configurator/src/Command/ConfigureCommand.php`, `configurator/src/Command/Migration20230807Command.php`, `configurator/src/Command/SynchronizeCommand.php`, `configurator/src/Configurator/Configurator.php`, `configurator/src/Configurator/Vendor/Database/DatabaseConfigurator.php`, … (+1380 more) — 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 01a1e513-0dfc-7f81-8393-2436d902135e · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 221 · Warnings: 1720 · Recommendations: 263 · Info: 29 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 16-11-2026 @ 15:56 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.